Studio One 2 Pro - any thoughts?

[ENV1]

The issue is if you want to send MIDI CC to a VST instrument. You have to set midi input for the instrument track to "LFOTool", but then you can't use MIDI to control LFOTool.

Of course you can.

Just create an additional Instrument Track and set Input and Output as required.

No problem at all.

[braj]

The issue is if you want to send MIDI CC to a VST instrument. You have to set midi input for the instrument track to "LFOTool", but then you can't use MIDI to control LFOTool.

Of course you can.

Just create a new Instrument Track and set Input and Output as required.

No problem at all.

Yep, and throw it all in a folder and group the tracks so you don't need to click 'record' to arm each individually.

I am finding MUX is cool to solve one problem but then creates a couple new ones. For instance it takes three clicks to bring up a bundled plugin's GUI. Kind of a drag.

Basically, I think S1 has to mature to get the functionality itself, a plugin seems inherently a work-around.

[bronxsound]

good for VSTi/VST hosting. not that good if you have hardware instruments in your setup. anyway i'm using it more and more often giving up with cubase.

I've got 1 hardware instrument, a Nord Wave, that I've only tried so far as a MIDI controller - what's the problem with hardware or does it just apply if you have more than one piece?

Cheers

for example lack of bank/patch selectors...
the problem is that there's no dedicated MIDI track type in S1. Instrument track accepts midi and can be assigned to the h/w unit but control of the unit is limited.

[samsam]

^ Yep, I had to resort to the manual last to work out how to use my Wave as a sound source as well as a controller and found out it takes setting up for 2 tracks, which is a bit like how Live was before the introduction of 'external instruments' and unfortunately a bit of a step backwards in comparison.

Another question - is there a freeze tracks function in S1?

Can't find anything in the manual and freezing tracks is something I do quite a bit in Live as each song gets CPU-heavy.

[standalone]

6.10.1 Audio Track Transform
6.10.2 Instrument Track Transform

[samsam]

6.10.1 Audio Track Transform
6.10.2 Instrument Track Transform

Hey thanks, different terminology to 'freeze'.

One thing I don't understand here - the manual mentions 'Preserve instrument track state' which is the same as Ableton's freeze, ie. you can go back to what you had before. However, the only part where it talks about reducing CPU is under 'remove instrument' which is not what happens with freeze; freeze removes the CPU hit of instruments and effects but you can go back to the original state if you wish but with what I'm reading, S1 doesn't have this?

I'll have to check how it works later when I'm in my studio.

[braj]

Yeah, in S1 it is called 'transform to audio track' and it creates a new track and gives you the option to preserve the track state, and remove the instrument so you can free up RAM/CPU.

[samsam]

^ Thanks but that's the part I don't get.

In Live when you freeze, CPU usage goes down but the instrument isn't removed, it's just frozen and can be unfrozen if you want.

Is there no way to do this in S1? No way to reduce CPU without permanently deleting the instrument?

Hopefully I'm just misunderstanding.

[braj]

^ Thanks but that's the part I don't get.

In Live when you freeze, CPU usage goes down but the instrument isn't removed, it's just frozen and can be unfrozen if you want.

Is there no way to do this in S1? No way to reduce CPU without permanently deleting the instrument?

Hopefully I'm just misunderstanding.

It doesn't really permanently delete the instrument, it saves the state of teh track and you can re-enable it if you need to later with all the instrument parts intact. You can also bounce a selection or a track. I agree it isn't my idea either but it does work.

[braj]

Anyhow, I agree it isn't perfect, which is part of the reason I'm stoked to get a new machine soon (ordered and on its way!) IMO S1 isn't great for marginal systems like my current old one, not unless you want to have RAM and CPU issues much of the time. It isn't the worst, but far from the best in that regard. Reaper for instance makes much more out of my old hardware than S1 can, but there's plenty of tradeoffs and I've found S1 is the better DAW for me, all things considered.

[Ciberithm]

The issue is if you want to send MIDI CC to a VST instrument. You have to set midi input for the instrument track to "LFOTool", but then you can't use MIDI to control LFOTool.

Of course you can.

Just create an additional Instrument Track and set Input and Output as required.

No problem at all.

I just tried this and it worked. I needed to create an instrument track, but choose LFOTool as the target instrument, not my synth. I had tried the multiple grouped tracks approach before, but all tracks were for the same synth.

[liquidsound]

when I try and manually configure them in MUX it doesn't seem to work. How do you do this properly? Is there an easier way beyond selecting the proper parameters from a list?

That's strange.... It works for me in S1. I just drag the parameter from the upper left corner display to the controller mapper on S1 and you are done!

Also you don't need three clics to get to your Diva for example. Just add the Diva to the group element in the front panel of the MUX by dragging it. You need to unlock the layout in the menu and then you can create al kinds of layouts for easy access and add controls buttons for modules etc.

There are also tons of shortcuts in the MUX to quickly access lots of things.

Like I said the MUX needs exploration and it's quite deep and complex. What it can be done with modulations and ADSR envelope, LFO AND a Multi-Point envelope to a VST parameter it's just the beginning.
Just right click in the MUX deep editor and choose the appropriate module.

BTW if you have a new idea just drop in the forum at MUTOOLS and tell Jo. If it is valuable he's always open to further implementations.

[braj]

Ok, it looks like I have some exploring to do then, off to Timbuktu! Livingston? Livingston?.......where's my hat?

[braj]

when I try and manually configure them in MUX it doesn't seem to work. How do you do this properly? Is there an easier way beyond selecting the proper parameters from a list?

That's strange.... It works for me in S1. I just drag the parameter from the upper left corner display to the controller mapper on S1 and you are done!

Can you explain this a little more?

[liquidsound]

when I try and manually configure them in MUX it doesn't seem to work. How do you do this properly? Is there an easier way beyond selecting the proper parameters from a list?

That's strange.... It works for me in S1. I just drag the parameter from the upper left corner display to the controller mapper on S1 and you are done!

Can you explain this a little more?

Sorry braj, I thought you were referring to map MUX to S1. My mistake.

In the MUX you have 16 knobs on top (you can scroll to see them all). You map a VST parameter(s) to those knobs by right click on them and choose edit. There you add as many parameters as you like to any VST you like and then you can map that knob to the S1 beautiful mapping panel.

Also, to add to your previous note, you can grab the VST icon from the deep MUX editor into the MUX front panel ( top level window) into that square area most often labeled Oscillator. Now you can just double click that dragged icon and the VST popsUp. So no need to go back in there for editing. You can rename any label, no need to have it named Oscillator.

Hopefullupy you'll play around with it and watch the videos on YouTube were Trancit made some little tutorials.
Trust me, it is Very Powerful and deep. I'm still learn the endless possibilities of it.
For me it's the perfect substitute to Reason RE by far.

Remember it's in Beta stage and Jo is fixing as many bugs as they are reported, ( please help him wit this if you can ) and adding more feature by the day.