View Bug Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001191DCP-o-maticBugspublic2018-02-05 16:172018-10-17 20:15
Reporterrobn Assigned Tocarl  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Platformx86_64OSFedoraOS Version25
Product Version2.11.0 
Target Version2.12.0 
Summary0001191: VF creation with sound is extremely slow
Description

I usually create a nice 5.1 audio mix for 2.0 content with external software.

But I've encountered an annoying bug several times now while trying to
create a VF with a 5.1 sound track for an 2.0 OV DCP.

The problem is that this VF creation (only some sound juggling)
is extremely slow: it takes way more time than the OV creation (which
includes JP2000 compression).

I've tried to reproduce the bug with some small test data, but
unfortunately every small test set I tried to create just works fine
and doesn't seem to show the problem .. :-)

So now I decided to generate a long test video (test image with
frame counter & info) and test sound files (containing just silence).
I carefully made the test content similar to one of the examples of
problem content (a 90 min movie) using the exact same number of frames
and audio samples:

    25fps_130811f.mp4   (130811 frames of 25fps test image)
    silence20.flac      (2 channels with 251157504 samples)
    silence51.flac      (6 channels with 251157504 samples)

Fortunately the problem can also be reproduced with this artificial test
content that is much smaller than the original movie (250 MB vs 20 GB).
I've made test content available here for download:

    http://berrymount.nl/dom_sound_vf_bug/
Steps To Reproduce

I tested with DOM 2.11.47

  • Create an OV DCP from 25fps_130811f.mp4 & silence20.flac
    Just map the 2.0 audio L & R in a 5.1 DCP (default DOM behavior).

  • Create a VF DCP that references to only the video of the OV
    Use silence51.flac for the new audio

Additional Information

Creating the complete OV takes approx. 3 hours on my machine (using all
cpu cores and 1.7 GB of ram). No problems here.

But creating the VF (which only needs to do some MXF audio-processing)
takes an large amount of time and uses 7.2 GB of ram. There is 1
thread/core used and you can see the pcm*.mxf grow very slowly in
the DOM project folder. It grows by approx 195 kB/s, which means that
the creation of the final 4.5 GB pcm*.mxf would take about 6.5 hours.
This is twice as long as the OV creation with the JP2000 compression!

BTW: it seems that the VF creation from this smaller synthetic .flac
audio file goes faster than from the bigger .wav (RF64) I normally use
in my workflow. But this example does illustrate the point though:
sound VF generation seems way too slow!

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work requiredUnknown

Activities

robn

2018-02-06 01:04

reporter   ~0002074

When I came back the VF creation had finished: it took 3 hours and 19 minutes.
This is less than the 6.5 hour I had estimated. But I think this is still much longer
than it needs to be!

(yes of course I checked that it was a real VF and not an OV instead! .. :-)
It is definitely an VF: it's only 4.5 GB big, no video data only the sound
5.1 MXF. And it has the same length as the 2.0 MXF, being both 6 channel MXFs)

carl

2018-02-06 11:44

administrator   ~0002075

70a7bb2bd72f90642e01ed660f7d7de495ea0370 should help with this (in 2.11.49)

robn

2018-02-06 22:05

reporter   ~0002079

Well "help with this" is a bit of an understatement: with 2.11.49 I can now
create the 5.1 sound VF in 29 seconds instead of 11940 seconds!! .. :-)

But there is a catch: it only seems to work when you do this:

  • start with a NEW empty project
  • add the silence51.flac FIRST
  • then add the referenced OV

If you reopen an existing VF project (even one just created like above),
DOM seems to hang: it uses 100% cpu and produces and endless stream of these in it's log:

di 06 feb 2018 22:56:01 CET: WARNING: Butler audio buffers reached 104156160 frames
di 06 feb 2018 22:56:01 CET: WARNING: Butler audio buffers reached 104157184 frames
di 06 feb 2018 22:56:01 CET: WARNING: Butler audio buffers reached 104158080 frames
di 06 feb 2018 22:56:01 CET: WARNING: Butler audio buffers reached 104160000 frames
.
.

And if you create your new project in the "wrong" order (adding the OV first and
the 5.1 sound second) the same thing happens!

mhm

2018-02-07 00:33

reporter   ~0002080

Just curious:

"I usually create a nice 5.1 audio mix for 2.0 content with external software."

What external software (and configuration/parameters) do you use for this?

Best,
Mattias

robn

2018-02-07 00:47

reporter   ~0002081

The "DTS Neural™ Surround UpMix" VST plugins are very good.
Usually just the default settings are fine.

Would be great if DOM supported them too! .. :-)

carl

2018-02-07 20:16

administrator   ~0002082

100% CPU hang should be fixed by 8bfe295dcc4e1753ee1c89310108bc6bc034cd61 (2.11.50).

robn

2018-02-08 01:24

reporter   ~0002085

Thanks, everything looks OK with 2.11.50 !

carl

2018-02-08 19:39

administrator   ~0002087

Cool, thanks.

Bug History

Date Modified Username Field Change
2018-02-05 16:17 robn New Bug
2018-02-05 19:46 carl Target Version => 2.12.0
2018-02-06 00:52 carl Assigned To => carl
2018-02-06 00:52 carl Status new => confirmed
2018-02-06 01:04 robn Note Added: 0002074
2018-02-06 11:44 carl Note Added: 0002075
2018-02-06 22:05 robn Note Added: 0002079
2018-02-07 00:33 mhm Note Added: 0002080
2018-02-07 00:47 robn Note Added: 0002081
2018-02-07 20:16 carl Note Added: 0002082
2018-02-08 01:24 robn Note Added: 0002085
2018-02-08 19:39 carl Status confirmed => resolved
2018-02-08 19:39 carl Resolution open => fixed
2018-02-08 19:39 carl Note Added: 0002087
2018-10-17 20:15 carl Status resolved => closed