Playlist contamination issue

Damir

Hi Peter, why is it whenever i choose last moment to autoplay to next song this setting remains as a permanent selection?
If i want a permanent selection i will use swipe to left on song and place a permanent autoplay command.
Why is it that I'm contaminating my playlist every time i want a once off auto play or repeat action, this becomes a nuisance because i have to go back to all those songs to put back my preferred settings.
This logic is not the same as ST3, it allowed us to have a default setting but it also gave us freedom to do whatever suited the moment and not upset our default settings.
Is this an oversight or a new logic thats meant to be in ST4?
Cheers Damir

peter

I have absolutely no idea what you are talking about.

Damir

peter I have absolutely no idea what you are talking about.

I don't blame you because things are too complicated and out of control.
In ST3 we had a very logical workflow because a lot of thought was put in to it .
I am talking about the auto play button that is in the top area of the screen that you can engage if you want normal play , auto play or permanent repeat of song.
This button in ST3 did the same job but it did not contaminate the normal song settings, it allowed us to use it anytime if needed while performing but it was not a permanent setting.
This makes a lot of sense, because the song we are performing with can be manipulated as needed but it also had a default setting.
So if i needed a permanent repeat or an auto play on certain songs i could engage this in stop mode , but if i then performed and wanted to disengage these settings, i could, but the next time you loaded this song the preferred default setting was setup for me.
At the moment this is not the case , as you use this button you are contaminating/changing all you songs , so next time you use this song you will get a surprise as this time you dont need the same settings.
This means spending hours putting back the preferred settings.
This is very inefficient. ST3 was much more logical to use.

peter

In ST3 that button did only modify the autoplay setting in the queue and not in the playlist the song has been loaded from. I think that was a bug. Therefore in ST4 the button modifies it in the queue and in the playlist. I think that's absolutely straight forward and the right thing to do.

Damir

peter In ST3 that button did only modify the autoplay setting in the queue and not in the playlist the song has been loaded from. I think that was a bug. Therefore in ST4 the button modifies it in the queue and in the playlist. I think that's absolutely straight forward and the right thing to do.

ST3 bug suited me much better because I could freely autoplay whenever in play mode without fear that I’m changing my default settings.
That makes a lot more sense, because you don’t need to worry if you use the function it’s going to bite you on the next gig.
Now if I choose to use this function I have to manually keep fixing it for next gig.
This make more work and no sense.
Good logic
In stop mode if you make a choice that becomes the default setting in play mode any change to that buttons status should be a temporary change.
This buttons operation is not global it’s song dependent.
This creates smooth workflow.

peter

I don't like the button behaving different in stop mode than in play mode. That will lead to lots of support requests why it does not work sometimes.

Damir

peter I don't like the button behaving different in stop mode than in play mode. That will lead to lots of support requests why it does not work sometimes.

My suggestion keeps the button behaviour as is, the only difference is when you are on stage and performing , making changes still behaves the same it’s just not a permanent change, because on stage we are manipulating this button in lots of ways to suit the moment , it does not mean we want the setting to remain a permanent change .
A permanent change can be done at home in stop mode , but on stage as the song is playing we have the option to fiddle any way we like but the next time we use the song it’s still how we set it in the first place.
Reason is after a few gigs the playlist would be constantly rearranged so unexpected auto plays might occur or the other way around where you normally need a an auto plays might occur you end up with a stop or a repeat .
It’s a much safer way to operate.
You always use the button the same way it’s just a logic state changes when in stop or play mode .
Stop mode assumes you are wanting a permanent setting and play mode assumes you are just temporarily changing states.
No usage difference , just a convenience for when you do the next gig.
No need to keep checking all your song settings are correct before a gig.

Kevtyler

Hi Damir, I’ve never understood the logic of toggle autoplay to be honest, a few months ago I was scratching my head wondering why weird stuff was happening.

My duo finishes set one on a big guitar hero song, I walk off halfway through and leave lightning boy to twiddle for 4 minutes, I was selecting a 20 minute interval song as next and toggled autoplay on that song, resulting in silence.

I though the most logical thing was that this song should just start, if for example I want a choice of 2 big songs at the end of set one and will choose at the last moment, ie, put Toto after Prince I need to faff about to ensure both songs are toggled to autoplay and ensure the interval is selected next. However if on the next gig I did Toto in the middle of the set, and I forgot to untoggle it, well I could be auto starting the interval by accident .
It is what it is, but I think autoplay should relate to the song you want to auto start , not the song you are currently playing yes?

I’m ok with it as it is but it’s not my idea of logic.

Cheers

peter

Maybe think of "Continue Playing" instead auf "Autostart" then it makes more sense to be placed on the previous song which should continue playing into the second. In the beginning when this feature was introduced in version 3 it was called continuous playback but everyone referred to it as autostart so the name changed with time and became the official name for this feature.

Kevtyler

peter thanks Peter

Yes I get what you are saying, but it’s just not logical to me that you could trigger your interval by mistake, but I accept that’s the way it is and realise I need to be vigilant.

Many Thanks Peter