Norman Black
Forum Replies Created
-
Norman Black
March 27, 2014 at 4:37 pm in reply to: Video Shot In 23 FPS Should I Still Render / Upload At 29 FPSKeep your original frame rate as long as it is less than or equal to 30fps. By 23fps, I assume you mean 23.98?
The online video servers normally have a limit of 30fps, so on those you should bring the frame rate down below 30fps. For example a 59.94 video would come down to 29.97. I cannot comment specifically about Facebook, but the others Youtube/Vimeo/Smugmug all do not alter frame rates less than or equal to 30fps. I would expect Facebook operates similarly.
-
By putting a computer to studio levels adjust on the media you are losing some levels information since the 0-255 range is being squished into 16-235. Those losses should be negligible, meaning not visible.
You were also losing those levels when using Cineform also when you are editing in a normal 8-bit project. Cineform is 10-bit and it might preserve a little more, but that technical detail is above my pay grade. You could ask GoPro.
If GoPro says that more info is preserved, with an 8-bit 0-255 converted to a 10-bit studio range, then a 32-bit project is the only way to preserve that, and it gets lost again when you render to a normal final destination.
-
Canon/Nikon/Panasonic/other DSLRs all record with full range AVC data, and they flag this as such in the AVC stream in a VUI option flag. This is also true for GoPro.
In the Cineform conversion the AVC input is being normalized to a studio RGB 16-235 output range. They can do this reliably because of the VUI option flag in the AVC stream.
When you input directly into Vegas, you get exact data recorded in the data stream completely unaltered.
Therefore you would require studio RGB output for encoding, and this is the normal case. You will need to add a levels adjustment from computer to studio RGB. If you want to try and use the extra range you can use custom levels and/or curves adjustments to go from full range to studio range.
With the studio Cineform files the Vegas preview window will be flat compared to playback of typical encodes player in a video player. With full range the preview looks good, but encodes will crush blacks and clip highs.
-
For me, I have only had playback performance problems with 1080p60 files in VP12. A test showed VP11 was okay with the same file. 30p files are probably still sapping the CPU some but it has not be a problem for me.
It is an issue. I have had a bug report to Sony for a couple of months now. I gave them a VEG file and 30 second sample videos. Who knows it they will ever say anything.
-
No you do not need it at all. I have put my GoPro MP4 files straight into the Vegas timeline.
The AVC video in the GoPro files is very compute intensive to decode, so *IF* your PC has trouble keeping pace for full frame rate playback, then the conversion to Cineform AVI files can help, or using the Vegas smart proxy feature can help.
-
Are you talking about the “Import tutorial” from the Help menu?
If yes, then that runs fine for me. I cannot find anything else about tutorials to watch in the application. I have free GoPro Studio 2.0.1. I don’t have premium or professional.
-
When you import a file that has both audio and video Vegas defaults to grouping the two events together. Therefore they move and trim together.
To temporarily ignore the event grouping, use the Ignore event grouping tool on the toolbar and then you can shift the audio relative to the video. Then do not forget to restore the toolbar button back to its previous state.
You can also ungroup or group events via the right click context menu.
You can move the snap offset position on the audio and then snap the audio to the start of the video. The snap offset is little white triangle in the low left corner of the event of the event.
As for moving a specific number of milliseconds, I do not know, but it must be an even multiple of frames and Vegas defaults to quantizing events on frame boundaries.
-
I have never done anything with 120fps output from the camera you mention.
That said, from your description it sounds like the camera output file is a “normal” frame frame of 30fps even though recorded at 120. The only thing I can offer is that maybe you need to turn smart resample off on the event(s).
Beyond that keep your slow motion and normal frame rate recording separate so that for normal you do not have to adjust the playback. Then again, you might be trying to do a speed ramp effect then then I am just speculating without information.
Also, do not put your jpg screenshots up as ZIP file. The cow forums have the ability to handle images directly via the image upload button so we do not have to download and unzip to view.
-
There are four text plug-ins in Vegas and you did not mention which you are using but an answer is mostly the same for all.
NewBlue titler Pro has a Fly-in animation which can be used.
For others…
You need to use Keyframes on the X position of the text. To get a gradual slowdown you can first try to change the keyframe curve type by right clicking the keyframe point and changing to something like fast fade.
If that does not give you want, then multiple control points to delay the point of the slow down might get you what you want. In other words, for a period of time you might want a constant speed and then a slow down. From the first to second keyframe would be constant/linear and then you would do your fast fade.
If that does not give you what you want, then you will have to play with the curve shape manually. In titles and text you click the curves button in the bottom right of the window and then on each keyframe point right click and select manual or split manual and then edit the curve shape with the bezier control points.
Lastly Titles and Text has predefined animations for slide in different directions. There is no control over the animation except for event length. To get what you want you will likely need a couple of adjacent events. I did this once with the fall down animation to control the speed of the fall down effect.
-
I’ll still use Mercalli 3 SAL, but if I ever have a need/desire to do Stabilization as a plug-in, I now know how to get what I want out of Sony Stabilize.