Button to batch change tracks.

MusicMan81

hello @peter , here’s an idea.

Can you add a “keyword” to use when you batch edit a song to multiple songs? Example

Apply the same changes to all songs tracks that contains the keyword ”click track”, so we can just put the name “Click track, color, bus routing etc..”.

I feel a little restrictive when the parameter that we can choose is “apply this changes to all songs that contains 12 tracks…. Because not all songs have the same amount of instruments, but in my case I name every track “Click track - Name of Song” so the change can be applied to all tracks in every song that contains the keyword “click track” so no matter if the song has 12 or 20 tracks it can be applied to the desire tracks using the keyword I want….

I hope I explained myself…

AnthonyB

MusicMan81 I think I had a similar sentiment when I saw the feature, along with trepidation around the fact that "apply to similar" didn't give me any control, I don't know what the matching logic is, and there doesn't appear to be a way to roll back if it gets it wrong. As a result, I want to use it, but probably won't.... yet.

I am extremely diligent and generally consistent in laying out:

What 'function' each track 'does', i.e. Track 1 is always Backing Tracks, Track 2 is always Clicks & Cues, Track 3 is always Guide Vocal. Equally, not every song in my collection has a Track 3. Some might even start getting a track 4 as I add in an additional guitar track. So there will be track inconsistency.
The audio file name always contains the 'function', i.e. Backing Track file name always has the word 'Music' immediately followed by a tempo (e.g. (t=120)), Click and Cues file name always contains the word 'Click&Cues' immediately followed by a tempo (e.g. (t=120))

So rather than relying on some fuzzy logic that I don't understand (yet. It's not like we've given Peter time to explain it!), and can't control, I would rather see a batch change engine where I have some control over words/phrases that are matched, and/or the Track number(s) the operation is applied to, etc.

I know this is the first iteration, so we are jumping ahead of things a bit. Definitely not having a crack at this, more a case of excited to see it and want to see some additional functionality before I risk using it.

I've used a lot of these types of 'mass batch processing' type tools in my IT life, and I also like to see a tool that at least shows an example of how your input will be processed on screen (this might not be practical on an iOS device). As I'm a little paranoid about irreversible operations, I'd even go as far as liking to see a 'test run' feature that spits out a log file of what would be 'operated on' and what the before and after would look like so I check check and validate before hitting 'Go'.

Now, I also appreciate that getting track naming wrong is not a 'destructive' process, and doesn't stop me using ST and playing my songs. It is really just mislabeling something which is not the end of the world. So, yes, I get it, I'm being overly paranoid and conservative.