IAC Driver and Cubase Elements
2 posters
Page 1 of 1
IAC Driver and Cubase Elements
Dear Developer,
attached you find a log file. The problem is, that Cubase generates a Number as a value for the IAC Driver on macOS:
Do you have a solution?
Thanks
Andreas
attached you find a log file. The problem is, that Cubase generates a Number as a value for the IAC Driver on macOS:
- Code:
<string name="Group" value="Generic Remote"/>
<member name="Values">
<obj class="CmString" name="InputDevice" ID="105553392897408">
<string name="s" value="MIDI System"/>
</obj>
<obj class="CmString" name="InputPort" ID="105553392902400">
<string name="s" value="758369181"/>
</obj>
<obj class="CmString" name="OutputDevice" ID="105553392903104">
<string name="s" value="MIDI System"/>
</obj>
<obj class="CmString" name="OutputPort" ID="105553392904128">
<string name="s" value="-1409225040"/>
</obj>
<obj class="FNPath" name="RemoteScript" ID="105553155383840">
<string name="Name" value="Generic Remote.xml" wide="true"/>
<string name="Path" value="/Users/omh/Library/Preferences/Cubase LE AI Elements 11/" wide="true"/>
<member name="FileType">
<int name="MacType" value="1413830740"/>
<string name="DosType" value="xml" wide="true"/>
<string name="Name" value="Generic Remote" wide="true"/>
</member>
<int name="PathType" value="2"/>
</obj>
<obj class="UPoint" name="Setup Window Location" ID="105553148093472">
<int name="H" value="50"/>
<int name="V" value="50"/>
</obj>
<obj class="UPoint" name="Status Window Location" ID="105553148085728">
<int name="H" value="50"/>
<int name="V" value="50"/>
</obj>
<obj class="CmString" name="defaultBank" ID="105553117859136">
<string name="s" value="VST 1-16" wide="true"/>
</obj>
</member>
</item>
<item>
Do you have a solution?
Thanks
Andreas
- Attachments
theomh- Posts : 2
Join date : 2021-06-25
Re: IAC Driver and Cubase Elements
Hi,
You don't say what the problem is...
For some reason Cubase on Mac doesn't store the midi port name in the configuration file, but that shouldn't cause any problems for the plugin. Please verify that the check mark in "Verify Ports" is cleared, otherwise the plugin will warn about this situation (but still work without problems):
(...though it should be cleared by default on a Mac, precisely because of this..)
I can see in the log file that some buttons still use the default midi ports (StreamDeck2Daw and Daw2StreamDeck) and if the Play button (used at the end of the log) is one of them, that's the reason to why it doesn't work.
The plugin has no problem working even though Cubase doesn't store the correct port name in the configuration file, just make sure that the selected Midi Out port from the plugin is connected to the Midi In on the Generic Remote (and vice versa)
You don't say what the problem is...
For some reason Cubase on Mac doesn't store the midi port name in the configuration file, but that shouldn't cause any problems for the plugin. Please verify that the check mark in "Verify Ports" is cleared, otherwise the plugin will warn about this situation (but still work without problems):
(...though it should be cleared by default on a Mac, precisely because of this..)
I can see in the log file that some buttons still use the default midi ports (StreamDeck2Daw and Daw2StreamDeck) and if the Play button (used at the end of the log) is one of them, that's the reason to why it doesn't work.
The plugin has no problem working even though Cubase doesn't store the correct port name in the configuration file, just make sure that the selected Midi Out port from the plugin is connected to the Midi In on the Generic Remote (and vice versa)
Re: IAC Driver and Cubase Elements
Hi again,
I had a new look at your log file and realize that I wasn't correct when claiming that some buttons use the default midi ports. Sorry
What I can see is that you use the same midi port as both Midi In and Midi Out - that will create a Midi loop that will break everything. Please configure two midi ports in your system, like:
I had a new look at your log file and realize that I wasn't correct when claiming that some buttons use the default midi ports. Sorry
What I can see is that you use the same midi port as both Midi In and Midi Out - that will create a Midi loop that will break everything. Please configure two midi ports in your system, like:
- IAC Driver Bus 1: Stream Deck Midi Out => Generic Remote Midi In
- IAC Driver Bus 2: Stream Deck Midi In <= Generic Remote Midi Out
Re: IAC Driver and Cubase Elements
Dear Admin,
thanks for investigating. I also read your installation instructions more carefully and could solve the problem. I simply had a wrong understanding, where the Generic template has to go. After installing it in Cubase, everything works now as expected. Sorry for "stealing" your time a bit ;-) and thanks for your awesome work
I use also Ableton and Logic from time to time, maybe I use your generic midi template with the Mackie control if I have a but of time.
thanks for investigating. I also read your installation instructions more carefully and could solve the problem. I simply had a wrong understanding, where the Generic template has to go. After installing it in Cubase, everything works now as expected. Sorry for "stealing" your time a bit ;-) and thanks for your awesome work
I use also Ableton and Logic from time to time, maybe I use your generic midi template with the Mackie control if I have a but of time.
theomh- Posts : 2
Join date : 2021-06-25
Similar topics
» Cubase Key Commands Not Showing in Cubase Plugin
» IAC Driver in MacOS
» IAC Driver Error
» Folder detection for LE/AI/Elements doesn't work as expected
» Key commands not working
» IAC Driver in MacOS
» IAC Driver Error
» Folder detection for LE/AI/Elements doesn't work as expected
» Key commands not working
Page 1 of 1
Permissions in this forum:
You cannot reply to topics in this forum