Zynewave@buendiainside wrote:
Yes, two midi inputs appear as:
iCON iControl v1.01
MIDIIN2 (iCON iControl v1.01)
and one midi output as:
iCON iControl v1.01In the midi input options of each track, two pairs of midi inputs appear as follows:
iCON iControl v1.01
iCON iControl v1.01 (with a 16 channels new box)
MIDIIN2 (iCON iControl v1.01)
MIDIIN2 (iCON iControl v1.01) (with 16 channels new box)
It sounds like you have selected the MIDI inputs/outputs on the MIDI page in the Audio/MIDI dialog. This is only needed if you want to record the input of the iControl. If you only want to use the device as a control surface, then you should only assign the MIDI in/out on the control surfaces page.
I don’t think there is something called “layers” in the Mackie MCU specification. A maximum of 8 channels is supported for each connected device, but there are button commands for moving the controlled channels up/down in banks of 8 or single channels. Maybe the iControl has an option to use these commands.
ZynewaveHi,
I assume you are talking about this:
http://www.icon-global.com/Controllers_MIDI+recording+controllers_iControls+.htm
When the iControls is connected through USB, does it present more than one MIDI in/out interface in the Podium Audio/MIDI dialog?
Can you describe in more detail how Podium crashes? Does it occur immediately on startup?
My best guess is that, as long as the iControl app is running, it keeps a lock on the MIDI interface. That is probably what causes Podium to fail to open the MIDI interface when it starts up. It shouldn’t cause Podium to crash though, unless the crash happens in the MIDI interface driver.
Zynewave@MikaFrench31 wrote:
Hi Frits,
To know when a solution will be developed for better management of Kontakt?
I look forward to it
Hi Mika, thanks for your patience on this matter. This is high on my priority list, but unfortunately I’ve had to spend some time on non-development stuff in the last few weeks. Once I can get back to fully concentrate on development, I’ll look into this. Hopefully within a month or two.
ZynewaveZynewaveZynewaveZynewaveIs it just with this one project, or all your projects?
Did it work in versions before 3.2.0?
If you bounce render the master track (not export), does the bounced audio play back ok, and are the left/right waveform overlays on the master track timeline aligned ok?
ZynewaveHi,
The easiest way is to do a complete DB rebuild, provided that you haven’t customized your plugin DB. You can also load the plugin DB project, reorganize the added/updated folders, and then resave the DB.
ZynewaveZynewave@Me le suono! wrote:
I set the six channels in the Sound Properties dialogue (5.1 surround), but during playback, I only hear the stereo channels. 👿
One of the limitations in Podium Free is that playback is restricted to two channels. If you try the Podium Demo, you should be able to verify that your surround file and routing is ok.
ZynewaveIf you want to apply fades or gain changes to bounced audio, you need to move it to a new audio track. These soundevent features are blocked when placed on bounce tracks, because otherwise redoing a bounce would not result in an identical reproduction of the unbounced audio.
ZynewaveZynewaveZynewaveThose of us here who have taken the time to renew and discuss Feature Requests are often met with no response at all from Zynewave when a simple, ‘yes, I will add that’ or ‘no, I can’t fix that’ would have been plenty and appropriate.
Yes, I intend to improve plugin support in the future. The plugin MIDI out routing was first discussed years ago on this forum, and back then I also said that I plan to support it. If it was a simple thing, I would have implemented it already. The problem is that I have received feature requests to keep me occupied for the next twenty years. Each user has his own idea of what essential features are missing.
Zynewave