1. Voukoder Pro
  2. Forum
    1. Unresolved Threads
  3. Documentation
  4. Downloads
  5. License
  • Login
  • Register
  • Search
This Thread
  • Everywhere
  • This Thread
  • This Forum
  • Pages
  • Forum
  • More Options
  1. Voukoder Pro
  2. Forum
  3. Voukoder Pro
  4. General

Dynamic file naming

  • Joe24
  • September 5, 2023 at 11:01 AM
1st Official Post
  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • September 5, 2023 at 11:01 AM
    • #1

    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.

    Edited 13 times, last by Joe24 (September 5, 2023 at 11:33 AM).

  • Vouk
    Administrator
    Reactions Received
    601
    Posts
    2,888
    • September 5, 2023 at 3:41 PM
    • Official Post
    • #2

    Yes, this will come soon!

    • Next Official Post
  • Vouk
    Administrator
    Reactions Received
    601
    Posts
    2,888
    • September 7, 2023 at 4:43 PM
    • Official Post
    • #3

    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
    • Previous Official Post
    • Next Official Post
  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • September 7, 2023 at 7:34 PM
    • #4

    Success! Rendered all regions with multiple output files per region using version 0.7.3. Thanks! 8)

    Edited 2 times, last by Joe24 (September 7, 2023 at 7:41 PM).

  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • September 9, 2023 at 5:48 PM
    • #5

    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.

    Edited once, last by Joe24 (September 9, 2023 at 7:44 PM).

  • Vouk
    Administrator
    Reactions Received
    601
    Posts
    2,888
    • September 10, 2023 at 6:53 PM
    • Official Post
    • #6

    Yes, I fixed this in the next version so $(OutputFileName) does not contain the extension anymore.

    Edit: This is fixed in 0.7.4.

    • Previous Official Post
    • Next Official Post
  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • September 15, 2023 at 8:29 AM
    • #7

    Confirmed working. Thanks!

  • Vouk
    Administrator
    Reactions Received
    601
    Posts
    2,888
    • September 16, 2023 at 10:26 AM
    • Official Post
    • #8

    Improved this a bit more.

    • Previous Official Post
    • Next Official Post
  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • September 16, 2023 at 10:58 AM
    • #9

    Excellent!

    Edited 2 times, last by Joe24 (September 16, 2023 at 11:43 AM).

  • Vouk
    Administrator
    Reactions Received
    601
    Posts
    2,888
    • September 19, 2023 at 6:42 PM
    • Official Post
    • #10

    Okay, I improved it even more. You can now even execute JavaScript in the file name using

    ${...}

    So you'll have all the freedom you want for dynamizing your filename.

    • Previous Official Post
    • Next Official Post
  • KillerHT
    Beginner
    Posts
    1
    • February 15, 2024 at 6:22 PM
    • #11

    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?

    Edited 2 times, last by KillerHT (February 16, 2024 at 5:13 PM).

  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • July 9, 2024 at 1:28 AM
    • #12

    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.

    Edited 7 times, last by Joe24 (July 10, 2024 at 12:56 AM).

  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • July 31, 2024 at 6:38 AM
    • #13

    This has been fixed. File and path variables are now working in VoukoderPro v1.3.0.0.

    Edited once, last by Joe24 (August 10, 2024 at 4:36 PM).

  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • January 26, 2025 at 6:33 AM
    • #14

    This appears to be broken again in VoPro v2.0.6. I'm getting:

    Code
    2025-01-25 22:29:30 (error)	[OutputNode.cpp:199] Unable to open output: #ERROR\#ERROR - GPU0 - h.265 DL v0.6.mp4

    using ${OutputFile.Path}\${OutputFile.Name} - GPU0 - BD v4.9.1.mp4 with the target folder of D:\temp


    UPDATE: Apostrophes (') in the filename cause the error.

    Edited 5 times, last by Joe24 (January 28, 2025 at 6:46 AM).

  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • February 14, 2025 at 8:48 PM
    • #15

    Apostrophe glitch remains in v2.0.7.

  • Joe24
    Intermediate
    Reactions Received
    14
    Posts
    222
    • March 7, 2025 at 11:15 PM
    • #16

    Still a problem in v2.1.0.

  • Vouk
    Administrator
    Reactions Received
    601
    Posts
    2,888
    • June 30, 2025 at 12:31 PM
    • Official Post
    • #17

    It has been fixed in the Voukoder Pro 3 version.

    • Previous Official Post

Users Viewing This Thread

  • 1 Guest
  1. Privacy Policy
  2. Legal Notice
Powered by WoltLab Suite™ 6.1.11