I can’t remove the jitter, right?

Rich Parry wrote on 10/21/2014, 8:02 PM
I believe I am trying to do something that I should not be doing, I’m moving an image across a screen too quickly, see the example video on Vimeo. The image jumps too many pixels from frame to frame resulting in jitter, jumps, or blur. Pick the term you like, but you get the idea.

Before I give up on the idea of sliding images across a screen, thought I would get confirmation that I’m wasting my time.

https://vimeo.com/109651805

In case it matters, I'm using VP13 and rendered in both 23.976 and 29.97 fps. No significant difference if any.

Thanks

CPU Intel i9-13900K Raptor Lake

Heat Sink Noctua  NH-D15 chromas, Black

MB ASUS ProArt Z790 Creator WiFi

OS Drive Samsung 990 PRO  NVME M.2 SSD 1TB

Data Drive Samsung 870 EVO SATA 4TB

Backup Drive Samsung 870 EVO SATA 4TB

RAM Corsair Vengeance DDR5 64GB

GPU ASUS NVDIA GeForce GTX 1080 Ti

Case Fractal Torrent Black E-ATX

PSU Corsair HX1000i 80 Plus Platinum

OS MicroSoft Windows 11 Pro

Rich in San Diego, CA

Comments

GeeBax wrote on 10/21/2014, 8:23 PM
It will not help the situation using 29.97 unless the original footage was shot at a higher frame rate, it will still need motion interpolation. However it looks to me as if you are using an interlaced source and have the frame dominance reversed. In project properties, try changing the field order and see if that helps.
johnmeyer wrote on 10/21/2014, 8:58 PM
Jitter is a function of field rate: the few the number of fields per second, the more jitter you will see, especially when the camera pans horizontally.

Notice I said fields, not frames. There is nothing that makes interlaced video less prone to jitter, but since the whole purpose of interlacing is to increase the number of "events" per second, and since most interlaced video is either 50 or 60 fields per second, that is WAY more than the 24 or 30 frames per second that you are contemplating using.

So, if you don't like jitter, shoot PAL or NTSC interlaced ("50i" or "60i"), or shoot 60p.
Duncan H wrote on 10/21/2014, 9:33 PM
Hi, I read the note posted by Rich and then tried a simple (equivalent?) reproduction of using track motion to slide a jpeg across a background. I'm using 25P and initially, rednering to a MC mp4 (720p) format, got very similar jittering. Then used exactly the same project, but rendered to AVI (Magic YUV codec) and got a WAY smoother result. How so?
Andy_L wrote on 10/21/2014, 10:21 PM
try this: watch your vimeo video but stand progressively farther away from your screen.

Did that fix the problem??
musicvid10 wrote on 10/21/2014, 11:04 PM
Make the video on vimeo downloadable.
That way we can see if they've done something, or if its a delivery / bandwidth issue.
larry-peter wrote on 10/22/2014, 9:19 AM
I haven't looked at your video, but there's an old-school film rule (based on 24fps/180 degree shutter) that a maximum panning rate on a non-moving subject is seven seconds to cover the width of the frame. If you're panning a still, you'd need to add some motion blur to make up for the shutter rate. As with most rules there are exceptional circumstances, but it's a good guide for 24p. You can interpolate for other progressive frame rates.

OldSmoke wrote on 10/22/2014, 9:33 AM
Also make sure the generated media matches the final render resolution.

Proud owner of Sony Vegas Pro 7, 8, 9, 10, 11, 12 & 13 and now Magix VP15&16.

System Spec.:
Motherboard: ASUS X299 Prime-A

Ram: G.Skill 4x8GB DDR4 2666 XMP

CPU: i7-9800x @ 4.6GHz (custom water cooling system)
GPU: 1x AMD Vega Pro Frontier Edition (water cooled)
Hard drives: System Samsung 970Pro NVME, AV-Projects 1TB (4x Intel P7600 512GB VROC), 4x 2.5" Hotswap bays, 1x 3.5" Hotswap Bay, 1x LG BluRay Burner

PSU: Corsair 1200W
Monitor: 2x Dell Ultrasharp U2713HM (2560x1440)

Rich Parry wrote on 10/22/2014, 10:12 AM
Thanks to all that replied. I'm sorry I wasn't clear, the checkerboard pattern was intended to simulate photographs, it is not video. I thought this was the best way to show my problem. The checkerboard pattern is a JPEG image representing photos.

I have made the video downloadable but here are some details. These parameters represent what I uploaded to Vimeo.

Bit rate mode : Variable
Bit rate : 9 941 Kbps
Maximum bit rate : 20.0 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 23.976 fps
Standard : NTSC
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive

CPU Intel i9-13900K Raptor Lake

Heat Sink Noctua  NH-D15 chromas, Black

MB ASUS ProArt Z790 Creator WiFi

OS Drive Samsung 990 PRO  NVME M.2 SSD 1TB

Data Drive Samsung 870 EVO SATA 4TB

Backup Drive Samsung 870 EVO SATA 4TB

RAM Corsair Vengeance DDR5 64GB

GPU ASUS NVDIA GeForce GTX 1080 Ti

Case Fractal Torrent Black E-ATX

PSU Corsair HX1000i 80 Plus Platinum

OS MicroSoft Windows 11 Pro

Rich in San Diego, CA

Laurence wrote on 10/22/2014, 4:12 PM
Check out the examples on my last post in this thread:

http://www.sonycreativesoftware.com/forums/ShowMessage.asp?ForumID=4&MessageID=896747

You have to look download and install the player to see the magic. That Sony player does a sort of bob deinterlace that is really wonderful is why.
John_Cline wrote on 10/22/2014, 5:31 PM
It's pretty simple, you're not using a high enough frame rate to move the graphics that fast. The integration time of the eye is about 40fps, anything lower than that will produce the judder you're seeing. That's part of why television was interlaced to begin with, to get a temporal resolution of 59.94 individual images per second. I never shoot 24p, ever.
Laurence wrote on 10/22/2014, 6:47 PM
Now that I've looked at the files in the post I must echo what John Cline is saying. You can only move an object in a video so fast as compared to the frame rate. The faster the frame rate, the more motion you can use.

Having said that, in your case you could probably keyframe in some blur on the axis of the motion. I have done that quite successfully on quick pans and tilts where the video was shot with too short a shutter speed.
Duncan H wrote on 10/22/2014, 9:20 PM
I'm still scratching my head.

Please see my post above. I've given 2 examples below. They are from the same project, 720p, 25 fps.

If I render with MC mp4 template I get this:

If I render with AVI (Magic YUV codec) then render mpeg 2 (720p, 25 fps) I get this:


I see a substantial difference, even more when I look at the "original" AVI (720p 25 fps), vs the MC mp4 (720p 25 fps), but I had to rerender the AVI through to an mpeg to enable upload to Youtube.

Any thoughts on why the difference?
Dramatically different level of "jitter". I find this surprising.