Studio One 7.2

[Digivolt]

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.

Did you try this ?

[wikter]

Yep, the standard way is by adjusting MIDI delay to negative times.

[jamcat]

That video is an older one of Gregor. His hair gets taller in each video. Compare that one to the recent videos on page 1, where he looks like he's ready to sing in a Die Schmiede cover band.

[stanft]

The issue with the broken delay compensation for external synths cannot be fixed with the record offsets. It is a bug that occurs when aux channels are used and is already confirmed by Presonus.

[THE INTRANCER]

Mojito - ReDesign, 8 years ago.

It pretty much follows in the same design of Presence and Mai Tai, but given their new instrument design of the recent romplers I'm not sure if Presonus has the same sights as they did in the past. The big issue I have with Studio One's instruments now is that there is no scalability of them plus add on the fact that you can't change the skin design of many of the instruments and effects. There doesn't seem to be any future planning of them or consistency in design either.


Anyway I still prefer simple gradients over background images for plugin GUI's.

[Bowsy]

Mojito - ReDesign, 8 years ago.

It pretty much follows in the same design of Presence and Mai Tai, but given their new instrument design of the recent romplers I'm not sure if Presonus has the same sights as they did in the past. The big issue I have with Studio One's instruments now is that there is no scalability of them plus add on the fact that you can't change the skin design of many of the instruments and effects. There doesn't seem to be any future planning of them or consistency in design either.


Anyway I still prefer simple gradients over background images for plugin GUI's.

Presonus Play Series take on Kontakt was my thoughts. They wouldn't touch instruments at one time now it's almost every update. Reminds me of Reason, more toys than tools aproach. Obviously they can't just pull features out of thin air as it's got a lot going for it already. I just wish they would address a few things people have repeatedly pointed out need fixing.

[qtheerearranger]

am I the only person that wishes presonus would integrate these romplers into one instrument? would be cool if it was like nexus inside of Kontakt with how minimal it is. if we could stack and multi out in the same instance.

so just gave studio one 7.2 a go last night - ran into a workflow issue I couldn't figure out how to not create patterns instead of midi regions when I was using impact - is there a way to change this?

7.2 runs a lot more smoothly on my machine - not just cpu but stability. I have a few projects I need to finish in Cubase but I may start my next stuff back up in s1. this is promising.

[Bowsy]

am I the only person that wishes presonus would integrate these romplers into one instrument? would be cool if it was like nexus inside of Kontakt with how minimal it is. if we could stack and multi out in the same instance.

so just gave studio one 7.2 a go last night - ran into a workflow issue I couldn't figure out how to not create patterns instead of midi regions when I was using impact - is there a way to change this?

7.2 runs a lot more smoothly on my machine - not just cpu but stability. I have a few projects I need to finish in Cubase but I may start my next stuff back up in s1. this is promising.

Not sure in V7 now Impact is part of piano roll etc, but if you right click the pattern or part, select Instrument Parts, you can convert part to pattern and pattern to part. It change's the option to which ever your using.

[wikter]

so just gave studio one 7.2 a go last night - ran into a workflow issue I couldn't figure out how to not create patterns instead of midi regions when I was using impact - is there a way to change this?

Are you using a Keys modifier to create patterns? Anyway, you can create a region in an instrument track and move to Impact lane.

[apoclypse]

am I the only person that wishes presonus would integrate these romplers into one instrument? would be cool if it was like nexus inside of Kontakt with how minimal it is. if we could stack and multi out in the same instance.

How else would they keep selling you the same thing over and over again and call it a “feature”.

[lfm]

am I the only person that wishes presonus would integrate these romplers into one instrument? would be cool if it was like nexus inside of Kontakt with how minimal it is. if we could stack and multi out in the same instance.

We that use Bluecat Audio Patchwork do that with anything we want, in any daw we want.
- does not tie us in like stock plugins and instrument they push on people

You can assign each synth inside to own stereo pairs or the same.

You can use loads of midi plugins in between to filter and route freely too.
- like Piz Midi Plugins

https://code.google.com/archive/p/pizmidi/downloads

Loads of daws have issues using VST3 version though, so use VST2 version and you are fine.

[wikter]

am I the only person that wishes presonus would integrate these romplers into one instrument? would be cool if it was like nexus inside of Kontakt with how minimal it is. if we could stack and multi out in the same instance.

We that use Bluecat Audio Patchwork do that with anything we want, in any daw we want.
- does not tie us in like stock plugins and instrument they push on people

You can assign each synth inside to own stereo pairs or the same.

You can use loads of midi plugins in between to filter and route freely too.
- like Piz Midi Plugins

https://code.google.com/archive/p/pizmidi/downloads

Loads of daws have issues using VST3 version though, so use VST2 version and you are fine.

That functionality is covered by Studio One Multiinstrument, supports internal plug-ins & effects. Sorry for those who ignore Studio One features.

[lfm]

That functionality is covered by Studio One Multiinstrument, supports internal plug-ins & effects. Sorry for those who ignore Studio One features.

Not anywhere as flexible, and you are locked into StudioOne.
- as I read your comment, you could not incorporate Kontakt, or?

I could continue using Patchwork presets in Reaper, Cubase before StudioOne and even now in Sonar and Samp ProX8.
- killer plugin

But it's down to that I already 2010 decided never using stock plugins and have everything third party. So rather simple procedure to swap daw since I do not need to relearn any plugins.

It's nice with plugins that free you up and assist you in that.

But it's nice if you enjoy what is in StudioOne, good luck with that feature request....

[wikter]

But it's down to that I already 2010 decided never using stock plugins and have everything third party. So rather simple procedure to swap daw since I do not need to relearn any plugins.

Yep, that's not a S1 user common problem. I've been using Modplug Trackers, Jeskola Buzz, Adobe Premiere, Sonic Foundry Vegas Pro, Cakewalk Pro Audio, Steinberg Cubasis+Cubase, eMagic Logic Audio, Digidesign Pro Tools, Ableton Live, Cockos Reaper, Kreatives Kristal Audio, Cakewalk Sonar, Samplitude Pro, Bitwig & some other pro DAW, I still keep active licenses for some of them.
I've switched projects several times from DAW to DAW and it's done easier by rendering audio. But in the case you have doubts about which DAW to stay, you're right, using stock plug-ins is a problem.
But not a Big One, moving projects by exporting just MIDI + audio sometimes leads you to get a better mix by changing plug-ins.
I decided to stay with Studio One when V2 was released and almost every feature I needed was covered then.
But I can understand people with a limited user background, I was also there some years ago.
It's not the plug-in, it's your ears. You rule, DAW is a tool.
PS: I also avoid stock plug-ins when their sound/interface/workflow is not better than third party

[lfm]

I decided to stay with Studio One when V2 was released and almost every feature I needed was covered then.

I have nothing against interface and workflow, but some things made me leave at v4.7x
- no sysex support to record external gear settings and presets
- all midi mandatory converted to automation

I had a Yamaha DP and had the strange fenomena when sending snapshot all settings it mixed sysex and CC in there
- I could not use that to just restore tunings and things
- I had to use special plugins like Ctrcl(or similar) where I could program the sysex sequency and send with a button in gui,

Most daws send back the midi recording just as you played it
- not StudioOne

When in the middle of recording somewhere appear a new midi CC, like turning a cutoff knob on a synth, turning leslie on Hammond and similar this happends
- first value of a CC appearing also is duplicated over to start of recording to create continuous automation

This does not play back what you recorded!!!!

I turned on leslie on Hammond in the middle somewhere, but when played back leslie is on from start.
- most daws have a feature to convert to automation if you want that
- StudioOne is mandatory doing that

When StudioOne v6 came I asked support if they have made conversion to automation a choice
- answer was, download demo and find out for yourself

When v7 came I asked support again
- and this time support agent really was interested to know exactly the problem
- so a bit of change of tone towards users
- but said he filed for future or something, no promises

New pricing model does not help reel in users either. Not sure where StudioOne is going.
- I see future StudioOne as a bouncing ball, smaller and smaller bounce until it dies