Source Audio Reflex to H90 MIDI issue

Tagged: H90 Source Audio Reflex

This topic has 3 replies, 2 voices, and was last updated 10 hours, 57 minutes ago by streamcore8.

Viewing 2 reply threads

Author

Posts
- January 10, 2025 at 9:37 pm #187646
  
  streamcore8
  Participant
  
  Hello,
  
  Tried to set up some MIDI presets with H90 for the first time, but it turned out H90 doesn’t respond to CC/PC commands from MIDI controller.
  
  Re-checked channel/controller settings multiple times, did some tests with cables, but root cause still doesn’t seem clear.
  
  The MIDI chain is:
  
  Morningstar MC6 Pro -> Source Audio Reflex -> Source Audio EQ2 -> Eventide H90 -> Source Audio Collider -> GFI Specular Tempus
  
  After exclusion of possible channel/command mismatches, I connected MC6 to H90 directly and it worked.
  
  Checked all the cables which were used before H90 and faced no issues.
  
  Chain Morningstar MC6 Pro -> Source Audio EQ2 -> Eventide H90 worked fine as well.
  
  Then I connected Morningstar MC6 Pro -> Source Audio Reflex -> Eventide H90 and issue has occurred again.
  
  What makes it even more strange that all pedals before and after H90 in initial chain take MIDI commands without any problems, the Reflex at first I thought that problem is in Reflex MIDI ports (damaged or something), put is this possible, if other devices respond fine?
  
  Could it be some compatibility issue?
  
  Thank you in advance.
- January 10, 2025 at 9:51 pm #187647
  
  streamcore8
  Participant
  
  Also just tried to set up an expression control in H90 through MIDI using Reflex just in case (I use TRS expression usually), seems to work fine, used following settings
  
  Reflex:
  
  Digital Out 1 (d1)
  
  Chan 4 (H90 channel)
  
  Type 7 (CC#7)
  
  H90:
  
  Preset Exp Pedal Flange
  
  Changed Control Source from Exp Pedal to MIDI CC CC#7
- January 12, 2025 at 11:49 am #187655
  
  brock
  Participant
  
  I have a similar setup here. To me, it sounds like the bottleneck is at your Reflex Merge function of its MIDI IN (MIDI OUT is not acting as a MIDI THRU). Have you checked its MIDI IN Channel? Press the footswitch long enough to get past the treadle CAL, getting to CH(x) in the display.
  
  Even that doesn’t ‘feel’ right, unless an upstream MIDI message from the MC6 Pro is changing your Reflex program unnoticed, somehow.
  
  You’re running a moderately complex MIDI system, so fortunately, you have a lot of routing options to get around most anything.
  
  I don’t think this is the core issue, but in my view, you are well past the limit of reliability with daisy-chained MIDI. 3, rarely 4 devices THRU for data corruption.
  
  You don’t need a separate MIDI THRU box. It’s all in creative routes with the MC6, and how you connect your devices to it.
  
  I’m out of town, so let me see if I can recreate the issue with the Pro, Reflex, H90 plus a couple more devices, and possibly offer a more solid solution.
  - January 15, 2025 at 7:09 pm #187721
    
    streamcore8
    Participant
    
    Thanks a lot for reply!
    
    I use Channel 2 on Reflex (some time ago I discovered that it ignores setting the Channel through Neuro app and set it using footswitch hold as you described) and Channel 4 on H90, double-checked this during tests.
    
    Tried to disable MIDI Merge function, but the issue is still persists.
    
    This chain is my first experience with MIDI, didn’t realize that such corruptions are possible, so I guess it’s a luck that only one device is affected in whole chain.
    Current workaround for me is to put H90 first after MC6, luckily the cable length was enough, other devices are working as well.
    
    Controlling the H90 using TRS Expression, so no any functionality loss here.
    
    If you have the time to reproduce the problem in future will appreciate it anyway, it will help to determine if this is a MIDI issue or some kind of hardware problem.
Author

Posts

Viewing 2 reply threads

You must be logged in to reply to this topic.