-
Pro 13 – curious bug on rewriting a rendered file of same name
This is a curious one. This is a piece of the directory I use for videos, input and output files, sorted in date/time order, most recent at the bottom. The bottom one was indeed rendered late last night.
https://peter-ftp.co.uk/screenshots/2016-08-26_152133.jpg
I rendered the shaded file on 8/8/2016 so the above stamp is about right for that render.
This morning I re-rendered it, overwriting with a file of the same name. Vegas asked for a confirmation of the existing file.
But look at the above date. It is not today’s. The time looks about right but the date is yesterday’s.
What this look like is that Vegas sometimes does what most accounting software does intentionally: pick up the system (computer) date when it is started and not change it afterwards as it rolls over at midnight. Accounting people like that because they can spend e.g. several days entering transactions which all apply to a given (single) day. Also accounting software allows you to manually set the program date to (within limits) anything you specify. But I doubt Vegas is doing this intentionally. I reckon it happens if you overwrite a file of the same name.
Win7-64, Pro 13, latest version. This issue is 100% repeatable.
The other thing I noticed is that a “rewrite” of the output file doesn’t change its size as displayed in Windows Explorer. So if e.g. you are trying to get a 5.2GB file just below 5GB (for Vimeo upload) by reducing the bit rate a bit, you don’t see the change unless you delete the file and then render it. I don’t know how Pro 13 achieves this… I know (from old DOS programming days) that you can rewrite an existing file and truncate it. And I am not confusing 1000 megabytes with a gigabyte, etc 🙂