I have three states set for a song, and a backing track in the media player, however when I select a different state (say the second one) media player stops and in fact the backing track is unloaded from the media player?
Cna soemone advise the best way to have a media player file continue regardless to which state is being used?>
Thanks
When you have a media player that spans states you can make sure it is loaded in the first state and then when create the other states it will copy over. If you already have the states made and no song loaded then you have to load the media player File on each state that is already made. The way states work is that the last selected state (check box filled) will be copied to the new state. Previously created states will not be affected just new ones. Hope this sorts it…
Thanks Dave - I wonder why three instances (eg if I have three states) of the media player are needed?? O would have thought it would have been an over-arching sort of tool.
Just thinking some more, I think I might create a “MediaPlayer” rack…and just insert that into each song…
Well trying to do a media rack just creates another set of problems (as in loadin songs and setting outputs within the rack itself…so I go back to the original question why the hell do we need to have a media player for each rack state? All I am doing is turning one on and one off…still cannot see how this should affect a media player?? When the media player is actually not part of any of the VSTi states or racks in the first place.
Hey Dennis, It’s not three instances, it’s three states of the same instance of the one media player. Sorry if my explanation was off. The problem you were having was that you added the media player and made some or all of the states before you loaded the media player with the wav or mp3 file. So say you then add a wav or mp3 file to the media player in state 1, if you now go to state 2 it would not have the file loaded yet because it was created before the file was loaded.
So when you want to have a media player that spans multiple states you should load the wav or mp3 file into the media player before you start making the states for your song. That way the wav or mp3 file will be copied over each time you make another state. You don’t need a rack but could probably make it work that way.
Edit:
If you already had a song with the states in it and then added a media player, it would automatically appear in all the states but would need to have the mp3 or wav file loaded for each state since all the states for the media player would have started out with no file loaded. So it’s more work but it does work, all you have to do to fix your current problem is,
a) make sure automatic save state is on
b) drag and drop the media file into each state of your song till it is present in the media player on all states.
Regards
Okay cool I get that…still don’t understand why though?? I mean if one is using the media player I would hazard a guess that 95% of it’s use would be for backing tracks and have nothing to do with instruments loaded…why C3 needs to have a “pseudo” MP in each state still escapes me.
I would have thought the instruments are the instruments and the media player is the media player, and turning one instrument on or off, really, (imo) should have no effect on a separate MP running.
Again, it is what it is so I just have to work with it.
A bit counter-intuitive but there ya go 
of course I could go back to just forgetting all about racks and load VSTs “standalone” and just bind an on/off button. In which case the question is why bother with racks in the first place. A question I asked (in not so many words) ages ago when considering upgrading to performer!
Cheers
It’s because you might want to have any number of actions with the media player based on states, like…
State a is backing track 1
State b is backing track 2
State c is backing track 3
State d is no track
another might be
State a is full volume
State b is 70% volume
State c is back to full volume
etc …
The list of state behaviors for the media player shows the rest of the possibilities. Hope this helps you see how the media player also acts like a vsti sometimes depending on how it is setup. Good luck with your solution. 
haha…how about if one just wants it as I am wanting it? Doesn’t seem possible. As I hinted above I think I am going to have to forget racks and just do song setups…at least they are straightforward. I knew this Performer version was going to be way over my head hahaha!
Anyway thanks for taking the time - appreciate it!
Hey Dennis,
“if one just wants it as you are wanting it”, they simply look at the “state behavior” tab on the left and de-activate the check at “selected file”. Having this check box activated means that Cantabile will check on each state change which selected file has been saved with the new state and (if this is different) change the file selection accordingly.
So, if you have this check box activated, you can (and must) save the active song with every state. If you don’t want to change selected songs with each state, simply unselect this state behavior and everything is fine!
Cheers,
Torsten
Hey Dave,
not 100% correct - the set of loaded files (the play list) within a media player are permanent for all states in a song. But what can change is the “selected file”, i.e. the one within the play list that is cued to play.
Easiest way to fix this is to simply turn off the respective state behavior for the media player.
But if one wants to keep the behavior active and maybe have the same file playing for states 1-3 and a different one for state 4, there is still no need to drop the same media file into each state. Simply select the file in the “presets/destination” column for each of the states and save the state (or use automatic save state).
Cheers,
Torsten
Thanks Torsten, I’ll give that a go!
Sorry Torsten, that does not work. When I select the second state the media file stops, although if I go back to state 1 it is there still playing away??? Re-select State 2 and it goes mute again. And so on.
Dennis
Hehe, I think I know what’s tripping you up now: take a look at the Route from your Media Player to Main Output (or wherever you route your Media Player) and watch what happens when you change the state: does it suddenly get de-activated when you change from state 1 to state 2?
This is because this route has “Enabled” ticked in State Behaviors - this means that Cantabile stores an individual “on/off” setting for this route with every state; and it seems that by default, it is off for any other state when you insert a media player into an existing song.
Easy solution: simply uncheck “Enabled” in State Behaviors for the Output Route from your Media Player and activate the route again; now it won’t get muted on state changes.
This is something that took some getting used to: whenever I insert a plugin or a rack, I take a look at its routes and decide which ones need to be switched by state and which are permanent for the song. For the latter, I uncheck “enabled”.
Hope this helps!
Cheers,
Torsten
I’m away from those files at the moment Torsten, but I’ll test that out when I get a chance a bit later on.
Thanks @Torsten for the correction and the solution. Appreciated. 
Hi @pax-eterna,
Is this resolved now?
I think the answers to your questions are all above, but to sum up: Cantabile will stop the media player if a different file is selected in each state. If you don’t want to switch songs between states then clear the “Selected File” state behaviour. If the file is continuing to play but sound stops then it’s probably a route being disabled.
Brad