-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
filename output #6
Comments
Hey Benno, thanks! I do hope it's a useful tool in your workflow. When you mention file naming options, are you talking about the Variable List popup button and serial number input? Since version 1.9 these options should both show up just above the Base Path property in the Properties section of the Compositor panel Node tab while any File Output node is selected. It's designed to mimic the same layout as seen in the Output section of the Properties panel Output Properties tab. If they don't show up, something must be breaking somewhere. I'd recommend checking terminal output to see if there are any plugin failure messages (in MacOS you need to first launch Blender from the terminal, I think in Windows you can open a terminal window after application launch). It would help to know what version of Blender you're using as well. I typically only test plugins in the latest public release of Blender, and the minimum version requirement could be outdated (sometimes I catch backwards incompatibilities, sometimes I don't!). If you're talking about replicating the Output tab in the Compositor panel, I can see where that might be useful for single-panel Blender layouts on small screens or similar situations...but it's not something that's in scope for this project. |
Hi John,
Thanks for the quick reply!
I see, but it's not exactly what I meant. What I would love to see is
either an option to add an automated prefix/suffix to file output outputs;)
This can be either in the tab in the image you send or in the preferences
window. This would save having to type/copy the variables in the output
names over and over again (and making mistakes). So it would be nice if all
you'd have to do is type ALPHA or MIST in the output list.
[image: image.png]
Kind regards Met vriendelijke groet,
Benno Bas
*www.bennobas.com <http://bennobas.com>*
06 526 70 455
…On Fri, 23 Jun 2023 at 17:12, John Einselen VF ***@***.***> wrote:
Hey Benno, thanks! I do hope it's a useful tool in your workflow.
When you mention file naming options, are you talking about the Variable
List popup button and serial number input?
Since version 1.9 these options *should* both show up just above the Base
Path property in the Properties section of the Compositor panel Node tab
while any File Output node is selected. It's designed to mimic the same
layout as seen in the Output section of the Properties panel Output
Properties tab.
[image: Screenshot-2023-06-23-at-10 49 03-AM]
<https://user-images.githubusercontent.com/82116640/248303774-b0d79b13-f144-4d66-882e-99732d659a10.jpg>
If they don't show up, something must be breaking somewhere. I'd recommend
checking terminal output to see if there are any plugin failure messages
(in MacOS you need to first launch Blender from the terminal, I think in
Windows you can open a terminal window after application launch). It would
help to know what version of Blender you're using as well. I typically only
test plugins in the latest public release of Blender, and the minimum
version requirement could be outdated (sometimes I catch backwards
incompatibilities, sometimes I don't!).
If you're talking about replicating the Output tab in the Compositor
panel, I can see where that might be useful for single-panel Blender
layouts on small screens or similar situations...but it's not something
that's in scope for this project.
—
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUXRFV4UMINLPIIPSZIMOK3XMWW4NANCNFSM6AAAAAAZRSVPNQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi Benno, Thanks for clarifying! If I understand correctly, you're looking for something that, instead of entering a collection of variables every time like I think there could be some user experience challenges with implementing this (how to indicate that the Blender inputs are being augmented outside of what's visible in the two text fields), and some practical production challenges if it's implemented globally (any change in one production would affect all other productions, and disabling/enabling or installing a new version of the plugin would wipe out all of those settings). I'm afraid it's a little outside the scope of this project for now, but it's an interesting request. Do you think a preset system where you can define your own variable as a collection of other variables would be a potential solution? I know it wouldn't be fully automated, but it'd be partway there. Basically defining a custom string as a collection of other strings; This approach would solve my visibility concerns, since the prefix/suffix variable would be included as part of the text input field, and allow for very flexible usage (completely customisable, and multiple presets if needed). Though the issues with defining presets globally remain...they'd still disappear every time the plugin was disabled/enabled, and any change in one production would affect all other productions. What do you think? All the best, |
Sound good! |
another one that seems really promising but i cant get to work is https://blendermarket.com/products/renderstacknode. Which allows for strings nodes as inputs for filenames. |
I'll consider adding a presets system, hopefully in a way that integrates nicely with existing systems. Full disclosure; if I figure out an approach I think works well, it's going to be a while before I can get to it. Thanks for the input! |
Yes no rush! I'm already really happy with your addon |
Hi!
Great addon! been looking for an addon like this for a while!
If I could make one request is that i would like to see the file naming options in de side tab of the compositor just like in the output properties tab.
Kind regards,
Benno
The text was updated successfully, but these errors were encountered: