Thanks for coming to the review
Follow me here.
The song in two tracks [ TRACK / VOCALS]
The first time that the two tracks converged at a single bus [Bus 7]
Both track and bus are sent through aux' for additional processing*
Some aux' then converge with this bus [Bus 7] which includes 'the splitter'. Proprietary to PreSonus, any other DAW options are lost here.
The reverb processed audio is now introduced [RVRB] and combined [Bus 11]
The sound is being constructed layer by layer, relative to each other. All is definitive and exponential.*
The last of the aux' converge [Pre Set] followed by a final bus to close it all in [Set], utilizing the 'splitter' again followed by sidechained processing, the most delicate of the process'.
This is the sound that will be reproduced during live performance, and where things take a turn into the depths.
This song is mixed @ its highest block size.
2048 @ ~50% cpu
It must be performed @ any of the lower possible sample rates for reduced latency
We'll finally manage to consolidate the sound as reduced as possible to fit the constraints of the system and allow PreSonus to run the full session lightly encumbered in low samples.
We then replace the prerecorded vocal with the audio input in from the live performance.
Cool. We seem to have it all under control right? What?
THIS IS ONLY ONE SONG.
THIS SESSION IS IMPORTED INTO THE MASTER SESSION WHICH HOSTS 8 OTHER SONGS LIKE IT, EACH WITH THEIR OWN SPECIFIC ROUTING, FX CHAINS AND PLUGIN SETTINGS.
This example song is taking up ~23% cpu.
The cpu is clocking. None of the other songs' FX are engaged, one song (maybe even 2) can be fully engaged at one time but will struggle otherwise anywhere beyond this.
The session is controlled on stage by the PreSonus Studio One Remote.
In a real world scenario, this would be a similar to a theater play. Think of the song as the props and the plugins as the costumes. Shifting and changing between scenes, FX chains. PreSonus, a finely tuned ensemble of a performance vehicle, carrying the performance from start to finish.
I am CERTAIN this can work. The deactivation of entire plugins introduces POPS and CLICKS. (THE PROBLEM)
HOWEVER, (SOLUTION) these pops and clicks are NOT above a global mute. I repeat.
If we mitigate the ENTIRE issue of the pops and clicks by first MUTING the bus before deactivating/reactivating plugin(s) chains we will have arrived
The ability to run entire songs concurrently is not specific to singer songwriter. This affects music globally, beyond both genre known and unknown. Imagine the endless applications.
The ability to flip between songs seamlessly within one session. Although our current systems aren't yet equipped, our minds are.
If we can put it together... We will.
Enable automation for the Activate All Inserts - we have the workaround
If you made it to the bottom of this post, slap a thumbs up on it
If you thought, NMAD, slap a thumbs up on it
23x8, wheres my calculator, slap a thumbs up on it
Slap a thumbs up on it
Presoniuns for life