Studio One 7.2

[jamcat]

Tuner² is awesome and universally useful. I’d much rather have it than some niche Native Instruments controller thing.

[Fornicras]

Tuner² is awesome and universally useful. I’d much rather have it than some niche Native Instruments controller thing.

I don't know if this is satire or for real.

[jamcat]

Well, I use Studio One's tuner. It's even part of my template. I don't really know what Native Instruments Kontrol is, but I seriously doubt it is relevant to me since I don't own anything from Native Instruments.

[stanft]

It is not only Native Instruments. Arturia has abandoned S1 support in their current controllers, too. All other DAWs are supported though.

[Digivolt]

It is not only Native Instruments. Arturia has abandoned S1 support in their current controllers, too. All other DAWs are supported though.

They haven't abandoned support, it's a Presonus issue when it comes to supporting the controllers custom scripts as far as I understand it, certainly at least in the case of Native Instruments

[stanft]

They haven't abandoned support, it's a Presonus issue when it comes to supporting the controllers custom scripts as far as I understand it, certainly at least in the case of Native Instruments

The result is the same. What do we get instead? New ROMplers as major features that nobody needs.

I would be okay with a missing controller integration if they concentrated on important stuff like fixing the delay compensation for external instruments that has been broken for years now.

[Digivolt]

The result is the same.

I guess, but it's unfair to blame the likes of NI or Arturia for loss of support when they update their hardware, it's the fault of Presonus who may or may not be holding back support for a future update to encourage users to pay for another year of updates

[Fornicras]

It is not only Native Instruments. Arturia has abandoned S1 support in their current controllers, too. All other DAWs are supported though.

It feels like my curse.
I used FL Studio for a while, and almost no controller supported it; it wasn't even listed as "works in xxx DAW" section of the controller.
Then I switched to S1, and now all of a sudden the same thing happens for S1 while they write FL Studio supported or even have a custom script for almost every new controller.

[stanft]

I guess, but it's unfair to blame the likes of NI or Arturia for loss of support when they update their hardware, it's the fault of Presonus who may or may not be holding back support for a future update to encourage users to pay for another year of updates

I didn't want to blame NI or Arturia ... I'm with you that Presonus is the problem here. That's also the reason why I have cancelled my Presonus subscription. The last year was really disappointing. Instead, I have switched back to Cubase/Ableton and couldn't be happier.

[Vocalpoint Studios]

I guess, but it's unfair to blame the likes of NI or Arturia for loss of support when they update their hardware, it's the fault of Presonus who may or may not be holding back support for a future update to encourage users to pay for another year of updates

I do not for a moment think that Presonus is blatantly (and on purpose) suddenly deciding to "hold back" anything in order to get me to pay for another year of updates. OR to drop support for any controllers. Especially in the case of NI and their new MKIII v2.0.5 firmware.

From what I understand - there is a ***t-load of scripting and other work that needs to be done to support this new FW and that takes time.

S1 is (if history serves) headed to a major v7.5 update here this fall and I would be shocked if this update does not include all the tasty integrations that this firmware brings.

Just because a vendor does not support a new firmware on Day 1 - is not a reason to assume everything has gone to s**t. This stuff takes time to get right - espeically with the userbase of the NI controllers.

Would rather have Presonus do their usual excellent job instead of trying to rush something out the door - just cause it's "there".

As far as the "updates" renewal goes - we are all adults (I hope) and each can decide for ourselves if renewing is a good thing or not.

You certainly are not being forced to do anything - you can carry on with your perpetual license forever if you choose to.

VP

[stanft]

[..] Would rather have Presonus do their usual excellent job instead of trying to rush something out the door - just cause it's "there". [..]

Arturia's Keylab mk3 has been out for a year now. The Keylab Essential mk3 was released in May 2023, the Arturia Minilab 3 in October 2022 - that's nearly three years. I would not call it "to rush something out" if these were supported now. All "major DAWs" are supported ... Cubase, Logic, Live, FL Studio, Bitwig ... even Reason is supported. It seems like S1 is no longer a "major DAW".

I know that there are features that may be more relevant to others. But we are talking about controller support ... and I guess that a lot of S1 users do use at least one controller keyboard in their setup. Especially as there are better DAWs than S1 if you have a lot of hardware and do not rely on plugins (and controllers). And if I could choose between 2-3 ROMplers or a proper support for the current controllers on the market, I would choose the latter.

[Vocalpoint Studios]

Arturia's Keylab mk3 has been out for a year now. The Keylab Essential mk3 was released in May 2023, the Arturia Minilab 3 in October 2022 - that's nearly three years. I would not call it "to rush something out" if these were supported now.

Can't speak to Arturia specifically. And of course I understand that this burns you to some degree - but you have no idea why Presonus is choosing to handle (or not handle as it were) Arturia this way.

That said - assuming that it should "just happen" - because "other DAWs" have it - has no bearing on anything.

Where is it stated that every DAW has to fully support every controller? There could be a half dozen reasons why things are the way they are. Only Presonus knows for certain - but I would be very surprised if it is malicious in any way.

VP

[thievedletter]

Tuner² is awesome and universally useful. I’d much rather have it than some niche Native Instruments controller thing.

Kinda misses the point that the Tuner already existed in its most universal form already (i.e. chromatic) and has for years.

[jamcat]

Tuner² is awesome and universally useful. I’d much rather have it than some niche Native Instruments controller thing.

Kinda misses the point that the Tuner already existed in its most universal form already (i.e. chromatic) and has for years.

My comment was in direct reply to someone saying "They must be busy refining the tuner" as to why there isn't support for the latest Kontrol update. I think Fender/PreSonus knows their userbase, and I'm sure more people use the Tuner than use Kontrol scripts(?) or whatever it is that owners of NI controllers want. That's not to say Kontrol support won't get updated, but to me and most Studio One users, the Tuner is more useful and central to working in Studio One, and any refinements are welcome.

I actually only recently started using it, and only because the Tuner² update brought it to my attention. I had always used AmpliTube's tuner, and then the one in TONEX, but I like having the tuner in an insert on my audio input channel, and recently added it to my template. It's been a really valuable addition to my workflow.

[thievedletter]

but to me and most Studio One users, the Tuner is more useful and central to working in Studio One, and any refinements are welcome.

Yeah, I'm not sure when you were elected to represent "most" users, considering you mentioned you just started using it. You even proved how redundant it is in your comment.