Impulse Note Names are 1 octave deeper. C3 instead of C4.
KeyNo 71 has to be B4 (B3 on Impulse) and not B5
yes, actually me too just finished mapping with this setup shifted 1 octave down 
The question of shifted octave: Now i read there are 2 standards:
c3=60 and c4=60 oook… after 30 years of digital music approach i discovered it now 
Zynthian= C4=60
Novation=C3=60
Anyway: i think CUIA it’s one of most wonderful options implemented in zynthian.
Is there a way to use it with CC ?
for example for audio/midi recorder would be useful instead of wasting keys or pads. there are transport buttons available on most keyboard controllers, but obviously their custom mappings are fixed to specified CCs.(at least on Impulse…)
kindly warm regards 
The zynthian has a "midi-learn-"function. You can adress the most controllers to CC-Numbers.
Then you can edit the Impulse-controllers to that numbers.
The Zynthian has a Audio- and Midi-Recorder-function. You can Midirecord all commands comming from the Impulse.
Hi Jose,
please update the key 71. Its not B5, its B4!
And perhaps you can notice, that the Impulse has another kind to count (1 octave deeper)
keep healthy
Yes Micki I know it. But my goal would be to map transport buttons to audio or midi recorder instead of wasting drum pads or keys. Transport controls on impulse can be set in MMC or cc mode, but their parameters are read-only. (And maybe wouldn’t be editable as note numbers) for this Reason asked about using cuia with cc instead of notes. From rewind to record button they cover cc112>117. If there was a way to adapt cc numbers to audio-midi recorder section using Zynthian ui script… Would give a try (even if not familiar with python)
[EDIT]
In theory the option “system message” on midi options should satisfy use of transport protocol, but for a reason i don’t know i noticed it works with DAWs only…
I think that was probably me !
The original concept was driving the GUI interface entirely from a MIDI keyboard, as you could pretty much guarantee they might be available. The keys where mapped so the select or back,or its nearest equivalent sat under the thumbs . . .
You make me look at the Motor61 Transport buttons in light of this. 
And pushing the buttons from left to right, twice each, produces
zynthian-ceed.local is on MIDI Channel 3
So we have:
Control 115 << 127 on each press Rewind
Control 116 >> 127 on each press Fast Forward
Control 117 [ ] 127 on each Press Stop (red Square)
Control 118 > 127 on each press Play
Control 120 @ alternates 0 (Not Lit) ,127(Lit) Loop
Control 119 O alternates 0 (Not Lit), 127 ( Lit) Record.
1 Like
cute,ah? 
Anyway, midi filter mapping on webconf should do the trick, routing uneditable CC to note numbers corresponding tu CUIA but… master channel seems to be protected. if i set ch#16 (my actual master channel) nothing happens. and if i set ch 16 in wizard, the result is #ch15 . is it normal?
Chipping in as I have an impulse, and while i don’t have a solution for this without changing zynthian itself, I can share the idea I’d prefer to use:
- zynthian ‘transport functions’ (rec/play/pause of audio and midi) could be remapped to whatever CC codes an instrument uses (as stated, at least the impulse has them hard coded, so can’t use MIDI learning for it)
- the 8 knobs in the Impulse can be MIDI-taught. But it would be great if we could map those to the 4 zynthian knobs main function - maybe using channel 16 for that.
- we have 8 (+1 for master) assignable buttons+sliders and 8 pads on the impulse. While we could map 4*3 buttons/pads to get the equivalent functionality of the zynthians short/medium/long presses, it would be great if the same MIDI CC could achieve the three presses based on durations.
I’ve been reading these forums a lot, and I don’t think these are possible - but does anyone knows if there’s a technical reason, or is it just because nobody has shown interest for it?
Finally - I’ve been using a nanokontroller2, just because it’s easier to map all those 4*3 zynthian push button functions, and the transport buttons are assignable in that one. But I’d love to have everything in just the impulse, one day!
@ivanmonterosso suggested using midi filter mapping - I’ve never tried, maybe some of the above are already possible. Will report after trying that! Thanks
hi edgar, actually i mapped CUIA related to encoders action exactly on those buttons instead of drumpads (they accept note number, surprise!! ) decided to map just some of switches (ignored some bold-long) but enough to control a touch-only zynthian.
These can be enough.
Regarding zynthian knobs, actually just one is important for UI navigation: select knob.
As you can see, a special select knob emulation exists (value up/down) not useful in others.
The others are mainly used on instruments and that stuff is completely midi cc assignable, so impulse knobs know their job very well
.Seriously, Midi filter works. but not on master channel. doing a scan with midi log, discovered channel 16 is totally masked…by now i tested other channels and works… play button now plays a note on synth over channel 1
1 Like
honestly, i can tell you after having tried all day (we have too much time, at the moment… ) , having a bold/long press coded in a simple one is not as terrible as i would expect…
I noticed it’s important to map short/bold select and short/bold snapshot, absolutely. One for layer post-editing, the second for load/save snapshot page, you can reach only with bold press.
Short/bold Layer are second in priority, but serves layer switching and it’s somewhat important in single layer setups.
Back switch can stay single.
I’ve not played in this area in a while. I will see if I can get The Motor61 controlling the expected behaviour for the Audio Recorder. ( Not sure how to do the MIDI recorder control except via a change of MIDI environment using MIDI Profiles).
These don’t seem to be standard MIDI Machine control codes, presumably Behringer has just kept it simple and highjacked some of the undefineds.
119 Would Toggle Audio Record
118 Would Restart Play of current selected audio from Start.
120 would Start Loop Play.
Controlled from the MIDI channel 2 ( Channel 3 in the Human world)
But it seems to do something!!!
No MIDI Rules …
The Play and stop buttons function as expected, but repeated presses of stop produce .
ERROR STOPPING MIDI PLAY
‘NoneType’ object has no attribute ‘pid’
Interestingly it also controls zynthian-touch.local as well across QMIDInet 
That’s quite valid! I confess I was just going for a future-proof feature mapping (zynthian encoders - impulse knobs/buttons), but it is true, i don’t use more than 6 buttons on “daily” use. It’s just that I’ll always have that feeling that there’s something possible with the software that I can’t really access that easily
we have too much time, at the moment
Silver linings, huh? 
I wouldn’t say it’s a top priority, at least for the impulse - there’s buttons/pads aplenty. But I do second that I use snapshot/select bold/short presses more than the layer/back ones. That said, I’m definitely not as frequent a player as others here, so use cases may differ!
Don’t remember any discussion about it. I think that would have been the original concept, as I was thinking of how to work entirely without encoders, and I think we added mouse control ( Well turned the cursor on anyway) so I started to use that as my GUI control, so would have moved on to that, then we got into using GPIO pins to allow selection of functions, then we got involved in Keyboard over USB as that was the easiest way of adding nicely formatted controllers ( I use foot swithes that behave like ASCII keyboards), an so the concepts got implemented but possibly not refined.
1 Like
This is already a hugely customisable little beast, and it does so much more than I’ve been able to explore. But we’ll always find different use cases, specially if we have to reorganise space to accommodate office working that takes over the space previously used as a studio… Hence, trying to make do with less gadgets
Thanks for your input guys!
Hi Ivan,
there are a lot of ideas for solving this problem.
I try to make a difference between editing and playing. With the impulse, we have 25 patches. So it is possible for me to use one for editi-purposes and the other for playing.
Now I am working on a playback-controller with an old R3. That will send all needed commands if it’s ready. (time is no question…)
another idea is to use the bulk-dump feature of the impulse. I think it could be possible to send and receive bulk dumps to the R3 and then we have uncountless patches.
But you are right. If we have transport-knobs, they should work like transport-knobs, with the possibility to change between audio and midi. I think that’s only a question of the time. And the guys here are the best 
1 Like
On impulse it’s the only choice for transport buttons - MMC or CC. As expected, CCs are different between devices, but it’s fine.
So, i don’t know if Midi filter totally excludes master channel for some reason… if it’s an issue, could be a lot easier doing routings for these buttons,. practically everything would be possible.
yes, two templates it’s the best deal. No doubts.
R3? you mean the Korg R3? it’s soooo cute…
Hi @wyleu!
You can change the behaviour of transport keys on the ROTOR. They can work in 3 different modes, being CC one of them. You also can use MIDI MMC and MIDI System Real-Time, the later is currently implemented (but quite untested) on zynthian. Simply change the MIDI transport mode from the ROTOR config menu and enable system messages on your zynthian.
Regards,
Ahead a play in that menu but was a little bit confused by the clunky interface…