Aaron Star
Forum Replies Created
-
[Martin Leisborn] “If so, what other alternatives are there in order to get 422 to Vegas?”
Sony Broadcast has devices to record in 422 and higher, most people on this forum are not in that ballpark. Check out the PMW-1000. It is really odd that Sony of all companies does not have a “Ninja” like device that records to all Sony Codecs. I guess they feel that device would cut into their camera sales to much.
HDCAM SR and SR-Lite are 444 & 422 mpeg4 intra with uncompressed audio channels.
XDCAM422 – clearly stated and highly optimized workflow in Vegas.
XAVC-intra – PMW-1000 now supports recording in HD in XAVC-Intra 422. XAVC is like MP4 2.0, which is a higher MPEG4 profile than AVC, and it uses multi channel uncompressed audio. XAVC also supports 4k bitrates where as HDCAM and XDCAM do not. In my opinion XAVC is pretty much just HDCAM 4K or HDCAM 2.0
REDCODE don’t forget about Redcode – Red One cameras these days are really cheap and the Red shoots in a 12-bit JPEG 2000 Wavelet codec. Redcode is natively supported in Vegas.
-
What Gpu, and how are you connecting the monitor to make it the preview display?
Are you trying get to get a full screen preview on a second display?
-
I would like to know more about your source material, and the plugins in use. The Best setting is multithread optimized, it could be something in the render chain that is limiting your render performance. Could be the way the GoPro format and magic bullet are being handled. However, I did not see plugins in use at least on the point where the cursor was.
You could also try rendering to XDCAM-EX.MXF and upload that directly to YouTube.
I would try building a sample project where you compare source media in XDCAM-EX, HDCAM-SR, or Cineform.avi, then render to Sony AVC “internet 1920×1080-30p” around 16MB/s profile, or XDCAM-EX.mxf. Do this in CPU only mode, unless you have a 290X or better AMD GPU.
-
I would run the files through ffmpeg, re-writing the files to a new container. If that does not work, convert the footage to hdcam-sr-lite or xdcam-ex. Those formats will edit much smoother and with less system overhead.
-
Ffmpeg can re-wrap the file to mov without recompression.
Catalyst prepare might be able to convert the files to something like hdcam-sr-lite, cineform, or even xdcam-ex since it’s only 36mbs video.
Resolve would work too convert, or just work the footage in resolve. Resolve calls hdcam-sr-lite sony mpeg in an MXF container.
-
Your shutter speed will stay the same. After the fact, your conversion from 50p to 25p will be just dropping every other frame. Effectively showing each remaining frame twice as long for the one second duration. Does that make sense?
-
You might need an apple to encode the actual Prores format.
You could try sending them a test using FFMPEG encode to Prores, as they may not even know the difference.
download FFMPEG, then use the following command:
ffmpeg -i “input-filename” -vcodec prores -acodec pcm_s16le -ar 48000 -ac 2 “output-Filename”.mov
Add -profile 2 or 3 to the command to get Normal or HQ
Not really sure what you project master footage was encoded in, but make sure you final render out is roughly the same quality as the ProRes HQ. Something like Cineform-High, HDCAM-SR, SR-Lite, XAVC-I or at least XDCAM422 before the encode to ProRes. Clearly your final render should be in 32-bit Video Levels if moving to 10-bit codec levels.
-
HP is boycotted as far as I am concerned. This after reading they cut 30,000 jobs in the US, but are ramping up H1B applicants and stating they cannot find tech skills in the US to do the jobs… Yeah right. More like they cannot find the skills at the low price they would like to pay in US.
You can build a similar Xeon System with off the shelf parts and not pay HP for their time and engineering. Use AMD for the GPU, and not the w7100 which is cheapo board gear towards people like HP building mass systems. Go with a W9100 if you really need a Pro level card, or a 390X/290x, or Fury-X for the best GFLOP performance in OpenCL. This would make a good Vegas Pro 13 machine.
The GFLOP performance on an AMD M395x Mobile/integrated chip is not the same as a 390x desktop card. The Desktop 390X is nearly 2x the GFLOP of the M395x. So the apple configuration looks great, but devil is in the marketing details. iMacs are also prone to heat issues that burn’em up faster, so that you have to buy another one that’s more updated. most people I know that have iMacs have them in the shop way more than any PC I have ever owned. Part of the design and marketing Apple has going.
Catalyst Edit Engine is different from the Vegas handles hardware, so may be not be limited to AMD for best performance. In my testing of Catalyst Edit, it seems to perform very well on the same AMD GPU hardware selected for Vegas.
Changing to FCP is a personal choice, and not a necessity as Vegas 13 is not going anywhere. Catalyst Edit appears to be slowly gaining the features that we expect from Vegas. I think another 6 months to a year and Edit will have pretty much 80% of anything we expect from Vegas.
-
I would try this.
- Set project settings to 4×3 HD project resolution.
- Use pan/crop on 16×9 media in the timeline to scale such that there is no letter box.
- Render project to 4×3 HD profile that matches the project settings. (may need to create your own.)
This process should render 4×3 video only, however, 16×9 streaming services will still pillar box the 4×3 video.
-
Get a PC monitor with HDMI and see what you get from the output. You could also buy the device, test it, return it if it does not work, then share the results with the forum.