Encore 5.5, Windows 7, 64-bit
When I import an m4v asset, the system memory usage will keep going up. Eventually, the system will use up all physical RAM and becomes useless. This is observed in task manager.
However, there is no process that uses this amount of RAM in process tab. Encore uses only about 1.5 GB. There is nothing else using more than 200 MB.
Once I kill Encore, the system memory usage goes down to about 1.5 GB from 8 GB.
Normally, when this happens, I just restart Encore and import in another way (drag-drop, right click to import). A few tries later, I will have a successful import with peak memory usage less than 3 GB.
However, now I got 1 hour m4v (1 hour) that can't pass no matter what I tries.
Has anyone seen similar things happening?
I guess the obvious question is... what are the exact parameters of your file?
IE- what are your export settings from Premiere Pro?
Simply because I don't care to get into bit budgeting and calculations, I always export DV AVI Widescreen from PPro (I edit AVCHD, but do not have a BluRay burner) and then let Encore do "automatic" encoding to calculate the best fit on a DVD
I have never had a single problem doing that, with timelines up to, and in one case slightly over, 2 hours
Post your file details and maybe someone will be able to comment
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4.1
Format settings, CABAC : Yes
Format settings, ReFrames : 3 frames
Bit rate mode : Variable
Maximum bit rate : 35.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 29.970 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Interlaced
Scan order : Top Field First
Some of these video have problem imported as Encore insisting on transcoding them again. However, this one belongs to the other half that does not have this problem.
I'd need to correct my claim. It does not cause out of memory error by exhausting virtual memory. It just uses up all physical RAM and causes extensive disk activity. So if I can put up with the long delay with disk activity (nothing else will work), it can import the file successfully.
The source video are system are on differet a hard drive. So it's definitely not not b/c reading in the video.
I wonder if it's matter of miscalculation of available RAM. It may try to use all the physical memory possible to speed things up. But it does not do the math right.
Europe, Middle East and Africa