Page 1 of 1

import ´n export MIDI-MAP on WIN11-64 to OSX (m1) and return

Posted: Sun Mar 16, 2025 09:16
by CDRowell
Is something wrong or have I done something wrong? Who knows the solution? 🤨

I'll try to describe the problem:
- in avenue i created a MIDI map for APC-40 MKII in OSX SEQUOIA (silicon or m1)
- I copy the APC40MKII-MIDI.xml map file from the avenue location on the OSX hard disk to a USB-STICK
- I deactivate avenue to use the avenue license on WIN11 (just to make sure I'm doing everything right)

- I copy the APC40MKII-MIDI.xml map file from the OSX USB-STICK I just wrote to the avenue location in WIN11 64 pro
- I activate avenue and configure the midi ports so that avenue communicates with the APC-40 MK II
- in avenue I go to midi-edit and select the just imported MIDI-MAP APC40MKII-MIDI.xml

after all this: N O T H I N G H A P P E N D!
the map does not even work on WIN11 with the midi controller... even if i try the opposite way.


PLEASE HELP!!!

Re: import ´n export MIDI-MAP on WIN11-64 to OSX (m1) and return

Posted: Tue Mar 18, 2025 11:09
by Zoltán
The midi devices might get different naming in OSX and Windows, sounds like what happens for you.

Re: import ´n export MIDI-MAP on WIN11-64 to OSX (m1) and return

Posted: Wed Mar 19, 2025 15:11
by CDRowell
Thank you for replying. To understand you right: I only have apc40mkii and on different OS the same Hardware is identified with different names, right?

But i assigned it in resolume before - seems a bit strange the the app don't like the allocation i made. If it could be the case you described it should be made more easy for users...

Re: import ´n export MIDI-MAP on WIN11-64 to OSX (m1) and return

Posted: Wed Mar 19, 2025 15:57
by Zoltán
We have a ticket for this where we're looking into how the different OSes are behaving different exactly, and how we can make the transition between mac and windows easier.