For some reason my new AHFX isn’t receiving program changes. Im trying to save a preset to a pattern on my digitone2 but the presets dont come up on ah when changing patterns on dn. I tried adding a trig on the first step of the patterns with a Plock. but still not working.
The presets come up on AH when I trigger the midi track in the live view on DN. I’m very confused as to why it doesnt work when triggered on the sequencer.
Both machines have the latest firmware and midi setting are good. This works with my prophet 6 but not on analog heat.
Hoping this is possible.
Update: I’ve gotten the AH to receive program changes. But it’s only working between some patterns but not others on my DN2. I’m beyond confused as to why it only works with some.
Any help would be greatly appreciated!
I have no idea what the problem with your program change is, but if it were me I would open a brand new project to use as a test platform then set up the midi and some arbitrary pattern changes, doesn’t have to be anything special just something that runs for however many steps and then changes, use that to see if the program changes are consistent. If it changes consistently, then the issue is probably somewhere in your settings on the original project.
If it’s not the midi settings themselves then I’d look at things like is there a trig condition on the track? is there a neighbor trig active on an adjacent track that could be affecting it? is there any difference in the scale setting of different tracks making them different lengths? and if so, what is the master change length set to? Does it actually change in your project but just take an extra cycle through the pattern to play? if so, is there other additional midi which could be causing the bandwidth to bottleneck the midi data and delaying the PC signal? I don’t know if any of these could be it, but it’s possible.
I’d also check the ahfx bug reports thread and see if anyone had any similar issues. If you can’t come to a conclusion, I’d contact elektron before deciding that it’s a bug because stuff like this is usually something benign like one setting that went unnoticed or one small change that needed to be made, a forgotten trig, something. If elektron decides that it’s a bug, then all you can do is help them document it.
When you are trigging the track manually and it changes programs, the DN2 is acting as a midi controller and outputting midi directly as a result of the trig being pressed, so it should be immediate and that sounds like the behavior you’re getting when you described being able to change the program from the DN2 manually so, on most levels, it sounds like it’s working fine there. The midi track which is sending the PC message should also be generating midi and what you want to identify is what is different about the times that it does work and does it do that at a regular interval? Things which happen at regular intervals are almost without fail settings related. If it does it randomly then look back to something like trig or track conditions for probability.
If you ultimately can’t find a solution then maybe you aren’t doing anything wrong and then again, I’d encourage you to contact elektron, but in the interim you can at least try the troubleshooting with a new project / clean slate and then that way it isn’t impacted by any settings in the current project which you’re having issues with.
Don’t know if that helps, but it’s some stuff you can try.
1 Like
Thanks for all that I appreciate it. The program changes works except for one pattern and I have no idea why at this point.
Not sure what you mean by master change length. I tried everything and no idea why it’s not working on this one pattern. I thought it was a matter of the master settings. But I guess not? My setup is pretty simple and I didn’t do anything differently in this pattern so I’m completely stumped.
1 Like
I’m talking about here, where you set the master length of the pattern and then the reset length determines when all patterns will cycle back to the first step of the sequence. This should really only apply if different patterns are set with different lengths independent of each other and I only mentioned it because it’s a possibility in an outside situation, just sometimes I think when troubleshooting we have to think outside of the obvious.
If it’s just one pattern though, there must be a setting impacting it and I doubt it’s the above mentioned issue. Is there any other midi going on in that specific pattern other than sending the PC to the AHFX? I think that something must be specifically going on there.
You can mostly rule out the AHFX as the problem if you set the same PC event to a different AHFX preset and the issue still exists in that pattern with a different preset, if for some reason it starts working with a different preset then I guess something could be going on with the AHFX, but it sounds unlikely to me. It seems much more likely the issue is something in the DN pattern than the patch it’s attempting to change the AHFX to.
I’ll try and think of anything else that might be relevant but nothing is jumping out at me. Make sure you check for any other locked trigs or yellow trigs that might be impacting your PC (assume you already did but just saying).
Gotcha. Yeah so digitone is sending midi to prophet 6, through the prophet to AHFX. So thats probably it. The only difference with the dn pattern is that it’s 8 bars long but I think that’s the only difference between all the other patterns.
I’ll double check to see if it’s the ah preset but I don’t think that’s it.
I think that it must be the pattern length if that’s the only anomaly. We would then need to explore why.
I’ll have to test this when I’m home later and get back
Ok if I’m around I’ll definitely help you brainstorm it, at this point I’m not positive but I would encourage you to try the same basic test of this pattern without the prophet 6 in the middle as your first step just to confirm that there is nothing in between which is causing the anomalous behavior. I really doubt that it is but it’s usually best to eliminate the simplest things and work outwards from there. Once you’ve confirmed that it has nothing to do with the prophet in the middle, it will be more productive to just focus on the specifics of that pattern which is having problems.
I’m pretty sure that Elektron devices always send PC at the end of a pattern, so something must be preventing it from getting to that “end” whatever that would mean in this case. If it’s on the first step of the pattern, you can also always try microtiming the trig which is sending the PC command to right before the first step instead of on the first step, but cross that bridge when we come to it, as they say.
Awesome yeah I’ll report back tomorrow. Thanks so much!!
