KVR Audio

graspee · Post by **graspee** » Sat Jul 18, 2020 2:56 am

Another thing that annoys me is that S1 5 STILL doesn't work with FL ASIO. It hasn't ever worked with it AFAIK. It's not just me either, other people have reported it.

tonedef71 · Post by **tonedef71** » Sat Jul 18, 2020 3:29 am

graspee wrote: Sat Jul 18, 2020 2:56 am Another thing that annoys me is that S1 5 STILL doesn't work with FL ASIO. It hasn't ever worked with it AFAIK. It's not just me either, other people have reported it.

In what way does FL ASIO not work in Studio One Pro?

lfm · Post by **lfm** » Sat Jul 18, 2020 6:59 am

WatchTheGuitar wrote: Tue Jul 14, 2020 6:53 am lfm, are you using ReWire to run the SysEx in another DAW now?

Sorry, I missed your post.

No Cakewalk by Bandlab has full sysex support, both sysex manager and can record on track.

But in StudioOne I used a plugin https://Ctrlr.org where I could add buttons to a gui and assign sysex to those. Quite cool, I did knobs too that vary a parameter in the sysex sequence. So I could send to set parameters for Rhodes effects like tremolo or phaser to piano.

So I had that barried in the project and activated when I started a session.

So sysex can travel through to midi ports this way.

Then I swapped piano to Kawai MP7SE and never needed to do this, all could be done through panel on that piano. But I use for synths to just dump sysex in Cakewalk.

WatchTheGuitar · Post by **WatchTheGuitar** » Sat Jul 18, 2020 7:45 am

Nice. The original 12 Tones Cakewalk was my first home MIDI DAW, that and an AWE 32 card with a Yamaha daughter-board and occasional version upgrades lasted me for a good few years. I wish every DAW had as good MIDI editing capabilities. Think they’re so good in Cakewalk because they had to be, it used to be the whole enchilada.
So easy to tweak stuff in the event viewer or run a quick and easy CAL script.
I only moved away from Sonar when the Gibson stuff happened and bought a number of other DAWs to audition long term as a replacement.

Kalonai · Post by **Kalonai** » Sat Jul 18, 2020 8:19 am

graspee wrote: Sat Jul 18, 2020 2:56 am Another thing that annoys me is that S1 5 STILL doesn't work with FL ASIO. It hasn't ever worked with it AFAIK. It's not just me either, other people have reported it.

Why would you use FL ASIO though? What's wrong with ASIO4ALL, or even better, your audio interface (if you have one) driver?

lfm · Post by **lfm** » Sat Jul 18, 2020 8:27 am

Yeah, I had Cakewalk Pro 3.0 late 80's with a MusicQuest soundcard/midi interface or something, on MSDOS.
Already then had sysex manager.

So how it's missing in modern daws is a mystery. Most allow to record on track, but not allowing that even is strange. At least StudioOne have support for it in built in midi monitor, which is cool. So as I did send from a plugin worked.

Looking Behringer Neutron, it was heavily relying on sysex stuff for many things. It's part of every synth, and other rack units like amps that have presets also do some I had, like Marshall JMP1 rack unit.

WatchTheGuitar · Post by **WatchTheGuitar** » Sat Jul 18, 2020 8:31 am

It can get lonely being command line people in a drag and drop world.
Easier is not equal to faster or better.

Back to Studio One - what's the end date on the current v5 intro sale?

Trancit · Post by **Trancit** » Sat Jul 18, 2020 9:01 am

tonedef71 wrote: Sat Jul 18, 2020 3:29 am
graspee wrote: Sat Jul 18, 2020 2:56 am Another thing that annoys me is that S1 5 STILL doesn't work with FL ASIO. It hasn't ever worked with it AFAIK. It's not just me either, other people have reported it.
In what way does FL ASIO not work in Studio One Pro?

It works without any problems... I use it since years without any issues at all...
And as already mentioned there is always ASIO4All too and if both don´t work it´s obvious that´s a different problem with the machine and not with the software...

oneway · Post by **oneway** » Sat Jul 18, 2020 2:32 pm

lfm wrote: Tue Jul 14, 2020 3:59 am First change of midi cc is recorded on clip and sent at start of clip instead - not when you started tweaking. For me this was showstopper - maybe no problem for others.

Personally I prefer the current behavior for 80% of situations. It should be an *option* in the MIDI section like other DAWs, as it depends on what parameters you are automating in what instrument. Most of the time the behavior you’re asking for with your specific case of on/off automation would not be my preference, so really an option is all that is needed.

graspee · Post by **graspee** » Mon Jul 27, 2020 3:24 pm

Trancit wrote: Sat Jul 18, 2020 9:01 am
tonedef71 wrote: Sat Jul 18, 2020 3:29 am
graspee wrote: Sat Jul 18, 2020 2:56 am Another thing that annoys me is that S1 5 STILL doesn't work with FL ASIO. It hasn't ever worked with it AFAIK. It's not just me either, other people have reported it.
In what way does FL ASIO not work in Studio One Pro?
It works without any problems... I use it since years without any issues at all...
And as already mentioned there is always ASIO4All too and if both don´t work it´s obvious that´s a different problem with the machine and not with the software...

Well it's not just me for whom FL Asio does not work.
It's not a problem with the machine since 5 other DAWs on here work with FL Asio.
To answer earlier posts, why would I use it over ASIO4ALL is because I want to hear other audio while using Studio One and I want to be able to sample from the stereo mix output of the pc.
Another person asked in what way does it not work well there's no sound and the transport will not move.

VariKusBrainZ · Post by **VariKusBrainZ** » Mon Jul 27, 2020 5:04 pm

Reports it to Presonus or get a suitable soundcard.

chk071 · Post by **chk071** » Mon Jul 27, 2020 5:12 pm

VariKusBrainZ wrote: Mon Jul 27, 2020 5:04 pm Reports it to Presonus or get a suitable soundcard.

Not sure if it'll be high priority for them.

graspee · Post by **graspee** » Mon Jul 27, 2020 5:53 pm

VariKusBrainZ wrote: Mon Jul 27, 2020 5:04 pm Reports it to Presonus or get a suitable soundcard.

It's not my soundcard. I repeat 5 other DAWs work with FL Asio on the same computer.

WatchTheGuitar · Post by **WatchTheGuitar** » Mon Jul 27, 2020 5:57 pm

graspee wrote: Mon Jul 27, 2020 5:53 pm
VariKusBrainZ wrote: Mon Jul 27, 2020 5:04 pm Reports it to Presonus or get a suitable soundcard.
It's not my soundcard. I repeat 5 other DAWs work with FL Asio on the same computer.

Steals a sound card and wants support for it? smh

/s

lfm · Post by **lfm** » Mon Jul 27, 2020 6:42 pm

graspee wrote: Mon Jul 27, 2020 3:24 pm It's not a problem with the machine since 5 other DAWs on here work with FL Asio.
To answer earlier posts, why would I use it over ASIO4ALL is because I want to hear other audio while using Studio One and I want to be able to sample from the stereo mix output of the pc.
Another person asked in what way does it not work well there's no sound and the transport will not move.

Reminds me of some conflict when 2 software use the same audio drivers and ports or something. Usually you tell daws to either grab exclusive ownership or to release driver when loosing focus etc.

I solved it once by setting other drivers for Windows, so media player would work with that and I could use asio for daw.

There is usually problems involving sample rate as well, that one app run 48k like for YT and another do 44k in daw etc - I had strange issues with that. In Reaper and Sonar and other daws too. Reaper screemed not getting the driver up when started, Sonar just changing playrate wrong suddenly.

Software made for grabbing into media are screen recorders, they can capture what is heard at the same time. Most o the time I just loop back output to another input and record.

So would not say it is a bug at all - just a common conflict of interest. Some drivers will allow some things, others not.

Look into screen recorders or if there is similar for audio alone. Capturing that you can access that later.

Studio One Version 5.0 Predictions and Requests