0xtob / dsmi

Automatically exported from code.google.com/p/dsmi
2 stars 3 forks source link

"Error initing MIDI2UDP!" #16

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install LoopBe1
2. Unzip DSMI
3. Launch DSMIDIWiFi.EXE

What is the expected output? What do you see instead?
Expect to see Input/Output selection window. Instead, see error dialog box,
"Error initing MIDI2UDP!"

What version of the product are you using? On what operating system?
DSMIDIWiFi.EXE 1.01, LoopBe1 1.5.1, Win 7 64bit.

Please provide any additional information below.

Original issue reported on code.google.com by bfre...@gmail.com on 21 May 2010 at 6:24

GoogleCodeExporter commented 9 years ago
I'm seeing the same thing but with the only difference being XP SP3 (32 bit).

I know it worked a while back, so I'm assuming that a recent MS fix may have 
broken something.

Original comment by Chris.O....@gmail.com on 16 Jun 2010 at 5:32

GoogleCodeExporter commented 9 years ago
I'm dual booting, with two physical drives in this system. Win7 64 and XP SP3. 
I don't have the issue in XP. Just Win7.

It is a mystery! :)

Original comment by bfre...@gmail.com on 16 Jun 2010 at 9:40

GoogleCodeExporter commented 9 years ago
DSMIDIWiFi.EXE 1.01, LoopBe1 1.5.1, Win 7 64bit. After clearing "Error initing 
MIDI2UDP!" dialog I receive "Could not bind to port9000!" dialog. Also receive 
"Could not bind to port9000!" dialog when selecting input or output ports.

Original comment by cthulhu...@gmail.com on 28 Jun 2010 at 9:58

GoogleCodeExporter commented 9 years ago
I'm having the exact same problem as cthulhu232, and I have the exact same 
setup.  Pretty frustrating.

Original comment by hill5...@telus.net on 22 Jul 2010 at 2:40

GoogleCodeExporter commented 9 years ago
I disabled LoopBe1 and installed Midi Yoke and everything is working fine. I 
subsequently uninstalled LoopBe1 

Which makes me wonder.   How are you supposed to use LoopBe1, when it only has 
one input and output?

Original comment by Chris.O....@gmail.com on 22 Aug 2010 at 3:33

GoogleCodeExporter commented 9 years ago
same here. winXP sp3, maple midiport. please resolve.

Original comment by botofogo...@gmail.com on 11 Oct 2010 at 6:02

GoogleCodeExporter commented 9 years ago
Same here, Win 7 64 bits.

Original comment by guy.si...@gmail.com on 15 Oct 2010 at 1:13

GoogleCodeExporter commented 9 years ago
Same problem here windows xp sp2

Original comment by Ax2par...@gmail.com on 9 Jun 2011 at 3:17

GoogleCodeExporter commented 9 years ago
same probs on windows seven 64bit french full edition....

Original comment by luda...@gmail.com on 10 Nov 2011 at 2:06

GoogleCodeExporter commented 9 years ago
I am a dj it not working ok howe can i fick it

Original comment by 3565jlz...@gmail.com on 16 Jan 2012 at 8:28

GoogleCodeExporter commented 9 years ago
for the "Could not bind to port xxxx" issue....i think it means another program 
is using port xxxx so download a port diagnostic tool like 
http://www.nirsoft.net/utils/cports.html then look at what is on port xxxx

Original comment by be.e...@gmail.com on 4 Mar 2012 at 10:46

GoogleCodeExporter commented 9 years ago
check youre taskmanager. you will see that the program will still be there and 
you wont be able to kill it

Original comment by Lord...@gmail.com on 7 Apr 2012 at 11:26

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
anyone?

Original comment by felipe....@gmail.com on 1 Jul 2012 at 6:37

GoogleCodeExporter commented 9 years ago
running linux mint 13, same story. nothing i do changes anything

Original comment by marckee...@gmail.com on 28 Apr 2013 at 11:47

GoogleCodeExporter commented 9 years ago
Ubuntu 12.04 same error

Original comment by Crossfad...@gmail.com on 19 Aug 2013 at 3:59

GoogleCodeExporter commented 9 years ago
On ubuntu 13.10 I had the same error, solved with :
sudo apt-get install libasound2-plugins:i386

It seems that many necessary lib files need to be on x86 version.
On ubuntu 64bit, since 13.10 the x86 libs are managed like this :
sudo dpkg --add-architecture i386

But it does not work for all apps, so you need to check every lib and do :
sudo apt-get install package-name:i386

It worked well for me

Original comment by pierrelo...@gmail.com on 13 Mar 2014 at 6:15