15 posts
Page 1 of 1
Hello All,

I have been noticing an issue with the native Expander plug-in in Studio One V6.x and I was wondering if anyone else could try to reproduce the issue.

My system: Mac Studio M1 Max, 32GB Ram, macOS Ventura 13.2.1
My Interface: Presonus Studio 1824 running the latest firmware and Universal Control.
My issue:

1: Start new session (any sample rate)
2: Just add a loop or some audio to a new track.
3: Insert Presonus native Expander plug-in on the insert of the loop/audio track.
4: Hit play and watch/hear the Expander working without issue.
5: Hit stop on playback.
6: Hit play and watch/hear the Expander is not working.
7: Hit stop on playback.
8: Click the "Power" button in the Expander plug-in to toggle it off then back on.
9: Hit play and watch/hear the Expander working again.

Now when you hit stop on playback the Expander plug-in is not working again until I toggle the plug-in power button off/on.

I am thinking this could be more to do with Studio One running on the Apple M1 series chips but I wanted to see if anyone in the community has a Mac Studio and willing to test out the above scenario as well.

Thank you,

-TK-

Attachments

[ Play Quicktime file ] ExpanderIssue.mov [ 11.4 MiB | Viewed 2887 times ]

User avatar
by Blame Karma on Mon Mar 27, 2023 10:31 am
No problem here on an M1.

Mac Mini M1 / Ryzen 1700X - W10 / Sphere / 1810c / Apollo Twin
User avatar
by jmsstks on Sun Apr 23, 2023 2:36 pm
I've been having the exact same issue, although I'm using S1 v5.5.2.86528

For a little while I wondered if I had the settings setup right in the plugin, but they indeed are right, and (just like you've experienced) sometimes work after refreshing, but then seem to be triggered by something in playback and the yellow-line indicator seems to lock in place.

This also seems to be happening in projects that I've had for a while, with the expander working fine.

Interestingly, I'm also on M1 MacBook, with Ventura 13.1 - Would be very intrigued to know if other users are having the same issue with similar spec..... and more importantly, if there's a workaround to sidestep this in the short term, until it can be sorted by the developers.
User avatar
by harryleebartel on Mon May 29, 2023 10:37 pm
Im having the same issue. 14" M1 Macbook Pro
User avatar
by PreAl on Mon May 29, 2023 10:52 pm
Apart from the person on version 5, can you confirm you are using Studio aone 6.1.2?

Maybe this article will help..

https://support.presonus.com/hc/en-us/a ... our-system

And this post...

viewtopic.php?f=151&t=51547

Or not! :)

Intel i9 9900K (Gigabyte Z390 DESIGNARE motherboard), 32GB RAM, EVGA Geforce 1070 (Nvidia drivers).
Dell Inspiron 7591 (2 in 1) 16Gb.
Studio One Pro 6.x, Windows 11 Pro 64 bit, also running it on Mac OS Catalina via dual boot (experimental).
Presonus Quantum 2626, Presonus Studio 26c, Focusrite Saffire Pro 40, Faderport Classic (1.45), Atom SQ, Atom Pad, Maschine Studio, Octapad SPD-30, Roland A300, a number of hardware synths.
User avatar
by harryleebartel on Fri Jun 02, 2023 6:22 pm
Yes i'm on 6.1.2. I like to keep everything up to date so i'm also on the latest Ventura. To me it just seems like a bug of some sort, Everything else works perfectly fine just Presonus Expander Plug in.
User avatar
by graytermedia on Sat Jun 03, 2023 11:44 am
Just tried it here with ver 6.1.2 (system specs in sig) and could not recreate the problem.

tg

Mac Studio (2022) M1 MAX / 64GB / 2TB HD / macOS Ventura 13.5.1 / RME BabyFace Pro FS / SSL UF8 + UF1 + UC1 / Roland SYSTEM 8 / Komplete S61 / Keylab 61 mkII / Studio One 6.2 / Pro Tools Studio 2023.9 / Nuendo 13 / Reaper 6 / UVI Falcon / Komplete 14 / Omnisphere / Keyscape / Trilian / V Collection 9
User avatar
by jkevinpowell on Wed Jun 21, 2023 3:53 pm
I consistently have the problem on my end. That doesn't help you, but know you're not alone and the problem has been around for a minute I think.

System: Mac Pro M1 Max, 32GB Ram, macOS Ventura 13.4
Interface: Tascam 16x08 running the latest firmware
Software: Artist 5.5
User avatar
by bradleysobie on Mon Sep 25, 2023 6:57 am
Same issue for me on 6.2.1.94935.... m2 macbook pro
User avatar
by jmsstks on Tue Oct 24, 2023 1:54 am
jmsstks wroteI've been having the exact same issue, although I'm using S1 v5.5.2.86528

M1 MacBook, with Ventura 13.1


I've since upgraded to V6 and frustrated to note I'm having the exact same issue.
User avatar
by mariomajkic on Thu Nov 02, 2023 2:12 am
Same issue here. Mac Mini M2.
User avatar
by JaEMob on Mon Jan 15, 2024 10:43 pm
Exact same problem here.
SO V6.2.1.94936
MacBook M2 Pro
Sonoma 14.1.2
User avatar
by tomorrowstk on Wed Jan 17, 2024 8:49 pm
Honestly I'm kind of glad to see I'm not the only one with this issue. Just as a note to this issue. I have done complete wipes of my Mac Studio M1 Max system and reinstalled S1 V6.X.X as the only application and I can still recreate the issue. This does not happen on my Intel based Macs from what I have tested. Maybe one day we will see a fix for this as I really do enjoy the S1 native expander plugin.
User avatar
by JaEMob on Wed Jan 17, 2024 10:36 pm
When im finished my current project im going to upgrade to V6.5.2. (so maaybe in a week or two or...? (^^;) ). Secretly hoping that will fix it, but not really counting on it working :P.
In the meantime, submitting a request/ticket at support.presonus :)
Will report back if i learn something useful.
but not really counting on that either.... :P
User avatar
by abryan on Thu Feb 08, 2024 2:46 am
Experiencing the same behavior v6.5.2 on MBP M1 macOS, Ventura 13.6.3. Makes it usable.

15 posts
Page 1 of 1

Who is online

Users browsing this forum: No registered users and 106 guests