Project too big ....

Geoff_Wood wrote on 10/29/2014, 5:50 PM
.....just.

DVD 4.7G media, V13 project rendered separate MPG2 and AC3 streams, PAL 720x576, 50i, 16:9, audio 2-chan 192kbps AC3.

Not wanting to re-render in DVDA - is there any way I can delete a small chunk off the end of the project (ie Split/Delete) and burn, or do I have to go back to V13 , delete it there , and re-render (what a pain !) ?

And what's the best way to estimate the end size of a project before rendering from Vegas ?

Late edit - Oh yeah DVDA 5.2

geoff

Comments

PeterDuke wrote on 10/29/2014, 6:53 PM
DVDA is not an editor, so do your trimming in Vegas.

A popular calculator is Mark's Bitrate Calculator
http://www.johncline.com/bitcalc110.zip


By the way, DVDA often over estimates the size of the DVD it is about to create. If you think it should fit, create a folder only, and then check its size. Look at the actual bytes to see if it is under 4,700,000 bytes and not use the size quoted by Windows in KB, MB or GB because these are kibibytes etc., not kilobytes, etc.
EricLNZ wrote on 10/29/2014, 8:13 PM
Geoff, you can trim off the beginning or end of a compliant video without causing recompression. Double click the thumbnail to open it in the Timeline pane and move the yellow flags. I occasionally have to do it when compiling DVDs with other people's files that contain too much black at beginning or end.
Geoff_Wood wrote on 10/29/2014, 11:15 PM
Tried that.

It seems to change the amount playable on the resultant DVD, but not the total data size written to the disc.

... which is a pity. Sure, reducing the source media is an 'editing' function, but such a feature you would think would be trivial to implement . Or maybe not ?

geoff
TOG62 wrote on 10/30/2014, 2:23 AM
The easiest solution is to render to a folder, ignoring the warning that it's too big. Then open the VIDEO_ts folder in DVDShrink and allow it to automatically reduce the size to fit a DVD.

The process is fairly quick and painless an will allow you to keep all the content.
Geoff_Wood wrote on 10/30/2014, 3:26 AM
I want to avoid re-encoding, which DVD-Shrink does, or DVDA does if you tell it to.

geoff
Jack S wrote on 10/30/2014, 12:54 PM
If your project, when created to a HDD folder, is marginally bigger than can be fitted onto a DVD, DVD Shrink will create a standard size DVD folder with no noticeable degradation. Before embarking on Blu-Ray I used DVD Shrink whenever my projects were too big. Try it. You'll be surprised at the resulting quality.

My system
Genshin Infinity Gaming PC
Motherboard Gigabyte H610M H: m-ATX w/, USB 3.2, 1 x M.2
Power Supply Corsair RM750X
Intel Core i7-13700K - 16-Core [8P @ 3.4GHz-5.4GHz / 8E @ 2.50GHz-4.20GHz]
30MB Cache + UHD Graphics, Ultimate OC Compatible
Case Fan 4 x CyberPowerPC Hyperloop 120mm ARGB & PWM Fan Kit
CPU Fan CyberPowerPC Master Liquid LITE 360 ARGB AIO Liquid Cooler, Ultimate OC Compatible
Memory 32GB (2 x 16GB) DDR5/5200MHz Corsair Vengeance RGB
MSI GeForce RTX 4060 Ti 8GB - Ray Tracing Technology, DX12, VR Ready, HDMI, DP
System drive 1TB WD Black SN770 M.2 NVMe PCIe SSD - 5150MB/s Read & 4900MB/s Write
Storage 2 x 2TB Seagate BarraCuda SATA-III 6.0Gb/s 7200RPM
Windows 11 Home (x64)
Monitors
Generic Monitor (PHL 222V8) connected to GeForce RTX 4060 Ti
Generic Monitor (SAMSUNG) connected to iGPU

Camcorder
SONY Handycam HDR-XR550VE

Geoff_Wood wrote on 10/30/2014, 4:09 PM
How can it do that - a better encoding algorithm than anybody else has been able to achieve ?

I'll give it a try then !

geoff
Arthur.S wrote on 10/30/2014, 5:08 PM
From memory, DVD Shrink doesn't re-encode, it compresses. Can anyone confirm?
Chienworks wrote on 10/30/2014, 5:28 PM
The impression i got from the description a few people in here have given is that it's smart enough to find wasted space in the MPEG2 encoding that isn't necessary, and copy only what is necessary. Sounds a bit like voodoo to me. I can't imagine any decent MPEG2 encoder putting much wasted space in the output file.

In any case, if the needed reduction is more than a few percent, it will decode and re-encode, which will be an additional compression process.

That being said, i've seen stuff 'shrunk' with it, and it is pretty impressive.

Geoff, regarding trimming in DVDA, you are correct in that all it does is restrict the playable portion of the file. Then entire file, including the trimmed off portions are still physically burned to the disc.
Chienworks wrote on 10/30/2014, 5:32 PM
For estimating project size i've never gone wrong using the formula 600 / minutes - audio bandwidth.

For example, if i have an 85 minute project, 600 / 85 = 7.059. Subtract about 0.192 for my usual audio template of 192Kbps = 6.867ish. Encode at an average bitrate of 6,866,823 and it'll fit. I usually subtract an additional 1% or so for space for menus and wiggle room, but when i do that i always end up with an image that occupies 99% of the disc, so i'm just being paranoid.

Never pay attention to any numbers that DVDA shows on the screen.
Steve Mann wrote on 10/30/2014, 8:52 PM
With VBR, It's impossible to estimate the compressed file size without compressing the video. This is because the compression is a moving target. Scenes with little motion will compress easily, and scenes with a lot of motion and changing background need a lot more compression.

If your VIDEO_TS folder in Windows is 4.3Gb (as reported by Windows Explorer) or less, then it's fine to burn your DVD.
Chienworks wrote on 10/30/2014, 9:16 PM
Steve, that's why the compressors offer a 2-pass option. That does allow an accurate estimate. Using 2-pass i've never had a final render be more than a 10th of a percent different from the estimated size.
Steve Mann wrote on 10/30/2014, 10:29 PM
The render as 2-pass option still doesn't know what your video contains. A one-hour talking head interview or panel presentation will render a smaller MPEG file than a one-hour sports video with lots of pans and changing backgrounds.
EricLNZ wrote on 10/30/2014, 11:34 PM
The render as 2-pass option still doesn't know what your video contains.

But surely after the first pass it does so on the second pass it uses up every bit giving you the same file size as if you'd used CBR?
Chienworks wrote on 10/30/2014, 11:49 PM
[i]"The render as 2-pass option still doesn't know what your video contains."[/]

That is exactly the point of a 2-pass render. Vegas experiments with the contents of the video on the first pass, seeing what it can compress by how much. Then when the second pass starts, it does know what the video contains.
johnmeyer wrote on 11/7/2014, 6:15 PM
I want to avoid re-encoding, which DVD-Shrink does, or DVDA does if you tell it to.There are several slightly incorrect statements about DVD Shrink in this thread.

While it is true that DVD Shrink does not re-encode, it DOES change and degrade the video. The guy who actually wrote DVD Shrink provided a detailed explanation of how it worked, over a decade ago. The original post no longer exists, but it is quoted here:

DVD Shrink Explained

The key paragraph from the long, but excellent explanation:

DVD Shrink achieves compression by removing some of the residual data. This process is called requantization. Selected DCT coefficients are scaled down (thus reducing the number of bits required to store them) and a corresponding scale value for these coefficients (quantizer scale) is scaled up. The result is a less accurate description of the same residual data, which takes up less space. Note motion vectors are left unmodified by this process."



Arthur.S wrote on 11/9/2014, 7:04 AM
Incredibly clever programme. I still use it now and again. Haven't come across anything to beat it - paid or free.