KVR Audio

SLiC · Post by **SLiC** » Thu Oct 20, 2022 2:01 pm

skijumptoes wrote: Thu Oct 20, 2022 1:21 pm You obviously had no negative issues with it then? ...Guessing it's easy to unload/remove if any issues did present itself.

None at all, it's been around a long time and updated often...I can't see I really understand it all, but it works to just set and forget...this is a good review/explanation https://www.geekiest.net/post/Process-Lasso-Pro-Review

Kalamata Kid · Post by **Kalamata Kid** » Fri Oct 21, 2022 6:58 am

I am thinking about getting Lasso Pro.
It runs $40,
Do they have a Black Friday sale?

Bartone · Post by **Bartone** » Mon Oct 24, 2022 11:35 am

I have been reading several comments about S1 6 and in many places questions pop up regularly “is this bug fixed already?” “How about this bug it has been for ages?” and it seems no not really fixes for many bugs people are hoping to be fixed.

After readin all those many questions about unfixed bugs, I have to ask: why Presonus doesn’t seem to be eager to fix bugs?

skijumptoes · Post by **skijumptoes** » Mon Oct 24, 2022 12:06 pm

Bartone wrote: Mon Oct 24, 2022 11:35 am After readin all those many questions about unfixed bugs, I have to ask: why Presonus doesn’t seem to be eager to fix bugs?

Depends which bugs you are refering to, I guess?

Many issues i've seen posted are just mis-interpretation on how routing or a particular function operates.

BONES · Post by **BONES** » Mon Oct 24, 2022 12:12 pm

Bartone wrote: Mon Oct 24, 2022 11:35 amAfter readin all those many questions about unfixed bugs, I have to ask: why Presonus doesn’t seem to be eager to fix bugs?

When someone mentions a bug, how many other people also have it? Just because someone has a problem, doesn't auutomatically mean it's a bug in Studio One and if only one person in 100 has it, it's likely not going to be easy to track down and fix.

wuworld · Post by **wuworld** » Mon Oct 24, 2022 7:48 pm

Anybody finding an issues with the midi? Doesn't seem the timing is right.

EnGee · Post by **EnGee** » Mon Oct 24, 2022 8:17 pm

wuworld wrote: Mon Oct 24, 2022 7:48 pm Anybody finding an issues with the midi? Doesn't seem the timing is right.

I don't trust 100% the timing in Windows! It is sometimes accurate and sometimes not! If you try to insert a midi track (or empty instrument) and try to hit a key and record with the metronom on, then you see it is not accurate (not only S1, but Cubase and Live, so I don't think it is S1 related problem).

On Mac, I did the test and I thought I have the quantisation on! But it was off. It was accurate 100% on all DAWs.

Anyway, if you insert an instrument, the midi timing seems better! The thing is (for my PC) not replicable. It is like random! Sometimes I restart the PC and it seems ok and sometimes not! So, for me the solution is to record quantise at 1/32 for example, and then maybe "humanize" a little the timing.

AdvancedFollower · Post by **AdvancedFollower** » Thu Oct 27, 2022 8:53 am

Studio One also suffers for having a smaller user base, since it means bugs that are specific and limited in scope and/or not very severe often don't get reported as frequently and might stay under the radar for longer. They also don't seem to have a lot of actual producers or mixing engineers on the beta team, so the DAW rarely gets any real-world like testing on actual projects until the update is released to the public.

The APDC (delay compensation) bug on sidechains that existed during much of the 5.x cycle is a good example. It took months until PreSonus even understood the problem people were actually reporting, and lots of people claimed they didn't have the bug (it did affect everyone, but if you used plugins with low latency and didn't rely heavily on sidechains, you were less likely to notice if the sidechain was a few ms off). Such an error in a more widely used DAW would have caused much more of a stir.

The automation rendering bug is another example, no one (including PreSonus) seems to fully understand what causes Studio One to very occasionally ignore automation during (non-realtime) rendering, but the bug itself has been around at least since SO 3.5. Since it's so rare, and you can simply "shake the box" to sidestep it, the bug just keeps getting passed down in release after release.

Danilo Villanova · Post by **Danilo Villanova** » Thu Oct 27, 2022 11:28 am

I emailed them to BEG them to fix the Sampler One bug with time stretching that has existed for years and been reported many times online.

They asked for a video to see what’s wrong...

BONES · Post by **BONES** » Fri Oct 28, 2022 1:26 am

What's the bug?

Trancit · Post by **Trancit** » Fri Oct 28, 2022 8:25 am

BONES wrote: Fri Oct 28, 2022 1:26 amWhat's the bug?

Curious too...

spaceman · Post by **spaceman** » Fri Oct 28, 2022 8:25 am

Can you post a video?

EnGee · Post by **EnGee** » Fri Oct 28, 2022 8:44 am

Danilo Villanova wrote: Thu Oct 27, 2022 11:28 am I emailed them to BEG them to fix the Sampler One bug with time stretching that has existed for years and been reported many times online.

They asked for a video to see what’s wrong...

Do you mean this?
https://answers.presonus.com/57444/bugs ... ose-studio

Trancit · Post by **Trancit** » Fri Oct 28, 2022 10:30 am

EnGee wrote: Fri Oct 28, 2022 8:44 am
Danilo Villanova wrote: Thu Oct 27, 2022 11:28 am I emailed them to BEG them to fix the Sampler One bug with time stretching that has existed for years and been reported many times online.

They asked for a video to see what’s wrong...
Do you mean this?
https://answers.presonus.com/57444/bugs ... ose-studio

It says it was fixed in 5.1.2

Danilo Villanova · Post by **Danilo Villanova** » Fri Oct 28, 2022 11:44 am

EnGee wrote: Fri Oct 28, 2022 8:44 am
Danilo Villanova wrote: Thu Oct 27, 2022 11:28 am I emailed them to BEG them to fix the Sampler One bug with time stretching that has existed for years and been reported many times online.

They asked for a video to see what’s wrong...
Do you mean this?
https://answers.presonus.com/57444/bugs ... ose-studio

No, this: https://answers.presonus.com/69915/foll ... sample-one

A video someone made:

After a back and forth, in which they asked for video proof, I asked them "It has been widely reported online. Can I least get confirmation that this is an acknowledged bug?"

This is their answer: "Hi,

Thank you for contacting PreSonus Technical Support.

That is with our development team, please check back on future releases to see if there has been an update."

So, not feeling reassured at all... they refuse to properly acknowledge it as a bug.

Studio One 6