11/9/2023 0 Comments Studio one 5 vs cubase 11![]() We should be happy with all these possibilities.Ĭlick to expand.So with Studio One you can Alt-Drag an effect and drop it anywhere. The GUI is more appealing anyway than the one of Cubase.Īgain, for me personally, working with mainly CC data and expressions maps (sound variations in S1) Cubase wins here.īoth DAW's are great, to conclude. I think for elaborate and complex, let's say: EDM work S1 is preferrable. It eventually comes down to the job that your DAW has to do for you. Other pro for S1 is that when you move notes horizontally all relevant CC data join the party. The same work can be done also in the VST instrument part in the main screen, but for me it feels very different, mainly because I tend to miss out things. Up to now there is only a CC number indication (next to program change etc.). SWAM, all, yes all parameters are indicated by name in the add/remove section of controller lanes. The absence of this in S1 was very often a negative factor in my workflow.Ĭubase however misses that great feature that indicates a specific parameter in many plugin's while adding them. I have many of them working in Cubase, a huge time saver. no saving of controller lane presets (in a basic xml file, what is supposed to be I guess). no midi inserts: there are some fine easy to use performer scripts in the logical editor to randomize things or change CC numbers It can be solved somehow in S1, see: multi instrument tracks, but mixing layers remains easier for me in Cubase. I do this for layering reasons, very handy working with many VSL libraries, especially when combined with VEP. no midi sends, a feature that I often use to send data from a track to other instruments. I don't do any video scoring, mostly mockup's.Īlthough there are many appealing features in Studio One there are some for me important gaps. Last year I seriously tried out Studio One 5 with all its free (!) updates. - 5.5 GB free system disk space required, plus 20 GB for optional content.I am a Cubase user since version 5 up to 11 now.- For using Reason as an AAX plugin, Pro Tools 12 or later is required.- For using Reason as an AU plugin, a host with AUv2 support is required. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |