Ari

Congratulations on the release - but I must say - just 4 fixes after 2 months?

Not exactly sure how to process that....

VP

Congratulations on the release - but I must say - just 4 fixes after 2 months?

Agreed!

Vocalpoint wroteCongratulations on the release - but I must say - just 4 fixes after 2 months?

Don't forget that PreSonus Software is responsible for many PreSonus software products (not just Studio One). So you can guess that they didn't spend two months working on just these four fixes

jazzundso wrote So you can guess that they didn't spend two months working on just these four fixes

The positive vibe that I am taking from this very sparse release is that if there are more 6.x releases in the pipeline - the next one (v6.6.x) should be worth waiting for

VP

Vocalpoint wrotethe next one (v6.6.x) should be worth waiting for

Yes that is my thought exactly!

I see that improvement to the Revoice Pro integration was part of this update. That, in itself, would be a welcome improvement for me!

Vocalpoint wroteAri

Congratulations on the release - but I must say - just 4 fixes after 2 months?

Not exactly sure how to process that....

VP

Agreed. I have several messed up sessions due to VST issues I reported in November. I wish I had noticed before I saved them in 6 so I could continue working on them in 4.

Being unable to use certain VST effects has effectively halted my production since discovering this. I've been checking for updates every other day for two months hoping for fixes.

laskop64 wrote Being unable to use certain VST effects has effectively halted my production since discovering this. I've been checking for updates every other day for two months hoping for fixes.

Laskop64

Maybe a topic for a new thread - but what issues (with what VST FX) are causing you problems?

If these are third party FX - that is generally not a Presonus thing.

Let me know.

VP

Vocalpoint wrote

laskop64 wrote Being unable to use certain VST effects has effectively halted my production since discovering this. I've been checking for updates every other day for two months hoping for fixes.

Laskop64

Maybe a topic for a new thread - but what issues (with what VST FX) are causing you problems?

If these are third party FX - that is generally not a Presonus thing.

Let me know.

VP

At first there was the VST GUI issue with plugins such as Maschine VST and Helix Native which was fixed by 6.5.1.

However, I had then discovered afterwards that Waves mono/stereo components (such as ReelADT, UltraPitch, Abbey Road Chambers, among others) have the unprocessed audio coming out of the right channel and the processed audio coming out of the left channel when audio tracks are set to Stereo, and it likewise occurs on Virtual Instrument output channels as well since they are stereo. This is happening regardless of the WaveShell version.
The aforementioned effects still work correctly in Studio One 4 and in other DAWs I've briefly tested, so I am not convinced this is something Waves caused. I just found the installer for 6.1.1 in my downloads, so I installed it and discovered that the plugins are working correctly in that version as well. I'm convinced the 6.5 update is responsible.

I was told the issue was passed to QA, but I don't know the result of that and they said just watch for an application update, hence my disappointment with 6.5.2.

Disappointing to see that the pan bug when exporting stems still exists. Stems still do not export with panning information when exporting in "track" mode. Support confirmed it as a bug in November.

This issue is being ignored release after release. I've been trying to show some patience but it's now rapidly running out. This is a serious issue with controllers,.ticket was created ages ago,.issue was confirmed.

viewtopic.php?f=151&t=51589

jazzundso wroteDon't forget that PreSonus Software is responsible for many PreSonus software products (not just Studio One). So you can guess that they didn't spend two months working on just these four fixes

Maybe they finally did something with the Atoms but I'm not holding my breath.

I have no opinion about the speed of fixes. I feel the same about the stem export !
There are some bugs that makes them not the same as what happens during the global export.

Same kind of problems in the "convert to audio file" button. It convert a track with fx and then you loose all the alternative takes of the regions.

In Logic Pro, there is a "freeze track" button that is very useful and that will not mess anything up.

I wish Studio one fixes those issues soon.

Vocalpoint wrote

jazzundso wrote So you can guess that they didn't spend two months working on just these four fixes

The positive vibe that I am taking from this very sparse release is that if there are more 6.x releases in the pipeline - the next one (v6.6.x) should be worth waiting for

VP

@Vocalpoint, I love your optimism! unfortunately I think that 'Fender-Presonus' will release a 7.x.x instead. I believe in an acceleration of the paid versions for S1....
Cubase-Yamaha has a paid version every year. This is what risks happening to S1. I wish I was wrong...

patricemazmanian wrote@Vocalpoint, I love your optimism! unfortunately I think that 'Fender-Presonus' will release a 7.x.x instead. I believe in an acceleration of the paid versions for S1....
Cubase-Yamaha has a paid version every year. This is what risks happening to S1. I wish I was wrong...

Indeed I fear that to be the case, but that's just speculation. If Presonus is reading this, can I remind them that not only do we pay for the product, we pay for the support and that certainly means bug fixes. A certain flour/eggs/butter/milk based DAW forgot about that and the rest is history. Don't be that DAW. Hoping this is just a blip.

stiull some white flashes when opeing popup menus under macOS. (logged bug)

patricemazmanian wrote @Vocalpoint, I love your optimism! unfortunately I think that 'Fender-Presonus' will release a 7.x.x instead. I believe in an acceleration of the paid versions for S1....
Cubase-Yamaha has a paid version every year. This is what risks happening to S1. I wish I was wrong...

Well - if history serves (and it usually does) - IF (a big IF) a 7.x appeared anytime soon - it would completely shatter all usual release cycles in S1 history.

V1 Sept 27, 2009 - October 31, 2011 = 765 Days
V2 Oct 31, 2011 - May 20, 2015 = 1298 Days
V3 May 20, 2015 - May 22, 2018 = 1099 Days
V4 May 22, 2018 - July 7, 2020 = 778 Days
V5 July 7, 2020 - Sept 29, 2022 = 815 Days

Now for discussion - let's assume May 2024 - a month which shows up a lot in the Presonus timeline:

V6 Sept 29, 2022 - May 21, 2024 = 601 Days

This would be the shortest major version cycle ever - by a lot.

Also interesting is a look back where history shows that only the "even releases" - V2 and V4 - had x.6 update releases which brought a lot to the table. 2.6.x was huge and so was 4.6.x.

And of course - the next "even" release is v6...

Looking at this and reading the tea leaves that Ari (and others like Rick Naqvi) has sprinkled about what's up in 2024 - my prediction is we see a "killer" 6.6.x set of updates well before a v7 hits the streets.

Always happy to be wrong but just 4 fixes after two long months means something and I do not think it means "we are sitting around"...

VP

Let's not forget that those 2 months included a major, annual holiday/vacation season. I'm surprised that there was a release big or small in mid January.