Midifighter Twister + axo


#1

Is there someone out there using a MF twister, if so , how do you get the MF-cking thing to work with AXO?
I had it working a while ago but then I seemed to have changed some stuff and know I can't get it to work again regardless of what I try.
After some fruitless hours of changing usb ports i'm ready to call it a day..

The only thing I need it to do is control some parameters in my patch via midi.

signing off,
Geoff.


#2

I don't know the twister first hand, but some things you try-

There's a really handy object that I think is just called Monitor, drop it in a patch and make it live and it will show you any midi activity in the console window. So you can see what's coming in.

And check the midi channel in the patch settings.


#3

Im using the twister and it works very well with axoloti. Make sure to set your patch on the right midi channel!


#4

MIDI Fighter Twister works very well with the Axoloti.


#5

Hi guys, thx for the info and replies.
at Blindsmyth : Which channel in patch are w'e talking about here exactly?

I'll give it another whirl soon and let you know what went down..
hasta pronto, Geoff.


#6

Hi,

again I was fruitless(not entirely albeit) in my efforts however tru reading in various posts I've come to the conclusing that I don't grasp /know how to subpatch correct..so, can anyone show me how to make a subpatch with +1 osc that are then selectable (flip tru) via midi and be midi controllable themselves.(the osc can be the same channel I guess because there's only one used at every moment, right?)
I'm assuming that the best way to go for the selecting thing would be a logic counter with demux which aI saw in another post and tried but was unable to configure correctly..

thanks in advance, Geoff.

ps : Asking a lot here but still: ) If ever there's someone in Gent area (I live near Dampoort station) who is somewhat addept and can take some time to get me around with axo some more , that would be lovely.


#7

i read this 3 times but having a hard time understanding what you want.

subpatch because you want polyphony? or why? or are you still having issues connecting your midi fighter?

you want to be able to select different oscillators via midi? CC or note on? cycle through or direct select?

please clarify then i can try help
oh and if you're in gent go fucking find @johannes hahaha


#8

Hi there weasel79,

I've includud the patch so you can see what I'm trying to do
WIPSIREN.axp (11.3 KB)

I want to be able to switch or cycle through (push button on MFghtr) between for example different lfo/osc/filter s and then be able to control parameters in the activated item.
(I don't think the mux with readiobutton is advisable , maybe that logic counter thing I saw on th eboard somewhere bu tit didn't work so I put it back in to test swithing between with my mouse )

subpatch because:
*it 'll probably use less cpu
*because (I think) if I want to control with different midi cc and note due to not able in parent patch(right?)
*in my patch we're talking the lfo /osc sections(I only need to control their respective pitch values..)

Actually I live a block away from Johannes , but I don't want to bother him with my noob Q's.. I assume he's got a full agenda.
There's more finetuning questions ahead (this is for play on soundsystem) so I need to harness the frequencies a bit , but that's for when the basic structure of the patch is optimised and operational.
Btw I'm quite happy with the sounds it can produce.one of th emain reasons why I opted for this route because with trad. HWsirens you're stuck with the circuit , next to being abl eto incorporate the fx.
Hope this brings some clarity.
kind regards and all the best, Geoff.


#9

ok i had a quick look:

  • unless you want polyphony i don't think you need a sub patch in your case
  • instead of the radio button you want a midi/in/cc i object with the CC number of your "cycle"button. the trigger output of that object should go into a logic/counter trig input, and the green o output of this counter object goes into the muxing objects.

now this part, sorry, but the grgammar makes me not understand again haha

*because (I think) if I want to control with different midi cc and note due to not able in parent patch(right?)

you don't need a sub patch either for different CCs, you can just add several cc i objects if you want to control several parameters by unique midid CCs...

the midi channel issues someone described as a possible problem above can also be fixed in the main patch by going to the patch settings and changing the midi channel.

if you still have issues with the incoming data i strongly recommend adding a midi monitor object as again someone else said before.

i also just now understood you made this as a convenient dj/soundystem siren thing, so for that case you definately don't need a polyphonic subpatch. and don't worry about efficiency cause this patch will probably barely scratch the 5% usage mark of an axoloti.

if you want to improve on efficiency and latency though, one advice would be to avoid any "patch" cables going upwards. search for "execution order" on this forum, all cables should ggo from left to right, top to bottom. you can achieve this by just rearranging your objects so they are side by side. (title bar counts here) and not above/below each other