Norman Black
Forum Replies Created
-
Hopefully if works out.
In my mind the real question is who/what is putting XDCAM in MOV. You must be getting stuff from some Mac people. They transfer everything into MOV.
In the long run you may be better off avoiding using Quicktime with Vegas.
-
Apple does sell an mpeg-2 decoder.
https://store.apple.com/us/product/D2189Z/A/quicktime-mpeg-2-playback-component-for-windows
It’s only $20. I do not know if it will work with your files.
-
That file that does not open is exactly what I thought it might be. It is an XDCAM file that for some reason was put into a Quicktime MOV file.
If you can get that stuff remuxed into an MP4 file then Vegas will handle it properly. MP4 and MXF are the container formats that Sony seems to spec for XDCAM, and that is the format Vegas generates as well.
Avidemux will not put PCM audio into an MP4 file. Avidemux does not support MXF. I am not sure what other GUI muxer does. A fairly simple ffmpeg command should do it.
ffmpeg -i input_file -c:v copy -a:v copy -chunk_size 64k output.mp4
If transcoding:
Don’t worry about optimal settings in Handbrake for each video. Once you figure out something you like then it will work for all. In Handbrake use the constant quality setting. For best edit/decode performance maybe use Baseline profile. Bigger file but edit performance can be better. -
Don’t know Adobe media Encoder.
About generational loss.
Depending on the source video format, probably mpeg-2, and the audio format, there is a possibility of remuxing the data streams into a container Vegas handles. Vegas is very picky about what audio format can be with a specific video format. Maybe you can just split the audio and video into two files. Vegas will accept mpeg-2 video in stand alone files. Avidemux might be the easiest tool to try this with.
We really don’t know anything specific about your file(s). A MediaInfo report would/might help (free utility).
As for transcoding and keeping quality the same no flat answer can be given. If converting from mpeg-2 to AVC it is generally said the AVC bitrate can be half that of mpeg-2. So a bit above half should be “safe”.
-
That codec ID seems to point to an mpeg-2 format. Quicktime does not by default come with mpeg-2 decode ability. One can purchase an mpeg-2 codec for Quicktime.
Something like Handbrake or Cliptoolz convert or ffmpeg may be able to transcode that for you to an AVC or other format Vegas can import.
-
When logged in. I click my name in the upper right of the page.
Then on that page I click, Edit profile. The check option is on the edit profile page. -
It might have something to do with the Hide Newbie posts option in your profile.
-
If you Google for “RGB shift OR split OR twitch effect Vegas” you should find some tutorials that seem to use the 3D stereoscopic effect shift in Vegas. May or may not give what you want.
-
It looks like an RGB shift effect. One or more RGB channels separated/offset from the others.
Vegas does not have an effect like this built-in. NewBlue FX offers one but it is a part of a large effects package.
-
Nothing you can do.
Mainconcept AVC does not support your GPU. MC AVC is old and is hard coded with support only for older GPUs. In the case of AMD, 5xxx and 6xxx series.
Note that Vegas will still be using GPU for your effects and video compositing.
Also, the Mainconcept AVC encoder on CPU is just plain slow. The Sony AVC encoder is much faster in general.
I use frameserving to ffmpeg to access the x264 AVC encoder which is much faster than both of the above with higher quality as well.