Dynamic file naming

  • Output-file naming is a problem in VoukoderPro. To date, including the current version (0.7.2.8), file naming choices are: either completely custom, or completely set by the NLE.

    For one thing, if you manually set the file name in your VoPro Scene, this makes it super easy (barely an inconvenience) to accidentally overwrite a previous render, because all output files encoded with that Scene will have the same name.

    If you're using VoPro to encode multiple formats from the same NLE render, you cannot use the NLE-supplied name because then all your output files are simultaneously attempting to have the same name. Chaos ensues (although VoPro now has a lockout in this situation and will refuse to encode at all).

    Further, if you are using the Render Regions function in Vegas, each rendered region file will overwrite the previous one. If you rendered 3 regions, you'd be left with only a single video file which would contain the last region rendered. The first 2 regions will be lost, overwritten.

    Would be nice to see some rule-based dynamic naming functions. For instance:

    • Perhaps a function for simple sequential naming. I.E., if "00000.mp4" exists, name output "00001.mp4". Or an unconditional master counter, like the log file naming system.
    • Suffix-based naming with wildcards, based on the filename supplied by the NLE. I.E., NLE filename: "Lost in the Woods.mp4", VoPro options: "%NLEfilename - %VoProScene - %seq.mp4", VoPro output filenames would be something like: "Lost in the Woods - Monochrome 8K - 00000.mp4" and "Lost in the Woods - 192 kbps ABR - 00000.mp3".
    • Date- and time-based names.

    13 Mal editiert, zuletzt von Joe24 (5. September 2023 um 11:33)

    • Offizieller Beitrag

    Please check out version 0.7.3.

    Supporting these variables in the file name:

    VariableDescriptionExample
    $(OutputAbsoluteFileName)Absolute full file namec:\users\daniel\Desktop\videos\ExampleVideo.mp4
    $(OutputFilePath)File pathc:\users\daniel\Desktop\videos
    $(OutputFileName)File name (w/o extension)ExampleVideo
    $(OutputFileExtension)File extension.mp4
    $(Year)Current year2023
    $(Month)Current month11
    $(Day)Current day21
    $(Hours)Current hours17
    $(Minutes)Current minutes31
    $(Seconds)Current seconds59
  • Is $(OutputFileName) supposed to include the filename extension? It currently does, as seen in above screenshots. Only reason I ask: there is a separate $(OutputFileExtension) variable.

    Einmal editiert, zuletzt von Joe24 (9. September 2023 um 19:44)

  • hello, if I write ${OutputFile.Absolute} OR ${OutputFile.Path}

    I give the error, why?

    folder "videos" in desktop alreary created by me.

    VoukoderPro-1.0.0 & Resolve 18.6

    ${OutputFile.Name} and extension works fine.


    And is there any possibility to specify a relative path - where the source is?

    2 Mal editiert, zuletzt von KillerHT (16. Februar 2024 um 17:13)

  • Yes, this is currently broken in all VoukoderPro release versions to date (v1.0.0 through v1.2.5). Seems to be a path-parsing error.

    Using ${OutputFile.Path}\${OutputFile.Name} - GPU0 - BD v4.9.mp4 with the target D:\temp\channel 1\bike_5sec.voukoderpro gives me the following error:

    Code
    2024-07-09 15:30:32 (error)    [OutputNode.cpp:210] Unable to open output: D:    empchannel 1\bike_5sec - GPU0 - BD v4.9.mp4


    So instead of D:\temp\channel 1\bike_5sec - GPU0 - BD v4.9.mp4, the program tries to create a file named D:    empchannel 1\bike_5sec - GPU0 - BD v4.9.mp4.

    7 Mal editiert, zuletzt von Joe24 (10. Juli 2024 um 00:56)