Stop Adding Enscape/Date in Batch Render File Names.

  • It's a huge waste of time to delete Enscape / Dates in the batch render file names one by one when the render files are linked to InDeisgn / Photoshop. . I will be glad if I just missed an option to turn that off.


    If not, could you please add an option to batch render and make the file names only as the scene name.

  • L.S I wrote an AutoHotkey script that strips off the date/time info from the filenames and replaces it with a selected project name, it also saves the rendered png’s to the selected project folder in both hires jpg’s and emailable size jpg’s.

    I’m sure I had a post here about it, I’ll see if I can find/link to it.


    Here we are, no one seemed interested in it so I never followed up RE: Batch render view and file name

  • I agree. I HATE that it auto inserts Enscape into the name. Renders are typically for clients. They don't care the render software used and it's the wrong place for enscape to be advertising itself. If it's going to auto-name then it should use the name of the project itself. I'm ok with the date format though.

  • Thanks L.S , while this is currently not possible, I have forwarded your inquiry as a feature request accordingly - We appreciate the input.

    Demian Gutberlet

    Is it complicated to make the batch file name as _"file name"+"scene name"_ only? Any chance this could be implemented any time soon?Or Enscape team made a decision that it has to have Enscape name in batch file name?


    Paul Russam

    Thank you. Would you mind sharing your script, please?

  • You can't just name the file that by scene and/or file name only because not everyone renders by scene and it doesn't factor duplicated or multiple renders of the same scene. To be clear it's not hard to code for it (by having incrementing numbers and/or auto-checking if that file name exists prior to rendering) but the easiest way (for the programmers) is to have the timestamp somewhere in the name since it's always going to be unique. It doesn't and shouldn't start with enscape though. They already give you the option when exporting to exe to name and brand toward the client (or renderer). The file name should maybe go along with that variable already offered.


    If anyone is interested, I can whip up a microsoft powershell script along the lines of the authotkey script mentioned above or I can make something similar but different. Also, windows natively will allow auto renaming multiple files and will simply increment them up by number... just select all and rename - then fill in the name you want and it will add a number at the end. It's simply that this is a wasted step (and therefore time when typically in a rush) because enscape hasnt fixed this part yet.

  • jlo WPS would be a better solution than AHK as it’s already built into Windows.

    I’ll put a zip of what I’ve done with AKH here and if you want to create it’s WPS equivalent I’d probably abandon my version for it.


    I’ll post it later when I’m at the office.

  • AutoHotKey script attached

    !! DO NOT USE IT UNLESS YOU'RE FAMILIAR WITH SCRIPTING !!


    Reqd:

    AutoHotKey

    ImageMagik (used to make the jpg versions)


    Assumptions:

    I render everything to one specific folder which I then use as a source for the AHK script

    I render at 4000x3000 png

    I batch render

    All my projects are in folders with identical name structures - nnn-project name

    All my project folders are in a common 'projects' folder

  • It's a huge waste of time to delete Enscape / Dates in the batch render file names one by one when the render files are linked to InDeisgn / Photoshop. . I will be glad if I just missed an option to turn that off.


    If not, could you please add an option to batch render and make the file names only as the scene name.

    For this very reason I don't use the batch feature. Having no control or overwrite over the file naming convention makes the batch feature unproductive.
    I do Post Process on every render and I use Photoshop's link feature to make the process somewhat nondestructive. Due to a auto generated file naming convention Enscape uses I find zero value in it as I would have to manually edit the file names to maintain the established links. This is fine for one or two renders but not 10-15

    A perfect and very simple solution is adopt the camera/scene name. This is what also every professional dds/render engine software does. Do this and the Batch function will have far more value to users.

  • You can't just name the file that by scene and/or file name only because not everyone renders by scene and it doesn't factor duplicated or multiple renders of the same scene. To be clear it's not hard to code for it (by having incrementing numbers and/or auto-checking if that file name exists prior to rendering) but the easiest way (for the programmers) is to have the timestamp somewhere in the name since it's always going to be unique. It doesn't and shouldn't start with enscape though. They already give you the option when exporting to exe to name and brand toward the client (or renderer). The file name should maybe go along with that variable already offered.


    If anyone is interested, I can whip up a microsoft powershell script along the lines of the authotkey script mentioned above or I can make something similar but different. Also, windows natively will allow auto renaming multiple files and will simply increment them up by number... just select all and rename - then fill in the name you want and it will add a number at the end. It's simply that this is a wasted step (and therefore time when typically in a rush) because enscape hasnt fixed this part yet.

    Thank you very much, jlo. It will be very helpful to have a properly functioning batch file saving feature. Unfortunate that a user has to create a script, not Enscape.

  • For this very reason I don't use the batch feature. Having no control or overwrite over the file naming convention makes the batch feature unproductive.
    I do Post Process on every render and I use Photoshop's link feature to make the process somewhat nondestructive. Due to a auto generated file naming convention Enscape uses I find zero value in it as I would have to manually edit the file names to maintain the established links. This is fine for one or two renders but not 10-15

    A perfect and very simple solution is adopt the camera/scene name. This is what also every professional dds/render engine software does. Do this and the Batch function will have far more value to users.

    It frustrates me so much every single time. I also have renders linked to InDesign / Photoshop. It's so much easier to just copy the file in an archive folder, then rewrite new renders with the same name so that linking stays the same.

  • For this very reason I don't use the batch feature. Having no control or overwrite over the file naming convention makes the batch feature unproductive.
    I do Post Process on every render and I use Photoshop's link feature to make the process somewhat nondestructive. Due to a auto generated file naming convention Enscape uses I find zero value in it as I would have to manually edit the file names to maintain the established links. This is fine for one or two renders but not 10-15

    A perfect and very simple solution is adopt the camera/scene name. This is what also every professional dds/render engine software does. Do this and the Batch function will have far more value to users.

    +1000

  • Quote

    jtubb as I would have to manually edit the file names to maintain the established links.

    that’s what my AHK script does, it creates a dated folder in the project folder and copies the renamed renders into it. Assuming the scene name hasn’t changed, the filename for any particular scene will be the same in each batch or renders.

  • that’s what my AHK script does, it creates a dated folder in the project folder and copies the renamed renders into it. Assuming the scene name hasn’t changed, the filename for any particular scene will be the same in each batch or renders.

    I'll have to take a look. If it works well, Enscape Devs take a look as well this are the things we need.

  • I agree. I HATE that it auto inserts Enscape into the name. Renders are typically for clients. They don't care the render software used and it's the wrong place for enscape to be advertising itself. If it's going to auto-name then it should use the name of the project itself. I'm ok with the date format though.

    Would it be too much to ask to allow users to set a project name instead of "Enscape"? I would like that very much.


    I use a photo viewer app (FastStone) to batch rename/resize/convert to jpg after I complete a set of renderings. (I always export to PNG & double resolution before I save as high quality jpg.)

  • L.S , I've had a chat with PM accordingly, and want to share the good news immediately:


    We've decided based on your Feedback and internal discussions to indeed implement a way to easily replace the name "Enscape" in batch exported render file names. This feature will present options to instead select the project name, company name, or simply a name of your choice instead. We're of course still fine-tuning the plans behind this function so there may be even more options available as well.


    Overall this is something we plan to add with 3.4, or if time and development resources allow for it perhaps even 3.3 (Or a preview prior). No specific promises I can make yet besides that this will be surely added! Thank you all very much for the input again. :)