Studio One 7.2

[SeeingInMidi]

This just brings up another issue, why doesnt s1 have internal midi routing yet.

For what specific purpose? (not that I‘m denying the need). But, e.g., it’s already possible to redirect a track lane (with a MIDI Arp) to another track lane.

Assigning midi from one plugin to another, such as Midishaper and Melda MCCGenerator

[Crossinger]

This just brings up another issue, why doesnt s1 have internal midi routing yet.

For what specific purpose? (not that I‘m denying the need). But, e.g., it’s already possible to redirect a track lane (with a MIDI Arp) to another track lane.

Assigning midi from one plugin to another, such as Midishaper and Melda MCCGenerator

Ah, okay. You mean direct connectivity without the workaround of track redirecting.

[wikter]

Can I do it with audio tracks?

As long as you have an audio>MIDI Converter, of course. You could do It with samples within Impact. MIDI is really cheap spec.
But it's easier using a MIDI loopback utility.
Start with this:
https://www.tobias-erichsen.de/software/loopmidi.html

Next step, learn how to create your own custom devices. This is not in the manual, not even specced. It's something you can do by editing XML files.

This just brings up another issue, why doesnt s1 have internal midi routing yet.

Rerouting MIDI internally is possible. Rerouting to an "external device" is done by tricking with external loopback, but it's a different way because in a device the same Control can perform different functions. MIDI Loopback utils exist since Windows 95 and even before. The range of loopback applications is limited even inside experimental rigs because the trend is to integrate everything in a single application.
For those rare cases when you need a loopback, you can rely on external apps

[SeeingInMidi]

Can I do it with audio tracks?

As long as you have an audio>MIDI Converter, of course. You could do It with samples within Impact. MIDI is really cheap spec.
But it's easier using a MIDI loopback utility.
Start with this:
https://www.tobias-erichsen.de/software/loopmidi.html

Next step, learn how to create your own custom devices. This is not in the manual, not even specced. It's something you can do by editing XML files.

This just brings up another issue, why doesnt s1 have internal midi routing yet.

Rerouting MIDI internally is possible. Rerouting to an "external device" is done by tricking with external loopback, but it's a different way because in a device the same Control can perform different functions. MIDI Loopback utils exist since Windows 95 and even before. The range of loopback applications is limited even inside experimental rigs because the trend is to integrate everything in a single application.
For those rare cases when you need a loopback, you can rely on external apps

I know, but im just saying S1 should support midi routing natively. i
I couldnt name you one other DAW that does not support this feature natively.

[wikter]

I couldnt name you one other DAW that does not support this feature natively.

Curious...
How do other DAW support script automation?

[Bowsy]

Last I checked it still had the latency problem that's been around since 2015. Midi track out to Midi track in internaly between two plugins. Arp to VSTI for example. If any of the plugins produce latency it throws the ARP playback out of sync with the host by the same amount of latency, add more plugins to the inserts with higher latency and it jumps to the higher amount. It plays in via midi controller and prints out fine but DAW playback sync is out of wack with other tracks in the project. Doesn't matter what you use third party as long as latency is present. The built in midi FX obviously work a little different in S1 as they get dumped onto the same Instrument track. Can't say I have actually used those in a few years but that's how I remember it.

It worked perfectly fine upto the point they added Dropout Protection and Low-Latency Monitoring. At least that's when I noticed it. If they fixed it great but it was still present in V6 when I checked. It's been brought up many times but that got brushed under the carpet like the old forum exactly were some of us repeatedly told them about it.

Still on the fence with this company for obvious reasons, cheap update prices don't alter the fact I've yet to see anything they promised other than a price hike at the pre launch of 7. Play series type Instruments every update don't do it for me either.

I decided to wait 12 month and see how it pans out with the Fender direction. I still Like S1 and use V6 along with Cubase.

[wikter]

Last I checked it still had the latency problem that's been around since 2015. Midi track out to Midi track in internaly between two plugins. Arp to VSTI for example. If any of the plugins produce latency it throws the ARP playback out of sync with the host by the same amount of latency, add more plugins to the inserts with higher latency and it jumps to the higher amount. It plays in via midi controller and prints out fine but DAW playback sync is out of wack with other tracks in the project. Doesn't matter what you use third party as long as latency is present. The built in midi FX obviously work a little different in S1 as they get dumped onto the same Instrument track. Can't say I have actually used those in a few years but that's how I remember it.

It worked perfectly fine upto the point they added Dropout Protection and Low-Latency Monitoring. At least that's when I noticed it. If they fixed it great but it was still present in V6 when I checked. It's been brought up many times but that got brushed under the carpet like the old forum exactly were some of us repeatedly told them about it.

Still on the fence with this company for obvious reasons, cheap update prices don't alter the fact I've yet to see anything they promised other than a price hike at the pre launch of 7. Play series type Instruments every update don't do it for me either.

I decided to wait 12 month and see how it pans out with the Fender direction. I still Like S1 and use V6 along with Cubase.

What about disabling drop protection??

[Bowsy]

Last I checked it still had the latency problem that's been around since 2015. Midi track out to Midi track in internaly between two plugins. Arp to VSTI for example. If any of the plugins produce latency it throws the ARP playback out of sync with the host by the same amount of latency, add more plugins to the inserts with higher latency and it jumps to the higher amount. It plays in via midi controller and prints out fine but DAW playback sync is out of wack with other tracks in the project. Doesn't matter what you use third party as long as latency is present. The built in midi FX obviously work a little different in S1 as they get dumped onto the same Instrument track. Can't say I have actually used those in a few years but that's how I remember it.

It worked perfectly fine upto the point they added Dropout Protection and Low-Latency Monitoring. At least that's when I noticed it. If they fixed it great but it was still present in V6 when I checked. It's been brought up many times but that got brushed under the carpet like the old forum exactly were some of us repeatedly told them about it.

Still on the fence with this company for obvious reasons, cheap update prices don't alter the fact I've yet to see anything they promised other than a price hike at the pre launch of 7. Play series type Instruments every update don't do it for me either.

I decided to wait 12 month and see how it pans out with the Fender direction. I still Like S1 and use V6 along with Cubase.

What about disabling drop protection??

It makes no difference. It was pesent before V3 then they fixed it and broke it again towards the end of V3 if memory serves me right. I'm not even 100% sure DP LLC caused it second time round I just remember it never worked again like it did in the early revisions of V3 around the time they introduced it. I moved from Cubase at the time as S1 was tight with regards to syncing internally. The subject was brought up enough on the old forums, pretty much after every major release. It was pointed out by a plugin maker who I won't mention with regards to one of his plugins. The post is still in the support section to this day.


"May 19, 2015
Studio One has had a bug for a long time now that realtime MIDI sent from plugins is erratic by the buffer size, although I believe it records precisely. Lowering your audio buffer size should reduce the erratic timing, but the best thing obviously would be for them to fix this"

Use zero latency plugins and your fine, it's probably why a lot of people never noticed it using low latency plugins then printing out, but it's there alright.

[Bowsy]

If they fixed this in V7 I will hold my hands up and purchase it today.

[jamcat]

It makes no difference. It was pesent before V3 then they fixed it and broke it again towards the end of V3 if memory serves me right. I'm not even 100% sure DP LLC caused it second time round I just remember it never worked again like it did in the early revisions of V3 around the time they introduced it. I moved from Cubase at the time as S1 was tight with regards to syncing internally. The subject was brought up enough on the old forums, pretty much after every major release. It was pointed out by a plugin maker who I won't mention with regards to one of his plugins. The post is still in the support section to this day.


"May 19, 2015
Studio One has had a bug for a long time now that realtime MIDI sent from plugins is erratic by the buffer size, although I believe it records precisely. Lowering your audio buffer size should reduce the erratic timing, but the best thing obviously would be for them to fix this"

Use zero latency plugins and your fine, it's probably why a lot of people never noticed it using low latency plugins then printing out, but it's there alright.

Which plugin format are you using?
Which OS?
How old is your computer?

[Bowsy]

It makes no difference. It was pesent before V3 then they fixed it and broke it again towards the end of V3 if memory serves me right. I'm not even 100% sure DP LLC caused it second time round I just remember it never worked again like it did in the early revisions of V3 around the time they introduced it. I moved from Cubase at the time as S1 was tight with regards to syncing internally. The subject was brought up enough on the old forums, pretty much after every major release. It was pointed out by a plugin maker who I won't mention with regards to one of his plugins. The post is still in the support section to this day.


"May 19, 2015
Studio One has had a bug for a long time now that realtime MIDI sent from plugins is erratic by the buffer size, although I believe it records precisely. Lowering your audio buffer size should reduce the erratic timing, but the best thing obviously would be for them to fix this"

Use zero latency plugins and your fine, it's probably why a lot of people never noticed it using low latency plugins then printing out, but it's there alright.

Which plugin format are you using?
Which OS?
How old is your computer?

Format was aways VST2 or VST3, they only have to produce latency above zero. It was present from V3 to V6 on a 6700k, 9900k and 13900k Intel system on Windows 7 to 11 that I currently use today. I always buy the best componants at the time money no object with regards to Windows systems.

Try it yourself. Midi out to Midi in using two Instrument tracks, a third party ARP to a VSTI. Scaler to a VSTI for example were your using one plugin to trigger another across two instrument tracks. If anything used has zero latency the DAW won't produce the problem. Load any plugin with latency onto the chain via inserts say 25ms. The play back sync of the Arp will be out of time by the latency added to the chain of 25ms. If the ARP or VSTI produces 25ms then the ARP will be out by 25ms. Throw something like an Ozone module on the inserts in that chain that produces over 100ms and you will hear it instantly against a click track. Every now and again it will force a re-sync if you start play from 0 in the project but if your working on looped sections a few bars in the sync issue is back. The old forums were wiped clean otherwise I would of posted the links showing it.

The only work around is to reduce your buffer rate as low as it can go because DP won't have any affect on it, it's based on the buffer size of your interface setting not DP. If they fixed it in V7 great, but I've yet to see any fix in the patch notes released to this day. It prints perfectly fine once you know it's there, it's the play back sync against other tracks in the project that is the problem. I keep Cubase at hand for this reason plus the fact I still enjoy using it.

[slackhead]

I have this exact issue in v7.2 (Windows), so it's not fixed yet.

[Bowsy]

I have this exact issue in v7.2 (Windows), so it's not fixed yet.

Had a feeling it wasn't.

[Resonant- Serpent]

Hardware synth inputs routed to Aux tracks (as recommended in their tutorials) is still broken. No plugin delay compensation, so every render is off by however high your buffer is.

[lfm]

Hardware synth inputs routed to Aux tracks (as recommended in their tutorials) is still broken. No plugin delay compensation, so every render is off by however high your buffer is.

I think the easiest thing to do is apply a delay on the track itself, here thinking midi part.
- plus or minus 100 ms

Made a little list of each hardware synth calibrating to perfect aligned midi on the grid and check how it is offset as audio response come in. So add a delay accordingly and trying until it lines up.
- so taking such values from my calibration list as tracks are added with each synth

I last ran v4.6 in 2019, might be plugins to use that define this. Cubase has something like that but really awkward to use locking up the audio inputs for that very purpose.
- so just made the simplest solution as described

For hardware StudioOne has Pipeline XT plugin which allows for external audio insert effects
- maybe something these today for instruments too
- not sure if it can be used with inputs only, it might