Neo Scene changes clips from 23.98 to 29.97 at DVinfo.net

Vincent Tsu · March 30th, 2010, 07:49 PM

I'm surprised no one has posted about this yet, but whenever I use Neo Scene to convert 1080/24p clips from a Canon 7D or 5D mkII, the frame rate is changed to 29.97. Is anyone else seeing this? All I want is for Neo Scene to convert the H264 files to the ProRes or Cineform codec without mucking around with the frame rate.

Of course, I could just use Canon's new "EOS MOVIE Plugin-E1 for Final Cut Pro" to convert to ProRes, which based on my testing, renders colors most accurately compared to the original H264 files (I'm seeing slight color shifts when using Neo Scene and even Compressor...which is a shame, since both of those programs are very well threaded and can max out the 8-cores on my Mac Pro). But I do like how Neo Scene "flattens out" or "un-crushes" the black levels when converting to the Cineform codec.

David Newman · March 30th, 2010, 11:36 PM

NeoScene has got stuck thinking all your sources are Canon 5D's pre-firmware upgrade. Delete this
/Library/Application Support/CineForm/Custom Settings/MOV/avc1/_last.plist
and it will work again.

Vincent Tsu · March 31st, 2010, 01:06 PM

Thanks, David! That did the trick.

Mike Snapp · March 31st, 2010, 08:01 PM

Neoscene is telling me it is unable to determine the frame rate and my 7d footage shot at 24p is converted to 30p. I filled out a support ticket and the response was to install the latest version of quicktime. The requirments page for Neoscene states that quicktime is "NA". Now I'm reading that I need to delete something to get it to work properly?

David Newman · March 31st, 2010, 08:11 PM

Talk again to support, as this thread is about the Mac -- you are talking about a PC I gather.

Mike Snapp · March 31st, 2010, 08:25 PM

Yes I'm using pc.

Vincent Tsu · April 8th, 2010, 12:57 AM

Hi David, Another problem I've run into with NeoScene (Mac) is that the "Limit YUV (Canon 5D)" setting doesn't seem to work when outputting to the ProRes codecs. It only works when the Output Format is set to one of the Cineform codecs. Can you confirm this on your end? My workflow is ProRes currently...would like to switch to Cineform, but the RT effects enabler isn't working for me...

So (at the risk of sounding like a total complainer!) I was under the impression that the new FCP RT enabler is supposed to allow RT effects (like cross dissolve). I'm unable to playback even a 1 sec. cross dissolve without a dropped frame warning. My system should be plenty capable (8-core Mac Pro, 12GB RAM, 400MB/s+ RAID) and I think I have my sequence settings correct (Dynamic for both Video Quality and Frame Rate, Multiclip Playback unchecked). Any idea what might be wrong?

Thanks!

Vincent Tsu · April 8th, 2010, 01:03 AM

Scratch that last bit about RT effects not working in FCP. Right after I posted that, I tried turning OFF External Video (I run a Kona 3 card) and voila! Even a 6 sec. cross dissolve played back without dropping frames. Would be nice though if I could playback with External Video ON. ;-)

David Newman · April 8th, 2010, 09:12 AM

The "Limit YUV (Canon 5D)" set only works with CineForm, as the fix is done in the codec not the converter -- so ProRes can't do it as is.

It is possible to run RT through the Kona 3. I've done it myself, but I'm not a Mac guy so I'm not sure what are the settings. Support should have this info, but expect a slower response as we are all moving to Vegas for the week of NAB.

March 30th, 2010, 07:49 PM	#1
Vincent Tsu Tourist Join Date: Feb 2007 Location: Culver City, CA Posts: 4	Neo Scene changes clips from 23.98 to 29.97 I'm surprised no one has posted about this yet, but whenever I use Neo Scene to convert 1080/24p clips from a Canon 7D or 5D mkII, the frame rate is changed to 29.97. Is anyone else seeing this? All I want is for Neo Scene to convert the H264 files to the ProRes or Cineform codec without mucking around with the frame rate. Of course, I could just use Canon's new "EOS MOVIE Plugin-E1 for Final Cut Pro" to convert to ProRes, which based on my testing, renders colors most accurately compared to the original H264 files (I'm seeing slight color shifts when using Neo Scene and even Compressor...which is a shame, since both of those programs are very well threaded and can max out the 8-cores on my Mac Pro). But I do like how Neo Scene "flattens out" or "un-crushes" the black levels when converting to the Cineform codec.

March 30th, 2010, 11:36 PM	#2
David Newman CTO, CineForm Inc. Join Date: Jul 2003 Location: Cardiff-by-the-Sea, California Posts: 8,095	NeoScene has got stuck thinking all your sources are Canon 5D's pre-firmware upgrade. Delete this /Library/Application Support/CineForm/Custom Settings/MOV/avc1/_last.plist and it will work again. __________________ David Newman -- web: www.gopro.com blog: cineform.blogspot.com -- twitter: twitter.com/David_Newman

March 31st, 2010, 08:11 PM	#5
David Newman CTO, CineForm Inc. Join Date: Jul 2003 Location: Cardiff-by-the-Sea, California Posts: 8,095	Talk again to support, as this thread is about the Mac -- you are talking about a PC I gather. __________________ David Newman -- web: www.gopro.com blog: cineform.blogspot.com -- twitter: twitter.com/David_Newman

April 8th, 2010, 09:12 AM	#9
David Newman CTO, CineForm Inc. Join Date: Jul 2003 Location: Cardiff-by-the-Sea, California Posts: 8,095	The "Limit YUV (Canon 5D)" set only works with CineForm, as the fix is done in the codec not the converter -- so ProRes can't do it as is. It is possible to run RT through the Kona 3. I've done it myself, but I'm not a Mac guy so I'm not sure what are the settings. Support should have this info, but expect a slower response as we are all moving to Vegas for the week of NAB. __________________ David Newman -- web: www.gopro.com blog: cineform.blogspot.com -- twitter: twitter.com/David_Newman

March 31st, 2010, 01:06 PM	#3
Vincent Tsu Tourist Join Date: Feb 2007 Location: Culver City, CA Posts: 4	Thanks, David! That did the trick.

March 31st, 2010, 08:01 PM	#4
Mike Snapp Tourist Join Date: Mar 2010 Location: Waukesha WI Posts: 2	Neoscene is telling me it is unable to determine the frame rate and my 7d footage shot at 24p is converted to 30p. I filled out a support ticket and the response was to install the latest version of quicktime. The requirments page for Neoscene states that quicktime is "NA". Now I'm reading that I need to delete something to get it to work properly?

March 31st, 2010, 08:25 PM	#6
Mike Snapp Tourist Join Date: Mar 2010 Location: Waukesha WI Posts: 2	Yes I'm using pc.

April 8th, 2010, 12:57 AM	#7
Vincent Tsu Tourist Join Date: Feb 2007 Location: Culver City, CA Posts: 4	Hi David, Another problem I've run into with NeoScene (Mac) is that the "Limit YUV (Canon 5D)" setting doesn't seem to work when outputting to the ProRes codecs. It only works when the Output Format is set to one of the Cineform codecs. Can you confirm this on your end? My workflow is ProRes currently...would like to switch to Cineform, but the RT effects enabler isn't working for me... So (at the risk of sounding like a total complainer!) I was under the impression that the new FCP RT enabler is supposed to allow RT effects (like cross dissolve). I'm unable to playback even a 1 sec. cross dissolve without a dropped frame warning. My system should be plenty capable (8-core Mac Pro, 12GB RAM, 400MB/s+ RAID) and I think I have my sequence settings correct (Dynamic for both Video Quality and Frame Rate, Multiclip Playback unchecked). Any idea what might be wrong? Thanks!

April 8th, 2010, 01:03 AM	#8
Vincent Tsu Tourist Join Date: Feb 2007 Location: Culver City, CA Posts: 4	Scratch that last bit about RT effects not working in FCP. Right after I posted that, I tried turning OFF External Video (I run a Kona 3 card) and voila! Even a 6 sec. cross dissolve played back without dropping frames. Would be nice though if I could playback with External Video ON. ;-)