MIDI-OX User Forum - Print Page


    
      
        MIDI-OX User Forum
        (http://www.midiox.com/cgi-bin/yabb/YaBB.pl)
      

        MIDI-OX >> MIDI-OX Beta Bugs >> Boogie on Route 66 :-) (6.7b3)
        
(Message started by: not2good2c on Jul 12^th, 2003, 11:54am)

Title: Boogie on Route 66 :-) (6.7b3)
Post by not2good2c on Jul 12^th, 2003, 11:54am

Cheers ;-)… (10h after)

I wanted to compare the sound of my onboard XG chip versus the sound of S-YXG. Differences in sound were obvious, but I wanted to see if these resulted from different effect levels etc. For this purpose I loaded the S-YXG player (with which I could easily solo each voice) and an XG-editor for editing the sound, because the S-YXG player is too commonplace for me to understand. Both ~~synthesizers~~ the player and the editor used the same MidiYoke Junction and I was switching them from one synth to another with the all-new routing interface.

The problems started when I had switched both the player and the editor from one synth to another for several times. I had made edits to the sound with the editor, but as the player always sent the information stored at the beginning of the MIDI file, I was making use of the editor’s Refresh function after starting playback. At one point it became audible that the data sent from the editor (SysEx) does not reach the output any more (although the editor was connected to it). When I stopped the player, cleared both the Input and the Output monitor, checked the routing, then refreshed the parameters from the editor once again, I could see that SysEx data sent from the editor was displayed in the Input monitor, but not in the Output monitor.

When I let the bird out of the cage and called it back again, I realized that SysEx data from the editor reached the port that was connected before closing the ports, but did not reach the port (after its reconnection in the routing interface) that was disconnected before closing the ports. CC’s passed, but SysEx didn’t.

:8{)

P.S. I have reproduced this bug (10 hours after). If you can’t reproduce it on other systems, try Windows 98.

Title: Re: Boogie on Route 66 :-) (6.7b3)
Post by Jamie OConnell on Jul 15^th, 2003, 2:09pm

Quote:

When I stopped the player, cleared both the Input and the Output monitor, checked the routing, then refreshed the parameters from the editor once again, I could see that SysEx data sent from the editor was displayed in the Input monitor, but not in the Output monitor.

When I let the bird out of the cage and called it back again, I realized that SysEx data from the editor reached the port that was connected before closing the ports, but did not reach the port (after its reconnection in the routing interface) that was disconnected before closing the ports. CC’s passed, but SysEx didn’t.

Is it possible, that Pass SysEx got turned off? Or the [x] Exclusive box got turned off in the connection properties? To access connection properties you right-click on the connection line.

Title: Re: Boogie on Route 66 :-) (6.7b3)
Post by not2good2c on Jul 16^th, 2003, 7:36am

The Exclusive (SysEx) box is checked in Connection Properties and the SysEx branch exists in the MIDI Devices tree, but SysEx does not pass.

In conclusion: After opening the MIDI ports (at program start or later), SysEx passes only to the port that was ~~open~~ connected before closing the ports.

Title: Re: Boogie on Route 66 :-) (6.7b3)
Post by Jamie OConnell on Jul 20^th, 2003, 1:30pm

OK. Thanks for the info.

Title: Re: Boogie on Route 66 :-) (6.7b3)
Post by not2good2c on Jul 21^st, 2003, 8:15pm

That there's a place where everyone stops to boogie on Route 66? ;{)