Page 1 of 1
Canon HV20 HD M2T fast motion problem in VS X2
Posted: Fri May 01, 2009 5:13 pm
by pkalen
VS X2 seems to have a problem deinterlacing or interpreting the yellow channel. I am slowing down a sequence of a hurdler. The camera (Canon HV20 shot in HD and M2T is captured by HDVSplit) is stationary as the hurdler runs past. Shutter speed is 1/1000th of a second. In the still capture from VS below, all seems pretty good except the yellow channel is about a frame ahead. The same occurs after rendering. I have 4 of these clips and they all react the same way, so it isn't a problem with a single clip. I put the same raw clip in VLC. It plays perfectly and the resulting still capture is also perfect. (Ignore the red artifacts and the grain, I had to turn off graphics acceleration to get a screen capture.) It is disappointing, because a potentially great sequence will be mediocre at best. I figure nobody has a cure, but I might get lucky. I will report this to Corel support, but the canned response will be meaningless.
Perry
VS X2 Pro version 12.0.98.1 (with patch)
NTSC drop frame (29.97 fps)
MPEG files
24 bits, 1440 x 1080, 29.97 fps
Upper Field First
(MPEG-2), 16:9
Video data rate: Variable (Max. 8000 kbps)
Audio data rate: 224 kbps
MPEG audio layer 2, 48 KHz, Stereo
VS X2 project image capture
VLC printscreen

Posted: Fri May 01, 2009 5:35 pm
by Black Lab
Looks like it could be the dreaded
Rolling Shutter that effects CMOS chip cameras. At this time there is no fix for it, but I understand it is being worked on.
I am in the market for a new camcorder, and I'm a big fan of Sony. But I shoot a lot of sports, and Sony has gone almost exclusively to CMOS chips. Therefore I am seriously looking at the Canon XH-A1, which uses CCD chips.
Posted: Fri May 01, 2009 6:00 pm
by pkalen
Thanks for the quick reply Black Lab. I read about the rolling shutter before, but didn't know when it would affect me. There couldn't be too much "roll" in 1/1000th of a second. It still seems strange that VLC could overcome this and get it right.
Perry
Posted: Fri May 01, 2009 6:27 pm
by Black Lab
It still seems strange that VLC could overcome this and get it right.
That's a valid point, so maybe my theory is incorrect.

Posted: Fri May 01, 2009 6:29 pm
by Black Lab
Have you tried rendering the clip to a video file? How does it look then?
Posted: Fri May 01, 2009 7:33 pm
by pkalen
The rendered clip has the same characteristics as the image capture.
Tried it both interlaced and frame-based, NTSC DVD and Same as Project.
Posted: Fri May 01, 2009 7:39 pm
by Black Lab
Strange indeed. You say you captured with HDVSplit. What happens if you capture with VS? (Just grasping at straws here).
BTW, is that your daughter? Tell her to rotate her trial foot. With her toes pointed down she'll clip a hurdle.

Posted: Fri May 01, 2009 8:05 pm
by pkalen
I will try capturing with VS and see what happens.
Posted: Fri May 01, 2009 8:21 pm
by pkalen
Just did the VS capture with same results.
BTW, not my daughter. I make a highlight video for the track team at the local high school. I will pass along the tip.
Posted: Fri May 01, 2009 10:13 pm
by Black Lab
Hmmm. How are you capturing? What are the connections?
Posted: Sat May 02, 2009 3:32 am
by pkalen
Capture is by firewire on the motherboard.
Thinking about finding some other software (Pinnacle, Vegas, Adobe) to render these high speed shots correctly and bring them back to VS to complete the project.
Perry
Posted: Sat May 02, 2009 3:52 am
by Ron P.
I'm not sure that any of those in the consumer products would be able to do so any differently than VS. I'm not saying that to be partial to VS, just that I've used them in the past, and what you're needing to do requires a high-end editor. Maybe Sony Vegas Pro, or if you had a Mac, Final Cut. High shutter speeds need high-end editors to do them justice..

Posted: Sat May 02, 2009 3:20 pm
by pkalen
Don't get me wrong, I enjoy using VS. It does everything I need it to do except for this problem, OOH and moving paths or pan and zoom on a png with a transparent background.
I sent a detailed email to Corel through their support page. We will see what comes of that.