Alternative, customizable Firmware for PaintAudio MIDI Captain Controllers

Ok cool, sounds like NRPN is the way to go eventually. Is there a way to send custom cc messages that include your cool toggle/momentary setup? It would be great if the led reflected whether the cc was on/off. I'd also like to send one message on pedal down and another on pedal up for things like record/play in the looper. Is this possible with your current setup? I can sort of do some of this with the stock firmware, but I think yours has more capabilities and a sweet gui!
A CC isn't really "off" or "on"... It's just a value.
 
The messages for sending and receiving values do not have to be the same type....you can send CC but request NRPN to get the states. However that doesnt make much sense because the CCs are programmable in the Fractal, while the NRPNs are fixed to one parameter.....lets see what it turns out
 
Hi, I have an FM3 and I’m considering buying a MIDI Captain.
Before I decide, I’d like to know if it’s possible to set it up like this:
• 8 switches = scenes 1–8
• 2 switches = preset up / preset down

What’s essential for me is bidirectional MIDI communication so that the LEDs reflect the current scene. For example, the LED of the active scene switch would be lit in a different color, while the others stay in another color — making it clear which scene is currently selected.

This functionality would be the deciding factor for me to purchase one.

Thanks a lot!
 
Hi, I have an FM3 with a MIDI Captain 10 switch... I'd like to know if there's any news on the PySwitch implementation with Fractal... does the switch state feedback system work when I turn it on or change presets?..Thanks
 
Hi! MIDI Captain 10 and FM3 user here, if you need testers, I am available too :)
I already use PySwitch with my Kemper, it is stunning!
Thanks!
 
Hi :)

i recently developed an alternative, custom firmware for the MIDI Captain series of controllers which can communicate in a bidirectional way, similar to the Fractal MIDI specification. It has at first been developed to control Kemper Profilers and has a pretty broad user base there already, but is basically designed to support multiple clients devices.

I would love to add Fractal support, but don't have a Fractal device myself, so i would need people who can help by testing the firmware dev versions for me during the development process.

You can check out the project online: There is a web based Emulator which is used to configure the MC, but also emulates the PySwitch project in the browser, so just have a look to get a first impression: (sorry i am not allowed to post links, so replace the dots please) pyswitch(dot)tunetown(dot)de

The project is hosted on Github: github(dot)com/Tunetown/PySwitch
In the Kemper forum, there is a massive thread about it, it is linked in the README on Github.

If there is interest and i have some people for testing, i would give it a shot. Please post here if you can support this :)
hi tunetown if you want i can help
 
Hi all,

sorry for not responding so long, but i currently do a complete overhaul of the PySwitch firmware which will be very easy to adapt to the Fractal products.

The main reason was the constant demand for more features than the RAM of the Midi Captain could take with the OO design i did in the first place (i was new to the field, too ;)), but the new design is much more flexible, minimal and there are several hardware drivers i rewrote in the course, so this will be slick ;)
 
Here is the MIDICaptain10 -FM3MKIITurbo, program, I wrote this for my own taste. Everyone can use it at their own risk. v5.x is bidirectional, both MIDI cables are required. Read the description.
v4.x is only a one-way controller. Since I can't insert a link or file here, I'll send the link to anyone who's interested.
 
Hi all,

sorry for not responding so long, but i currently do a complete overhaul of the PySwitch firmware which will be very easy to adapt to the Fractal products.

The main reason was the constant demand for more features than the RAM of the Midi Captain could take with the OO design i did in the first place (i was new to the field, too ;)), but the new design is much more flexible, minimal and there are several hardware drivers i rewrote in the course, so this will be slick ;)
FM3 only sends the heartbeat and the PC message by itself, everything else has to be asked by sysex. But I solved it, I made a program for myself that works bidirectionally. If anyone is interested, I shared it on google drive, I will send you a link.
 
Here is the MIDICaptain10 -FM3MKIITurbo, program, I wrote this for my own taste. Everyone can use it at their own risk. v5.x is bidirectional, both MIDI cables are required. Read the description.
v4.x is only a one-way controller. Since I can't insert a link or file here, I'll send the link to anyone who's interested.
Hi! Could you send me the link? Also, could you tell me a bit more about the V5 regrading the bidirectional features? Will only the switch LEDs be synced, or is there anything else?
 
Hi! Could you send me the link? Also, could you tell me a bit more about the V5 regrading the bidirectional features? Will only the switch LEDs be synced, or is there anything else?
yes sync: led , scene name preset, bpm. fm3 program change (preset). dedicated fx table (personal preference)
 
Here is the MIDICaptain10 -FM3MKIITurbo, program, I wrote this for my own taste. Everyone can use it at their own risk. v5.x is bidirectional, both MIDI cables are required. Read the description.
v4.x is only a one-way controller. Since I can't insert a link or file here, I'll send the link to anyone who's interested.
this is not pyswitch, I made this for myself, it won't work with FM3 like the kemper, it doesn't send messages by itself, only PC bpm and clock, everything has to be queried with sysex code. I worked on it from scratch for about 12 days, 2 hours a day. Read the description. The latest version 5.7 is in the noexp directory
 
Thanks! Feel free to start the thread yourself. I’m happy to be a contributor and keep the code updated in the Drive folder for the community. I just wanted a reliable controller that fits my own needs for my live performances, and I'm glad if others find it useful too. Regarding the source code and programming details, I'd prefer to discuss those specifically with other developers/experts.
 
I just meant because this is not related to Pyswitch, which is the topic of this thread.
My apologies, I’d just like to clarify that I only posted here because the thread title mentions alternative firmwares in general. My solution is a completely separate development and is not related to the PySwitch project, but I hope you don't mind me sharing it here. Regarding the source code and programming details, I’d be happy to discuss them with you or anyone else interested in a deeper, developer-level look at the implementation.
 
Back
Top Bottom