How to use controller object?

#9

I for example dont know how to patch the program change /preset change thingy that it supposed to be inside the controller object. and how and where to reference to the patches on the sd card.. there are many things to consider I guess... I havent tried yet.. Maybe sometime later..

#10

HA! just found it took me some time I was looking in the settings dialog found in the patch window. not the preference dialog found in the axoloti window.

#11

Ok, I've noticed that something change between my initial dev of this, and the release.
so Ive updated my first post here, to ensure it contains 'correct information'
(as some things here were misleading)

#12

So, I tried following these instructions and got this message in the console window of axoloti:
Using controller object: Controllers/Program Change Control
attempt to create object from subpatch file : objects/Controllers/Program Change Control.axs
attempt to create object from subpatch file : /Users/Mubali/Documents/axoloti/objects /Controllers/Program Change Control.axs
Unable to created controller for : Controllers/Program Change Control
Generate code complete

What am I doing wrong?

edit- I should add that I'm the one Jaffa is referring to with the performance coming up, and I used the exact same patch as what was uploaded in Jaffa's post regarding getting the patch changing to work.

#13

can you try to remove the spaces from the names.

also, /Users/Mubali/Documents/axoloti/objects /Controllers/Program Change Control.axs
looks a bit odd, there appears to be a space after objects and before controllers...
can you check the object search path doesnt have a leading space in the name.

#14

That was it. I since the full path isn't shown in the controller object path, I didn't see the extra space. Looks like it loaded up fine now. Thanks man. Glad it was something simple.

#15

yeah, on the new stuff, I'll add file dialogs, so you don't have to enter path names, will make it easier

#16

That would definitely help, thanks for your efforts on this!

#17

Got it working too, following the new instructions :smile:

Routing the audio input directly to the output in a controller object also works now. I tried that ealier with no luck, but I think it was because of the wrong path for the controller object.

Thanks :smile:

#18

I got mine to work, but I have a strange quirk that happens. In order for me to be able to send patch changes to the axoloti from Live 9.5, I have to enter card reader mode, and then eject the sd card from finder. Then I can play only one patch that I have selected, and when I select a different patch, there is no sound. I have to redo the process of entering card reader mode and so on again.

I'm wondering if anyone is having a similar issue?

#19

This is unlikely to be about controller objects, and more about patch loading generally.

I think we need to test and isolate the issue in 2 ways:
- don't use controller objects.
- check its not something within your patch, i.e. use a very simple patch

can you try with a very simple patch
e.g. create 2 patches , one that just plays a sine wave, the other a saw... and has your program change logic in the patch directly. (i.e. not using controller objects)

post them here too...
(if you find its not controller object, please create a new topic in the helpdesk)

Im a bit limited in time at the moment so don't have time to do the above to test it, so would be helpful if you could give it a try.... then I can pickup on what you have done :wink:

#20

Ok, so I tried the tests to isolate the issue, and was not able to isolate it. I cannot select more than a single patch if the logic change is in the patch itself or the controller object. I made two simple patches that have the functionality built into it, but that didn't work either. Totally puzzled as this was working more or less as of yesterday. MUBSaw osc basic.axp (3.5 KB)
MUBSine osc basic.axp (3.5 KB)

#21

@Mubali if you rename your patches to MUB000.BIN (previously MUBSI.BIN) and MUB001.BIN (previouly MUBSA.BIN)
it does work!

Carefully follow this post https://sebiik.github.io/community.axoloti.com.backup/t/tutorial-how-to-change-program-on-axoloti-from-external-controller/969

#22

I had already had these saved on the card under the proper formatting, but still encountered the same issue. I just resaved the axo patches to reflect the same name MUB001.BIN and MUB002.BIN and received the same issue. Patch will play for a second, then when trying to switch patch, can't play anything else

#23

they work for me too...
I didn't bother renaming the patches, I just used card reader mode to rename them.

which version of axoloti are you using?
@keyman , were you using the released 1.0.6 version?

if you start the patches in live mode, does it switch away... or keep running the patch?

Im a bit lost, patches seem fine, the only think I can think of is:

  • incorrectly named, or not in root directory on sd card
  • the start.bin doesnt have your patch switcher in it
  • you have not rebuilt them, and done the upload since you added the switching logic.
  • if your using Live then its not sending program changes when you think it should. (I actually used Max to send the program changes)
  • for some reason your not getting program changes messages to the Axoloti... but I assume you getting others, so that seems odd.

Im assume your using the latest version of the Axoloti software, and that is one of the release builds (1.0.6)

(I'll confess I'm using a development version, but this is unlikely to change the functionality)

the entering sd card mode is a 'red herring', I think this is just because you are restarting the axoloti board, you would get the same if you power cycle it.

can you let us know more about your setup, e.g. which OS, which version of Axoloti etc... not that it makes a difference, but still good to know.

#24

Well, oddly enough after a couple of reboots and placing my patches back on the card, it seems to work again. Not sure exactly why it freaked out. I'll check to see if my start.bin has the patch switcher in it. I'll make sure it does just in case, but now it seems to work and I don't have the controller object enabled at all. So at least having the patch change in the patch itself seems to work for the time being. It started working again once I provided separate power for the axoloti instead of powering it via a powered usb hub. Well, it's working now, so we'll see if anything else happens.

#25

??To rename or not rename... I was also referring using card reader mode :wink:

yep!! 1.0.6 (bring on a new version) :sunglasses:

Not sure if its for me; going live with say MUB001.BIN (MUBSaw osc basic.axp) and then send program ch 2 switches for
MUB002.BIN (MUBSine osc basic.axp) and the back and forth; if you do send prg 3 or say 99 it "disconnects" (maybe adding some empty/dummy patches do the trick, if needed)

It is a bit messy :dizzy_face: but only a matter of getting used to, future "how to" will help.
Sending patches to SD card and having to rename them... I'm sure this will improve in some new versions.

#26

Oh @thetechnobear and adding @jaffasplaffa Program Change to a controller object patch works great!!, throw in some empty patches (with controller object :wink:) and now I can have 16 PRG Categories!!)

example
00 to 07 LEAD
00-saw
01-sine
02-triangle
03-supersaw
04-empty
05-empty
06-empty
07-empty

08 to 15 BASS
08-simplebass
09-empty
.. you got it by now... and replacing empty for new patch, as you go along :wink:

#27

hint: johannes is adding some extra functionality in this area for the new release, which will make this much easer to manage :smile:

#28

Did the extra functionality in this area for the new release ever materialise do you know ?
Is this a reference to PatcherBanks ?

I'll admit that I am currently stumped. Can't understand this controller object thing at all. sorry., I can see your explanation is detailed,. I just can't get my head around it at all