GH13 Native 24p/Neoscene...

Chris Light

Chris Light

Veteran
I always used Neoscene to remove pulldown/transcode my GH1 footage before applying pTool.

Now with 24p native ptool setting, i know i no longer have to remove pulldown, but is there still an advantage in transcoding to Cineform .avi for editing rather than editing the .mts files directly in Sony Vegas? (i'm using Platinum 9).
 
Last edited:
what you expect from transcoding?
mts = mpeg2-ps (x264+ac3)
to which avi want ? if leave same (x264+ac3) - only changing container ... think you will not get somethink better (only if vegas have bug with mts itself /in previous versions that was mainconcept part/ ) , if change any part of codec in conversion - you loose quality and possible additional artifacts that come from colorspace conversions ..., or if you make it uncompressed - file will be veery big
 
i don't care about large file sizes. I'm not sure if Neoscene colorspace conversion (4:2:0-->4:2:2) has negative side effects.....that's my question. i should have stated that more clearly.
 
if your primary Neoscene usage is 4:2:0->4:2:2, so partial advantage persist (as last :2 is got from interpolation) for keying (are you use green background scenes ?)

if neoscene works in native YUV colorspace - must not be negative effect, but positive from interpolation you need to estimate by self (possible there is not big impoovement).
 
i suppose there is no need for Neoscene with the PTool at this time then...the extra colorspace will likely not create a noticable difference in quality, as i do no greenscreen work. Thanks again for your input!
 
I'm on a 2ghz Dual Core laptop so editing on AVCHD is too choppy for me. The nice thing about Cineform is that even really weak systems can edit it.
 
Only problem is that the 24p setting has known bugs. I've had to go back to the 60i wrapper and processing it with NeoScene.

Chris
 
Neoscene is also a full intra frame codec too. You have fully rendered frame for frame files. If you are using heavy FX or layering multiple clips, it will make for cleaner renders to final output.
 
I've got a quad core and it chokes on AVCHD in Vegas 8...especially when you start stacking tracks and making changes...it REALLY grinds down. It cuts through Cineform files like butter.

The native 24p is cool, and I've been playing with it. But for the time being, I'll keep reverting back to the factory firmware settings. I'm going to keep converting to Cineform regardless, so removing pulldown is a non-issue.

It is, however, nice to be able to just pull out the SDHC card and play the "C" settting + native 24p footage on my Panasonic Blu-Ray player, if I wanna watch some home videos I shot that day and don't feel like screwing with the computer yet.
 
Hello All,
Noob here my first post, so pardon me if I have somethings wrong :-\

So does having native 24p files really help out in the grand scheme of things?
If some are STILL transcoding to neoscene with 24p checked then might as well uncheck native 24p--right?

I'm running a win7 8gb RAM q6600 (quadcore) OC'ed 2.4 ghz machine, and have noticed when doing stacked fx/layers, rendering/previewing AVCHD seems to be slow?

I'm wondering which would be more desirable in terms of quality/efficiency:
-C setting
-Native 24-p Checked
-5% chance of write error due to 24p bug
-No In-Cam playback
-slow rendering/preview due to AVCHD

vs.

-C setting
-Native 24-p UNChecked
-No Write Errors to SDHC
-Cam playback available
-Transcode AVCHD -> Neoscene = faster rendering/preview

vs.

-Experimental D setting with 24p Unchecked (assuming fast SDHC)
-Higher bitrate = better quality?
 
You must log in or register to reply here.
Back
Top