VV4.0d seems to have a bug with the 'Frame Rate' setting not INTERNALLY sticking when you initially create a new project. Outwardly the frame rate seems to be whatever you set it to, but internally VV is still operating with a 29.97 project.
If you use anything but 29.97 you're in for a world of confusion if you don't re-set your frame rate AFTER the project is created. Once you do that, everything seems to be fine.
This makes me VERY PARANOID that there might be other less easy to spot settings are aren't really getting set when you start a new project (like render quality etc.)
Here's details & how to reproduce it:
1. Create a new project (starting with the NTSC DV tempate so we're all on the same sheet of music), and then change the frame rate to 12.000 (Half Film) and the Ruler Time format to 'Absolute Frames'
2. I set my grid format to 'frames' for clarity, shut off snap to grid to avoid confusion, make sure Quantize to frames is on.
3. Zoom into your timeline until you can see the grid lines, more your cursor to frame 60 WITH THE KEYBOARD KEYS -- if you use the mouse, you'll see it may snap within the grid boundaries. Drop a marker here. -- NOTE on your time display that the closest you can come to frame 60 is 59.940 -- Leave the cursor here
4. Goto File...Properties and note that the frame rate still SEEMS TO BE '12.000 (Half Film)' -- Change the frame frame to '29.970 (NTSC)' and hit APPLY -- you should still be able to see the marker on the timeline, and the marker time did not change (still 59.940), but the grid lines did.
5. Now set the frame rate back to '12.00 (Half Film)' and volia! The marker and cursor are now EXACTLY at 24.000 (where they should have been) -- And now the frame rate setting seems to have really stuck this time.
So in conclusion, it seems like when you initially set the frame rate in the new project dialog, the OUTWARD label seems to stick, but the internal setting stays at 29.97 -- oddly, the GRID SETTING seems to reflect the OUTWARD frame rate
Can anyone else verify this bug?
Thanks,
Jon
If you use anything but 29.97 you're in for a world of confusion if you don't re-set your frame rate AFTER the project is created. Once you do that, everything seems to be fine.
This makes me VERY PARANOID that there might be other less easy to spot settings are aren't really getting set when you start a new project (like render quality etc.)
Here's details & how to reproduce it:
1. Create a new project (starting with the NTSC DV tempate so we're all on the same sheet of music), and then change the frame rate to 12.000 (Half Film) and the Ruler Time format to 'Absolute Frames'
2. I set my grid format to 'frames' for clarity, shut off snap to grid to avoid confusion, make sure Quantize to frames is on.
3. Zoom into your timeline until you can see the grid lines, more your cursor to frame 60 WITH THE KEYBOARD KEYS -- if you use the mouse, you'll see it may snap within the grid boundaries. Drop a marker here. -- NOTE on your time display that the closest you can come to frame 60 is 59.940 -- Leave the cursor here
4. Goto File...Properties and note that the frame rate still SEEMS TO BE '12.000 (Half Film)' -- Change the frame frame to '29.970 (NTSC)' and hit APPLY -- you should still be able to see the marker on the timeline, and the marker time did not change (still 59.940), but the grid lines did.
5. Now set the frame rate back to '12.00 (Half Film)' and volia! The marker and cursor are now EXACTLY at 24.000 (where they should have been) -- And now the frame rate setting seems to have really stuck this time.
So in conclusion, it seems like when you initially set the frame rate in the new project dialog, the OUTWARD label seems to stick, but the internal setting stays at 29.97 -- oddly, the GRID SETTING seems to reflect the OUTWARD frame rate
Can anyone else verify this bug?
Thanks,
Jon