MIDI - midnams - making it work with XV-5080?

[lanstrad]

I am trying to find way to make things work for this module in PT11. Just new to ''midnams'' and realized (after 2 years using the module easily in Cubase) that I could also be able to select patchs and banks for this module within PT.

However, if I try to do it, I get the message : ''MIDIServer patch file, bank or mode informationnot available for this MIDI instrument''

See 3 attached images for more. I can see the midnams for the XV-5080, but if try to connect to it, same mesage...)

What am I missing ?...

My setup, if this can help: the XV-5080 is linked from/to a MOTU USB MIDI Express 128 port (in and out), while I use a controller (M-Audio Axiom 49) connected direct to a USB port in the computer (not through the MIDI interface, because I also use this controler for NI soft-instruments).

PT 11 on Mac OSX 10.8.5

Thanks,
Rob

[lanstrad]

Oups.. Bump !

Guess this silence means I better keep working MIDI intensive projects with Cubase...

Seriously ?

And yep: the OSX MIDI Studio shows the device and it shows its connexions from/to the MIDI interface. So issue is not with OSX I guess... (?)

[philgrab]

Midnams are a curse. The same file that works on a Mac, won't work on a PC. What I do is grab a midnam file that is a known workable file for my OS (which is Windows, sorry). Then I create a copy and tweak it for the patches and device I need. Just spent 6 hours building a midnam for a Lexicon 300 reverb from the 1980s. Almost pre midi standards reverb and that was a major pain.

If you have another midi device that works, just use it's midnam file as a template otherwise things like spacing and "&" symbols will drive you crazy.

I don't know why DAW manufacturers don't just give you templates you can input the patches in to. I know Sonar does this but Protools does not. There is one site you can try to see if they work. This guy is a mac OS guy and has created a bunch of these http://digicake.com/midnams/

[ChuckS]

To the OP - Patch lists were broken in PT11 and 12.0 - thread here: http://duc.avid.com/showthread.php?t=349183 Working in 12.1 - 12.6

Originally Posted by philgrab

Midnams are a curse. The same file that works on a Mac, won't work on a PC.

Never had this problem. Same .midnam and .middev files work here cross platform.

[philgrab]

Originally Posted by ChuckS

Never had this problem. Same .midnam and .middev files work here cross platform.

What are you connecting to? That makes a difference. If it's some modern device already listed in the application then sure, that will work. Such as synths, keyboards or drumpads. For vintage gear, this is not the case. I just went through many hours of this. Downloaded a mac oriented midnam, did not work in Windows. Had to rebuild the file from scratch.

[ChuckS]

The patch lists and dev definitions are just standard XML files. Not sure what your reference was to & signs and spacing. Does your editor handle XML? I looked at the Lex 300 provided at Digicake, looked fine. The last one I did for the MicroKorg came from there and cross platform was no issue.

[lanstrad]

[QUOTE=ChuckS;2388067]To the OP - Patch lists were broken in PT11 and 12.0 - thread here: http://duc.avid.com/showthread.php?t=349183 Working in 12.1 - 12.6


==== Oh...llly...S**t ! Then here's the problem. And this has never been fixed in 11.3.1 either ? (that's my version on that desktop... where I aim to keep 11.x.x for a while. I do have 12.6 on my Macbook but my setup is not connected here... I like the AVID way of forcing people to upgrade to solve issues...

[philgrab]

Originally Posted by ChuckS

The patch lists and dev definitions are just standard XML files. Not sure what your reference was to & signs and spacing. Does your editor handle XML? I looked at the Lex 300 provided at Digicake, looked fine. The last one I did for the MicroKorg came from there and cross platform was no issue.

Trust me, the Lex 300 on Digcake does not work in Windows 10, PT12.6. That's the file I had to rebuild. Besides syntax errors the spacing is critical and those were off as well, plus, if you have the latest version 3.5 of the hardware chipset, the names and preset locations are all off. Anyway, not my thread. I did not have problems by the way with any of the 11 and 12 versions of PT with midname files but once again, on Windows here and my midnams were created under previous versions. They worked all through those versions.

[ChuckS]

Originally Posted by philgrab

I did not have problems by the way with any of the 11 and 12 versions of PT with midname files but once again, on Windows here and my midnams were created under previous versions. They worked all through those versions.

Yes, patch names broken was a Mac thing. Windows worked fine through all versions. The difference is that patch names and the MIDI Studio are handled entirely within PT for Windows, whereas on the Mac OS, coremidi comes in to play. Something wasn't connected right in the 32 to 64 bit conversion.

[lanstrad]

Well, unfortunately this thread has became a Mac vs Windows discussion about the issue, at least in part.

ChuckS, don't know what you mean by saying the issue was repaired in PT 12.6, I just updated my Macbook to it, and connected everything there for a test, and I still don't get very much - only difference is, after replacing the file by the one found here :http://digicake.com/midnams/ - at least I don't get the message I was referring to anymore, but I still get the boring window with 1 to 127 patches, no way to select a different bank, and overall the same stupid result.

I'm still stucked with this issue in PT and will probably just bring the project to Cubase which can deal with my external devices as well as with NI.

Thanks,
Rob