Just want to know how many people here use Native 24p.

rundavids

rundavids

Well-known member
Hey guys, I'm using C Settings with native and I'm getting some awesome footage. Maybe, just maybe I may get a speed card error, but it's rare. I'm using a Transcend class 10 8gb card. Just want to know how many other folks out there choosing to use Native. I know a lot of people are having problems, but it seems so rare to me to get any errors. I wouldn't mind it one bit at all. Maybe that's just me.
 
I unchecked native and haven't had a lockup since.
Will be headed out to the prairie again this weekend so I'll know for sure if it was the native setting that was causing my lockups.
 
i use native 24p/C settings with no issues. BUT, so many variables will yield different results. SDHC choice (i use SanDick Extreme 16G Class 10), shooting conditions, lenses, etc. I can also transcode when i need to if i decide to change settings...see where i'm going with this? Variables. and a lot of them. There's no "one size fits all" solution.
 
I'm actually using C-settings with the native 24p on Class 6 and 10 cards and have yet to get an error. When I wasn't trying to get one, and even then it's tough. So I think unless your work mainly consists of spazzing out in front of a lot of bushes, you should be fine.
 
seanmcleod said:
I'm actually using C-settings with the native 24p on Class 6 and 10 cards and have yet to get an error. When I wasn't trying to get one, and even then it's tough. So I think unless your work mainly consists of spazzing out in front of a lot of bushes, you should be fine.
Click to expand...
Exactly. I think there is a bit too much hype over the failure rate in this mode. I’ve been enjoying my camera for over a month now without any problems whatsoever using 24p. The one time I did have issue was when it was pointed out to me that it could fail on a static shot in bright daylight while filming bushes. So…I tried it…and sure enough (4 out of 5 times) it failed. But that only happened because I went looking for it. In practical use however…no problems. If I remember my settings correctly I’m at 60, 62, 70 24p checked GOP set to 6 (I think) or 4. The image is clean and very detailed.
 
Ian-T said:
...If I remember my settings correctly I’m at 60, 62, 70 24p checked GOP set to 6 (I think) or 4. The image is clean and very detailed.
Click to expand...


Awesome...I'm going to give those settings a shot since I'm off this weekend...and have a new Sandisk Class 10 card to test out!
 
swyzlstyx said:
Awesome...I'm going to give those settings a shot since I'm off this weekend...and have a new Sandisk Class 10 card to test out!
Click to expand...


Just tried it: Camera froze instantly after hitting record button...pointed at a wall. :D Oh well...it's fun killing time.
 
swyzlstyx said:
Just tried it: Camera froze instantly after hitting record button...pointed at a wall. :D Oh well...it's fun killing time.
Click to expand...
I'll try to find the exact settings. I was talking out the side of my neck earlier. But I do get an average 45 to 50 MBps.
 
Using C Settings w/ Native 24p on a 8gig Class 10 SanCard. Been working like a champ.
 
I've only got a weird "pulsing" thing only once when I was shooting a window blind. But never got it again. It was weird. But Native and C settings rock.
 
Me too, Native 24p and I have taken GOP to 2 occasionally and streamparser shows every second frame I frame so motion is very smooth stream an almost constant 35 Mbs with peaks to 55 Mbs and it still wont lock up...
Bushes grass all ok .,,
Only time it locked up was doing video of moon through my canon fd 300mm F4L seemed to be too much for it for whatever reason.
cheers
Larry
 
I don't use native24p - I am hacking and getting good results but I just can't afford a card error when I'm on set so I'm playing it "safe," "safe" being a highly hacked consumer-oriented Lumix camera as "A" cam on a feature film :)
 
The disturbing problem I found in testing Native 24p is that it sometimes produces corrupted recordings that appear to play back normally. These flaws are visible but not easy to spot without using a frame analyzer. What seems to happen is that the AVCHD codec runs out of bitrate before encoding all frames in a GOP. It is then forced to write one or more empty frames at the end of the GOP. This causes the video to appear to pause or briefly revert back to the previous key frame at unpredictable points in the timeline.

While this encoder malfunction is fairly rare, I saw it often enough to conclude that it made Native 24p too unstable to support in my 40Mbps AVCHD High Reliability Patch:

http://dvxuser.com/V6/showthread.php?t=219132
 
Using Rambooc1 settings with Native 24P unchecked because of all the issues described by others using the native patch. Rendering all GH1 footage to 25P Cineform HQ files using Neoscene then editing in Premiere CS3 and the footage looks stunning.
 
Was using Native on scandisk extreme 8gig until I went into the jungle and then couldn't get the thing to stop freezing. Wide and kit lens stopped down or fully open, no good with C settings and native. Before my gorillas in the mist adventure, no problem. I switched back to 'c' settings and no native. All smiles so far.
 
how many on here are using a lower gop from 6 to 2 with 24pn ?i know larry said he has not run into issues with gop of 2 ..i never tried lowering the gop under 12, i wounder how much better or worse the quality would be, im thinking to lower the gop to 2 i need to lower pretty much all the bit rate values (compared to gop 12)
 
You must log in or register to reply here.
Back
Top