Yes, I notice the same behavior here using Program Change.
It seems to me that this a bug, given that we want to reset something each time a pattern is launched.
Am I correct ?
I just found out as well, that having automation default values set means, that each time Hapax receives and / or sends program change, it also spits out all the CCs with default values. Which of course messes up the synth patch that was just loaded.
This behavior doesn’t make much sense to me. It even does it when I mute all the automation lanes. This is clearly a bug in my view and / or we are missing additional menu item in the program change section that sets the behavior of default values in response to program changes, especially those program changes that occur without the pattern being changed as well.
I disagree. I think that ensuring that current automation values are always applied is the most consistent and predictable behavior. Since by default PC are only sent when changed it makes sense that default values take precedence, otherwise the same pattern would result in a different state depending on whether PC is resent or not.
Also PC are sent immediately when a pattern is selected but automation is only sent when it’s playing.
I agree that muting a lane should also mute the default value though. It would be a more useful feature.
Regarding the other points, I don’t have enough Hapax experience to fully understand / evaluate that … hovewer I would argue the default values should NOT be applied when I am just sending PC from external keyboard controller to browse patches on the synth I am just playing / writing with. The same goes when changing patches with encoder on Hapax.
Anyways, as Maarten has suggested, I will have to redo my first instrument definitions and don’t use the default values.
Hey, i am using default values to make the patch without touching the synth, all values sent from Hapax to my DSI Tetra, this way i don’t need to save the preset in the synth and could use the same basic or a favorite preset without change the original values and send all default values from Hapax, it’s like saving the synth presets in Hapax.
This is how I’m trying to use it too, when starting a new pattern with a new preset I like to have it toned down quite a bit so that it’s not a loud change and then twist the knobs myself to manipulate the sounds.
Saving the presets in this state would mean my most used presets being hardly audible when switching to them on the synth.
The “funny” thing is, it doesn’t seem to work the same with internal destinations. The external CCs are spit out even when the sequencer is not running. But for the internal destination to respond, the sequencer needs to start / run.
That caused me some confusion, as I have started to use Effects on/off automation lanes and default values to have control over Effects state per pattern before learning about mute locks (or however it’s called).
Yes, this.