BIG midi problem with pt10

[Trommelfell1]

I have a BIG problem.
My system is win7 64 bit and Pro tools 10.

Audio works fine but midi crack up my computer.

My audio gear is: digi002 rack, Sonic core creamware.
My midi gear is: digi002 rack, Sonic core creamware and midi express 128 and aturia factory.

Midi input works fine with Digi002 rack, and Aturia factory.
Midi output works fine with Digi002 rack.

Every time when i choose midi in or midi out - midi express or sonic core, there is no signal and the hole damthing hangs up (no bluescreen it hangs completly).

So in Cubase all midi in and out is fine -sonic core, midiexpress, digi002, aturia factory.

and by the way i launch protools as Admin, and all drivers are the latest (64bit driver).

any help??

ps: the midi out of motu midiexpress and sonic core is EMULATED!!

my english is not so good but i try

[8dB.co.uk]

Have had the same problem since going from 7.4 on XP 32bit to PT9CPTK on Win7 64bit.

Been hounding support but with nto luck yet. I'll keep you posted. You are not alone!

AWS

Originally Posted by Trommelfell1

I have a BIG problem.
My system is win7 64 bit and Pro tools 10.

Audio works fine but midi crack up my computer.

My audio gear is: digi002 rack, Sonic core creamware.
My midi gear is: digi002 rack, Sonic core creamware and midi express 128 and aturia factory.

Midi input works fine with Digi002 rack, and Aturia factory.
Midi output works fine with Digi002 rack.

Every time when i choose midi in or midi out - midi express or sonic core, there is no signal and the hole damthing hangs up (no bluescreen it hangs completly).

So in Cubase all midi in and out is fine -sonic core, midiexpress, digi002, aturia factory.

and by the way i launch protools as Admin, and all drivers are the latest (64bit driver).

any help??

ps: the midi out of motu midiexpress and sonic core is EMULATED!!

my english is not so good but i try

[Trommelfell1]

So this is a Pt10 and Motu and sonicore conflict in Win7 64bit
the products of m-audio are not emulated and funktion as well (tested with the usb uno from m-audio).

So i shell the new (6month old) Motu midiexpress and buy two 4x4 midisports ae in cascade for pro tools....

THANX SOFWARE SH**T

[Midimax]

I would like to join you in raising one more voice of anger.
I have just bought MOTU Micro Lite - 5 MIDI INs/Outs.
I can't understand why the MIDI IN ports appear as normal MIDI ports and work correctly, while MIDI Outs of the MicroL Lite are all [Emulated] and do not work.

I have checked the same ports in MIDI-OX and played a MIDI file with MIDI-OX - sent via the MIDI Out port to the instrument without any problems.
How can AVID ignore these issues?

[8dB.co.uk]

My midi gear -

Romio 2 USB
MOTU micro express USB
Radikaltechnologies SAC2.2
Korg MicroKontrol USB
Digi 002 FW
MBox2 USB
Korg X5 (midi only)

All have 64bit drivers except the Radikal, which is why I need to use other midi interfaces to get more MIDI outs. For some reason if I use THRU ports, at least some of the data gets stripped.

The Avid/Digi kit has full MIDI IO. Everything else passes MIDI IN to ProTools but only Avid/Digi kit passes MIDI OUT. All the other outputs show as "EMULATED".

This is way deeper than a couple of manufacturers having conflicts - it is down to how ProTools interacts with Windows 7 and its hardware resources.

AWS.


Sent from my XT910 using Tapatalk 2

[pranza]

i feel you -- even on windows 11
solution - install loopmidi and midi ox
that way you can choose non-emulated midi _out_ for pro tools (loopmidi) and route it where needed.
i had to do this to be able to use frontier alphatrack controller with pthd 10...