Hi, I’m trying out gig performer for mac.
I’m a keyboard vocalist and have about 400 backing tracks.
Is there a way to select a track in the streamer from a song in set list? What I don’t want is 400 rack spaces as I only need about 50 for my keyboards.
Also my tracks are surround files with channel 3 as the click. How can I assign the third channel from the audio streamer?
Cheers Allan
Since you didn’t get a response yet from someone who really knows this, I will throw out what I would explore.
Could you set up a widget that changes tracks.
Then one way to do it would be to create a new variation for each track.
I would use Setlist mode.
I would connect each variation to the particular song (or song part) you use it in. (Or you could use multiple rackpaces and variations in a single song (which you could connect to different song parts), as many as you want).
Then, when you want to change the backing track, you would just switch songs (in setlist mode) or song parts (which would change the rackspace variation).
There are probably other ways to do this without changing variations. So, maybe someone else will have a better idea. (There are usually multiple options to get what you want with GP).
Also, you are changing recordings (“tracks”) when you change variations if you do it the way I am suggesting. So, I am not sure if this is a preferred way of doing this because it means some audio (I think) has to be loaded into ram each time you pick another backing track. Maybe that is okay because it streams from disc? Maybe it depends on how powerful your system is?
The other option would be to create a different rackspace for each backing track. If you do that GP makes sure it loads whatever it needs in ram when you load the gig file. But, as you note, that would require 400 rackspaces.
Like, I indicated. I could be off base. I am still learning about the SAP.
(There may be a way for loading and switching between tracks within the Streaming Audio Player. I do not know it that well and mostly use if for one shot samples type of things, rather than background tracks)
Good luck!
I understand you don’t need 400 rackspaces but why not have 400 songs (which take up very little space) and use a song part action to select the song
See, I told you someone who knew what they were talking about would chime in! Hah!
This is exactly what I was looking for, thank you so much.
I love this solution except for one thing. For example, my first song part triggers the action and selects the track I want to play - this is great. Then, I start it playing. When I go to my next song part, it remains playing - perfect. But sometimes during a song, I want to return to the first song part. When I do, the audio stops playing. I’m assuming this is because returning to the first song part has again triggered the action to select a track, which I’m also assuming stops play. I’m now trying to figure out how to keep the audio playing when I return to the first song part.
If the action could be triggered when selecting a song (rather than a song part) in the set list (seems to me it can’t), then I don’t think I’d have this problem.
Any ideas?
You can simply duplicate the first song part and remove the trigger in the duplicate. Then instead of returning to the first song part, go to the duplicated part. Only use the first song part for triggering those kinds of actions.
He’s talking about what happens when you return to the same song part that has an action which selects a track in the SAFP. When you return to that song part, the action is re-triggered and the track which is playing stops because it got reloaded.
The solution is to duplicate the song part and remove the action that selects the track–and use that part after the initial load instead of the 1st song part. The track will continue playing since it isn’t getting reloaded.
Thanks for the response edm11. Yeah, I knew that would be a workaround, but I was trying to avoid creating another song part - especially when a song already has a lot of them.
I understand, minor inconvenience.
Fortunately there’s no resource overhead for song parts, so adding one doesn’t change things in that regard.
Why? You can have hundreds of them per song if you want, all that gets stored is a reference to a rackspace/variation pair, a few values (tempo, bpm, some MIDI messages if you define them) and some actions, if you define them.
I’m not worried about stressing GP, just me.
It may be that I should change the way I bounce from part to part, but currently I map four pads on my Akai pad controller to up to four song parts (the max I’ve ever needed). Of course, I could have mapped a pad to advance to the next song, but at the time my brain preferred a one-to-one pad-button to song-part correspondence. (i.e. pad-1 = song-part-1, etc.)
So, for me, the SAFP select title implementation on the song part kind of breaks my current style. I was just wondering if there was a better workaround than creating another song part.
I do think that having a Select Title action available on the song itself, would be a good idea though.
Thanks for the reply.
Oops,should read:
mapped a pad to advance to the next song**-part**
