D8Bridge stopped working after update to W8.1

[RustyNotes]

I don't know what I did wrong.. but i can't run D8bridge anymore since i upgraded to Windows 8.1
When I run D8Bridge, an error comes up saying: Could not initialize COM port from last configuration

I have a serial to usb-adapter, and no matter which USB port I plug it in, it doesn't work. When I look in the Device manager, it says that I'm connected to "com port 5", and even If i choose com 5 in D8Bridge, I'm out of luck. Same thing happens if i try to plug it in another USB port (for example "com port 3"). Same thing there, same error. I've tried to uninstall the drivers and re-installed them, but no luck there either.

Do any of you have a fix for this? If not.. Marc.. please hurry with D8brige 2.0 so I can use it with ethernet!

[Marc Girard]

It might be that the fact that W8.1 has changed the COM port? Just saying, if it was working in Win7/8, it should work in 8.1, there's no "major" changes. Kinda hard to diagnose over a forum post...

[RustyNotes]

Yeah I know. When I get home, i'll try reinstall loopmidi and everything else and take some snapshots

[RustyNotes]

nope.. doesn't work..



FULL IMAGE: http://i42.tinypic.com/10wpb4n.png

[Marc Girard]

nope.. doesn't work..

I just installed Windows 8.1 on my laptop. Will investigate that problem.

[bitSync]

nope.. doesn't work..



FULL IMAGE: http://i42.tinypic.com/10wpb4n.png

I noticed it looks like you have an orphaned MIDI Output port for Mackie Control Unit 1 (unless the LoopMIDI ports are numbered from 0 rather than 1 and for some reason 0 doesn't show up). It looks as though all your port assignments may have shifted "left" by 1 port. I've seen this in D8Bridge v1.1 repeatedly as a consequence of any number of circumstances including adding or deleting MIDI devices or device driver updates between D8Bridge invocations; installing Windows 8.1 might qualify as one of these circumstances, I don't know. My theory is that the D8Bridge v1.1 MIDI port mapping is using discrete indices or offsets to MIDI ports rather than the actual port identity, so if the MIDI port mapping changes in the port array between D8Bridge invocations, D8Bridge doesn't know and just uses its last known index/offset. You may want to remap your loopMIDI ports using the D8Bridge GUI (Start with the highest numbered MIDI port first (Port 6) and work downwards, otherwise, if you try to assign e.g., Port 5 when it's already assigned elsewhere, bad stuff happens and you'll have to reboot D8Bridge).

This may not fix your COM problem, but who knows... Best of luck!

[bitSync]

Also, the port order for MCU3 seems inconsistent with MCU1 and MCU2. The order is reversed?

[RustyNotes]

well, i can't change any of the left hand side ports.. the program freezes and i have to do the old good ctrl+alt+del to close it. The right hand side I can change.. but not the left. Hah, fun! Can't wait for version 2.0 ^^

[RustyNotes]

ok, just tried setting everything up correctly. All ports as they should be and the right COM. Still the same thing. So I give up and will be waiting for version 2.0 instead

[bitSync]

well, i can't change any of the left hand side ports.. the program freezes and i have to do the old good ctrl+alt+del to close it. The right hand side I can change.. but not the left. Hah, fun! Can't wait for version 2.0 ^^

To reiterate, you need to start with the highest numbered LoopMIDI port first, port 6, then work downwards to port 1. If you try to assign a port that is already assigned, e.g., like trying to reassign port 5 when it's assigned elsewhere, the program will lockup and then you'll have to kill the d8bridge.exe process for sure.

Also, probably the easiest thing you can do is to just shut down D8Bridge (make certain the process is not running, sometimes it looks like it has shut down when it hasn't), delete config.d8b (every freakin' instance of it on your machine) and start D8Bridge again. This will force D8Bridge to create a new config file as though this is its first invocation and you can start fresh with your port assignments. This might help you with your COM problem as well.

You are using the 32 bit .exe, right?

Let us know how you make out.