Aaron Star
Forum Replies Created
-
More “Media Info -application” on the source media might help. Then let people know the details of your project settings (screenshots), and what render template you are attempting to use. There should be no reason to use uncompressed for a wedding video.
The way I would handle that type of change is to use FFMPEG and extract the audio from source media. Then make changes you want to the audio. Then re-mux the audio track back to the video source, this will copy the video with no re-compression.
-
Download a utility called Media Info, then switch it to Text mode and post the media file info.
Screen shots and as much info you can provide as possible will help the community assist more.
Does the Blackmagic playback utility give you sound?
Did you verify that you were recording audio using the pass thru HDMI or SDI out interfaces? Those recorders are pretty simple and just record to formats that expect uncompressed audio in multiple channels. If there is no audio, there may not be audio recorded, or audio was at a very low level.
You might try selecting a 1 sec section of the audio and hit S. Then right click on the small audio clip and choose normalize from the options. If there is audio, normalize will raise the levels such that you can see your peaks. If you see audio at that point, you need to determine how to raise your audio levels so that you are not clipping where you need. Things like mic bumps and other pops in a long clip can make normalize not work well. Selecting a clipped section where good audio dialog is recorded, then normalizing that section, then expand the edges of that clip to the full clip is a good work around for normalizing audio. Then you can clip up the file into sub clips.
-
On the Camera shoot in:
MXP (1920 x 1080) or
NTSC 60p (1920 x 1080)For Render Settings:
This will depend on if you are trying to capture 60P or not. If you are just doing 30P, you can use one of the Internet profiles that matches your project settings and the bit rate is somewhere around 16Mbs average. What you really do not want to do it overly constrain your bitrate on render such that motion artifacts are added. Get more upload bandwidth if you uploads are taking to long.
For 60P camera footage, you would want to upload with 2X the bitrate of 30P, so 16Mbs-32Mbs for video side. You may need to create/modify a profile to adjust for 60p and the higher bitrate.
If upload bandwidth is not a problem, you can alternatively upload a format like Prores, or XDCAM-EX. Youtube re-encodes your material to fit inside the bitrates they like to stream at, so provide them with enough extra bandwidth that they are not doubling up on your compression artifacts.
Youtube formats:
https://support.google.com/youtube/answer/1722171?hl=en -
“Do I then turn off AutoRipple?” Always work with this off, and CNTL+L only when you need that edit. Make sure to set auto ripple to All Tracks, that tends to be the edit most are looking for.
Basic 2 camera:
Sync the footage on multiple video tracks, using one of the methods outline above.
When editing the material, switch cameras by right clicking on the top video track clip >switches >mute. To switch back, you just un-mute the top video clip. Having a blank top video track allows you to position the cursor better and get a cut across all the video and audio tracks. No need to delete the muted sections. This will work with multiple camera angles by muting clips layers down to the camera you need.
-
In the project settings, there is “Match Media” button to help with setting the project correctly to your source media.
Another way is to drag and drop the 1st clip to the timeline in a new and clean project. Vegas will auto set the project settings to the media dropped on the time line.
If there is no render profile that matches (=) your project settings, you will have to modify one. Vimeo will appreciate sticking to video standard resolutions and frame rates. 1920×1080 @ 59.94 hz/FPS in your case if your media is actually 60p.
Research what Vimeos stream rates are for 60p material, and them provide them with 2X the bit rate on upload. That is more a rule of thumb. Let them throw away the extra data to optimize the re-encode of your material. Of course this assumes you shot at a bitrate that exceeds what they stream at.
If you need more help, post media info (its an app) on your source footage. The community will help more, with more info provided.
-
Posting screen captures can help the rest of us help you.
Also download a copy of “media info” this helps with determine your source material format.
Download a copy of “Speccy” if you do not know exactly what your system specs really are.
Creating a new blank new vegas project, then dragging and dropping a media clip to the timeline, will setup the Vegas project for what you need to edit that media.
-
I just made a post about OBS recording yesterday. You might want to try those settings. The overall thread also says why playback can be strange in Vegas from encoders like OBS.
https://forums.creativecow.net/thread/24/1016586
If your “fan is going crazy,” it sounds like your system might be to weak to push what you are asking it to do.
Increasing the Key frame setting will make Vegas work hard to build frame from all the Long group of pictures. More I frames (keyframes) with a high bit rate, will make the system work hard, increase your file size, and pretty much only improve timeline indexing. I would just use the 0 setting, which is Auto. The bottom line .264 encoded files are not really great to edit with. It would be nice if OBS and others supported intra frame encoding. Especially with such high motion in a game, but they lean towards record length and not quality.
-
With high bit rates and 60p encoded into a normal AVC/.264 format, you need to select the High Profile. With MC AVC encoder, I would try the variable bit rate mode with your Average at 25Mbs, and the peak at 50mbs. The final will most likely not peak to 50mbs, and uploading a 25mbs bit rate allows YouTube to throw away some image info when it compresses down to 12Mbs.
Xavc is really just a higher profile (5) than normal AVC/.264 High profile(4).
I made a post yesterday on the same topic:
https://forums.creativecow.net/thread/24/1016586 -
In OBS, you can try these settings for recording footage to be edited in Vegas. This is not a streaming live profile.
AVC 1080 at 30P gives a good image 22Mbs, so for 60P you just double it.
pay attention to the advanced tab “custom x264 settings” and enter:
-r 60/1 –8x8dct
This will make the encoder stick to a 60P format which will edit better in Vegas. The file will still show as variable, but if you check the frame rate with ffprobe, you should see:
r_frame_rate=60/1
avg_frame_rate=60/1Disable resample on the clips on the time line. Drag and drop the 1st clip to a new project time line to set the project settings.
See the attached photo for settings.
When encoding to MP4 use MC encoder with these settings:
-
“drop like shadowplay or obs footage ” Yes. that is why you need to try xsplit, because it records with a fixed frame rate. The others like OBS record in a variable frame rate that Vegas displays as corrupt video. Variable frame rate is a neat way to compress video, but an NLE like vegas requires a constant frame rate. Professional video editing requires close tolerance with frame timing. Poorly coded or cheap video hardware will drift. That is why good video hardware is expensive.
You also do not know what your “media info” is. Switch the media info app to text mode and paste what is shown.
You need to stop blaming Vegas, you are just displaying your ignorance about video editing. Vegas has been around for 16 years, software does not make it that long without being to edit video properly. You need to figure out what you are doing wrong in your workflow.
