Welcome, Guest
Username: Password: Remember me
NOTE: This forum is community powered. Please be mindful that long time community members are here to help as part of a community effort. If you have a specific issue (e.g. hardware, failure), please use our tech support portal (Support menu - > Contact Us). Thanks a lot of your help in making a better community. :-)

TOPIC: New Dirac 2.0 cannot find your device? My solution

New Dirac 2.0 cannot find your device? My solution 2 weeks 6 days ago #43707

  • HansVanEijsden
  • HansVanEijsden's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 13
  • Thank you received: 11
  • Karma: 2
Dear all,

I couldn't get Dirac 2.0 to work on my Mojave iMac (2012, 27"), although it worked fine on my Mojave MacBook Pro (2015, 15").
And yes, I was launching Dirac 2.0 (2.2.3 to be honest) from the DDRC24.app ("Start Dirac Live Software" button).

This evening I decided to do some debugging.
I went to Applications -> MiniDSP and right clicked on DDRC-24.app and then "Show package contents". Then I went to Contents -> Resources -> add and double clicked "minidsp_dirac" to launch the app in terminal.
It gave me an interesting error: "ERROR [runChangedIpJob] Error: bind: Address already in use". Yay!

So I decided to run "minidsp_dirac --help" in terminal. This was the output:
$ /Applications/MiniDSP/DDRC-24.app/Contents/Resources/add/minidsp_dirac --help
Dirac IO example server
Usage: /Applications/MiniDSP/DDRC-24.app/Contents/Resources/add/minidsp_dirac [OPTIONS]

Options:
  -h,--help                   Print this help message and exit
  -d,--devs                   List the available (Portaudio) devices, for debugging.
  -u,--uuid TEXT              Assigns the server the given unique device identifier.
  -n,--name TEXT              Assigns the server the given name.
  --model-name TEXT           Assigns the server the given model name.
  --manufacturer TEXT         Assigns the server the given manufacturer name.
  -p,--port INT                Sets the TCP port to listen to, default is 5000.
  --http-port INT              Sets the HTTP port to listen to, default is 8080.
  -l,--log-level TEXT in {DEBUG,ERROR,FATAL,INFO,TRACE,WARN}
                              Log level. Default is INFO.
  --no-input                  Disables using default input audio device

Do you see what I see? DDRC24.app needs two unused (default) ports: port 5000 and port 8080. But... my port 8080 was in use, because I have a Java program running on my machine, 24/7 listening on port 8080.
After changing the port of the Java program to port 8081 and restarting the Java program, Dirac 2.0 finds my DDRC24! Finally!

To test which program is using your port 8080, run (for example) this in Terminal:
sudo lsof -n -i4TCP:8080 | grep LISTEN
And to test for port 5000:
sudo lsof -n -i4TCP:5000 | grep LISTEN

Good luck!
Last Edit: 2 weeks 6 days ago by HansVanEijsden.
The administrator has disabled public write access.
The following user(s) said Thank You: devteam, ross, denver8me4dinner, rodrigaj

New Dirac 2.0 cannot find your device? My solution 2 weeks 6 days ago #43709

  • rodrigaj
  • rodrigaj's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 8
  • Thank you received: 1
  • Karma: 0
And if the ports are not in use and you run those scripts in Terminal, what can you expect to see?
The administrator has disabled public write access.

New Dirac 2.0 cannot find your device? My solution 2 weeks 6 days ago #43710

  • HansVanEijsden
  • HansVanEijsden's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 13
  • Thank you received: 11
  • Karma: 2
rodrigaj wrote:
And if the ports are not in use and you run those scripts in Terminal, what can you expect to see?
A blank line: no output.

P.S. I changed something in my post above: I included "sudo" in front of the lsof commands, to run them with the necessary privileges.
The administrator has disabled public write access.

New Dirac 2.0 cannot find your device? My solution 2 weeks 6 days ago #43713

  • denver8me4dinner
  • denver8me4dinner's Avatar
  • Offline
  • Gold Boarder
  • 3038564518
  • Posts: 252
  • Thank you received: 47
  • Karma: 6
Added positive karma

Excellent, thank you!
The administrator has disabled public write access.
The following user(s) said Thank You: HansVanEijsden

New Dirac 2.0 cannot find your device? My solution 2 weeks 6 days ago #43731

  • Rusev
  • Rusev's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 15
  • Thank you received: 1
  • Karma: 1
for windows ... cmd command

netstat -ano | findstr 8080
The administrator has disabled public write access.

New Dirac 2.0 cannot find your device? My solution 2 weeks 6 days ago #43737

  • aedagnino
  • aedagnino's Avatar
  • Offline
  • Junior Boarder
  • Posts: 25
  • Thank you received: 5
  • Karma: 1
Well... I haven't been able to use 2.0 on a DDRC-24... I'm using Mojave in a 2012 Macbook Pro and I've installed, deinstalled and reinstalled everything, upgraded the firmware, refreshed... and everytime I press the start dirac live button in the ddrc app it opens the firmware upgrade tool. Any suggestions?
The administrator has disabled public write access.

New Dirac 2.0 cannot find your device? My solution 2 weeks 5 days ago #43746

  • ChristianJo
  • ChristianJo's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 1
  • Thank you received: 1
  • Karma: 0
@HansvanEijsden: added karma, your solution helped me with mine :)

My setup: DDRC24 with MacBookPro (Mojave) and bootcamp Windows10.

Problem: On my Mojave and Windows10 Dirac won't connect. Device not found / network unavailable.
Both ports (5000 and 8080) on Mojave / Windows10 were unused, but I have different devices (diskstation, PanasonicTV, Denon AVR) with apache web servers running on port 8080.

After disconnecting these devices from my network, Dirac program is able to connected to my DDRC24 under Windows10.
My Mojave Dirac setup still not able to connect to DDRC24.

I'm fine with Dirac under Windows10 until MiniDSP/Dirac change their communication ports.

Hope, this will help others. best Christian
Last Edit: 2 weeks 5 days ago by ChristianJo.
The administrator has disabled public write access.
The following user(s) said Thank You: HansVanEijsden

New Dirac 2.0 cannot find your device? My solution 2 weeks 5 days ago #43766

I found what I consider a flaw in the plugin -> Dirac launch:

They use hard-coded ports 5000 and 8080 to communicate with no way to override the default or set the "-p" or "--http-port" command line parameters!

I already had an HTTP server (BlueIris surveillance) in my LAN on port 8080 (the secondary de-facto standard after port 80). I had to reconfigure my server to another port, redo all the firewall, and reconfigure all my web clients, but Dirac now launches properly.

IMHO, this is a major fail in MiniDSP/Dirac's part in basic software/network engineering.
Last Edit: 2 weeks 5 days ago by [email protected].
The administrator has disabled public write access.
The following user(s) said Thank You: Rusev

New Dirac 2.0 cannot find your device? My solution 2 weeks 5 days ago #43770

  • aedagnino
  • aedagnino's Avatar
  • Offline
  • Junior Boarder
  • Posts: 25
  • Thank you received: 5
  • Karma: 1
Well, finally was able to run Dirac 2.0!
Running OSX Mojave, Dirac 2.2.3 on a Macbook Pro 13" Mid 2012. Previously when I pressed the start dirac button in the ddrc-24 app it opened the firmware upgrade tool... still does that, but I opened the Dirac Live app from the finder after pressing the start dirac button and it all works! Been able to do the measurements and run the filter.
I have my dirac 1.0 filter on slot 1 and dirac 2.0 filter on slot 2 for comparisons... I'll have to probably tweak and do more measurements, but the difference is not subtle at least in my system. Voices and instrumentes are clearer, soundstage is bigger. I'm happy!
The administrator has disabled public write access.
The following user(s) said Thank You: HansVanEijsden
Moderators: devteam