Proxy video creation in VP12

Kommentare

megabit schrieb am 17.11.2012 um 13:36 Uhr
The Proxy Stream 1.5e that Willem has linked us to, does NOT seem to work properly in VP12.

After rendering the first clip in the queue, its stops with the error message saying something to the effect that the resultanf proxy file cannot be accessed. Of course, the rendered file is present where supposed to, and in good condition, too.

So, to all that do Vegas scripting, a kind request:

1. Could you please check what's wrong with the script?

2. Could anyone attempt to leverage the script functionality by adding automatic selection of all files, present (or selected) in the current project? Right now, each relevant clip in the entire source directory must be selected manually.

Of course, ask for doing this much work I'd never dare, were it not in the interest of the entire Vegas community here. Not to mention that such an improved script could become a payable asset (I'm sure many would pay if the price is right).

Piotr

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

altarvic schrieb am 17.11.2012 um 14:03 Uhr
Vegasaur contains Proxy Media Builder, but it is not free
Satevis schrieb am 17.11.2012 um 14:18 Uhr
Exactly. The nominal frame rate people see in Media Info or other tools is quite meaningless in this scenario, which brings us full circle to my first post in this thread.
Ehemaliger User schrieb am 17.11.2012 um 16:04 Uhr
Megabit,

in Proxy Stream there is an option to select all files in a folder by checking the file extensions that you want included.

Dave T2
megabit schrieb am 17.11.2012 um 16:20 Uhr
Yes - but auto-selection of media in the current project would be even better :)

Piotr

AMD TR 2990WX CPU | MSI X399 CARBON AC | 64GB RAM@XMP2933  | 2x RTX 2080Ti GPU | 4x 3TB WD Black RAID0 media drive | 3x 1TB NVMe RAID0 cache drive | SSD SATA system drive | AX1600i PSU | Decklink 12G Extreme | Samsung UHD reference monitor (calibrated)

farss schrieb am 17.11.2012 um 16:38 Uhr
"The nominal frame rate people see in Media Info or other tools is quite meaningless in this scenario, which brings us full circle to my first post in this thread."

Not at all. It brings us to the point that it is largely meaningless in any scenario, that there is no purpose served in having it at 23.976 when that is not the matching source frame rate and forcing reference to the source frame rate does nothing other than add complexity.

Bob.