PreSonus Forums

There is a major bug with midi events crashing Studio One 5.4

Draging any midi event, with three C notes spaned across any octaves will result in a crash, topic below:

https://forums.presonus.com/viewtopic.php?f=151&t=46327

Still not fixed in 5.4. Maybe in version 15?

The send drops into nowhere when opening simple presaved template, and inserting Sample One, or whatever else instrument:

The multi format mixdown in a nice feature.

ianaeillo wroteAnyone having issues with updating universal control? Mine no longer shows my quantum nor does it connect to my app but the interface still functions as expected.

Happened with my Quantum 2626. I had to completely remove the power chord and the TB cable from the interface then, shut down the computer. After a restart, the 2626 was correctly shown in UC. It was a little frightening.

Hackintosh here but I guess it’s a Mac specific bug…

patricebrousseau wrote

ianaeillo wroteAnyone having issues with updating universal control? Mine no longer shows my quantum nor does it connect to my app but the interface still functions as expected.

Happened with my Quantum 2626. I had to completely remove the power chord and the TB cable from the interface then, shut down the computer. After a restart, the 2626 was correctly shown in UC. It was a little frightening.

Hackintosh here but I guess it’s a Mac specific bug…

Nope, happened/is happening here on doze. I'm not sure what to make of it, but several of us have had it.

reggie1979beatz wrote

patricebrousseau wrote

ianaeillo wroteAnyone having issues with updating universal control? Mine no longer shows my quantum nor does it connect to my app but the interface still functions as expected.

Happened with my Quantum 2626. I had to completely remove the power chord and the TB cable from the interface then, shut down the computer. After a restart, the 2626 was correctly shown in UC. It was a little frightening.

Hackintosh here but I guess it’s a Mac specific bug…

Nope, happened/is happening here on doze. I'm not sure what to make of it, but several of us have had it.

I guess the only workaround would be to downgrade UC and firmware, annoying for all users affected…

BTW, it’s fine for me on the Windows 10 side (dual boot Mac/Win). Weird…

Having the same problem with UC (on Win) with Quantum and downgraded. UC came back. I tried upgrading again, and this time, the driver didn't work in Studio One. So I downgraded again.

I posted on the Quantum forum, and the suggestion was to uninstall completely, reboot, then reinstall the latest fresh. Haven't tried that yet.

I'll try that later, right now I'm not going to stress

Regarding the Plugin Nap feature, my early tests didn't yield any benefit.

My current session (VSTi orchestral based, with a dozen-plus VST plugins and inserts) was running at 83% max CPU at 256 buffers. When engaging Plugin Nap, ironically, my max CPU increased to 87%. (I tested this twice to confirm the anomaly). I'm supposing that there may be a hit for turning things on and off.

So, I went back to conventional approaches and raised my buffers to 512. This made a huge difference: With and Without Plugin Nap enabled, my max CPU reached 53%.

Similarly, I increased buffers to 1024, and both with and without Plugin Nap enabled, my max CPU hit identically at 48%.

A few early conclusions (many of you likely know all this already):
- VST Instruments are not affected by the "Nap". i.e. They don't Nap, and accrue no benefit.
- I do see that there are Nap advantages when all my channels aren't playing. However, if at the climax of a song all of your channels are playing -- then having Nap engaged still won't have any impact. So, the Plugin Nap is most effective when needed least (i.e. during soft sections of your song, when multiple tracks aren't playing). To get the desired impact of reduced CPU, you actually have to have tracks being NOT used at peak moments.
- The benefits will increase the more plugins you have. (at a dozen, it made no positive difference, and actually was detrimental at lower buffers. At several hundred, this feature could be golden!
- To save CPU at peak moments, raising buffers is still the king.

Craig

Yeah, I'm sure some people are tired of me saying so, but at this point, "nap" is so limited and uninspiring that I've just got it turned off.

It's not a bad idea, but it seems half-baked at this time. Still, I love the effort.

reggie1979beatz wroteYeah, I'm sure some people are tired of me saying so, but at this point, "nap" is so limited and uninspiring that I've just got it turned off.

It's not a bad idea, but it seems half-baked at this time. Still, I love the effort.

To be honest if I have plugins taking up CPU it means I'm using them - to "nap" them during say a playback or mix is pointless for me. If I'm really bothered by CPU usage, I print the track to audio. So it is not much use to me - but I'm interested to find out what others would use this feature for and what problems it solves for them.

I get that.

The "thing" that I get about "nap" is that it "should" be used as a crutch to give "unused" plugs a rest when not being used.

A fantastic Ideal in theory. But again, it seems to be a bit half-baked.

I dunno, maybe we are on to something for the future, but as of now, I'm just going to leave it off.

And one other thing that I think deserves attention: What I've seen in viddy's about nap, has almost NOT been on my system. It's not just me folks, it's an issue for more than that.

Just sitting here pondering about the "Nap" feature and why it has an ON/OFF switch at all.
If it was the greatest thing since sliced bread then why not just include it?
Unless there is something "potential" that can happen but no-one has stumbled over it.
... and also what is it with the symbol, are they just "mooning" us? why not zzz's isn't that napping?

... ohh and what was the greatest thing before sliced bread?

peterbirch wrote... ohh and what was the greatest thing before sliced bread?

The toaster

I think plugin nap is one of the greatest new features added in years! I have had sessions where my cpu was dropped by 30 % because of the nap, that is massive improvement if you ask me. Really happy about that

I will say that the plugins you use and if they nap or not make a huge difference how much benefit you'll get. Waves plugins with the analog button won't nap, unless you turn the "analog" off. Same with the analog style plugins that cause some kind of noise floor.

j0001s wroteHaving the same problem with UC (on Win) with Quantum and downgraded. UC came back. I tried upgrading again, and this time, the driver didn't work in Studio One. So I downgraded again.

I posted on the Quantum forum, and the suggestion was to uninstall completely, reboot, then reinstall the latest fresh. Haven't tried that yet.

Tried it, same ol'. Not sure what to do. I guess another support ticket

Selecting midi note or notes in the Editor can result in the note or notes freezing, has only happened in 5.4. Selecting a midi note it turns white and once you have moved it or lengthened it it stays white and does not allow you to deselect it. This has happened on one note and also when moving a group of notes and appears to be random as in sometimes it does and sometimes it doesn't. Anyone else had this problem?

Thanks in advance,

Gerry

I did. It also happen to me only once thus far.