Export naming for versions
Answered
Iam noticing a bug with when exporting image versions. The naming module does not add the "Filename Number Suffix" to versioned images, only work normally for original images.
I noticed this bug from the very first time I use ON1 (Oct2022), now opened ticket #349882
-
We are just users here, you have to report bugs to ON1 support. You can open a ticket at this link and you should attach your examples to it.
0 -
Yes, I understand that and I did, Iam just looking for some one that had the same issue and have some user side solution to remediate it at the time we wait for bug be fixes. I have a lot of work to do and I cant wait days to get answered and weeks to get bug fixed.
If no user have the temp fix or cant help, great, but I tried and thats the way I need that rush support.
Thats the reason I open a ticket and post here waiting for some user/user solution and help like Brian does. Thanks
0 -
This is working properly for me on a Mac M1 mini.
Here are the settings I used:
-1 -
Thanks Brian, but if you set as mine, how it results? Be aware that only happens when name the versiones images not the originals
I have prefix "MrTech-" followed by token "Filename Number Sufix"
I think is a sofware bug because I tried the same after many ON1 reinstall including trying in another computers and same happens to me
0 -
That was my bad, sorry. I set up my export settings wrong. Yes, I get the same results and now that I think about it that is exactly what I would expect. Don't forget that the virtual image doesn't actually exist so it has no filename of its own and therefore no filename number.
I would still report this to support. How to submit a problem to ON1 Tech Support
0 -
Right, but I do expect the name also be virtualized so I can export the same original filename but with v1, v2, v3 and so on at the end.
That is what I logically expected
0 -
It may be what you expected but it isn't how the program works.
I've already told you to report this to support. See what they say. What else do you want me to do?
-1 -
That no make sense to me, No worry about ticked, that was the first thing I did. Let see what happens
Thanks anyway
0 -
I use ON1 intensively and I was very confident this reported issue is a software bug.
ON1 development team recognize this as a bug and is at bug bucket to be solved.
0 -
Thanks for the update.
0 -
Despite what has been posted here, per yet another email string trying to get this fixed last week - ON1 isn't planning on addressing this issue unless the RAW Project post https://www.on1.com/products/photo-raw/ideas/idea/include-version-in-export-naming/ gets voted up enough...
This has been a huge turn off for me since I reported it to tech support right when 2023 came out, they confirmed and over a month later pushed it to the RAW project where it was confirmed a bug so nobody has had any thought confirmed bugs needed to be voted up...0 -
I hope them fix it on next version 2024
0 -
A year after the bug being confirmed and being told it was being addressed then, to now be told it still exists in the next version and if it ever gets fixed you'll have to pay to get it isn't giving me any faith in future software reliability or reason to give customer loyalty let alone recommend to students or peers. If you can't keep up with bug fixes before releasing next major versions then you're really just forcing a subscription model. Aside from the vast majority of the software industry making continued patching a standard Affinity & Capture One (leading adobe alternatives) have both committed to this practice. The entire file naming and batch export features are utterly useless when a bug just forces every single file to be named the same anyway and every single image version must be exported one by one and manually renamed before moving to the next.
0
Please sign in to leave a comment.
Comments
13 comments