dawman wrote:OK here's the deal.
dawman wrote:
Before the XITE-1 project is even loaded, my SE-1X was recieving note on/off and MSB/LSB, PrgmChng data from the XITE-1 MIDI Out, hardware that is.
O.k.,- let´s go step by step:
SE-1X MIDI-In is connected to XITE-1 MIDI-Out (which is XITE-1 MIDI destination).
dawman wrote:
Then I load the project and the XITE-1 MIDI Out gets shut down.
Normally that means,- there isn´t the XITE-1 MIDI destination device loaded in that project or,- it is loaded into that project but it´s not wired to any MIDI source.
In both cases,- no MIDI info at XITE-1´s MIDI-Out.
dawman wrote:
Then I go to the project window, and disconnect the XITE-1 MIDI Destination module and I get no sound, no MIDI data transfers either.
Isn´t that normal ?
1.)
that line verifies there is the XITE MIDI destination loaded into that project because otherwise you´d not be able to disconnect it.
2.)
Probably because of a up to now unknown sequential order of devices loading while the project loads and w/ outboard hardware already connected (SE1-X /XITE-1 MIDI-Out),- it might be, XITE-MIDI destination was already active
before the project loading procedure was finished completely and there was a MIDI info stream being transmitted to SE-1X
until something broke
when the project loading procedure was finished,- maybe the MIDI line running from (?) wherever to XITE MIDI destination (XITE-1 MIDI-Out),- so any transmission of MIDI info stopped.
dawman wrote:
It's a peculiar oddity I never noticed.
Well, that´s hard to find out and could be a bug which happens occasionally only,- but also would have to be reproduced repeatedly to confirm it´s a bug.
To me,- it appears to be a software thingy.
dawman wrote:
But on my 88 note controller prior to the project being loaded, I can see the SE-1X reciveing note on/off, PrgmChng, and MCB/LSB data.
Now we come to the point where it´s hard to follow.
IMO what you see on your 88 note controller is what it transmitts,- not what SE1-X receives.
Assuming your 88-note controller´s MIDI-Out is connected to XITE MIDI-In (XITE MIDI source in the project) and SE1-X is conncted to XITE MIDI-Out (XITE IDI destination in the project),- how comes you have any visual info on your 88-note controller about SE1-X receiving MIDI info ?
Where do you see that,- in the display of the 88-note controller ?
That said,- it would be only possible when your controller supports such a feature and when SE1-X supports that too by reporting received MIDI Info via it´s MIDI-Out back to the device connected to it´s MIDI-In.
(think of it like a plugin reports parameter status to the Behringer BCR2000 in a bi-directional MIDI setup).
You use a Casio controller and I doubt it supports that,- in fact, I don´t know any keyboard MIDI controller supporting this, except the Panorama P4 and P6 specially designed for Reason,- and I also doubt SE1-X does.
But (!!!) - IF the SE-1X MIDI-Out is connected to somewhere MIDI-IN in that hardware MIDI setup w/ several MIDI connections made in the SCOPE project,- it´s imaginable you had a MIDI loop which stopped MIDI transmission.
dawman wrote:
Once the project is loaded, the XITE-1 MIDI Out is now what is sending data to the SE-1X. So the virtual MIDI module has now taken over and is sending the data from the hardware MIDI out, so this isn't a dual stream actually, but a switcher type of action.
Well, that indicates you probably had a MIDI loop resulting in a MIDI buffer overflow somewhere, which stops MIDI transmission and looks like a switcher type action for a period of time.
When you disconnected the XITE MIDI destination as described above, you probably killed the MIDI loop, resulting in normal operation later.
dawman wrote:
I disconnected the XITE-1 MIDI Destination module and the SE-1X recieves nadda, nothing.
Very unique scenario I never noticed before.
See above.
dawman wrote:
This tells me that during a shutdown/reboot, if I ran extra outputs from the Analog out of Solaris, I could switch from Bank 8 where my programs are stored using the Toslink to AES/EBU connection on the XITE-1, and go to an exact Duplicate of that Bank, only Bank 7 would have the Analog outs instead of the digital, and my 88 note controller could still control the SE-1X via the XITE-1s hardware MIDI out.
I would have to use the Barbettas and only change Banks on the Solaris, and shove the Analog out of the SE-1X "y'd" analog cable all the way into the Barbettas, as they have a Mixer/PA interface in the rear where Hardware effects loops, and multipole I/Os reside.
This is pretty good to know, but Scope has never crashed on me...ever. Years of 6 nights a week and not once have the cards, or the XITE-1 ever crashed. It was one of the reasons I stayed with Scope once I had the choice of buying a Receptor and hardware, or the XBox. I am glad I stayed the course.
Ehmmm,- now this is way too much off topic because the 1st target was to find out the MIDI issue in your hardware setup and SCOPE project.
Assuming you loaded a project you use frequently and in a never modified state and the project as well as the hardware setup worked before as it should and always,- you might have had just only a random occuring error.
I´d think of it in depth only when you´re able to reproduce the issue for several times.
From the very beginning,- I thought of a MIDI loop error but held back commenting on that, not knowing your MIDI hardware wireing and how the MIDI wireing in THAT project looks like.
In fact, I´d double check for any MIDI loops in SCOPE project when the issue comes back.
You use a lot of small MIDI devices in your projects like mergers, re-channelizing and such and if one of these little toys craps out in the project for a period of time (eventually during the procedure loading a/the project), there is a chance all comes from there.
But there´s also VST stuff involved in your setup,- so that might also causing a (non constant) MIDI loop somewhere while all is loading.
dawman wrote:
Sheeez...I need a Jager.
Me too,- NOW !
Bud