DeMux and Memory Leak at DVinfo.net

Mark Pavy · January 7th, 2011, 02:52 PM

I've just found out that the MVC encoder I plan on using for my 3D project needs the left and right stream separate ie it won't accept the muxed Cineform stereo file. I can see a"script" for demuxing the stereo files but have no idea how to use it. Can somebody tell me how to demux the stereo file back into left and right.

I've also experienced strange RAM behaviour with the last 2 releases (289 and 290). During playback in the Premiere timeline and during rendering to Cineform files from the timeline the RAM usage climbs and climbs until it reaches 100% (I have 24gig ram) and then things start really slowing down and the machine is unworkable. With both releases I've had to revert back to version 278 which seems to work well with my computer( except that I can't open files in the trim/source window in Premiere). With 278 the Ram usage with both editing and rendering is completely normal (doesn't get above 20% most of the time) but as soon as I change versions to 289 or 290 the RAM usage problem occurs (in both 289 and 290 I can use trim/source window in Premiere). Any ideas?

Carlo Macchiavello · January 8th, 2011, 04:43 AM

mee too...
i remove neo3d, quicktime, premiere
i install again last quicktime, premiere (and i not update to last 5.03 but i leave 5.0.0) and neo3d v290, and all work fine.
i see that there is an update 5.2.8.291 now
i download it and verify.

David Newman · January 8th, 2011, 10:31 AM

I could be 5.0.3, we had problems with it, although I haven't seen a memory leak except: are you using side-by-side 3D with burn-ins or tools enabled? That had a memory leak and was fix in the latest build.

David Newman · January 8th, 2011, 10:45 AM

Mark, which MVC Encoder are you using?

There is a batchDemux script here http://cineform.com/downloads/BatchDemux.zip

Unzip and double-click on the vbs file, and you should be able to work it out.

Mark Pavy · January 8th, 2011, 01:34 PM

Thanks Dave, the script works, thankyou.

I haven't purchased anything yet, I am looking at the DoStudio MVC Encoder.

I have downloaded and installed 291 and after a very quick test of playing the timeline it appears that the memory leak is fixed. I haven't had the opportunity to test for memory leak in rendering out as yet, but will report asap.

Once again thanks for your support.

Mark Pavy · January 8th, 2011, 03:59 PM

Yes! Best release ever for me, everything in my workflow works great.

Great work.

January 7th, 2011, 02:52 PM	#1
Mark Pavy Regular Crew Join Date: Sep 2010 Location: Central Coast Australia Posts: 56	DeMux and Memory Leak I've just found out that the MVC encoder I plan on using for my 3D project needs the left and right stream separate ie it won't accept the muxed Cineform stereo file. I can see a"script" for demuxing the stereo files but have no idea how to use it. Can somebody tell me how to demux the stereo file back into left and right. I've also experienced strange RAM behaviour with the last 2 releases (289 and 290). During playback in the Premiere timeline and during rendering to Cineform files from the timeline the RAM usage climbs and climbs until it reaches 100% (I have 24gig ram) and then things start really slowing down and the machine is unworkable. With both releases I've had to revert back to version 278 which seems to work well with my computer( except that I can't open files in the trim/source window in Premiere). With 278 the Ram usage with both editing and rendering is completely normal (doesn't get above 20% most of the time) but as soon as I change versions to 289 or 290 the RAM usage problem occurs (in both 289 and 290 I can use trim/source window in Premiere). Any ideas?

January 8th, 2011, 10:31 AM	#3
David Newman CTO, CineForm Inc. Join Date: Jul 2003 Location: Cardiff-by-the-Sea, California Posts: 8,095	I could be 5.0.3, we had problems with it, although I haven't seen a memory leak except: are you using side-by-side 3D with burn-ins or tools enabled? That had a memory leak and was fix in the latest build. __________________ David Newman -- web: www.gopro.com blog: cineform.blogspot.com -- twitter: twitter.com/David_Newman

January 8th, 2011, 10:45 AM	#4
David Newman CTO, CineForm Inc. Join Date: Jul 2003 Location: Cardiff-by-the-Sea, California Posts: 8,095	Mark, which MVC Encoder are you using? There is a batchDemux script here http://cineform.com/downloads/BatchDemux.zip Unzip and double-click on the vbs file, and you should be able to work it out. __________________ David Newman -- web: www.gopro.com blog: cineform.blogspot.com -- twitter: twitter.com/David_Newman

January 8th, 2011, 04:43 AM	#2
Carlo Macchiavello Regular Crew Join Date: Oct 2010 Location: italy Posts: 107	mee too... i remove neo3d, quicktime, premiere i install again last quicktime, premiere (and i not update to last 5.03 but i leave 5.0.0) and neo3d v290, and all work fine. i see that there is an update 5.2.8.291 now i download it and verify.

January 8th, 2011, 01:34 PM	#5
Mark Pavy Regular Crew Join Date: Sep 2010 Location: Central Coast Australia Posts: 56	Thanks Dave, the script works, thankyou. I haven't purchased anything yet, I am looking at the DoStudio MVC Encoder. I have downloaded and installed 291 and after a very quick test of playing the timeline it appears that the memory leak is fixed. I haven't had the opportunity to test for memory leak in rendering out as yet, but will report asap. Once again thanks for your support.

January 8th, 2011, 03:59 PM	#6
Mark Pavy Regular Crew Join Date: Sep 2010 Location: Central Coast Australia Posts: 56	Yes! Best release ever for me, everything in my workflow works great. Great work.