Norman Black
Forum Replies Created
-
[Márcio Nascimento] “I rendered in vegas mainconcept FullHD 24p 40Mbit but Archtect warned me: “The overall bit rate is greater than 28 Mbps.”
40Mbps is the MAXIMUM Blu-ray spec bitrate. Not the average. Most BD movies are in the 18-25Mbps average for video bitrate.
-
AVC = H.264, H.264 = AVC.
Mainconcept AVC does support Baseline, Main and High Profiles.
Mainconcept supports single pass VBR, two pass VBR or constant bitrate.Sony AVC is single pass VBR.
In Sony AVC, the AVC selection is always High profile. To get to Baseline and Main you have to select memory stick. Who knows why SCS makes the Render as templates so quirky.
Only Sony AVC can output to an AVCHD m2ts file container.
Mainconcept AVC is probably better at low bitrates than Sony AVC, since it uses more B-frames, but who cares. Neither Mainconcept or Sony AVC are remotely close to x264 in this regard.
-
[Blake Gibson] “So, I dropped 50 cineform files onto the timeline and it was fine, the filesurrogate didn’t even flinch, was sitting happily at around 50-100mb usage in task manager. I tried it with the same 50 prores files and the filesurrogate jumped up to 800mb, so surprises here.”
For Cineform AVI Vegas bypasses Video for Windows since it uses the Cineform SDK to directly use the Cineform codec. I believe I remember reading Newmann from Cineform state with was around Vegas 10, which is after Vegas stopped including Cineform according to JR.
fileiosurrogate is a 32-bit process of Vegas and is only used by 32-bit codecs in Vegas so most things will not touch/use this process. Really only Quicktime comes into this. Curiously the MP3 decoder is also only 32-bit in Vegas.
To Apple Quicktime on Windows is a video player only. A video player only needs to be 32-bit.
(rant on)
Prores is an issue for one reason and one reason only. Apple wants it to be that way. Prores started as an Apple specific clone of DNxHD which was Avid proprietary. The whole intermediate format is a mess because everyone has created their own proprietary formats over time. HDCAM SR, DNxHD, Cineform, Prores. DNxHD and Cineform have recently become SMPTE standards, but you have to pay buck to SMPTE to get the spec and reference source code, and who knows what licensing restrictions remain.Everyone wants to protect and build their own special turf. Avid and Apple especially. I just which Cineform/GoPro would have just put the codec into public domain. GoPro has no turf to protect and Cineform is an excellent codec. Arguably technically better than the simplistic DCT JPEG type codecs of DNxHD and Prores.
XAVC Intra is the only thing that has a chance to deal with this mixed stew we have right now. It is just AVC with restricted encoding options. The AVC codec is well known as are the MPEG-LA AVC licensing rules.
Vegas keeps all files open at all times and this causes the problem with Quicktime. It is a porker with RAM and DNxHD or Prores codecs. Hitfilm has the same Quicktime file problems with lots of files. Quicktime is what it is and it is important so people like Vegas should work with it. If you don’t then customers are stopped in their tracks. Really while editing you do not need a file open that is 10 minutes ahead on the timeline or behind. Having a background thread monitoring and maintaining the file open list is not terribly difficult, but such a change is BIG, and thus maybe dangerous, for people like Vegas to do.
(rant off) -
[John Rofrano] “[Blake Gibson] “after editing/grading etc: Cineform > handbrake h264 (that would mean I’ve gone from Prores > Cineform > Cineform > Handbrake”
If you want to use Handbreak then that’s the proper sequence. You can render and re-render to CneForm 10 times and not see any degradation in quality. This is what that codec is designed to do (be used in a production pipeline of multiple application transfers).”Handbrake cannot read the Cineform codec.
-
[Zach Noel] “However the 50Mbps bitrate is the conclusion I came to with the references below. Either way, I tried turning this down to as low as 1,000 and the error still occurs.
https://support.google.com/youtube/answer/1722171?hl=en
https://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#LevelsThe second link is also where I come to the conclusion for the High 10 profile”
Looking at your Youtube link, there is absolutely nothing about 50Mbps bitrate. For 1080 high frame rate it suggests approximately 12Mbps.
This Youtube encode pages says nothing about High10 profile. I am not sure what on your second link could make you think High10 is what is required given the Youtube encode recommendations. Just leave the Level setting at Auto.
Looking at your two x264 setting screen shots the main differences are the High10 profile and them colorspace option is different from the encode that worked.
-
Your bitrate in the screenshot is 50Mbps. That is a truly massive bitrate for HD with the AVC codec and you are not going to see a difference between any AVC encoders at such high bitrates. At such high bitrates you are not going to see differences between Medium and Veryslow encodes in x264. That bitrate is over twice the average bitrate of HQ Blu-rays and 5X of Youtube.
Second what is the High10 profile you chose in your failed encode try. That is probably the source of your failed encode. Video for Windows (AVI) can only ever be 8-bit. Also your sources are probably only 8-bit.
-
One thing to try with these things is to disable GPU support in preferences and see if that helps when rendering.
-
Changing the bitrate will not really change the file encoding speed. It will only affect the final output file size.
-
Your source file was using bitrate X and your output was using bitrate Y, where bitrate Y is greater than bitrate X.
You can use the free MediaInfo utility to determine what your source bitrate(s) are if you want to replicate that value.
Your files have a video bitrate and an audio bitrate. You can control both in your Vegas render templates.
-
[Stephen Mann] “The GPU setting in Preferences is for preview. Your GPU, display and driver combination probably won’t work for preview.”
A point of pedantic info. The GPU setting in Preferences works on preview and rendering. It is the option for the video rendering engine of Vegas which of course is used for preview and generating a file.
The GPU setting in a render as template is for the file encoder use of GPU if it supports it.
Both options are independent of each other.