Ken Diewert
April 25th, 2010, 11:37 AM
Tried to see if this was covered somewhere, but couldn't find it. I'm looking at updating my firmware from version 1.10 to version 2.04 I believe it is. The reason I haven't already is that my workflow works very well right now, and I'm reluctant to start messing with it.
Can anyone comment on how NeoScene plays with the new firmware version when converting? I know that Neoscene converts from 30p to 29.97. I've got a project that I'd like to shoot in 24p. I edit in Vegas 8.0c.
Chris Barcellos
April 25th, 2010, 01:04 PM
Ken:
Works just fine. The resulting footage is no different in terms of structure from the 7D, which has already been working with NeoScene. Just have it set not to change anything, and it will automatically detect whether you shot in 30p or 24p, and it will automatically convert it to 24p. You need to go to 2.04 because it gives you 24p, and some new sound controls too !
Matthias Krause
April 25th, 2010, 01:45 PM
Well, not so fast... I have trouble with NeoScene converting 25p as 24.975 fps... Very bothersome if you try to sync it. You have to change the playback rate to 1.001 for each and every file... Itīs apperently a bug NeoScene is working on. Canīt speak for 24p conversions though.
Ben Denham
April 25th, 2010, 04:52 PM
I've had no problems converting 25p files with neoscene. Matthias, why are you converting 25p as 24.975 fps? You do realise that 25 fps is a PAL standard that, unlike the NTSC frame rates, it is dead on 25 fps, right? Why do you need the odd frame rate of 24.975? No angst here, just curious as to your reasoning.