 |
|
|
02-06-2022, 03:48 AM
|
#1
|
Human being with feelings
Join Date: Mar 2010
Location: Worldwide
Posts: 1,053
|
Batch File - $track doesn't work? (FIXED)
In the Batch File converter, I usually use the $track wildcard to name the processed files. However, for some reason, it is not getting the full track names.
Can anyone check this? I'm on the latest version.
|
|
|
02-06-2022, 07:02 AM
|
#2
|
Human being with feelings
Join Date: May 2017
Posts: 2,971
|
Seems reasonable to me. Batch works on a subdirectory, not a track. Look for a different wildcard, something like $filename.
|
|
|
02-06-2022, 07:04 AM
|
#3
|
Human being with feelings
Join Date: Mar 2010
Location: Worldwide
Posts: 1,053
|
Quote:
Originally Posted by Philbo King
Seems reasonable to me. Batch works on a subdirectory, not a track. Look for a different wildcard, something like $filename.
|
No, all the items are ON TRACKS. $track always worked. Are you able to test this?
|
|
|
02-06-2022, 08:00 AM
|
#4
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 14,239
|
It was actually sort of a bug that this ever worked, as it's easy to add media items to the converter and then either edit the project or close the project and open another one, in which case the $track wildcard would resolve to the wrong thing. The batch converter makes a copy of the media item, so it's no longer associated with the project it originated it. There's no straightforward way for the batch converter to be able to resolve the $track or $tracknumber wildcards.
[edit] see https://forum.cockos.com/showthread.php?t=261724
Last edited by schwa; 02-06-2022 at 08:08 AM.
|
|
|
02-06-2022, 08:23 AM
|
#5
|
Human being with feelings
Join Date: Mar 2010
Location: Worldwide
Posts: 1,053
|
Quote:
Originally Posted by schwa
It was actually sort of a bug that this ever worked, as it's easy to add media items to the converter and then either edit the project or close the project and open another one, in which case the $track wildcard would resolve to the wrong thing. The batch converter makes a copy of the media item, so it's no longer associated with the project it originated it. There's no straightforward way for the batch converter to be able to resolve the $track or $tracknumber wildcards.
[edit] see https://forum.cockos.com/showthread.php?t=261724
|
Ah what! That's a shame, as it's worked perfectly like this for years. So what is the point in having this wildcard then?
|
|
|
02-06-2022, 08:35 AM
|
#6
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 14,239
|
The $track and $tracknumber wildcards work fine when rendering, adding metadata to a rendered file, creating a file during recording, or consolidating. It's only in the batch converter context that there is no connection between the convert file list and any specific project.
We could store the track name with the media item when it's added to the batch converter, which would give the expected result most of the time, but could give unexpected results if you add a media item to the batch converter and then edit the project. But i'm not sure if working right most of the time is better than not being supported at all.
Last edited by schwa; 02-06-2022 at 08:40 AM.
|
|
|
02-06-2022, 08:44 AM
|
#7
|
Human being with feelings
Join Date: Mar 2010
Location: Worldwide
Posts: 1,053
|
Quote:
Originally Posted by schwa
The $track and $tracknumber wildcards work fine when rendering, adding metadata to a rendered file, creating a file during recording, or consolidating. It's only in the batch converter context that there is no connection between the convert file list and any specific project.
We could store the track name with the media item when it's added to the batch converter, which would give the expected result most of the time, but could give unexpected results if you add a media item to the batch converter and then edit the project. But i'm not sure if working right most of the time is better than not being supported at all.
|
OK thanks, I'll look into some more. Cheers.
|
|
|
02-09-2022, 03:08 AM
|
#8
|
Human being with feelings
Join Date: Mar 2010
Location: Worldwide
Posts: 1,053
|
Quote:
Originally Posted by schwa
The $track and $tracknumber wildcards work fine when rendering, adding metadata to a rendered file, creating a file during recording, or consolidating. It's only in the batch converter context that there is no connection between the convert file list and any specific project.
We could store the track name with the media item when it's added to the batch converter, which would give the expected result most of the time, but could give unexpected results if you add a media item to the batch converter and then edit the project. But i'm not sure if working right most of the time is better than not being supported at all.
|
Actually, just coming back to this. I have to say that changing the way this works has a big negative effect for me personally. I only ever use batch process in one project, so removing the ability to get the names from the tracks has basically broken it.  Surely I can't be the only person that this affects??
I've tried to find an action to set the item names from tracks, but I can't find that.
Can't you just put this feature back to #track? I really can't see the benefit of removing it.
|
|
|
02-09-2022, 04:48 AM
|
#9
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 14,239
|
This was changed because the previous incorrect behavior was negatively affecting users, as reported here: https://forum.cockos.com/showthread.php?t=261724
The next release (not 6.47, but the one after) will resolve the $track, $tracknumber, and $itemnumber wildcards in the batch converter to whatever the state of the project was when the media item was added. That will probably be fine, since the media item itself gets rendered in whatever state the project was when the media item was added.
In other words, if you add a media item to the batch converter and then edit the item in the project and change the track name afterwards, those edits won't affect the converted file.
|
|
|
02-09-2022, 05:15 AM
|
#10
|
Human being with feelings
Join Date: Mar 2010
Location: Worldwide
Posts: 1,053
|
Quote:
Originally Posted by schwa
This was changed because the previous incorrect behavior was negatively affecting users, as reported here: https://forum.cockos.com/showthread.php?t=261724
The next release (not 6.47, but the one after) will resolve the $track, $tracknumber, and $itemnumber wildcards in the batch converter to whatever the state of the project was when the media item was added. That will probably be fine, since the media item itself gets rendered in whatever state the project was when the media item was added.
In other words, if you add a media item to the batch converter and then edit the item in the project and change the track name afterwards, those edits won't affect the converted file.
|
Ah yes, that sounds like it will sort it out. Will there be a beta of this release. I really need it asap.  Thanks.
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 01:57 AM.
|