Studio One Pro Feature Requests
At PreSonus, we care about the needs of our users. Let us know which features you would like to see us implement next. Your feedback and comments are highly appreciated! Tell us how we're doing!
Changelog
At PreSonus, we care about the needs of our users. Let us know which features you would like to see us implement next. Your feedback and comments are highly appreciated!
Feature Requests
At PreSonus, we care about the needs of our users. Let us know which features you would like to see us implement next. Your feedback and comments are highly appreciated!
+1000 and the ability to save the clips for later....
I also thought about adding this function! I think this is very important function in DAW of 21 century.
I long wanted this in Cubase, but never knew how to request it to them. Brilliant idea. From a programming standpoint I could see them not quite getting why. But where many VST effect parameters affect the music as much as MIDI CC Lane data does, it would be very 'musical' to keep them in the same place. Great request!
Somewhat related to this FR is the way FL Studio, Reaper, Reason, Logic, and other DAWs are able to handle automation as blocks that can be manipulated like any other regular (copy, pate, move, etc). I find this approach particularly useful and I think it could complement this FR here very well.
Here's what this looks like in FL Studio:
@ Scoox answer I don't know FL very well indeed. So fair enough, I will remove my duplicate remarks since this request is also about keeping musical data (notes) and (several) automation/controller parameters together, which indeed is different from dedicated automation clips.
I don't agree about the linearity, since part automation can be treated like your examples, which is exactly what this request is about. If the VST plugin allows it, I already prefer to use part automation over regular automation tracks to control insert parameters for the exact reason I can create ghost copies, rename/color them and move them from song to song or VST to VST and of course keep the automation protected by the regions.
+1 I think about it too... Must be able to migrate the settings of automation in the classic style and returning to automation clips. http://answers.presonus.com/3257/fr-so3-export-musicloop-with-automation-from-insert
I have been lobbying for a functionality like this during by Cubase days (without success!) and now again for Studio One. Studio One is pretty close to what it takes but has not gone all the way. Please Presonus make this a reality for V3.x Thank you!
I was referring to keeping control data and musical data together.
Currently we can only record and send part automation to inserts that support MIDI when we set up a dedicated MIDI track for those inserts.
If we are able to select a part automation lane for any VST parameter in the song (Global part automation), regardless if the track is in direct relation with the insert (or instrument), we would be able to keep parameter modifications that do relate to the sound chain but not the data chain, together.
Of course one could also use parts then that (exclusively) hold part automation to control different devices within the song.
Hi this feature would be great and I have suggested it too! This would solve so much workflow issues with automations! Look here: https://answers.presonus.com/39492/automation-events-best-improvement-automations-can-imagine
Really hoping this feature will be added in v5, it's very important. Having used Ableton Live and Bitwig, where you can automate, besides instrument parameters, any FX and mixer parameters as long as it's on the same track, this severely limits creativity.
Re. global automation, it would be good if an automation envelope could be linked to several parameters in varying ratios. This one-to-many relationship is similar to modulators in Bitwig, except using automation. There would also need to be a 'link manager' where users could see what global automation envelopes are linked to, delete links and open the target plugin associated with each parameter.
Hey niles!
You mentioned in another thread (MIDI Direct Input for Effects Inserts) that this request also covers sending musical data from a part to an effects insert on another track. Maybe it's my Studio One noob-ness showing but I don't get that impression from the request. How would this system cover that situation?
Regards
Dropping by to make some noise, this FR is very important. Anyone who's used Ableton or Bitwig knows it.
Please PreSonus give us this! It is SO SO needed!