I can't C a Major problem with that...

 

I am a S1 legit user and I do like S1.
But honestly, these bugs really really are super annoying.

There is another one from version 5 which I pointed out but hasn't been corrected.


- Create 4 audio tracks (more than 2 tracks)
- Select all the tracks and pack folder.
- assign a Bus channel to the folder
(Now you will see all the tracks are routed to the Bus you just created)
- Now go inside the bus and select any 2 random tracks and again pack folder.
-Now the tracks inside this new folder are routed to Main Out.
So basically, the routing was reset when you do a pack folder inside a 'Bus assigned folder'. Expected behavior would be, "The tracks inside the new folder will still be routed to the Bus, not the Main Out". So basically the issue is, Pack folder command resets the Bus assignment. This is a deep Bug.

 

they are both not a good look for major released software, because either way people will assume that the rest of it is plagued with bad code you just haven't found to be somehow defective yet.

it's funny to me, because only recently I commented that Studio One users seem to complain the least of any DAW users (with problems) !

 

Unfortunately, I confirm.

 

The thing is S1 is really good feature-wise: very fast, easy to use but still with a lot of features, nice stock plugins...

But these big unresolved bugs are becoming more and more unjustifiable. Some of them are old. I can see that spooking away pros or just anyone who has does complex projects

 

Last edited: Sep 20, 2021

I didn't test this but by reading 3 page of confirmations I can confirm.

 

I've noticed that all DAWs have this problem. I don't know what S1 is getting bashed for this so often. Take for example Bitwig. My god, they have so many bugs and they didn't fix for years that you could think they consider this as a feature. I didn't use it for the last 1.5-2 years, but considering all the complains from my friends, who us it obsessively, I would say the situation hans't changed dramatically.

And what "old bugs" does S1 still have?

 

Seems like Presonus added additional checks that R2R missed out

 

That's interesting and food for my thoughts, because I haven't done any complex track in a long time. (I use Reaper or S1)
So maybe I'm letting myself being influenced by unfair criticism.

 

it happens in legit version too... it's not a check, it's a bug

 

I didn't get it. If I was the coder, I don't see that as a bug, it should be intensional. You packed some tracks and then you pack some of them again. That means you want to seperate them from the first package. So they reset the output assignment. Why do you wanna pack tracks which are already packed?

 

Because of this thing called decluttering.
First of all I had seperate similar tracks, say 8 pair of Left Right Background Vox. So I packed all the 16 mono tracks and then added a Bus to the folder so the Folder also acts as the Bus. Then I added several effects on the Bus. Now I want to take each Left-rigt pair and want to pack folder so that I will have 8 folder tracks inside and I know I have 8 stereo BGV folders. That is entirely for decluttering purpose. Now as soon as I do it, the output bus will get reset.

There are many other scenarios but mostly folder tracks (not Bus fulder) are there for decluttering purpose and no one wants to have the output bus being reset on packing Folder.

Thanks to almighty or whatever, that you are NOT THE CODER. I am relieved for that honestly.
I talked to the actual Presonus guys (as I have a lot of acquaintances working at Presonus) and they all agreed about this bug which is called "Output Bus resetting on Packing Folders" and it was a deep rooted bug. Some of it was resolved in v 5.3 I guess and some are still not, which will be fixed soon.

 

I guess I'll just stick with 5.3 for now.
I get no crash in 5.3 when doing what is described in the first post.

 

5.4.1 has been out about 5 days now.. issue has fixed along with a pile of others.. i am constantly here looking for it.. fingers crossed it will show up soon.

 

Yes, if you are creating a song with ONLY such C1-C2-C3-C4 notes in a single Instrument track, S4 crashes. but if you are using any other notes within this event, or creating more instrument tracks with other note combinations, it wont crash.

 

The bug was fixed with the last official update.

 

This isn't true.. it's much more sinister than that.. they could be spread across multiple events across different points on the timeline and also have other notes mixed in.. certainly was that way for me.. anyway.. lets hope we're not waiting too long for 5.4.1 to appear here.