Why did you leave Studio One?

Audio Plugin Hosts and other audio software applications discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

apoclypse wrote: Mon Dec 28, 2020 5:23 pm
oneway wrote: Sun Dec 27, 2020 6:59 pm Sure, it’s easy, but it could be a lot easier for MIDI. Currently, you can’t drag multiple MIDI parts to the browser at once as separate files. Drag/drop or not, many other programs have a batch export feature.
Yeah. I wish they would address this at some point.
Then, when you drag MIDI data back into the arrange view, it will often open a new song without asking. Presonus have known about that for years, no clue why they’ve never fixed it.
How are you dragging the midi into S1? If you drag the file into the top area like the ruler it will try to open the midi file as a new song if you drag it directly into the arranger it will drag in the midi.
Directly the arranger area. It either has to do with the file size or the MIDI file type number. I’ve asked support about it before, they have acknowledged that yes, they have asked the developers to address it before and no, it has not been addressed yet.

Post

I left Studio One maybe 8 years ago because FL Studio has a better piano roll. Then I moved to Live recently, and now I'm transitioning back to Studio One. I agree that Studio One is where people end up more than leave; even when I used FL I think I admitted that Studio One was a "better" all-around DAW. Fantastic piece of software (FL is great too)
"FriendZone"

Post

oneway wrote: Mon Dec 28, 2020 5:25 pm
apoclypse wrote: Mon Dec 28, 2020 5:23 pm
oneway wrote: Sun Dec 27, 2020 6:59 pm Sure, it’s easy, but it could be a lot easier for MIDI. Currently, you can’t drag multiple MIDI parts to the browser at once as separate files. Drag/drop or not, many other programs have a batch export feature.
Yeah. I wish they would address this at some point.
Then, when you drag MIDI data back into the arrange view, it will often open a new song without asking. Presonus have known about that for years, no clue why they’ve never fixed it.
How are you dragging the midi into S1? If you drag the file into the top area like the ruler it will try to open the midi file as a new song if you drag it directly into the arranger it will drag in the midi.
Directly the arranger area. It either has to do with the file size or the MIDI file type number. I’ve asked support about it before, they have acknowledged that yes, they have asked the developers to address it before and no, it has not been addressed yet.
Okay. I haven't run into that particular issue in a while so I assumed it was resolved.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

I really liked the overall feel of studio one. But the audio stretching was broken and made it unusable. I'm on Ableton now. There are some things I definitely miss like ghost clips and macros but I make it work.

Post

[nx] wrote: Mon Dec 28, 2020 5:42 pm I really liked the overall feel of studio one. But the audio stretching was broken and made it unusable. I'm on Ableton now. There are some things I definitely miss like ghost clips and macros but I make it work.
My main issue with timestretch on S1 is the limited algorithms and types compared to Bitwig, Ableton, and Logic. Transient detection is a bit wonky too. They should really address this.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

wuworld wrote: Sat Oct 24, 2020 7:18 pm Why did you leave Studio One?
There was a burning desire to fuel my G.A.S., as my addictive personality was easily persuaded.

Post

apoclypse wrote: Mon Dec 28, 2020 5:45 pm
[nx] wrote: Mon Dec 28, 2020 5:42 pm I really liked the overall feel of studio one. But the audio stretching was broken and made it unusable. I'm on Ableton now. There are some things I definitely miss like ghost clips and macros but I make it work.
My main issue with timestretch on S1 is the limited algorithms and types compared to Bitwig, Ableton, and Logic. Transient detection is a bit wonky too. They should really address this.
If I remember correctly there was a brief period where they added a new zplane update that was really buggy. It's understandable that a third party library they license has a bug, but it was still annoying as the problem got fixed pretty slowly. Even though it's not how it works, I like to imagine two Support teams for Presonus and Zplane asking each other if they've tried reinstalling each others' software :lol:

With time stretching and transient detection, I've found them good but they have some unconnected dots. They use the same zplane algorithms as other DAWs but didn't make a few more variations on them like other DAWs seem to have done. I personally didn't like REAPER's approach of just opening up all the settings to the user, but Live's variations for different program material (beyond the Drums/Sound/Solo algorithms) was nice.

As for transient detection, I've actually find it to be good, but again they didn't connect the dots for different situations. Auto transient detection only has one setting, but there are a few places in the program (Impact import) where you can only use auto transient detection. And they (as far as I can tell) accidentally reversed the quantize behavior of transient bands mid-3.0. They haven't fixed it for so long that I'm guessing it has become "the way it's always been, right?" :wink: Again, sounds good, but some unconnected dots.

Post

oneway wrote: Mon Dec 28, 2020 6:23 pm...They haven't fixed it for so long that I'm guessing it has become "the way it's always been, right?" :wink: Again, sounds good, but some unconnected dots.
Ironic with respect to the discussion in the other thread :D
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

antic604 wrote: Mon Dec 28, 2020 6:26 pm
oneway wrote: Mon Dec 28, 2020 6:23 pm...They haven't fixed it for so long that I'm guessing it has become "the way it's always been, right?" :wink: Again, sounds good, but some unconnected dots.
Ironic with respect to the discussion in the other thread :D
The transient band issue, if you go back and look at release notes, was an actual bug with Slicing. It was quantizing to the wrong point of the Slice (and consequently Transient Bands). When they fixed it, they only fixed it for one and not the other. Release notes said it was fixed, the people who were only using Slicing said "works great," and here we are.

Post

Serious question, what do you use transient detection for? Is it to do with time stretching? I've never used, nor had a use for, time stretching and if I did I think I'd want to do it non-realtime in Audition or somewhere like that, not in my sequencer.
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron

Post

BONES wrote: Tue Dec 29, 2020 2:41 am Serious question, what do you use transient detection for? Is it to do with time stretching? I've never used, nor had a use for, time stretching and if I did I think I'd want to do it non-realtime in Audition or somewhere like that, not in my sequencer.
In my case mostly for slicing drums if I don’t feel like slicing manually. Otherwise it’s most for time stretching even though I do through this manually as well since S1 transient detection imo is not very good. Sometimes its way off especially on drums.
Studio One // Bitwig // Logic Pro // Ableton // Reason // FLStudio // MPC // Force // Maschine

Post

BONES wrote: Tue Dec 29, 2020 2:41 am Serious question, what do you use transient detection for? Is it to do with time stretching? I've never used, nor had a use for, time stretching and if I did I think I'd want to do it non-realtime in Audition or somewhere like that, not in my sequencer.
Time stretching in conjunction with quantizing, and sample slicing and rearranging. Transient detection is also used when you drag a loop into Impact and select Spread Across Multiple Pads, but I use Serato Sample for that now anyway.

Audio Bend is faster, but the quirks they’ve left in it has me using Melodyne for the first two more and more. Presonus hasn’t updated/improved Audio Bend in a long time and they keep emphasizing their Melodyne support so I’m taking the hint, so to speak ;)

I don’t like taking files in and out of external audio editors if I don’t have to. It’s more immediate in the Arrange View/Audio Editor/ARA window, and quality-wise outside of Melodyne almost everyone is just licensing zplane afaict.

Post

It's something I do so very, very rarely that taking it outside of my host wouldn't be an issue. In fact, slicing a loop is something I think I have only ever done as a beta-tester, to make sure it worked as advertised. I can't imagine ever having a use for it in my actual work, especially now, in the face of the thousands and thousands of drum samples we got with Battery/Komplete. I probably haven't previewed even one-tenth of them, there are so many.
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron

Post

I slice audio all of the time. It's one of the primary things I do with multi-track drum recordings with many takes. Slicing and dicing them together to comp the best performance.... transient detection really helps speed that up.
My Youtube Channel - Wires Dream Disasters

Post

That's why I have around a dozen different drum instruments - perfect timing first time, every time.
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron

Post Reply

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