I have a strange Syntakt issue where I have a volume drop after a pattern change. In this example I switch from pattern 1 to pattern 2 and when switching back to pattern 1 the volume is quieter than it was at first., However after pattern 1 has looped once you can hear the volume rise back to normal volume at around 26 seconds.
volume sounds the same to me except many sounds have lowpass filter on pattern 2, could it be that you have modified pattern 2 with ctrl-all and lowpassed most of the tracks?
Yes the pattern volume on pattern 2 is a different pattern and is lower but that’s not what I am pointing out. I am comparing the initial volume of pattern 1 to the volume after coming back to the same pattern after a pattern change. Makes sense?
You should hear the overall audio level drop when returning to pattern 1 (compared to the initial volume of pattern 1 before the pattern change) but then increase back to normal after the whole pattern has looped again at about 26 seconds in. To me the volume change is quite audible.
If you are up for it then try loading the project file in your Syntakt and switch from pattern 1 to 2 and then back to 1 and you will hear what I mean.
I don’t have a syntakt to load the project, was just listening to the audio, but I don’t hear difference in pattern 1, just to confirm I’ve downloaded your sample and it’s exactly same level
Yes but when pattern 1 returns it at 16 seconds in (about the middle of your image) at a noticeably lower level then ramps up to normal level at about 26 seconds (where you put the last arrows after the volume increase). Maybe this will clarify:
I’ve double checked with the video and what you referring to as second Pattern 1 volume peak is incorrect, at that point you’ve cued Pattern 1 again but it doesn’t come in until Pattern 2 finished it’s 16 trigs, the volume increase is when the actual pattern change happens
afiak there’s no direct jump on syntakt so pattern changes happen only after the current one finished it’s run based on the CHANGE in the page menu
if you look at the video the second you let go of the Pattern 1 button you can see the sequencer already running on trig 2, that means you wait almost a whole cycle for the Pattern 1 to come in again, and that’s where the volume jump comes in
if you want to change faster you need to cue the pattern before it hits the last trig in the cycle
btw, a good way to double check is to use chain or song mode to automatically change the patterns for you, as far as I can tell you’re just hearing the second pattern where you’re expecting pattern 1 to be
Sorry but you are incorrect - the pattern change back to pattern 1 happens at the 16 second mark. Pattern 2 plays from 8 seconds in until the pattern change at 16 seconds.
Do you have a long trig on the FX track on the filtered version? Maybe that is so long that it keeps certain values different for a period of time after the pattern change?
Sounds like it’s attached to the reverb setting. I hear the volume change, but mostly because the increased resonance brings back the fullness of the low end.
Check any fx trigs or conditional trigs, anything locked where it might be hiding. It could also be a level parameter drop, but like I said, I’m hearing mostly the change in reverb or something attached to fx impacting the perceived overall level in that section.
It’s almost like the wet / dry mix of the FX on the track changes and then gets pulled back up. The level of the track seems dependent on the wet mix for overall volume, or something like that.
Thanks for pointing me in right direction. I discovered that the filtered track (pattern 2) does have a 1/16 note trig on the FX track of the last step of the pattern that somehow seems to affect the the amplitube level of the FX track when going back to pattern 1. Patttern 1 does not have any trigs on the FX track but I found that lowering the AMP Depth from the default value of 64 to 0 solves the problem! It doesn’t really make sense to me why this happens but seems like a hanging trig that gets carried over from the previous pattern that somehow resets after a pattern loop.
