Studio One 7.2

[dellboy]

I have just bought a Kurzweil K2700 keyboard and it has a built in usb audio interface and an editor app. Neither work under windows while running a daw, an essential need. Now add that I want to view a youtube video at the same time and that will not work either. If I do the same thing on a Mac with its brilliant core audio it all works. Hopefully, windows midi services will bring something similar to windows.

For the audio issues, enable 'Release Audio Device in Background' within Studio One to use your audio device in another application when Studio One is minimized. The Kurzweil audio drivers likely don't have multi-client audio support.

Thanks for the suggestion about releasing the audio device and the editor not being multiclient. After I read that I decided to try out the microsoft insider build 25 that allows windows midi services to be used. So I downloaded and installed the beta and spent some time configuring it. The result was that I now have multiclient midi and can run a number of midi devices at the same time.

[dellboy]

Yes, you are probably right. I was thinking more about the developer time that will be needed to make everything work. Maybe they could release anyway and it will start functioning when the new windows version is released.

Well - I am not a MIDI hardware maven myself - and every single thing that I do now in Studio One - WITH MIDI works perfectly.

I do not know the full story on what MIDI Services will suddenly bring to the table (outside of full support for MIDI 2.0 devices - which I have none) in Windows 11 - but I do know this has been a long time coming.

Just do not see this as being something that Presonus will hang their hat on in terms of keeping Studio One exciting or delay any releases for.

I mean - tons of S1 users use this app with no care for MIDI at all.

VP

I have now installed the microsoft beta and have multiclient midi in Studio One 6. However it has done nothing that I can see on the audio side. So it seems that Presonus and other daw developers will have to rework their audio framework to take advantage of the audio side of things.

[Vocalpoint Studios]

I have now installed the microsoft beta and have multiclient midi in Studio One 6. However it has done nothing that I can see on the audio side. So it seems that Presonus and other daw developers will have to rework their audio framework to take advantage of the audio side of things.

Do note that S1 v6 is now discontinued as well and dates back to a time well before any of this new Windows MIDI stuff was being developed. For certain - you won't see anything different with that version.

Any advantages with this (if there are any) - will need to come from a future version of S1

VP

[dellboy]

I have now installed the microsoft beta and have multiclient midi in Studio One 6. However it has done nothing that I can see on the audio side. So it seems that Presonus and other daw developers will have to rework their audio framework to take advantage of the audio side of things.

Do note that S1 v6 is now discontinued as well and dates back to a time well before any of this new Windows MIDI stuff was being developed. For certain - you won't see anything different with that version.

Any advantages with this (if there are any) - will need to come from a future version of S1

VP

You ask if there is any advantage to multiclient midi.

Well, currently I have Cubase, Reaper, Studio One, Waveform, and Bitwig all open at the same time and playing back some audio I have just recorded independently in each of them. I also have my keyboard editor open and making changes while I play back music in Youtube. All on windows 11. All using a cheap consumer grade audio interface. No expensive RME interface needed. Pretty impressive I think. Previously we had to buy a Mac to do this.

An Apple Mac machine adds "aggregate audio" to the mix allowing more than one audio interface at a time, and I have yet to find a way to achieve the same result in Windows Midi Service, but maybe its coming.

[Fidelitymusic]

An Apple Mac machine adds "aggregate audio" to the mix allowing more than one audio interface at a time, and I have yet to find a way to achieve the same result in Windows Midi Service, but maybe its coming.

You can do that with ASIO4ALL, but it's nowhere near CoreAudio's reliability and ease of use.

[dellboy]

An Apple Mac machine adds "aggregate audio" to the mix allowing more than one audio interface at a time, and I have yet to find a way to achieve the same result in Windows Midi Service, but maybe its coming.

You can do that with ASIO4ALL, but it's nowhere near CoreAudio's reliability and ease of use.

Core Audio is amazing.

[Branis]

An Apple Mac machine adds "aggregate audio" to the mix allowing more than one audio interface at a time, and I have yet to find a way to achieve the same result in Windows Midi Service, but maybe its coming.

I recently purchased VB-Audio’s Matrix Coconut for this purpose. It works flawlessly once set up.

[thievedletter]

It had SUCH potential...

Versions 3 and 4 made it seem like S1 would take over the industry. Now I wouldn't be surprised if they discontinued it next year.

A tragedy, really.

That's how I felt, when I got into Studio One. Felt like getting in on the ground floor of the DAW that was going to take over.

As someone that migrated from Cakewalk Sonar... Maybe I just have terrible luck.

Sorry for bringing this down on you all!

[tonedef71]

Doh!

The PreSonus developers have been hard at work releasing updates all along. We'd just been looking in the wrong place. Silly us.

[ffx]

WTF, so they are wasting their dev time on nonsense marketing features?

[HcDoom]

This is where our promised 3-4 major updates ended up…

[Digivolt]

Studio One gets changed to Fender Studio Professional in a few weeks, I joke, but it's sadly entirely possible

[jonljacobi]

Why sad about that?

[J Veronica]

Anyone else had midi controller issues with S1?

Tried to get a Behringer X Touch Mini set up and the S1 Midi Learn can't see any buttons or switches, just the rotary encoders.

What annoys me is the midi monitor in S1 is definitely picking up everything.

In Reaper everything immediately worked and was assignable. With much deeper options for integration.

Is Midi controller integration in Studio One just shit?

I'm on v6 so maybe it's better in V7.

[tonedef71]

Is Midi controller integration in Studio One just shit?

One frustrating quibble I have with the integration between my Korg NanoKey 2 MIDI controller and Studio One, is that Studio One is only able to recognize the MIDI controller when it is already plugged in to my PC before Studio One starts up. If I plug the NanoKey 2 into my PC after Studio One is up and running, Studio One fails to detect the controller when attempting to scan for new MIDI devices.

My issue is different from yours in that the behavior of the MIDI controller is the same in all of the MIDI applications that I use it with -- not just Studio One. I believe the MIDI controller issue that I deal with has to do with the way Korg implemented the USB driver (which may be due to the way the MIDI controller hardware itself was implemented).