Anyone actually use frames mode on the video track?

[Starcrash]

I never do. I don't know anyone who does. Having the video track(s) set to "frames" mode rather than "blocks" makes PT all sluggish because of the juice it takes to constantly redraw the frames. It seems completely useless because you can always tell what frame you are on by just looking at the BIG frame right in front of your face (the actual video picture). Who needs it, right? And yet, ...it defaults to "frames" mode every time you import a video. What's the deal? Am I crazy or has this changed since 7.2? I don't remember having to change the video track to blocks every single time. Didn't it used to remember your last used preference?

[bad jitter]

I do use it sometimes. When I receive a new picture with a some changes, I put it on new video track. When I zoom to the level I can see individual frames, it helps you to see how many frames have changed, when you compare the new and the old picture. Before multiple video tracks, I rarely used it.

[Phil Jeffers]

Good idea to double check sync (i.e. leading edge of 2 pip, or FFP), but never apart from that...

A 3GHz dual-quad Mac Pro may change all that though!

[gerax]

I use it from time to time to spot a certain point in the picture to sync something or to get a reference point for automations and such. I zoom at frame magnitude and put a marker exactly on the frame change, then I zoom back to normal and put the video track back into blocks, better yet, I also hide it from the timeline, and just look at the preview window and the big screen.

L.G.

[trakbytes]

...Am I crazy or has this changed since 7.2? I don't remember having to change the video track to blocks every single time. Didn't it used to remember your last used preference? ...

This has changed, and needs to be changed back. Several years (and versions) ago, PT changed to defaulting to frames mode. There was some outcry, and it was changed back to default to blocks. Seems the current generation of programmers haven't read the history. Don't know why someone decided to change it back to frames, but it should default to blocks. It's a nuisance the way it is.

Bob

[Reckless Erik]

...er, no it won't.

[sleadley]

Good idea to double check sync (i.e. leading edge of 2 pip, or FFP), but never apart from that...

A 3GHz dual-quad Mac Pro may change all that though!

This is no longer necessary as Pro Tools 7.3.x only cuts the video Track at a resolution of 1 Frame, so it will always cut correctly on the leading edge. However, I have it on most of the time and on my dual G5 2.3 GHz it does not seem to make the system sluggish.
my 2c
Simon L.

[Danny Caccavo]

This is no longer necessary as Pro Tools 7.3.x only cuts the video Track at a resolution of 1 Frame, so it will always cut correctly on the leading edge. However, I have it on most of the time and on my dual G5 2.3 GHz it does not seem to make the system sluggish.
my 2c
Simon L.

Simon is correct - the way we now draw the frames eliminated the need to default to blocks view.

Danny Caccavo
Digidesign

[Starcrash]

Still, I would much prefer it to default to blocks. Anyone else?

[DigiTechSupt]

In addition to what Danny and Simon said, since 7.2 frame view shouldn't make your system sluggish. The frame view performance has been significantly improved so it's not possible to "hang out" in frames view.

Also, the keyboard short cut to swith the video track back and forth from frame and block view is Control + Command, left or right arrow key. Be sure that the cursor is on the video track(s) that you want to change.

This is follows the audio track shortcut for switching between waveform, volume, etc.

Speaking of frames view, has anyone had a chance to play with Universe Window and it's frame view (Right click in the Universe window and choose video)? I find that many don't know about this. It can be a very hand tool for navigating the session based on a video scene(s) very quickly.

Jon Connolly
Digidesign Product Specialist