Surely somebody is editing native Flowmotion 2 24p footage and can comment on time-line responsiveness? Ideally, compared to one Driftwood's intra-frame settings, but any information at all(?)

Previously asked, no responses.

@ lpowell

"When shooting in 80% Slow-Motion 24H mode, the video is actually being recorded at 30p, but the MTS file is marked to play back at 24p. To make it play at its native 30p rate, no speed up is necessary, however, you must use a video editor to reinterpret the frame rate as 30p."

Sorry I see this only now. Yes I mad a mistake. BTW When shooting in VMM 80% is the real framerate 23.97 as usual 24p cinema mode? and conforming to 30p is the real framerate 29.97 also for VMM 80%? Right?

Thanks

@Lanz1 I fell into that trap some time ago: http://www.personal-view.com/talks/discussion/comment/57716#Comment_57716 It was a field issue and I found out how to properly import PsF video here: http://www.personal-view.com/talks/discussion/comment/57925#Comment_57925

LOL @LPowell

Direct quote from the training manual:

The basic point for driftwood planning is the position at which the driftwood quantity to be handled in the driftwood countermeasure plan is determined. The basic point for the driftwood countermeasure plan is placed upstream of the target protection area.

@GH2_fan - You must have inexplicably missed the following presentation, which was included in your standardized training packet (Figure 1. Flowchart of the Driftwood Countermeasures):

http://www.sabo-int.org/guideline/pdf/driftwoodCountermeasureGuideline.pdf

@rockhunter

just click on the vimeo logo and you'll go on the vimeo page. Full screen, scaling off and you are set!

On the comments there is a description how it was filmed.

Bye

@peternap A world of a difference.

@LPowell: Thank you for the very interesting explanations on HBR mode encoding.

I am not overly concerned with HBR quality since I'm not going to use it much. Nevertheless I wanted to find out whether the artifacts I saw in the "moving tree leaves" HBR recording were caused by an erraneous interpretation of the material as interlaced, so I did a test shot where I moved a page of a book with tables (many thin vertical lines) in front of the camera, brightly lit, at 1s/4000 shutter speed, such that if there was any kind of interlacing going on, I should clearly see it. But there wasn't any distortion in those lines, they looked perfecty straight. Only when shooting the same scenery with low light / high ISO, then I started to see some "zig-zag" artifacts, not unlike the HBR artifacts that I saw in the "moving leaves" shot, but also not easy to distinguish from the inevitable noise distorting the image.

I guess the different encoding the "even" and "odd" lines are subject could explain the difficulty of HBR recording in detail-rich scenes. When I look at the first .png Lanz1 posted above, the metal frame of the lantern seems to exhibit a little of that kind of "zig zag" artifacts I was also experiencing. But it could also be just unavoidable inaccuracies occuring at ~50MBit/s bit rate.

Download the original file to view in Fullscreen, or turn "scaling" on in Vimeo. The downloaded file will look way better. way.

@LongJohnSilver , wow, was this shot with GH2 !!!

I came across this teaser on Vimeo and I think it worths sharing

Shot on GH2 and FM.

View it in 1080p splendor

@LPowell & @peternap :

That's strange. The file is SD resolution and at 250KB and Q99 it shouldn't look like a Lego landscape. The OOF backgrounds are a mess, Lee. The insect's wing contours are a mess. The leaves are a mess. It looks like a JPEG saved at 60% compression when it shouldn't...

I'm reuploading the original attached JPEG (this time as PNG) to check if anyone sees the same as I do.