SWS Resources Problem

[kailuamusicschool]

Im trying to use the SWS track template load and save system and it is making weird problems when there is a folder involved. When I go to update the tracks it adds several folder sublevels

[Jeffos]

yes, it is normal the "auto-fill" (top left button) will scan sub-folders, sub-sub-folders, etc.. => if the folder is a leaf, just change the current dir (right-click on that auto-fill button > "Set auto-fill directory.."), if the folder contains sub-folders (with templates), just drag'n'drop the needed files from ean explorer/finder.

[pipelineaudio]

oops, I meant folder tracks. Im not sure Im doing it right

[semiquaver]

while were here i have a problem on mac with template resoursces: the templates work fine until I open a new project. Then I get a "could not find" error and the template file name in question is padded with a bunch of commas and other crazy charachters: eg "could not find "Templates/,,,,,,Pianoteq,,,%,,,,,"

[pipelineaudio]

this feature could be so amazingly powerful for multi song projects sharing say the same drum template

[Jeffos]

@pipe: ha! ok! sorry for the Englitch when you save a track that belongs to a folder, all the other tracks of that folder + the parent track are saved together in the template file (REAPER does that too). So when you "apply" such a file to a track, best effort: it will only use the first track of the file (so, here, the parent, with its folder state), hence the sublevels. Not sure applying a folder template to a normal/single track makes sense.. I'll add a warning message (such files with bundled tracks are more likely to be "imported" as new tracks rather than "applied" to existing tracks). HTH!

@semiquaver: what is your sws version? I have good hope it has been already fixed some time ago: can you confirm v2.2.0 #13 fixes it (avail here: http://code.google.com/p/sws-extension/downloads/list) ?

[kailuamusicschool]

Jeffos, maybe it will help if I explain better what I am trying to do

Lets say I have a 10 song album

I make a folder track for the drum tracks, which will likely have at least one subfolder in it

Lets say it looks something like this:


Track
1: Drums (this is folder start track)
2: kick
3: snare
4: Toms (toms sub folder start track)
5: Tom 1
6: Tom 2
7: Tom 3
8: Tom 4 (toms sub folder end track)
9: Hat
10: Ride
11: Overheads (folder end track)


So now, in the course of mixing the album, Ill make some tweaks to the tracks in the drum folder.

I might then want to apply those tweaks to the other songs

As it stands now, I have to save the tracks as a template, then go to the other songs, then paste in the new template, then move all the audio items, envelopes, etc to the new tracks

I would love to have a way to update the other songs less painfully

[gwok]

why don't you save fx chains instead of track templates?

[pipelineaudio]

Because its across several tracks

[Stu]

Originally Posted by kailuamusicschool

Jeffos, maybe it will help if I explain better what I am trying to do

Lets say I have a 10 song album

I make a folder track for the drum tracks, which will likely have at least one subfolder in it

Lets say it looks something like this:


Track
1: Drums (this is folder start track)
2: kick
3: snare
4: Toms (toms sub folder start track)
5: Tom 1
6: Tom 2
7: Tom 3
8: Tom 4 (toms sub folder end track)
9: Hat
10: Ride
11: Overheads (folder end track)


So now, in the course of mixing the album, Ill make some tweaks to the tracks in the drum folder.

I might then want to apply those tweaks to the other songs

As it stands now, I have to save the tracks as a template, then go to the other songs, then paste in the new template, then move all the audio items, envelopes, etc to the new tracks

I would love to have a way to update the other songs less painfully

Huge +1 for this, it would save so much time when working on albums.

[Jeffos]

Interesting, I see.. I think.. Let's take your example, what you would want is (?):
0) You have made some mods on your fav drum track folders
1) Select the 11 tracks of that drums folder (or just the parent folder "Drums"), click the auto-save button
=> all tracks of the folder get bundled in a single track template file (this is already the case today)
2) Switch to another project, select the 11 tracks of another "Drums" folder and "Apply template to selected tracks" (w/ the template file saved in 1)
=> the entire drum folder properties get updated but current items, envelopes and receives (if any) remain the same

is this right?

Today the Resources window and related slot actions preserve receives and items. In a next release, it will also preserve envelopes (and track folder states to make it dumb-proof). Also, as I said above, today "Applying template" only use the 1st track but I can make it work like 2)

[hopi]

I can make it work like 2

I think that is what pipe is after and I can surely see how handy this would be.

Now, thinking ahead, IF in the future it's going to also bring the envelopes over, that could be both a good thing and a not good thing...

Good if the envelopes are correct along the timeline for say the plugins, but not so good if they also are for say, vol and pan of the actual wav file...

So maybe "in the future" there could two varieties of this action: One with the env's and one without?

[pipelineaudio]

sounds perfect! I wouldnt want or need the envelopes or items, but I could see how people might

[pipelineaudio]

Any new ideas or workarounds on this?

[semiquaver]

Jeffos yes latest version takes care of the strange characters thanks.

[Jeffos]

Great, thanks semiquaver!

@pipelineaudio: what I described above will be avail in the next release (so it will be v2.2.0 #14, it should come very soon..)

Originally Posted by hopi

Now, thinking ahead, IF in the future it's going to also bring the envelopes over, that could be both a good thing and a not good thing...

You already got both options hopi: apply a track template including its items/envs OR apply a track template but preserve current items/envs (preserves track envs only, fx envs get removed as the fx chain replaced with the template one).

Ignore the arrows in that screenshot (it comes from another thread) but look at the bottom dropdown box: that's the diff between "Apply track template to sel tracks" and "Apply track template to sel tracks (+items/envs)":



You also have SWS/S&M "slot actions" with similar names. To save envs and/or items in templates or not, right-click the save button for options..

[pipelineaudio]

AWESOME!!!!