What we're really talking about is just a way to keep the CPU at manageable levels, which is often absolutely critical to actually hearing the end result.State-Space Modeled channel strips sound just like hardware
Presonus studio one keyboard shortcuts cover manual#
It would be nice to have the kind of recall Sammy does when a buss is (un)frozen without the manual workarounds. It's tediously manual and also confusing about what to leave unmuted when there's routing to other busses or FX channels. So it pretty much means going through manually and muting everything but the grouped tracks and the effects channels. That has the tendency to make all the others using it become active. Second, soloing just the tracks one wants doesn't quite work the same the FX channels have to be soloed also. time-consuming, and very hard to get it to sound the same without altering the routing of tracks in the project.įirst, the master buss effects have to be disabled or else they get added again once the bounce is imported. The closest thing I've found is bounce and import a new file, then deactivate and hide the buss and everything into it. I don't find S1 to have such an easy workaround for the lack of buss freezes. Also, some effects are just ridiculously CPU hungry (Soothe, anyone?). Some other tracks might have gotten louder and so now this track needs adjusting to compensate. As a mix progresses, stuff is added to reduce sound masking. (One might be wondering why would anyone need to freeze/unfreeze so much. Also, effect chains can be saved in a number-ordered sequence so it's still possible to retrace the steps. It might mean going back to the original and redoing some of the work but that's often a good idea anyhow. In practice, I find that if I save all of the original track files in a folder, the lack of multi-generational freeze/unfreeze issue is annoying, but not unmanageable. One can freeze a buss, which has the effect of freezing all the tracks into it along with the effects on the buss itself. If anyone knows differently, please let me know.īuss Freezes (and Unfreezes)- Pretty much what it sounds like. As far as I know, it's not option in S1 to, say, go back to the second frozen state if the track is currently sitting at its fourth, except to import the file again from the Bounces folder, which can get messy if any splices were use. So there's a sort of record kept of the "generations" of tracks frozen, and recall is simple. The difference is that in Sammy one can also unfreeze again to go back to the original. In this respect, it's so far similar to S1. And if one unfreezes it at that point, it reverts to the first frozen track, not the original. Multi-Generational Freeze (and Unfreeze) - In Samplitude, one can freeze a track,add more plugins and later freeze again. I did buy a current Samplitude copy recently just because of the freezing stuff though. Or cool effect & instrument chains, Drag & Drop, Pipeline, working ARA 2, etc.Yeah Sammy's got its strengths, though I still prefer S1 all in all. Beautiful waveforms (and Comparisonics option)īut none of the cool song creation features of S1 (i.e. I did poke around in the macro choices earlier and expected as much.Ĭan you elaborate on what you mean by Samplitude's buss and multi-generational freezing? This is an oversight really, and worth making a feature request for. That's not possible either, so then I looked at the channel macro editor which gives you yet another way, but they won't allow you to address send parameters on a channel, only insert parameters.
That's why I was trying to find another way round by just assigning both parameters to one hardware control via control link. There are no macro commands for addressing send pan, or channel pan, so that's a dead end. If the commands you need to achieve what you want aren't in the command list, then that's it. If what you want to do can be created from a combo of the available commands (and you can get very creative) then you're set. It's not something S1 does in the first place, so the commands to create it aren't there.Īll you need to do is create or edit a macro and look at the command list.
I know it's a silly example but it's like asking if you can make a macro to get S1 to cook your eggs for breakfast. You can't use macros to perform actions on parameters that don't exist in the software.
0 kommentar(er)
