The project I first experienced problems with contains the following:
- 1 video track + included soundtrack, containing a single mp4 file
- 1 audio mp3 for introduction music, with fade-in/out volume correction
- several png pictures, mostly used as overlay on some parts of the video
- 2 caption overlays
- 1 scrollling caption at the end of the video (credits)
- effects: aspect ratio correction on all items + fade-in/out transition on some items
- total duration: 3'40"
At project opening, VideoMeld uses ~100 MB.
When rendering using YouTube 720 preset, used memory jumps up to ~1.4 GB and goes down to ~1.1 GB after it. In the resulting mp4 file, some overlay pictures are missing and all fade transitions are very abrupt (no fade).
Rendering a 2nd time with the same settings, memory goes up to 1.4 GB again (and down to 1.1 afterwards), but some additional overlay pictures disappear from the output video...
I noticed, that as long as the total used memory remains below 1.3 GB (as stated by JakubM), everything works fine.
Typically, rendering the same project with YouTube 360 preset is ok.
As you suggested, I tested it with a very simple project, containing only the main video file. No effect except aspect ratio correction. With this, the memory usage is much lower and I did not manage to trigger the critical problems I had on the full project. However, looking again at memory usage, it looks like there are some resources that are not completely released after being used. With that simplified project:
- at project opening ~95 MB
- during first rendering ~415 MB
- after rendering ~150 MB
- during rendering ~440 MB
- after rendering ~170 MB
- during rendering ~445 MB
- after rendering ~180 MB
- during rendering ~450 MB
- after rendering ~180 MB
... I did not try any further
On the other hand I tried the following:
- just after opening again the simplified project, the used memory is 95 MB (private bytes)
- moving the mouse over the "star" on the top corner of the video track ==> 99 MB
- opening the video effects dialog (click on the star) ==> 137 MB
- close the dialog (cancel) ==> 102 MB
repeating the last 3 steps, I obtain the following memory usage values:
104 - 139 - 105 - 106 - 142 - 106 - 111 - 146 - 114 - 115 - 148 - 115 - 117 - 149 - 115 - 116 - 152 ...
It is not much, but it seems to allocate 2-3 MB more each time the video effect is opened.
Then I started playing a bit, first adding again one overlay picture, with fade-in/out transitions. When rendering (i.e. melding to file), memory usage jumped to 1.1 GB and came down to ~850 MB afterwards.
Adding a second picture, also with fade transitions, it peaked at 1.5 GB and I got the error message "Cannot create texture for 'TCanvasD2D'.
Again, the magic limit of 1.3 GB was exceeded and real problems started
Is there anything else I could do to help finding the cause of the problem?
Greetings,
Stéphane
ps: I did some more testing on another PC (Windows 7 pro instead of 8.1)
I have here another project, which is simpler than the one described above, but longer.
- 2 source mp4 files, inserted in several sections
- 11 png overlay pictures
- 1 scrolling caption fro credits at the end
- some fade-in/out transitions
- total duration: ~11 minutes
rendering with YouTube 260 preset, it runs all the way to the end.
Memory consumption is much lower than on Win 8.1:
it remains steady just below 400 MB for a long time, then suddenly
it starts going up, apparently just after a fade-out transition,
then increases again in a place where there is nothing particular in the
video and peaks at 953 MB. Just after that, the progress bar goes totally
black and the progress values continues to 100%.
At the very end (when reaching 100%) there is an error msg popping up:
---------------------------
Error
---------------------------
Access violation at address 6640F8C0 in module 'd2d1.dll'. Read of address 00000000.
---------------------------
OK
---------------------------
The msg appears a large number of times. Clicking ok just opens between 1 and 5 new
pop-ups. Impossible to get rid of it. Can only kill the application from the task manager.
The generated video is something like "myprojectVM61.mp4" instead of "myproject.mp4"
and the file is corrupt. From a certain point, which I suppose corresponds to the memory
peak during rendering, the screen goes totally black and only audio remains...
I also tried to used different settings, with an even lower output resolution, with the same
result...
Another test: after removing ALL png overlay pictures, the rendering ran through like a charm,
without memory peak nor error msg and the output video was clean. But of course, I am then
missing the overlay pictures
