Why did you leave Studio One?

Plug-in hosts and other software applications discussion
User avatar
KVRAF
32366 posts since 14 Sep, 2002 from In teh net

Post Fri Jan 22, 2021 2:04 pm

I haven't exactly left it but I'm not upgrading until MPE works for VST3 and AU plugins as well as VST2.

User avatar
KVRist
466 posts since 1 Apr, 2012 from bamboo tube

Post Mon Jan 25, 2021 10:04 pm

aMUSEd wrote:
Fri Jan 22, 2021 2:04 pm
I haven't exactly left it but I'm not upgrading until MPE works for VST3 and AU plugins as well as VST2.
I upgraded just for MPE and didn’t know the limitations. Dumb move. I don’t understand why they half-assed it.
Tangled roots perplex her ways.

KVRian
514 posts since 19 Oct, 2020

Post Tue Jan 26, 2021 2:02 am

anxiousmofo wrote:
Mon Jan 25, 2021 10:04 pm
aMUSEd wrote:
Fri Jan 22, 2021 2:04 pm
I haven't exactly left it but I'm not upgrading until MPE works for VST3 and AU plugins as well as VST2.
I upgraded just for MPE and didn’t know the limitations. Dumb move. I don’t understand why they half-assed it.
Because that's S1, everything they added to S1 is half-as sed. That's why I left.

User avatar
KVRAF
7956 posts since 4 Jan, 2017 from Warsaw, Poland

Post Tue Jan 26, 2021 2:34 am

aMUSEd wrote:
Fri Jan 22, 2021 2:04 pm
I haven't exactly left it but I'm not upgrading until MPE works for VST3 and AU plugins as well as VST2.
VST3 implementation in general seems to be a weak point. For example:
  • S1 doesn't receive MIDI CC from VST3 plugins, e.g. Reason Rack Plugin with an LFO inside to modulate a VST further in the chain;
  • S1 doesn't see internal audio chains of multi-band plugins like klioHearts' MultiPass or UA's Triad
Both features work just fine in Bitwig or Cubase (and only the 2nd works in Live, in v10.1 at least).
Music tech enthusiast.
DAW, VST & hardware hoarder.
My "music": https://soundcloud.com/antic604

User avatar
KVRAF
32366 posts since 14 Sep, 2002 from In teh net

Post Tue Jan 26, 2021 2:54 am

antic604 wrote:
Tue Jan 26, 2021 2:34 am
aMUSEd wrote:
Fri Jan 22, 2021 2:04 pm
I haven't exactly left it but I'm not upgrading until MPE works for VST3 and AU plugins as well as VST2.
VST3 implementation in general seems to be a weak point. For example:
  • S1 doesn't receive MIDI CC from VST3 plugins, e.g. Reason Rack Plugin with an LFO inside to modulate a VST further in the chain;
  • S1 doesn't see internal audio chains of multi-band plugins like klioHearts' MultiPass or UA's Triad
Both features work just fine in Bitwig or Cubase (and only the 2nd works in Live, in v10.1 at least).
Yeah and the big problem, particularly with more modern MPE plugins like Equator 2 and Plasmonic, is these don't even come as VST2.

KVRist
346 posts since 28 Jul, 2006

Post Wed Jan 27, 2021 6:22 am

I recently moved to and some stuff is baffling to me. The midi editor will randomly show (greyed out) notes from clips that aren't selected. I only want to see the notes on the clip or track I've selected.

Selecting and moving midi notes is weird due to weird default behavior.

Not having inserts and sends in the inspector is a piss off. I rarely used the mixer view in Cubase except when starting a mix or when automating. I hate using the mixer view to deal with plugins, it's too small and I often have to scroll to find a specific insert effect if that channels has a bunch of insert plugins.

KVRist
242 posts since 12 Oct, 2003

Post Wed Jan 27, 2021 6:56 am

briefcasemanx wrote:
Wed Jan 27, 2021 6:22 am

Not having inserts and sends in the inspector is a piss off.
If you are talking about Studio One this is not true.
You can even copy inserts and sends from inspector to other tracks headers in the arrangement
Screen Shot 2021-01-27 at 16.00.21.png
You do not have the required permissions to view the files attached to this post.

User avatar
KVRAF
2066 posts since 9 Dec, 2011 from falling

Post Wed Jan 27, 2021 7:04 am

Plugin sandboxing like Bitwig would be such a welcome feature for Studio One. I've had 3 instances of plugins crashing Studio One in the last month. Drives me loco. Still not leaving Studio One, but ....

KVRist
289 posts since 11 Dec, 2017

Post Wed Jan 27, 2021 3:04 pm

billcarroll wrote:
Wed Jan 27, 2021 7:04 am
Plugin sandboxing like Bitwig would be such a welcome feature for Studio One. I've had 3 instances of plugins crashing Studio One in the last month. Drives me loco. Still not leaving Studio One, but ....
Sandboxing is a dual-edged sword to me. Yes, it was nice when I used DAWs with sandboxing and I daydream of it whenever a plugin version ends up less than stable, but every time I have to open them up again I'm reminded of just how much overhead/latency that eats up comparatively. If you make sure to set up the DAWs with/without it with identical settings otherwise, it's pretty clear to see it's a drag on overall performance.

KVRist
346 posts since 28 Jul, 2006

Post Wed Jan 27, 2021 4:33 pm

ozinga wrote:
Wed Jan 27, 2021 6:56 am
briefcasemanx wrote:
Wed Jan 27, 2021 6:22 am

Not having inserts and sends in the inspector is a piss off.
If you are talking about Studio One this is not true.
You can even copy inserts and sends from inspector to other tracks headers in the arrangement
Screen Shot 2021-01-27 at 16.00.21.png
This doesn't show up by default and when I first bought S1 I watched a video about the inspector that didn't show this. Thanks for showing me the way! Now I'm less grumpy about S1.

The midi editor behavior is still weird to me but maybe there's workarounds to my issues.

KVRAF
6822 posts since 7 Oct, 2005 from NZ

Post Wed Jan 27, 2021 5:25 pm

briefcasemanx wrote:
Wed Jan 27, 2021 4:33 pm


The midi editor behavior is still weird to me but maybe there's workarounds to my issues.
What's weird? Give us an example.
Cubase Pro 11, S1v4, Notion 6, NI, Arturia, u-he, Synapse Audio, etc.
PC, MODX 6, KeyLab MK II, ATOM, iTwo interface, DT 990 Pro and HS7 monitors.

User avatar
GRRRRRRR!
11227 posts since 14 Jun, 2001 from Somewhere else, on principle

Post Wed Jan 27, 2021 7:40 pm

briefcasemanx wrote:
Wed Jan 27, 2021 6:22 am
Not having inserts and sends in the inspector is a piss off. I rarely used the mixer view in Cubase except when starting a mix or when automating. I hate using the mixer view to deal with plugins, it's too small and I often have to scroll to find a specific insert effect if that channels has a bunch of insert plugins.
I am 100% the opposite - I hate having to have the inspector open all the time in Cubase so I can do basic things. In Studio One I have never had to use the inspector at all, not even once, which I greatly prefer. Just as in a real studio, my workflow has always been based around the mixer so I like to have the mixer window always there and I like to be able to do as much as possible from that window. I really love the way I can directly access the controls of the stock plugins from the mixer strip without having to open the FX window or inspector. It's absolutely brilliant!
NOVAkILL : Dell G7 Core i7, 32GB RAM, Win10, Zoom U24 | Studio One | Thorn, bx_oberhausen, ARP Odyssey, JP6K, Hexeract, Vacuum Pro, TRK-01, Knifonium, Equator, VG Carbon, VG Iron | Uno, Analog Keys, Ultranova, Rocket.

KVRian
1303 posts since 2 Jul, 2007

Post Wed Jan 27, 2021 9:32 pm

I have this new issue with S1 where as if I turn on my hardware after I start s1, IT JUST FREEZES and crashes S1v5 latest version.. not cool.. It never did this before..but now it's like clock work.. Any idea's on what to try? should I delete the pref's folder?
Cpu: Win10/Intel Core i9-10900K
Tools: Slate VMS/Antelope Audio Discrete 8 Synergy Core/UA Apollo X6 Ultimate 8
Synths: Roland Fantom 7/Moog Subsequent 37/Kurzweil Forte 88/Virus TI2 61/Behringer DeepMind 12D/Akai MPC X

User avatar
GRRRRRRR!
11227 posts since 14 Jun, 2001 from Somewhere else, on principle

Post Wed Jan 27, 2021 10:45 pm

Yes, I am discovering more and more that S1 does NOT like it when you change your hardware configuration while it is running. The solution is to make sure everything is switched on before you launch it or close it first if you want to switch something on.
briefcasemanx wrote:
Wed Jan 27, 2021 4:33 pm
The midi editor behavior is still weird to me but maybe there's workarounds to my issues.
Yeah, that does get a little tiresome sometimes. What you need to do is deselect all the clips, then double-click the clip you want to edit and that should get you back to just the one set of notes. It happens to me because I accidentally select a second clip when I mean to do something else but the arrangement window still has focus. Once it starts showing ghost notes, though, it's hard to stop it unless you do what I said.
NOVAkILL : Dell G7 Core i7, 32GB RAM, Win10, Zoom U24 | Studio One | Thorn, bx_oberhausen, ARP Odyssey, JP6K, Hexeract, Vacuum Pro, TRK-01, Knifonium, Equator, VG Carbon, VG Iron | Uno, Analog Keys, Ultranova, Rocket.

User avatar
KVRAF
7956 posts since 4 Jan, 2017 from Warsaw, Poland

Post Thu Jan 28, 2021 12:09 am

briefcasemanx wrote:
Wed Jan 27, 2021 4:33 pm
The midi editor behavior is still weird to me but maybe there's workarounds to my issues.
BONES wrote:
Wed Jan 27, 2021 10:45 pm
What you need to do is deselect all the clips, then double-click the clip you want to edit and that should get you back to just the one set of notes. It happens to me because I accidentally select a second clip when I mean to do something else but the arrangement window still has focus. Once it starts showing ghost notes, though, it's hard to stop it unless you do what I said.
...or just use the visibility panel in the piano roll, which lets you select which midi tracks you see and which are available for editing.

(that thing in the upper-left corner)

Image
Music tech enthusiast.
DAW, VST & hardware hoarder.
My "music": https://soundcloud.com/antic604

Return to “Hosts & Applications (Sequencers, DAWs, Audio Editors, etc.)”