Green Solo button means you are in SOLO SAFE mode. In order to return that to normal hold SHIFT and click on that green solo button and it should go out or turn grey.

Unless you solo a channel that is routed to that buss and then that solo button will be normal yellow. Unsolo the track and it should go grey again. Saving like this will open again and be the same way. e.g. it should not go green again.

BTW Solo SAFE is now behaving differently in V4 that it did in V3 as well. If you click on a buss green solo safe button now in V4 nothing happens. In V3 you used to hear that buss. Now what happens is if you solo tracks sent to that buss (green solo) the buss remains audible e.g. if it has effects on it etc.. It is a little confusing.

Yes you describe step two.
This state does not persist. See step 5.

Thx.

Jemusic wroteBTW Solo SAFE is now behaving differently in V4 that it did in V3 as well. If you click on a buss green solo safe button now in V4 nothing happens. In V3 you used to hear that buss. Now what happens is if you solo tracks sent to that buss (green solo) the buss remains audible

Why did they change that? For what purpose?
For my workflow this is a step backward.

...and why does SOLO keep coming back after saving with an additional channel output?
Can anybody repro please?

Thanks.

PreAl wroteI have a strange issue in 4.0.1

1) stop SOLO Safe .
4) I save the song. (I actually reversed these thus no prompt))
3) I close the song.
5) I open the same song again - The green SOLO button is back!
Why? (Yes the project is DEF being saved).

Thanks...!

Confirmed

There is an issue with Solo Safe mode and busses. This has been reported and confirmed with the developers.

The issue with your specific example is changing from Solo Safe mode to no sole is not setting the dirty bit, thus the song closes without asking you if you want the save the changes.

It will be reported when I or another moderator gets the chance.

Thanks

Thanks.
I've created ticket at Presonus as well. Request #453639
BTW I am saving the song, the SOLO button state changes back after safe.

BTW not my quote?? Thx.

By changes back you mean is returns on reboot?
If so that is the dirty bit issue.

Please check my steps 2,3,4,5 in OP (and not what you've quoted as me, you seem to have altered my quote).

About as clear as I can get. No reboot happened, it's saving but forgetting the SOLO state.

Appreciated.

Are ther two issues?
I altered your steps because that is the way I closed it out of habit.
It still revealed the issue.

Because the dirty bit does not get set when you toggle the state of the solo safe it does not know to save that change.
So saving and closing or closing expecting a prompt to save yield the same results.

I'm just reporting the specific issue in the opening post. I'll just take it that it's the issue you are talking about. Thx.

Response from support who say the issue has also been in version 2 + 3 which is strange?

Going to be reported in beta forum..

It works correctly in 3.5. Maybe they don't understand the issue.

Reported:
Issue:
Solo safe does not set dirty (when toggled off) after opening a song with previously saved solo safe.

Steps: in 4.0.1
1) add channels.
2) put in the solo safe mode
3) close and save the change.

4) reopen ( solo safe there)
5) Turn solo safe off.
6) Close
7) Error: Prompt for change does not occur so the song will reopen with solo safe on.

Well guys I cannot get this behaviour. In Mac or Win 7. If I open a song that has green solo states present and then I change them back to normal solo state e.g. yellow solo states and save, and close, and then reopen the song comes back to me with no green solo states present at all i.e. all yellow as I left it.

When saving if I do nothing to the title I get the message to replace the song i.e. song exists of same name, do you want to replace. I just click yes and it saves. I close and then open it opens with no green solo states for me.

When saving if I change the title to something else it saves. If I open that song I also get no green states either.

I have tried creating a song with all yellow states i.e. no green states. I tried 10 audio tracks. 5 sent to a buss and the other 5 to another buss. It saves and opens that way. If I change to any green states and save it (new title though) it also closes and opens with all green states for me. If I change the green solo state song back to all yellow and save, even over the original yellow song or a new one, it closes and opens with no green states present as mentioned above.

Could it be just a Win 10 thing?

We have many confused here.
1) Solo safe not working on busses
2) Solo safe not setting a dirty bit.

Both have been documented with the developers.
EDIT looks like you change your post since I read it perhaps and we are posting together

jpettit wroteIt works correctly in 3.5. Maybe they don't understand the issue.

Reported:
Issue:
Solo safe does not set dirty (when toggled off) after opening a song with previously saved solo safe.

Steps: in 4.0.1
1) add channels.
2) put in the solo safe mode
3) close and save the change.

4) reopen ( solo safe there)
5) Turn solo safe off.
6) Close
7) Error: Prompt for change does not occur so the song will reopen with solo safe on.

PreAl wroteI have a strange issue in 4.0.1

1) Observe the output channel has a green SOLO button.

Capture4.PNG

2) I stop SOLO'ing (no longer a green button). BTW I have to hold down the shift button whilst pressing it for some reason.
3) I save the song.
4) I close the song.
5) I open the same song again - The green SOLO button is back!

Why? (Yes the project is DEF being saved).

Thanks...!

Your steps are def different than my OP. . I said in the OP it's definitely being saved.

If I'm going to look at your steps then step (6) would be save and then close. (You can even add a few extra steps beforehand if you like such as fiddle with the faders does not make any difference).

Cheers

The only thing for me is how the green solo state actually works in V4 now. If you solo a V4 green state buss directly, yes nothing happens. Before in V3 you heard that buss.

But green state soloing is still working in V4 by soloing any of the tracks assigned to that buss. You will still hear the track and the buss because the buss is safe.

It is either a bug or intended slightly different operation. I find its best to stay away from green safe soloing all together. Just use normal mode and select the things you want to hear. e.g. a track, and a buss. The buss gets added in so you hear the track and the buss.

You notice it save for me on the initial setting of the solo safe.

The error is in the second opening and toggle ing to off.
The program does not change that state.

BTW if you touch anything before step 6 other than toggling Solo safe it will work correctly because the other action sets the dirty bit.

Also, it is only the changing of state from on to off that is not saved.

Jemusic wroteThe only thing for me is how the green solo state actually works in V4 now. If you solo a V4 green state buss directly, yes nothing happens. Before in V3 you heard that buss.

But green state soloing is still working in V4 by soloing any of the tracks assigned to that buss. You will still hear the track and the buss because the buss is safe.

It is either a bug or intended slightly different operation. I find its best to stay away from green safe soloing all together. Just use normal mode and select the things you want to hear. e.g. a track, and a buss. The buss gets added in so you hear the track and the buss.

Perhaps start another thread about this as you cannot reproduce. Please see OP/topic.

Thanks.