Studio One 5 Available Now (5.3 Out June 29th, 2021)

[Trancit]

...
They don't work correctly in Studio One, they've acknowledged they aren't working correctly, they just will get around to fixing it when they decide it's an opportune/important time to fix it.
...

... but if Studio One gives users somewhere to set a negative track delay and it doesn’t works as expected, especially if it does work well in other DAWs, then I’d say it is an issue in Studio One.
...

Ok, I understand...

But is there any difference in the behaviour between using negative track delay or nudging the midi a bit earlier???

[xbitz]

but wasn't able to route MIDI in it to the slots of the mixer etc. ... to able to do it I should route back the MIDI from outside of S1 ... cmon, https://www.cableguys.com/midishaper-studio-one.html

I wouldn't trust that guide, as it's completely wrong for Bitwig, too:
https://www.cableguys.com/midishaper-bitwig.html

another hour playing (last chance ), so yepp MIDI can be routed to anywhere to the mixer / to instrument containers just needs an aux instrument track, modulation: out of the aux track should be routed to itself the inputs of the original track should be set to the out of the aux ... monitoring should be enabled (so auto-following monitoring stuff should be disabled in the preferences ... preferences/advanced/console/ ... monitoring)

ok let's add 3 to the routing of S1

[Trancit]

...ok let's add 3 to the routing of S1

Nope... never ever just because of that:

... monitoring should be enabled (so auto-following monitoring stuff should be disabled in the preferences ... preferences/advanced/console/ ... monitoring)

This is a 110% no-go...

[oneway]

is there any difference in the behaviour between using negative track delay or nudging the midi a bit earlier???

Theoretically? No.

Practically? Yeah. Unless you do this at the very end of the process, you wouldn’t be able to quantize, your events wouldn’t visually line up with other events, all the note editing features that rely on the position of the notes on the grid would stop working, etc etc.

Also even if you waited until the very end of writing to switch over to your “good” sample libraries you’d still have to calculate how much to nudge each track back. 500ms here, 125ms there, it’d get tedious.

And then if you had to edit it (let’s imagine it’s for a short film and needs a change) your midi would not line up with the grid at all...

[xbitz]

...ok let's add 3 to the routing of S1

Nope... never ever just because of that:

it can emit MIDI signals from the mixer inserts so yep the docs of Midishaper is totally misleading or outdated no need MIDI loopback

[Trancit]

...ok let's add 3 to the routing of S1

Nope... never ever just because of that:

it can emit MIDI signals from the mixer inserts so yep the docs of Midishaper is totally misleading or outdated no need MIDI loopback

I wasn´t refering to Midi Shaper at all...

I understood your comment refering to the admiral bumblebee rating and imho S1´s midi routing deserves more a -3 than +3 just because of the fact that you cannot lock monitoring in any way and as soon as you have to route midi from one to the other track you are not able to use the auto function anymore... this isn´t even laughable anymore ... this is a shame...

[Trancit]

Sadly I am getting disappointed by S1 more and more...

I bought Sphere for the first month because I was first of all interested in all the additional stuff they made and do not have any demo available... after using them a bit I now know the reason for that... I would be very upset if I would have spent any money on them...

After noticing that CTC-1 doesn´t do what I wanted of it at all and imho not working correctly, I am now very disappointed by the fat channel plugins...
Not only that they are distorting like hell if you hit them just a tad to hot (i.e. never experienced this with any other SSL buscomp clone but the Presonus Brit Channel distorts like crazy if you pass the -18db RMS mark) but all the additional comps do not react at all to any sidechain input...
Just the standard ones (Standard, Tube and FET) got sidechain inputs... all the other ignore them completely...
Huge bummer ... especially because of their silly implementation of the key filter... only a bandpass... honestely???

Will be my first and my last Sphere month...

[xbitz]

wow, so there is plugin level direct MIDI input (so not just the audio can be side-chained) too,

I think the concept is the same as in FL Studio, gonna check it, https://forums.presonus.com/viewtopic.php?f=151&t=28364

if CC messages from direct inputs can be multiplexed with the standard MIDI inputs of the plugins then I start to respect this DAW

ahha it's working, so the proper answer to my original question is the direct MIDI input routing

needs two tracks (multi-instrument container can't modulate itself it would be feedback looping and crashes S1 instantly... tried ) don't have to bother the track level MIDI inputs, one track with the instrument and other with the modulator, modulation triggering notes can be filtered out with using key ranges (lowest octave for triggering notes)

[WatchTheGuitar]

See I knew there would be a way to do it. And also that it would involve more instrument tracks than any sane person would have expected.

[antic604]

Sadly I am getting disappointed by S1 more and more...

Why do add-on plugins not working as you expect reflect badly on the DAW itself?

[antic604]

wow, so there is plugin level direct MIDI input (so not just the audio can be side-chained) too

How is that surprising or exceptional in any way? Those instruments have no track of their own (because they've been dragged to Console rather than Arranger), so you have to use direct input but otherwise you'd simply set their input to MIDI Monitor in the Track Inspector.

[xbitz]

^^^ I'm just demoing S1 everything is wow to mee in it, started to recheck S1 because I like the new score view of S1v5, the absence/limitations of MIDI routing was the only blocking point to update/reactivate my S1v5 plan o splice (this is why I'm not using Cubase/Logic routing is PITA in them)

[Trancit]

Sadly I am getting disappointed by S1 more and more...

Why do add-on plugins not working as you expect reflect badly on the DAW itself?

This wasn´t about Studio One itself but Sphere as a complete product respectively Presonus as a whole...software wise...
and tbh... without MixFX and internal plugin goodies I cannot justify using S1 over Reaper... there is nothing or better very little in S1 I would rate higher/better than Reaper...
I hoped Sphere would fix it for me as a better complete product but sadly nothing works as I would expect it (which I would have known long ago if there would have been any demos)...or even works correctly in my opinion...

So the complete package is worthless for me and as a standalone product S1 just doesn´t do it for me...
Too many glitches...
Too many inconviniences...
Too restricted...
Too many features just implemented halfbaken...
Too expensive for what it does...

Joe Gilder said in the Q&A video they want the customers as Sphere customers and to keep them they would have to deliver... sorry Joe... Presonus hasn´t delivered for me...

Bye bye S1... I really tried to like you but now you have to go...

[antic604]

...without MixFX and internal plugin goodies I cannot justify using S1 over Reaper... there is nothing or better very little in S1 I would rate higher/better than Reaper...

Right, from this point of view it makes perfect sense

[oneway]

Too many features just implemented halfbaken...

Funny, that was the reason I left REAPER for Studio One. I guess different features are important to different people!