PlanetZ forums - scopeusers.com

Anyone have any good troubleshooting tips for MIDI issues in Scope (with Xite-1)? I'm using Scope 7 on Win 10 32bit and MIDI is playing up for some reason.

Initially connecting a Roland PCR800 and new Launch Control XL3 via USB into a CME H4MIDI and then forwarding to Scope Xite-1 MIDI hardware ports not seeing anything coming through on the MIDI Monitor. Tried just hooking up the MIDI Keyboard device to the MIDI Monitor and still not getting anything to appear there.

If I hook up the MIDI Keyboard to a Modular patch, I can see the MIDI input light flash, but if I route to the MIDI output, that doesn't flash. Also the MIDI Monitor module doesn't show any messages.

I also tried connecting the Launch Control directly via its MIDI ports to the Xite-1's hardware MIDI ports and no MIDI coming through.

I can get the MIDI monitor to see timing messages if I hook up a MIDI clock module to it, but also BC Modules, like the BCM32 aren't registering MIDI messages.

Very confused!

P.S. I ran the Scope 7 installer again, in case any dsp files etc. needed fixing/overwriting. No change after that and a reboot

w_ellis wrote: Fri Jul 18, 2025 12:49 am Anyone have any good troubleshooting tips for MIDI issues in Scope (with Xite-1)? I'm using Scope 7 on Win 10 32bit and MIDI is playing up for some reason.

Initially connecting a Roland PCR800 and new Launch Control XL3 via USB into a CME H4MIDI and then forwarding to Scope Xite-1 MIDI hardware ports not seeing anything coming through on the MIDI Monitor. Tried just hooking up the MIDI Keyboard device to the MIDI Monitor and still not getting anything to appear there.

Roland A800 Pro, successor of PCR800,- here running via USB into laptop w/ RME Babyface.
OSS freeware MIDI Router runs the A800 Pro USB MIDI to RME Babyface MIDI-Out and into XITE-1 MIDI-In.
XITE-1/ Scope v7 x64 being controlled by 2nd laptop (also Win10 Pro x64).
So,- MIDI-In on XITE-1 works flawlessly here and I also run the USB MIDI data from A800 Pro thru the Scope project via sequencer MIDI destination to Reaper MIDI In.
It´s my smallest rig, both laptops running Reaper (alternately Cantabile lite) and both playing VSTis in harmony w/ Scope synths).

I´ll try to add a hardware MIDI module to XITE-1 MIDI Out and come back to you later.
I didn´t try that up to now, but cannot imagine XITE-1 MIDI-Out doesn´t work ... we´ll see ...

w_ellis wrote: Fri Jul 18, 2025 12:49 am If I hook up the MIDI Keyboard to a Modular patch, I can see the MIDI input light flash, but if I route to the MIDI output, that doesn't flash. Also the MIDI Monitor module doesn't show any messages.

I´d leave to CME H4MIDI out for the time being,- just only connect the PCR800 via MIDI-Out to XITE-1 MIDI-In, route to Scope MIDI Monitor, a Scope synth and then to XITE-1 MIDI-Out.
Then doing the same w/ PCR 800 USB running into OSS MIDI Router and from there to XITE-1 MIDI-Out.
Does that work ?
Here´s the OSS 64Bit version I´m using on Win 7 Pro SP1 x64 and Win10 Pro x64:
https://www.forums.scopeusers.com/viewt ... 06#p355506
There was also a 32Bit version available, but I lost the link.
I used it w/ my former 32Bit Win XP DAW and SCOPE/XITE.
With OSS MIDI Router, a hardware USB MIDI host device is obsolete.

w_ellis wrote: Fri Jul 18, 2025 12:49 am I also tried connecting the Launch Control directly via its MIDI ports to the Xite-1's hardware MIDI ports and no MIDI coming through.

That´s weird in deed !
You say,- MIDI-In on your XITE-1 doesn´t work too when connecting MIDI Out of launch control ???
And when you run something "sequenced" or "arpeggiated" from Scope project to XITE-1 MIDI-Out,- there´s also NO MIDI data present and no sound when you connect a sound generating MIDI device which offers a MIDI indicator led on it´s frontpanel?

w_ellis wrote: Fri Jul 18, 2025 12:49 am I can get the MIDI monitor to see timing messages if I hook up a MIDI clock module to it, but also BC Modules, like the BCM32 aren't registering MIDI messages.

I´d say that indicates MIDI In on XITE-1 works at least.
Are you sure there´s no MIDI (channel) filter present somewhere in your Scope project and/or in launch control or the CME USB-host?
have a look into CME configuration software (router, filter, mapper).



Bud

I'm running loopmidi and midiox on the same machine as Xite. (W7/32Bit).
MidiOX is great for debugging Midi on OS level.
Does it work when using the software-keyboard within scope ?

That's what I mean when I say MIDI Keyboard device.

Will do more troubleshooting with MIDI-OX later.

w_ellis wrote: Fri Jul 18, 2025 9:48 am That's what I mean when I say MIDI Keyboard device.

Will do more troubleshooting with MIDI-OX later.

Ooops,- no MIDI data from Scope v7 virtual MIDI keyboard in MIDI monitor ?
I guess that´s a software problem,- no?

But, I use that device on my 32Bit Win7 HP Server running Scope v7,- PCI in this case,- too.
It works in Scope v7 32Bit PCI AND in Scope v7 64Bit on XITE,- MIDI monitor too.

Seems like it was a weird Windows issue - actually the PC went a bit crazy and I ended up having to uninstall the latest "Quality" update (ironic naming) and now things seem to be back to working.

My 2 laptops both have the latest MS updates installed and there was no need to remove.
And,- all my Win10 Pro x64 machines are "Win10Privacy" tweaked.
No MIDI issues so far ...
BUT,- when I launched my laptop #1 next day after the latest MS update, the RME Babyface´s ASIO driver didn´t work anymore and I had to shut down the machine, disconnect the interface, re-connect and reboot.
All like it should be since then.

I didn´t recognize such behaviour w/ laptop #2 and XITE-1 connected.

*update:

ALL XITE-1 physical and sequencer MIDI I/O sources/destinations work perfect here, Win10 Pro x64 / Scope v7 latest build.
I´ve tested every combination of MIDI controller USB and DIN-MIDI, OSS MIDI Router, RME Babyface´s MIDI I/Os and SCOPE MIDI I/O devices,- everything across 2 laptops running simultaneously.



Bud

If a Windows update did not fully install, there can be any number of subsystems and windows that are impacted and failed to start. Impossible to know without digging in what was interfering, but my guess is something conflicted with the installation of the update, this does occasionally happen.