CONNECTIONS RAVEN MONITOR HDMI out > Kensington CV4000H (HDMI to USBC adaptor)>Computer (thunderbolt3 port) RME FIREFACE 800 > APPLE Firewire to Thunderbolt2> APPLE thunderbolt2 to Thunderbolt3 adaptor> Computer (thunderbolt3 port)
Audio is fine going in and out through the myriad of adaptors from the FF800. MIDI is fine going from the computer to an external keyboard via the FF800. RAVEN seems to work fine. BUT - Going from the External Keyboard to the computer via the FF800 produces a dropout every 5.5 seconds.
Unplugging the RAVEN HDMI cable from the Thunderbolt3 port solves the problem! Connecting everything to an older computer (iMac 2012 with Firewire 800 ports and mini display ports) also works fine.
So how do I connect the Raven to this new computer so that it doesn't interfere with my MIDI? And.... has anyone had this problem?
Last Edit: Apr 2, 2019 12:59:17 GMT -8 by sunlending
There is no reason HDMI would affect the MIDI signal, however there is a lot of adapters going and you could be overloading the bus.
If you quit V-Control Pro does it fix the issue?
Hi Jamey, Thanks for the prompt response. Yeah, my thought too about the adapter situation, but it's like a clock. Every 5 seconds. Doesn't matter if I play 1 note per second or two hands pounding away. At 5 seconds it drops for maybe 100ms or so, then the clock starts over for another 5 seconds. Quitting V control makes no change. Only unplugging it from the Thunderbolt3 buss. I also switched the two thunderbolt inputs. No change. I reported the anomaly to RME (but this was before I thought of removing the Raven from the setup) They replied with "No Known Issue". I do have a pad controller that is going in VIA USB which seems to work without issue. I assume that I could get an economical MIDI to USB adaptor and hopefully that would work. But it just adds extra cables, and uses up another USB slot, whereas the FF800 has been handling both audio and MIDI on the old system with one cable and coexisting happily with RAVEN. Both the old system and new system were both using OS 10.13.6, so I'm kinda ruling out the OS. Anyway, let this serve as a buoy in case anyone else has the problem. Any other thoughts, let me know. t,
Post by sunlending on Apr 11, 2019 14:13:45 GMT -8
UPDATE- SOLVED (I think) Looks like the culprit was a Kensington CV4000H (HDMI to Thunderbolt3) adaptor. We replaced it with a J5Create HDMI to Thunderbolt3 cable and all seems to be right with the world once again. (well.... as far as this audio stuff anyway) Not sure if the Kensington was faulty or just doesn't play well with others. Signing off until the next catastrophe.