Topic: Control Surface Zoom R16 not recognized

@Ohrbruch wrote:

>Note that it starts out in the arrangement menu, which may not be noticeable if the Zoom device does not have a display. You need to turn power on in an arrangement to make the faders active.

Hmm… I’m not sure If I got this right. Do you mean turning the Zoom on while I’m in an arrangement?

No, I mean make sure the power button in the arrangement editor is on. But it is also worth a try to power on the Zoom device while Podium is running, and if that doesn’t work, start Podium while the Zoom is powered on.

The MIDI indicator is lit green when I move the faders… but I can’t
find a “Follow control surface” menu item…

I assume you are looking for it in the mixer menu. If it’s not there then the Zoom is not auto-detected by Podium as a MCU compatible device. You can also check if the MCU mode is working by looking for the semi-circle channel indicators on the mixer strips, as illustrated in the guide.

Check the Zoom manual, and see if there is some option in the device setup menus where you can configure the MCU emulation.

Just to add my experience, Kore 2 (which since 2.1 is able to work as a midi controller hardware too) is not recognized too here. Kore 2.1 supports MCU mode.

Kore itself (if you load vists into it, morph between sounds and all, so by the way doing many things the legendary zgrid once was meant to be – so it would be a perfect companion for podium!) works nice. You switch between kore2 mode and midi mode, and I would be happy to control volume, pan, solo mute record on/off and stuff with the kore 2 hardware. I followed the manuals, but the auto-assign doesn’t work here.
I have no clue if Kore 2 could be used in the future as well to work as a midi controller for, say, Nucleum and its parameters…

Kore 2.1 works, besides other configurations for ableton live and so on, in mackie control mode. (HUI is not supported, whatever HUI is 🙂 ).

Here is how other hosts do it:

a) In Reaper I manually assign “mackie control universal” as controller surface mode. You then choose between 5 automation modes, trim/read, touch, latch, write and another.

b) In Tracktion (well, it’s Mackie, they bought Tracktion a long time ago) it works by assigning kore midi in and kore midi out to mackie control mode manually. All works well then in Midi control mode too.
(Just for the record: There are other bugs, for example if you want to search sounds in Kore, you can’t (at least some users mention that too) – Tracktion can’t, it seems, handle that Kore needs the keyboard keys for itself, and always “wants” to open something instead, so the basic use of Kore is not really possible in Tracktion…at least as far as I understand it. Mainly i tested it to find out how other hosts do it, because I want to have it work in PODIUM^^)

c) PODIUM: In Podium we have the procedure described in the manual, the auto-detection.
But Kore 2.1 is not recognized here as a control surface. Like the zoom mentioned in another thread.
I seem to have done the necessary steps, activated kore midi in, clicked the auto-detect button and so on.

another maybe useful addition:
In Reaper, you can NOT switch the Mackie control surface option on AND set the midi in of Kore in midi devices (there is only one Kore midi in, and this has to be used by the control surface assignment, so if you additionally switch midi in the reaper midi-devices on, you get the obvious error message, midi not available.)

In Tracktion, I enable both midi ins of my soundcard (Edirol Ua25) AND Kore, but after assigning the control surface in MCU mode the midi automatically “disappears”. This is nice, as you don’t get the error message like in Reaper, and the right device is automatically assigned to your Kore as midi controller.

So the ability to manually assign the MCU mode instead of the auto-detect method would be much appreciated here. Or maybe I missed something and besides what the manual states there is anything else I had to do to help auto-detecting. Kore2 CAN work in other modes than MCU, maybe this is a problem for Podium??? I would be very happy to be able to use kore and Podium together, in fact it would be all I needed. Up to now I will from time to time try Podium again, to see if this and automation (with midi learn like in some other hosts) will work the way I would prefer it. Automation “by hand” or with the mouse is superb in Podium.

So, Frits, many words to say that surely the users who stick to Podium as their one and only host come first, but I hope at least a bit of what I describe makes sense for “auto-detecting” and possible solutions. Cheers!

I’m about to bug-hunt, as there is always a big possibility that I missed something, of course, as I never used other automation as “by hand and mouse” before 😀