Using controller object to switch patches

[xoanxil]

Thanks philoop and thetechnobear for your time. I tried again and I think this is the problem. It says booth things, first:

Using controller object: x

and then...

Unable to created controller for : x

Here a terminal picture:

[thetechnobear]

ok... I think you need to go back a step or two... as its and issues with your paths

so :
Test 1
i) delete the extra 'objects' library you added, this is unnecessary .
ii) delete / move your custom 'cycle buttons' object... as we need to test with the one from the factory first
iii) cut n paste the following into preference/controller object (and make sure its enabled)
controller/cycle buttons
iv) compile a patch, and make sure the you see using controller object, but that you dont get the 'unable to created' error.

this should work.

if this works , move to test 2.. if it doesn't then stop at test 1!
Test 2

i) move your custom object to
documents/axoloti/objects
call it something different (testcontroller, so in file testcontroller.axs) , do NOT call it cycle buttons, we dont want a 'name clash' with the factory object
ii) open a patcher,
iii) check that you can see testcontroller , under home in the object browser
iv) select it in the object browser, this will bring its name to the top edit box
you can then copy the name, from here
v) go to preferences, and past the name into controller object
vi) compile a patch, and again check you get 'using controller object', but not the 'unable to create' error

[xoanxil]

Fist test is ok.

Test 2:

i) done √
ii) done √
iii) "check that you can see testcontroller , under home in the object browser" do you mean here?

[thetechnobear]

test 1 - cool

test 2
ok, you dont have 'home' listed, which means either your library setup is incorrect, or you are not putting the object where it needs to be.

your libs should be something like: (different username obviously)

then you need to put your object in
/Users/aturduxo/Documents/axoloti/objects
and it needs to be called something like
testcontroller.axs

(btw: you may, possibly, need to restart axoloti, after putting it in that directory, I cant remember off-hand)

if you still dont see the object in the object browser, then its not in the right place.
(I suspect this has been the issue from the start)

[xoanxil]

Nothing... I think it has to be related with the path:

When I reload objects these are the paths:

search path : /Users/aturuxo/Documents/axoloti/axoloti-factory/objects
search path : /Users/aturuxo/Documents/axolotiobjects
search path : /Users/aturuxo/Documents/axoloti/axoloti-contrib/objects

Is it normal the second path ending 'axolotiobjects'?

[thetechnobear]

no, thats wrong..

 /Users/aturuxo/Documents/axolotiobjects

should be:

/Users/aturuxo/Documents/axoloti/objects

to correct this:
file -> preferences
select the 'home' library in the list box, click edit

then check that the directory has a / at the end.

eg.

[xoanxil]

That was the problem! Now I can see if I can make it work...

[xoanxil]

Get it! Finally it was a silly, but important / I don´t know how it disappeared.

Thank you very much for your help.

Best!

[thetechnobear]

cool, glad you have got it working , happy patching

[xoanxil]

Hi,

I am trying to switch patches from SD using this as control object:

PC5 works fine. It goes up a number and I can listen next patch and, when it finishes, it starts again. But PC4 go directly to patch number 1 no matter where I am in the index.

What am I missing?

[hitachii]

Interested in bumping this for a solution as well. I use a logic/counter with two buttons via incoming midi CC, and only the one that counts up seems to work, but not downward.

[xoanxil]

Yes, it is weird because with s1 and s2 it works propertly. Lets hope someone can shed ligth on it. In the meantime, could you share how you implement the logic/counter? Thanks

[reubenfinger]

Apologies, I haven't read the full thread but there is a lot of good info in this thread about patch changing

Tutorial: How to change program on Axoloti from external controller!

Hey guys.. I just got around to changing presets on axoloti last night and thought Id share. I managed to get it working, but it took a few hours though... I tried many times first using the controller object.. But that doesnt seems to work here or else I am doing something wrong. And my friend have not been able to make the controller object work either. Great idea, just no luck yet.... I tried using controller object for two different things, but it hasnt worked for me in any of those si…

I personally use patchnames via strings to load patches. It is MattilynMattroes' version of patchloading, and is very effective. You essentially have an init patch that loads on start up containing all your patches. Then in every patch you have a button/controller etc that refers back to that patch and loads it. I use it with an Oled which is fantastic, but the approach is not limited to Oled.....in this thread I go into alot of detail, and give examples about how to do it....

SDcard Patch Bank

This post by Matt https://sebiik.github.io/community.axoloti.com.backup/t/tutorial-how-to-change-program-on-axoloti-from-external-controller/969/22 is how I manage patches, it's very easy to implement and faultless for me so far, all thanks go to Matt. Basically you have a patch that uploads at startup (he calls it init Malcolm, downloadable in the post) and that patch acts as a repository for all your Patches, in my case I scroll through them on my oled using an encoder and click it to select, Matt from memory uses mid…

The reason I mention it here is that I personally find it the most approachable, least complicated way of dealing with patches YMMV.

[xoanxil]

Thank you very much reubenfinger. I will try this other approach. Best

[reubenfinger]

You could try a logic/counter2 object it has increment and decrement inlets:
(http://www.privatepublic.de/public/factory-objectlist.html#o957830652)

Oh and just a really obvious thought, please forgive me if this has already occurred to you, but with troubleshooting I guess it's best to start with the basics, are the gpio's inverted, ie with a display bool attached does pressing the button trigger green light or the opposite.

[xoanxil]

Thanks reubenflinger

[xoanxil]

It seems there is some problem with bankindex object interpreting "-1". I have tried this simulation and it goes up and down correctly from constant number.

But with bankindex, even using debounce objects, it only counts up but not down. Doesn´t matter where index you are always go to 1.

[hitachii]

Though I haven't tested it personally, I would recommend Reubenfinger's advice of trying to switch by file name with patch/load fn, depending on how you name your files, you could use a logic/counter 2 attached to a string/indexed for yourpatch000.axp, yourpatch001.axp etc. or the counter multiplexed with some string/c objects attached if the names are different. The Axoloti is really reliable for recalling files by name with regards to samples and tables. It shouldn't be any different for patch names.

If you try this method, remember not to make your patch names longer than 8 characters. Not sure if that includes the .axp part. It goes against my examples above, but that was just for clarification.

[xoanxil]

Thanks hitachii. Control object was working nice for me using S1 and S2, but since I have not confortable access to them in enclosure and patchindex doesn´t work with GPIO, I am afraid that I will have to take that path. Lets try...

[hitachii]

Update on this because I hadn't read Matt's method all the way. Ignore the .axp part of my last comment, that was incorrect. Basically, follow his directions step by step. It works really well.

These are the few details that I had to test out, at no fault to the instructions, I'm just easily confused

• Along with uploading the init patch as the startup patch, upload all of the patches, including the init patch as a patch bank
• Since your files are in the bank, the naming convention should always be "/nameofpatch/patch.bin