The four input routing channels In the global settings reset to empty every time I restart. Is there a way to make the routings survive power cycles?
So I’ll be adding a way to create a template project that loads on boot, to the next firmware update. Then you’ll be able to configure settings such as input routing in your template and they should persist across restarts.
2 Likes
Using the new firmware 0.1.29, global routing still does not persist across restarts. I do [SETTINGS]>in 1 to out chan = 1, then save to the project named “template” in projects/, but the setting is lost after reboot. I guess it makes sense that global settings aren’t saved with the project, but then why don’t the routings in global settings survive a restart like the other global settings?
Also, when I edit a track’s routings via [EDIT][track], the setting does get saved with the template and persists across restarts. But changing the routing for any of the inputs always routes it to 1 and 2, where the track’s synth goes. If I set it to “-”, then the input is mute, but all the other settings 1-8 route the input to 1-2, the same as the track.
Ah sorry, this is a bug and I fixed it for next update.
Is there a stereo panner in the audio effect chain? The audio inputs routed to a track are fed into the audio effect chain just like the synth voices. Therefore if there is a panner in the effect chain (stereo, mono or reroute) it will pan all incoming channels: both the synth voices and the audio inputs.
1 Like
If you remove the stereo panner (and/or mono), then how do you determine the track’s routing? It appears to default to channel 1, but it would be nice to select the channel.
LATER: With no stereo or mono, it seems the output cycles to as many channels as the current polyphony setting. Is this in the manual somewhere?
So as you noticed by default the synth voices each play on a separate channel and then panners can be used to mix them to the desired channels. Removing stereo/mono and thus not having control over the exact channel layout is expected behavior.
Maybe we should circle back to the original question:
Am I correct in saying you want the inputs to pass through a tracks audio effects chain but not end up at the same outputs as the synth voices? Or was the question just for getting a better understanding of how it works?
First, I should understand how things work. I’m not at my PolyPulse right now, but as I recall, with only Track 1 playing, when:
polyphony = 1, Track 1’s output goes to output 1
polyphony = 2, Track 1’s output cycled between outputs 1 and 2
polyphony = 3, Track 1’s output cycled between outputs 1, 2, and 3
etc.
Was I confusing something?
While working through my (mis)understandings, one thing that would really help with how I want to operate is the ability for the global settings of the external inputs’ routing to persist across power cycles. In the other thread, you said that routing in global settings will now persist. Is it possible to get a hotfix of the latest firmware that includes that newly updated functionality?
This is correct and applies to all tracks. Each tracks (if no panning FX is present) renders its voices from channel/output 1 up to polyphony. Then after the audio effects the tracks are mixed, passed through the output FX chain and then go to the line outputs.
Quad engine is the exception: the four parts go to channel/output 1, 3, 5, 7 and if unison is 2 the parts to go 1+2, 3+4, 5+6 and 7+8.
Maybe this page helps with understanding the workings and relation between voices, audio effects and the outputs: Spatial audio - PolyPulse manual
I’ll publish an update this week!
2 Likes