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

        MIDI-OX >> MIDI-OX Beta Bugs >> MIDI-OX bug ?
        
(Message started by: emilioaparicio on Dec 15th, 2003, 7:06pm)
Title: MIDI-OX bug ?
Post by emilioaparicio on Dec 15th, 2003, 7:06pm
Friends:
Using MIDI OX as downloaded from home site.  (Not Beta)

It seems I am one of the few MIDI users working with several
input ports at the same time.  

MID OX fails to display port activity in ALL ports cpnnected.

I have an SB128 MIDI in-out, plus a voyetra V22 dual port In-Out.

OX finds correctly ALL ports, and it can connect correctly any of them.  They DO work alone or in combination with YOKE.  No problem.

But the Port activity display, (the one with a lot of fake LEDs)
shows only activity in the Blaster ports.   The other ports get
no light blinking.

Good for something?  (This report, of course)

For Jammie:   I think I saw this problem reported in other sections in this forum.

Mike Aparicio
Title: Re: MIDI-OX bug ?
Post by Jamie OConnell on Dec 16th, 2003, 2:54am
I have got an UM-880 8 port device I use in testing as well as MIDI Yoke and an older SB Live.  I have seen no errors on any of these devices under Windows XP -- what version of Windows are you using?  


Quote:
But the Port activity display, (the one with a lot of fake LEDs)
shows only activity in the Blaster ports.   The other ports get
no light blinking.


Well, of course, the blinking will only occur on ports that are actually routed: the SB Input to whatever it is connected?  How is your routing set up?  You should get one Output blink for every message displayed in the Output monitor.  What other input devices are connected?  Which ports are they attached to?
Title: Re: MIDI-OX bug ?
Post by emilioaparicio on Dec 16th, 2003, 12:31pm
Fine Jammie!

I am sorry if  I am creating confusion but, here is my review about my setup and connections:

PC:        Pentium MMX 400, 64 mB
OS:        Windows 95 (Shame!....  but I only have my Voyetra V22 card with only Win 31-95 drivers.
             System performs OK.  No apparent bugs or crashes.

Hardware:
              Soundblaster SB128 with MIDI MPU 401 single in-out port.   Creative drivers
              Voyetra V22 dual in-out ports.   Drivers for 3.1 and Win 95 ONLY.

Synths:   Korg-IX-300,   Korg WaveStation EX,  Kawai K1,  Roland Sound Canvas,  and of course
            the EMU 8000 inside the Blaster.

Software:

           Cakewalk 9 Sequencer.  
           MIDI-OX and MIDI YOKE.  (Also tried Hubie with same results)

Connections:

Hardware:       KORG IX-300 out to Voyetra Port 1 IN
                    KORG IX-300 in from Voyetra Port 1 OUT

                    KORG WS-EX  out to Voyetra Port 2 IN
                    KORG WS-EX in from Voyetra Port 2 OUT.

                    KAWAI  K1   out to SB128 MIDI port IN
                    CANVAS      in from SB128 MIDI port OUT

Via MIDI-OX:
                     Voyetra Port 1 IN  into Voyetra Port 1 OUT fo echo, and to YOKE 1 for hooks
                     Voyetra Port 2 IN into Voyetra Port 2 OUT for echo and to YOKE 2 for hooks
                     SB128   MIDI  IN into SB128  MIDI   OUT for echo and to YOKE 3 for hooks

                     YOKE 4 to Voyetra Port 1 OUT   (for programs to play)
                     YOKE 5 to  Voyetra Port 2 OUT   (for programs to play)
                     YOKE 6 to  SB128  MIDI   OUT   ( for the same)
                     

In Cakewalk:

                    Selected Inputs:   YOKE 1,2 and 3
                    Selected Outputs: YOKE 4,5 and 6


RESULTS:

All connections work OK,  allowing full echo in live performance, while recording the three
ports with Cakewalk.    Cakewalk echo is set to NONE.     Each port works with DIFFERENT
MIDI channels, to avoid replication.

Live performance is recorded without a glitch !!!!

But.... MIDI OX port activity shows LEDS only for SB128 card.   The other Status window, which
shows ALL data messages,  displays correctle for ALL THREE INPUT PORTS.

The malfunction is "white" in the sense it DOES NOT affect system operation.

MY GUESS:

OX somehow gets confused under Windows 95 with the signals from Voyetra Drivers.   Incidentally, the Voyetra drivers are Multi Client!!!.    How do I know this?  because When opened by OX,  Cakewalk still can open then and use them DIRECTLY, while te Blaster cannot
be opened directly by Cakewalk, if already opened by OX.

Anyay:   If OX can route properly the Voyetra signals, IT IS GETTING THE PROPER INPUT.
Hint:      Probably has to do with the way OX interrogates the old V22 drivers for Win 95.

Or......    I'm quite a  dummy........

Please ask whatever tests you might me to run here.

Mike Aparicio
Guatemala, Land of Eternal Spring...    and corrupted elections....
Title: Re: MIDI-OX bug ?
Post by Jamie OConnell on Dec 17th, 2003, 11:22am
I believe this is a Windows 95 issue, although I will try to reproduce on Windows ME (I don't have 95).  Thanks for the report.  Incidentally, the Port Status Windows is only an additional reporting View and will not affect operation in the rest of the application.
Title: Re: MIDI-OX bug ?
Post by emilioaparicio on Dec 19th, 2003, 12:39pm
Thanks for feedback J.!

In our third world countries Win 95 is well doing and... alive!

(If you need a copy !.....(grin)

Certainly OX works well as you said, and I do my playing and recording without a glitch.   But the indicators won´t go!!!

Of course it is a good diagnostics tool, I wish I could get it to work.

Do you think I could use Voyetra drivers (for Win85) under WME ?  If that´s the case I would reinstall again to see. And to help.

Regarding OX wish list, (gues this is NOT the place, but)...

Two things,  
a) Implementing PORT reassignment or remapping, to allow
   rerouting channels from one port into another.

b) changing  connections dialog, from the actual tree structure to some screen with arrowed lines connecting devices and showing direction of data flow.

This is important because I found VERY confusing to understand INs and OUTs.  (Mind tends to see things reversed,  when puting "things" INTO AN OUT and getting "things"" FROM AN IN....)

OK.

If you need ANY tests for the Win95 buggie, just Email!!!

Bye now!

Mike
Title: Re: MIDI-OX bug ?
Post by Jamie OConnell on Dec 19th, 2003, 6:41pm

on 12/19/03 at 12:39:55, emilioaparicio wrote:
Do you think I could use Voyetra drivers (for Win85) under WME ?  If that´s the case I would reinstall again to see. And to help.


Sure, why not?


Quote:
Regarding OX wish list, (gues this is NOT the place, but)...

Two things,  
a) Implementing PORT reassignment or remapping, to allow
   rerouting channels from one port into another.

b) changing  connections dialog, from the actual tree structure to some screen with arrowed lines connecting devices and showing direction of data flow.

This is important because I found VERY confusing to understand INs and OUTs.  (Mind tends to see things reversed,  when puting "things" INTO AN OUT and getting "things"" FROM AN IN....)


I believe both A) and B) are answered by the new Routings View in MIDI-OX 7.0.  Look in the MIDI-OX help file for more info.


MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1!
YaBB © 2000-2003. All Rights Reserved.