Studio One 7.2

[summer2000]

It's just a matter of Studio One being designed for multi-track audio recording. I think that's pretty self-evident. Everything people complain about regarding Studio One has to do with it not being designed for pre-fab loop construction production.

I moved to Studio One because it is designed for the type of work I do, and it works brilliantly for it. I AM IN THE RIGHT PLACE. YOU ARE NOT. It's not designed for the way loop producers work. Clearly. Or they wouldn't be constantly whinging and whining. They really should just f*ck off and go to Bitwig or Ableton instead of trying to hijack a DAW that is clearly not for them.

And soon many of those Studio One whingers and whiners might be contemplating on migrating to Cubase Pro 15. I'll leave it at that since I am not at liberty to elaborate on it at the moment. Patience Daniel-San. The best is yet to come.

[SeeingInMidi]

It's just a matter of Studio One being designed for multi-track audio recording. I think that's pretty self-evident. Everything people complain about regarding Studio One has to do with it not being designed for pre-fab loop construction production.

I moved to Studio One because it is designed for the type of work I do, and it works brilliantly for it. I AM IN THE RIGHT PLACE. YOU ARE NOT. It's not designed for the way loop producers work. Clearly. Or they wouldn't be constantly whinging and whining. They really should just f*ck off and go to Bitwig or Ableton instead of trying to hijack a DAW that is clearly not for them.

And soon many of those Studio One whingers and whiners might be contemplating on migrating to Cubase Pro 15. I'll leave it at that since I am not at liberty to elaborate on it at the moment. Patience Daniel-San. The best is yet to come.

Hope this isn't bait because this year has been underwhelming so far in terms of S1 updates.

[thievedletter]

It's just a matter of Studio One being designed for multi-track audio recording. I think that's pretty self-evident. Everything people complain about regarding Studio One has to do with it not being designed for pre-fab loop construction production.

I moved to Studio One because it is designed for the type of work I do, and it works brilliantly for it. I AM IN THE RIGHT PLACE. YOU ARE NOT. It's not designed for the way loop producers work. Clearly. Or they wouldn't be constantly whinging and whining. They really should just f*ck off and go to Bitwig or Ableton instead of trying to hijack a DAW that is clearly not for them.

The fact that you are arguing with people that have obviously been using the software much longer than you is pretty funny. Studio One has been catering to the sample using crowd for at least the last couple versions. I don't use samples much, but anyone who has actually been using Studio One for awhile would know this.

It's honestly pretty eventful to see this level of gatekeeping in the wild.

[jamcat]

The fact that you are arguing with people that have obviously been using the software much longer than you is pretty funny.

That's pretty unlikely. I've been using Studio One since 2010.

[wikter]

Studio One has been catering to the sample using crowd for at least the last couple versions. I don't use samples much, but anyone who has actually been using Studio One for awhile would know this.
It's honestly pretty eventful to see this level of gatekeeping in the wild.

S1 has been always oriented to LINEAR sequencing and it has still issues and lack sequencing patterns and assigning controllers. One of the problems about this is the controller integration. They don't have published manual to create those control device files, they probably rely on a single person to create it and it's not an easy task.
And without an open hardware integration, it's hard to compete with Ableton/Bitwig.
But it's a really stupid path from Presonus. Some of us asked them to publish the specs to format those XML and they never released a paper other than the plane user device creation which is a really limited way to access internals.
The way S1 automation works is more complex than Ableton/Bitwig. S1 has Global & Local modes, Local works as any Ableton controller, Global does it in a different way. (maybe Ableton has a Global Mode using scripts, bu I never found the way to do it... )

[stanft]

S1 has been always oriented to LINEAR sequencing and it has still issues and lack sequencing patterns and assigning controllers. One of the problems about this is the controller integration. They don't have published manual to create those control device files, they probably rely on a single person to create it and it's not an easy task.
And without an open hardware integration, it's hard to compete with Ableton/Bitwig. [..]

Ableton and Bitwig may be not the only competitors. Cubase‘s controller integration has been rebuilt from the ground up two major versions ago. And now it is really capable, programmable and documented! They even provide direct support for developers in their forums.

[thievedletter]

That's pretty unlikely. I've been using Studio One since 2010.

But didn't know it had a Tuner?

[ozinga]

The fact that you are arguing with people that have obviously been using the software much longer than you is pretty funny.

That's pretty unlikely. I've been using Studio One since 2010.

Why is it unlikely? How do you know?
I've been using since V1 and beta testing since V3

[jamcat]

That's pretty unlikely. I've been using Studio One since 2010.

But didn't know it had a Tuner?

You completely misrepresented what I said. I didn’t say I didn’t know about it. I said using it on an input was recently brought to my attention. Specifically, by this video from Joe:

[jamcat]

I've been using since V1 and beta testing since V3

Neat!
What’s coming in the next version? And when?

[J Veronica]

I spent my Friday noodling around with the chord track. It's more intuitive than I thought and I had a lot of fun with it.

If they added chord inversions to the chord selector I'd be even happier Maybe there is a way and I missed it.

[Aaron Pom]

I think it’s in the Root note option?

IMG_1949.jpeg

[J Veronica]

I think it’s in the Root note option?

Thanks. I had a look and didn't find that option. I guess it's no bother to move notes manually in the piano roll

[Crossinger]

I think it’s in the Root note option?

Thanks. I had a look and didn't find that option. I guess it's no bother to move notes manually in the piano roll

If you are willing to spend a few extra bucks on 3rd-party scripts and macros, then Harmony Wizard is worth a look:

https://manual.studioonescripts.com/harmonywizard

It also includes chord inversion. The link above points to the interactive manual.

[J Veronica]

I think it’s in the Root note option?

Thanks. I had a look and didn't find that option. I guess it's no bother to move notes manually in the piano roll

If you are willing to spend a few extra bucks on 3rd-party scripts and macros, then Harmony Wizard is worth a look:

https://manual.studioonescripts.com/harmonywizard

It also includes chord inversion. The link above points to the interactive manual.

Thanks. Harmony Wizard looks killer, but I only need the one macro, heh.

Hopefully Presonus will natively expand the piano roll macro options in the future.