Fender Studio Pro 8 Released

[tumface]

OK so why add a Studio Assistant button if it doesn't work? - I want to delete the button but it's not in the customise options

That's worrying... I hope they aren't adding ads for their subscription services to always-visible parts of the UI.

[jamcat]

So lots of AI-powered stuff, some more useful than others, some that requires a subscription. But still no improvement to automation.

Studio Pro still has no ability to change the destination plugin/parameter of an automation track. The best you can do is copy and paste the automation data into a new automation track pointing to the plugin/parameter you want to target. But because automation data doesn't use clip containers like MIDI does, that automation data is just loose in the automation lane, so you have to also set your paste point to the precise position of the first automation data point. And whatever you do, don't accidentally click inside the automation lane in the Arranger, because you will screw up your automation data, since it is exposed and unprotected by a part container.

Now imagine if you are using a bunch of plugins that require heavy automation, like SWAM, and a new version comes out and you have to migrate all of your plugin instances from the old version to the new version, meaning hundreds of automation lanes that have to be copied and pasted into new automation lanes at arbitrary automation points, instead of just reassigning the automation destination, or at least dragging automation part containers to a new automation track.

[dastewart]

Thanks for that. Just to clarify I mean the automation lanes in the arranger view (when you hit A or shift A)

Yeah, it should work with that. Once you set up mapping the synth parameter to the macro knob with the range assignment, you automate the macro knob instead of the original synth parameter.

I'm not quite sure I follow. I'm talking about automating things like the volume knob and send levels which I may want to shift by a db here and there.

[thievedletter]

If I'm understanding you correctly, you mean something like how the tempo track works. In the tempo track you can set max and minimum values, so the automated tempo can be within a range of, for example, ten BPM.
As far as I know, no, you can't do that with automation lanes. I can't think of an example, but I know there have been times when I have looked for that same function.
It seems like it should be pretty doable, since you're usually either working with 0-127, 0-100%, or -100%-+100%
I guess one argument against it would be that, at a quick glance, you might end up comparing apples to oranges, as far as scale is concerned. It would need to be implemented on a per-lane level as well.
That said, comparing the scale of volume automation to a wet/dry automation, is pretty meaningless anyway. So it would only even factor when directly comparing the same function.

I'd be all for that.

[dastewart]

If I'm understanding you correctly, you mean something like how the tempo track works. In the tempo track you can set max and minimum values, so the automated tempo can be within a range of, for example, ten BPM.
As far as I know, no, you can't do that with automation lanes. I can't think of an example, but I know there have been times when I have looked for that same function.

Yes, exactly that. It’s a fairly basic improvement which would go a long way towards making automation easier to adjust.

Thanks for letting me know it still hasn’t been added to v8. It’s a real shame but in keeping with their current strategy of simply trying to add more bullet points to the marketing literature and not paying too much attention to improving the basics.

[BONES]

I wish they would just make the actual DAW better.

That's always going to depend on what you use because I've never in my life so much as thought about looking at the chord tools. To me that kind of krap is nothing but bloat.

The best things added to studio one always seem to be coming from Lukas and not the Studio One people.

How would you even know who does what? I'm sure they have meetings and allocate jobs evenly and without bias.

Also, it would be great if dragging a clip with tablature didn't completely reset the tab numbers, which has been a problem since tab was introduced.

I don't even know what that means.

One thing that constantly irritates me is that the automation lanes are always scaled from 0 to max value so if you're trying to create automation with small differences then you have to massively zoom the window to be able to see what you're doing. And even then it can be tough.

Or you could just drag the bottom of that track down like I do.

I'm fairly sure this wasn't improved on v7 (I had the demo for a while) but maybe somebody can confirm if v7 and/or v8 fixed this?

It's not broken, it's just the way it works and it makes perfect sense to me.

So it looks like this is the update everyone was waiting for... just so they could complain about it. There is seriously no pleasing anyone.

[aMUSEd]

OK so why add a Studio Assistant button if it doesn't work? - I want to delete the button but it's not in the customise options

That's worrying... I hope they aren't adding ads for their subscription services to always-visible parts of the UI.

You can turn off the tabs for Splice and that other AI thing - just not the assistant which is ridiculous since it is only working if you have a sub

[tumface]

You can turn off the tabs for Splice and that other AI thing - just not the assistant which is ridiculous since it is only working if you have a sub

Yeah, I know. That's why I said it's worrying, because they specifically chose to not let you hide the one that's a subscription service run by them.

[tommijk]

Studio Pro still has no ability to change the destination plugin/parameter of an automation track. The best you can do is copy and paste the automation data into a new automation track pointing to the plugin/parameter you want to target. But because automation data doesn't use clip containers like MIDI does, that automation data is just loose in the automation lane, so you have to also set your paste point to the precise position of the first automation data point. And whatever you do, don't accidentally click inside the automation lane in the Arranger, because you will screw up your automation data, since it is exposed and unprotected by a part container.

I'm not sure I follow.. If you want to copy-paste automation, easiest way to do it is to select all the nodes, and then option+drag (on a mac) with mouse. You can paste it on same or different track, and can visually see where you land it. Quite easy, imo. And what do you mean with destination plugin of an automation track? It so easy to set up a new automation lane with any plugin, any parameter.. so changing a destination plugin seems irrelevant to me.

[jamcat]

Studio Pro still has no ability to change the destination plugin/parameter of an automation track. The best you can do is copy and paste the automation data into a new automation track pointing to the plugin/parameter you want to target. But because automation data doesn't use clip containers like MIDI does, that automation data is just loose in the automation lane, so you have to also set your paste point to the precise position of the first automation data point. And whatever you do, don't accidentally click inside the automation lane in the Arranger, because you will screw up your automation data, since it is exposed and unprotected by a part container.

I'm not sure I follow.. If you want to copy-paste automation, easiest way to do it is to select all the nodes, and then option+drag (on a mac) with mouse. You can paste it on same or different track, and can visually see where you land it. Quite easy, imo. And what do you mean with destination plugin of an automation track? It so easy to set up a new automation lane with any plugin, any parameter.. so changing a destination plugin seems irrelevant to me.

If you create a MIDI track and sequence a bunch of MIDI notes in it, you can simply select a different instrument to receive that MIDI. You do not have to select then copy all of your MIDI data and paste it into a new MIDI track if you want to send that MIDI data to a new instrument. The same is not true for automation data. Quite simply, I want to work with automation data the same way I work with MIDI data: with movable part container clips and the ability to change the target destination at any point.

If you only need to reassign one track of automation data to a new plugin/parameter, maybe it's not a huge deal to you to have to select all of the data points and then copy and paste them into a new track. But when you have to do this for dozens or even hundreds of automation tracks, it becomes an overwhelming task.

[pk-1]

I'm not sure I follow..

The rationale behind automation clips (or however you want to call them) is exactly the same as the one for audio and MIDI events on the track. You want to treat a certain part as a logical unit, not as an unstructured sequence of nodes, notes etc.

Quite easy, imo. And what do you mean with destination plugin of an automation track? It so easy to set up a new automation lane with any plugin, any parameter.. so changing a destination plugin seems irrelevant to me.

If you have a set of meticulously designed automation lanes for an instrument, say dynamics, vibrato, and filter for some VI, and then you swap out the instrument for another one, you start again by defining new automation lanes and copying over the content one by one. How much easier would it be to just select a new target parameter for the lane?

[heliacal]

Go listen to a Rick Beato interview with David Gilmore and how they were cutting actual tape to create edits for the sound SFX on "Dark Side of the the Moon" by hand one by one. What a bunch of whiners...

[Trancit]

...

The best things added to studio one always seem to be coming from Lukas and not the Studio One people.

How would you even know who does what? I'm sure they have meetings and allocate jobs evenly and without bias.
...

I think he means the script addons Lukas Ruschitzka is doing and selling on his own like:
https://s1toolbox.com/studioonescripts
and not if something in an S1 update is coded by Lukas...

[qtheerearranger]

can anyone try adding a new midi keyboard? does your midi receive and send drop downs disappear after checking the mpe box? happening on mac

[solar28]

OK so why add a Studio Assistant button if it doesn't work? - I want to delete the button but it's not in the customise options

That's worrying... I hope they aren't adding ads for their subscription services to always-visible parts of the UI.

You can turn off the tabs for Splice and that other AI thing - just not the assistant which is ridiculous since it is only working if you have a sub

It is early access for sobscription users. It will be released to everybody eventually.