Batch Converter: bug or FR?

JRTaylorMusic · 01-10-2022, 11:23 AM

I've added a few tracks across eight projects (open in tabs).
I'm using the wildcards $title/$track expecting them to export into folders corresponding to their respective project title (from Project Settings: Notes), however when I click Start Convert they are all exported to the same folder given the Title of whichever project tab is currently active.

I would expect the wildcard data take affect relative to the context whence added instead of at commencement of conversion.

schwa · 01-10-2022, 11:37 AM

Unfortunately the behavior you want isn't supported; once an item is added to the batch converter, it's no longer associated with the project it originated in, and wildcards will be resolved using whatever the active project is when the conversion occurs.

JRTaylorMusic · 01-10-2022, 11:42 AM

Thank you for the clarification! Is it worth a FR or would the complexity outweigh the benefit? I mean, it would be nice, but for me it's not a big deal now that I understand how it works. Thanks again!

schwa · 01-10-2022, 11:52 AM

The post was helpful as there's actually a minor bug in the current wildcard conversion -- the track and item wildcards will be resolved using whatever media item happens to be in the same location in the current project, not the source media item. We'll fix that so at least the $item related wildcards resolve correctly.

For the $track related wildcards, we may be able to support the track number and name for items that came from another project, or maybe not, we'll take a look.

For the $project related wildcards, I think the current behavior will remain, of using the currently active project to resolve them.

faun2500 · 02-09-2022, 05:16 AM

This ties in with my post about $track. Such an important feature!!

01-10-2022, 11:23 AM	#1
JRTaylorMusic Human being with feelings Join Date: Feb 2019 Location: Austin, TX Posts: 436	Batch Converter: bug or FR? I've added a few tracks across eight projects (open in tabs). I'm using the wildcards $title/$track expecting them to export into folders corresponding to their respective project title (from Project Settings: Notes), however when I click Start Convert they are all exported to the same folder given the Title of whichever project tab is currently active. I would expect the wildcard data take affect relative to the context whence added instead of at commencement of conversion.

02-09-2022, 05:16 AM	#5
faun2500 Human being with feelings Join Date: Mar 2010 Location: Worldwide Posts: 1,053	This ties in with my post about $track. Such an important feature!! __________________ newloops.com - Crazy deals on audio samples and sound banks! http://bit.ly/free-sample-packs- Totally Free High Quality Sample Packs

01-10-2022, 11:37 AM	#2
schwa Administrator Join Date: Mar 2007 Location: NY Posts: 16,955	Unfortunately the behavior you want isn't supported; once an item is added to the batch converter, it's no longer associated with the project it originated in, and wildcards will be resolved using whatever the active project is when the conversion occurs.

01-10-2022, 11:42 AM	#3
JRTaylorMusic Human being with feelings Join Date: Feb 2019 Location: Austin, TX Posts: 436	Thank you for the clarification! Is it worth a FR or would the complexity outweigh the benefit? I mean, it would be nice, but for me it's not a big deal now that I understand how it works. Thanks again!

01-10-2022, 11:52 AM	#4
schwa Administrator Join Date: Mar 2007 Location: NY Posts: 16,955	The post was helpful as there's actually a minor bug in the current wildcard conversion -- the track and item wildcards will be resolved using whatever media item happens to be in the same location in the current project, not the source media item. We'll fix that so at least the $item related wildcards resolve correctly. For the $track related wildcards, we may be able to support the track number and name for items that came from another project, or maybe not, we'll take a look. For the $project related wildcards, I think the current behavior will remain, of using the currently active project to resolve them.