I have several playlists, one in particular are my backing tracks (yes, I'm back) of which I have NONE selected (ticked), because that way the song I play is the only one played, right? It doesn't move on to another track while I'm grabbing my beer.
But it does- it starts playing the next (or first) track of any other Playlist that does have songs selected (ticked). So, say I have a playlist called "Restaurant Background" which is all James Taylor, etc with all the tracks ticked to provide continuous music for playing between my live brackets... if I play a backing track in Backing Track playlist, AC will automatically start playing the Restaurant Background tracks next.
In otherwords, it isn't playing back by separating the playlists. Make sense? Best I can figure is a single keystroke to "untick" or "tick" all the songs in that playlist. Is there one? (As against Select/Unselect). Or is there a better way?

Cheers, Graeme.

Hi,

To enable / disable multiple tracks at once, in the Edit menu there are several commands that you may find useful, Enable / Disable Selected, and Enable / Disable All.

In testing on v 1.49 just now, I am unable to replicate the behavior you describe of AC auto-playing enabled tracks from a different playlist if all the tracks in the current list are disabled... what version of AudioCodex are you using?

The expected behavior, if all tracks in the currently playing playlist are disabled, and loop mode is turned off, is that any track from that list plays once and then playback stops.

Any more info you could provide would be really appreciated, we have invested serious efforts towards getting this aspect of playback to behave nicely and we thought we had this licked, but it may be that there are loopholes which we haven't discovered yet, and if so, we would love to see them fixed

Cheers,

Mark

Okay, Mark- food for thought. After reading your email I've just tried to recreate the problem in my studio (rather than in a panic at a gig!) and achieved a few things. In a dozen attempts to recreate it, the problem occured twice. But wait! There's more!

I can also select a song from playlist A, STOP play and go to another playlist B, select another song and click PLAY, and it continues to play the track from Playlist A even though on returning to that list it appears as NOT selected. This only happens if you use the Transport buttons. Selecting PLAY with the ENTER key works okay. Maybe this is by design?

Also, the majority of times, when an unselected track finishes playing, if I click PLAY again (why would you, but...)the program freezes and I have to Force Quit.

By the way, after a Force Quit, any Effects Chain isn't in place on a restart.

Mind you, I'm version 1.43, so I guess there's a few upgrades I've missed. Maybe I should install any available, before we worry too much further?

Cheers, Graeme.

This post was last modified: 03-02-2009 10:11 PM by alex.

Hi,

When a track is loaded for playback and you pause (or the track finishes and you have no other tracks ticked in the current playlist ), the track you were playing will still be loaded in the playback engine; you can tell if a track is loaded as AudioCodex's window title will contain the name of the loaded track, and the name will also appear above the transport slider.

In such a configuration, if you simply view a different playlist and use the 'Play / Pause' button to start playback, any still-loaded track will begin / resume playing, and the 'currently playing' playlist won't change.

To set a playlist as the 'currently playing' playlist, you have to either double-click a track in that list, or else select the track and hit 'Return'... this loads the track, and also tells AC to use the list that track is from as the 'currently playing' playlist.

This modality was a conscious design decision, however I'm starting to think it might be better to follow iTunes modus operandi, which is to unload the current track if playback is paused and any list other than the 'currently playing' playlist is being viewed... we'll table this for discussion here at CodexDev HQ in the next few days.

The freezing issue you described sounds like something that was fixed in one of the updates after 1.43; we are also very close to releasing version 1.5, which has been subjected to extremely vigorous testing and includes many bug and inconsistency fixes, so you may even prefer to wait a few more days for the new version, but if you want to give 1.49 a whirl it should at least not lock-up in the particular situation you've encountered.

Cheers,

Mark

PS AudioCodex only saves all of its state information when quit normally; when the app is force-quit there is no opportunity to save state, hence the FxChain losing its config for next launch. You can force AC to save its operating state at any time by using 'File: Save Playlists', although I'm not sure if that command is present in 1.43.

Thanks Mark, I reckon for the first issue it's not really a problem- just something users need to know and- in fact -does allow you to "set up" a play situation in a separate playlist, while soemthing else is playing.

I've got a gig this Friday, so I'll wait until the last minute for 1.5, otherwise I'll give 1.49 a whirl. Either way, I'll let you know.

Cheers, Graeme.

PS. Have you put a crossfade in yet?