Controls unresponsive to modsources on stomp/fx devices

#1

I was playing with some FX today, and wanted to add a chorus to my synth with external control over the parameters. I've learned that most controls can be adjusted via the "modsource" object if they don't have an inlet, so I added those to the device but couldn't get it to turn. The same modsource can be used to adjust other parameters, but none of the controls on chorus, flanger, or any of the stomp/fx I tried seem responsive to modulation. Am I doing something wrong or is this a bug with the stomp devices? A demo patch is below.

Screen Shot 2015-10-19 at 10.11.25 PM.png978x508 40.8 KB

fx_modsource_test.axp (3.7 KB)

Object parameter control
Modulation woes, help this nooblecake
#2

ok, this is just an 'educated guess' , but I suspect the problem is stomp/fx is actually a subpatch (AXS) rather than an object,
and you are trying to modulate the parameters which are actually just 'put on the parent' from the real parameters inside the patch - and I suspect this is not working.

ie. I don't think you can (currently, bug?) modulate a subpatches parameters on the parent patch.

@johannes , I suspect the issue is that the parameters on the parent patch don't exist in the main parameter table... I pointed this out to you when I was doing the push controller... I suspect the mod source assumes it does?
(this is all just a guess, but its definitely a difference between an axo parameters and the parameters shown on the parent)

ALL, Id say its a 'bug' as we want AXS to behave as fully fledged objects... but please be aware it a bit tricky with the parameters exposed on the parent object. (complexity creeps in with poly patches etc)

workaround... well I don't particular like mod source anyway :smile: I think what I would do is copy the fx/chorus, and create inlets for depth/speed ... to implement either combine these inlets (best approach) OR use mod source within the subpatch where is should work.

#3

This may not add much @matthewcieplak , but if you select an stomp/fx on the little triangle and choose - edit object definition - it will open the respective *.axs

#4

I am also not to fond of the mod sources. Especially cause you cannot change the mod source amount when the patch is live.. And also you can not assign mod source amount to midi CC to control from a midi controller.... Those two features would make them way more useful.

Try this set up. It is a different approach but it works perfectly here :smile: You have to assing the depth for a midi cc and then set up a midi/intern/cc thin with a dial connected.

Also I am thinking why not just use midi cc to control it? That works fine here :smile:

#5

maybe just for Auto control?

#6

@matthewcieplak

What do you planning to use to automate the chorus?

#7

ummm, we have to ask this to @matthewcieplak :wink:

#8

Ah, thanks for all the info! I haven't really done anything with subpatches yet so am not fully clear on the way .axo/.axs interact, and whether I can update the stomp patches without getting into source/firmware changes. Looks like some of them can be used as templates – if I bring the subpatch into the main one that is.

I am trying to control the effect from a potentiometer that I have on my enclosure, which is wired into an external ADC chip (MCP3208, 12 bit) and going into axoloti over SPI. A script object sends these values to a ctrl/dial in the axoloti patch, the signal from which I want to send to various object controls. This works fine for most devices.

I'll try the midi CC route later today – was trying to use that as a workaround but couldn't find the right device for internal midi control (and didn't have a cable handy to try routing the output to the input). Technically this is losing resolution (midi CC is 8 bit) but maybe I can use pitch bend for 14-bit control?