-
Wedding DVD burning file size Vegas Render
-
[Derek Charles] “Also, aren’t most up to date DVD players equipped to where when inserted, an option comes up as if it were a USB stick or just reading the data off of the disc”
Technically , no. That’s not part of the DVD standard. Some players will play DIVX, MOV or WMV straight off a disc, but they are proprietary and uncommon nowadays. For those that do, there is usually a logo on the player. If you are authoring DVD’s for public sale, it’s best to stick to the standard.
When you author a DVD in DVD Architect, Nero or Power DVD, they convert your files into BUP, VOB and IFO files and create a VIDEO_TS and AUDIO_TS structure that DVD players instantly recognise.
My system specs: Intel i7 7700k 4.20 GHz, GTX570, 16GB RAM, Gigabye Z170 HD3, Vegas Pro 12 (x64), Windows 10 x64 Pro, Vegas Production Assistant 1.0, VASST Ultimate S Pro 4.1, Neat Video Pro 2.6
-
[Derek Charles] “Would the 1080 on the DVD just play as 720, or is that a strong NEVER play?”
That’s a very strong never. As Nigel said, the DVD spec support MPEG2 video only. You can use NTSC 720×480 @ 27.97fps interlaced, PAL 720 x 576 @ 25fps interlaced, or 720×480 @ 24fps progressive. That’s it. Audio can be PCM or AC3 for NTSC, and PCM, AC3, & MPEG2 audio for PAL. Those are your options.
The fact that any particular DVD player can accept other formats is totally non-standard and not advised unless you are making this for your personal use and own one of those DVD players and are fine with the disc not working in the future when the DVD player breaks and the new one doesn’t support those nonstandard formats anymore.
If you want to author in HD you need to Blu-ray not DVD.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Thank you – I’ve got the DVD issue down now.
There was a bitrate problem stated above I’m still not sure on if anyone else can chime in –
Is there quality loss from rendering a1080 file to 1080 file with the same bitrate settings? Like if you do with a jpeg?
I’m asking this for color grading and “rendering to a new track” for smoother playback on cpu.
Rendering to a new track keeps it at the original XAVCS codec…
But say I stuck with the 1080 mp4 with 4Mb avg and 8 Mb max as through the “Internet 1080 HD” render template as a render to new track – file is not as bigWhen am I losing latitude for color grading, levels, shadows highlights recovery, etc? Should I assume as long as the settings are the exact same I will still be able to adjust the footage without artifacts?
My original is 4k 100M edited on a 1080 timeline -
[Derek Charles] “Is there quality loss from rendering a1080 file to 1080 file with the same bitrate settings? Like if you do with a jpeg?”
Yes, if the codec is lossy. In your example jpeg is a lossy codec and every time you open the file, change it, and save it, you loose quality. PNG can be a lossless codec so you can change it and save it again and again and retain the original quality. QuickTime actually supports the PNG codec which provides lossless copies.
[Derek Charles] “But say I stuck with the 1080 mp4 with 4Mb avg and 8 Mb max as through the “Internet 1080 HD” render template as a render to new track – file is not as big”
Not a good idea. You will be loosing quality and disk space is cheap. Don’t do it.
[Derek Charles] “When am I losing latitude for color grading, levels, shadows highlights recovery, etc? Should I assume as long as the settings are the exact same I will still be able to adjust the footage without artifacts? “
It all depends on the codec. Lossy codecs will loose quality. Lossless codecs will not. The question is, will you see the loss? Rendering back to the same exact format and bit-rate I’m guessing you will not see the quality loss from just one or two generations, just like you don’t see the quality loss by re-saving a jpeg until you do it many, many times.
BTW, this is why people use Digital Intermediaries for color grading. They use near-lossless or visually-lossless codecs. The most popular intermediaries are Apple ProRes for the Mac, CineForm for Windows, and Avid DNxHD for both Mac and Windows. I would do all “render to new track” using a lossless digital intermediary codec or a vey high bitrate codec like Sony MXF 422 @ 50Mbps. That’s why on the Mac, everyone color grades with Apple ProRes and doesn’t even thing twice about it.
~jr
http://www.johnrofrano.com
http://www.vasstsoftware.com -
Since I’ve lowered my bitrates significantly, I’m noticing a big quality loss sticking under 4avg and 8max
– It is very unpleasing macroblocking – and added grain. I’m still confused in how I see users with the same camera, same 1080p and have a significantly lower 1080 file size uploaded, with higher quality playback… bitrates for Vimeo, YouTube etc.I’m not worried about disk space, I’m worried that people complain my large files on Vimeo take too long to load and if I upload to Facebook, the large file size will play back longer at 360p while its still trying to load and catch up to the 1080p stream.
-
I’m noticing the quality loss you speak of from the 4avg and 8max – It is very unpleasing macroblocking – and added grain. I’m still confused in how I see users with the same camera, same 1080p and have a significantly lower 1080 file size uploaded, with higher quality playback… bitrates for Vimeo, YouTube etc.
I’m not worried about disk space, I’m worried that people complain my large files on Vimeo take too long to load and if I upload to Facebook, the large file size will play back longer at 360p while its still trying to load and catch up to the 1080p stream. My original and Vegas stock render template says 24 max and avg 12 – and my video looks way better, just still to big in file size for online playback… How are these people able to have significantly lower file sizes and I dont see a quality problem?
-
[Derek Charles] “I’m still confused in how I see users with the same camera, same 1080p and have a significantly lower 1080 file size uploaded, with higher quality playback… bitrates for Vimeo, YouTube etc. “
You’re getting to the point where you’re recognising the complex artistry of rendering. You’ve now introduced another observation that needs to be understood: How can others do this? Prerender preparation needs to be considered. Already John has invited you to create a digital intermediary. Doing this has provided me with many opportunities to make sure my video stream is stable enough to go forward to Render and see how much video noise is present. The freebie s/w BitRate viewer has helped me to understand just where high “noise” areas appear and need further attention. Video noise is a real pain, and can eat up and effect bitrate efficiency. I use the NeatVideo product to smooth out video noise and get my video into a sweet-spot for stable bitrate rendering.
From my own experience, with video and render options that are on the edge or tipping point of size versus quality, there will be no simple, easy-fix for this. It’s good you’re now comparing others quality output. However and until you can directly quizz those that have done the quality you’re seeing, we can only guess. Do recognise that the “Industry” spend millions on developing rendering quality. They employ Render farms and many many hours of offline methods to get great product. Each and every second of capture to Edit are crawled-over to wrangle-in the noise and macro-blocking Monster!
Although my own rendering experience is limited to DVD, MP4, WMP and variations of MOV and digitital intermediaries of Lagarith and SONY MXF, I’m starting to think that you’ve got a combination of initial video noise, grain and the unfortunate effect of the processing of average bitrate of high BitRate. This is now getting into the area of segmented average and constant BitRate preparation.
Interesting thread.
* Grazie
Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge -
Thanks.
I’m starting to understand
– perhaps you can chime in on my issue with Neat Video
in this thread – https://forums.creativecow.net/thread/24/1020140 -
[Derek Charles] “I’m starting to understand”
Good. Derek, you need to be more consistent and forensic with your analysis. I write this stuff down. Leaping all over place will get all of us disconfabulated! Well, me at least. And, yes I did
[Derek Charles] “perhaps you can chime in on my issue with Neat Video in this thread”
where I read a bit more of your wrangling with Mercalli and NeatVideo. I can only garner that your original footage is both wobbly and noisy/grainy? Yes? In which case you’re starting off with a bit more of a problem than just BitRates and streaming – comparing others quality output. I also read there you’re using both Merc and NV chained together. This implies you’re giving the renderer/encoder the maths task of doing both sets of wrangling at the same time? Yes? Well, and in which case, don’t! Do one and then do the other. My preference would be for firstly NV, this’ll get you nicely FLAT images and THEN Mercalli. But, try reversing the order. You’ll soon enough find out.
Derek, we’re starting to understand the pickle you’ve got yourself into. Hopefully you can see it through and be happy with the outcomes. Oh yeah, any chance you can upload a small sample so I can view the issues? At the moment I’m thinking I’m second guessing just what it is we’re up against – yes?
* Grazie
Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge -
Don’t know what happened to my reply…. I’ll try it again:
[Derek Charles] “I’m starting to understand”
Good. Derek, you need to be more consistent and forensic with your analysis. I write this stuff down. Leaping all over the place will get all of us disconfabulated! Well, me at least. And, yes I did
[Derek Charles] “perhaps you can chime in on my issue with Neat Video in this thread”
where I read a bit more of your wrangling with Mercalli and NeatVideo. I can only garner that your original footage is both wobbly and noisy/grainy? Yes? In which case you’re starting off with a bit more of a problem than just BitRates and streaming – comparing others quality output. I also read there you’re using both Merc and NV chained together. This implies you’re giving the renderer/encoder the maths task of doing both sets of wrangling at the same time? Yes? Well, and in which case, don’t! Do one and then do the other. My preference would be for firstly NV, this’ll get you nicely FLAT images and THEN Mercalli. But, try reversing the order. You’ll soon enough find out.
Derek, we’re starting to understand the pickle you’ve got yourself into. Hopefully you can see it through and be happy with the outcomes. Oh yeah, any chance you can upload a small sample so I can view the issues? At the moment I’m thinking I’m second guessing just what it is we’re up against – yes?
* Grazie
Video Content Creator and Potter
PC 7 64-bit 16gb * Intel® Core™i7-2600k Quad Core 3.40GHz * 2GB NVIDIA GEFORCE GTX 560 Ti
Cameras: Canon XF300 + PowerShot SX50HS Bridge
Reply to this Discussion! Login or Sign Up