Here’s another debug script that polls for 30s and may log some more details, want to give it a shot?unbox_denon_poller.zip (1.8 MB)
Yeah would just need to change the write behavior a bit and add a new view, I can add that to my list of things to do here.
Nice glad it’s working, yeahh the html files are hosted on a local webserver so editing an existing one should work for you.
still no luck with PC and MAC works when it wants to and with previously described issues on my denon gear:)
Unfortunately I’ve tried everything and think it is my MacBook Pro that isn’t playing ball. I can try the Windows machine that I have but that is not solving the Mac issue. I will keep going though! I tried the updated 30s poller but still refuses to even show a connection.
I have checked my firewall setting and even disabled it to try it. One thing that I have noticed is that Unbox asks upon every opening if I want to allow connections. This didn’t happen in previous non-Denon builds, or at least from what I remember anyway. It is authorised in my firewall yet still asks.
I have found a few quirks with the “Cancel” button too. I’ll drop them here but I can log them officially in the GitHub section if you want?
Pressing the “Cancel” button when already on the Unbox home screen causes a few problems:
- The time delay slider to reset to the middle, even though the delay time is showing “0”.
- The colour picker for text resets the chosen colour back to the default black.
- The LOCAL URL and REMOTE URL get deleted from their respective boxes.
- When in Serato mode, the “Go live” indicator goes green and shows the last played track.
- Even going into the “Denon” option, shows the Serato “connected” indicator and track.
I think the way around it would be to remove the “Cancel” button from the home screen so it can’t be pressed and cause this glitch. It seems to all stem from this.
@ReOrderDJ Hmmm weird that Mac just stops working, I’m going to modify the go library a bit so we can see what’s happening in the Discover method on failure and see if that provides us any clues as to why this fails on Mac.
Oh yeah the Cancel button isn’t set up to do anything, but is set to type reset and seems to be breaking things, I’ll definitely remove that in the next release we get out here when we have Denon fully working. Thanks for the feedback as always!
Thanks for letting me know mate. As I said I am happy to jump on a call and help you figure this out. I am streaming daily now and this tool is something so essential that I can’t sleep knowing its working on sc6000 but not sc5000 i have
of course, we’re so close! yeah let me get this new debug script written up and I’ll have y’all post the output here, and we can go from there. i’m not great at golang so having you wait for me to write / lookup code on a call might be annoying haha
@ReOrderDJ @MrWilks here are two new debug scripts that log out more details as the discovery code kicks off, same as before you can unzip these and just run them, just make sure unbox isn’t open and stays closed while you run these debug scripts, please post your output here if you’re still unable to see a connection to your gear in the console output of these debug scripts. thanks!
Mac debug main.zip (1.8 MB)
Windows debug main.exe.zip (1.7 MB)
not sure if this helps but this is MAC withour running UBOX at ALL, just the main script you sent:
Last login: Thu Mar 11 17:13:45 on ttys000
The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh
.
For more details, please visit https://support.apple.com/kb/HT208050.
/Users/ReOrderDJ/Downloads/main ; exit;
Mac-mini:~ ReOrderDJ$ /Users/ReOrderDJ/Downloads/main ; exit;
2021/03/11 17:15:10 Listening for devices for 5s
2021/03/11 17:15:10 Discovery looping
2021/03/11 17:15:10 Started
2021/03/11 17:15:10 Discovery looping
2021/03/11 17:15:10 Bytes: 152, source: [::1]:61191, error:
2021/03/11 17:15:10 Checking IP:Port [::1]:61191
2021/03/11 17:15:10 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:15:10 Device was ourself
2021/03/11 17:15:11 Discovery looping
2021/03/11 17:15:11 Bytes: 152, source: [::1]:59724, error:
2021/03/11 17:15:11 Checking IP:Port [::1]:59724
2021/03/11 17:15:11 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:15:11 Device was ourself
2021/03/11 17:15:12 Discovery looping
2021/03/11 17:15:12 Bytes: 152, source: [::1]:52268, error:
2021/03/11 17:15:12 Checking IP:Port [::1]:52268
2021/03/11 17:15:12 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:15:12 Device was ourself
2021/03/11 17:15:13 Discovery looping
2021/03/11 17:15:13 Bytes: 152, source: [::1]:52892, error:
2021/03/11 17:15:13 Checking IP:Port [::1]:52892
2021/03/11 17:15:13 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:15:13 Device was ourself
2021/03/11 17:15:14 Discovery looping
2021/03/11 17:15:14 Bytes: 152, source: [::1]:58469, error:
2021/03/11 17:15:14 Checking IP:Port [::1]:58469
2021/03/11 17:15:14 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:15:14 Device was ourself
2021/03/11 17:15:15 Discovery looping
2021/03/11 17:15:15 Bytes: 0, source: , error: read udp [::]:51337: i/o timeout
2021/03/11 17:15:15 Timed out
2021/03/11 17:15:15 ::1 “OBS_Plug” “Icedream StagelinQ Receiver” “0.0.0”
2021/03/11 17:15:15 Added this device: ::1 “OBS_Plug” “Icedream StagelinQ Receiver” “0.0.0”
2021/03/11 17:15:15 Found devices: 1
logout
Saving session…
…copying shared history…
…saving history…truncating history files…
…completed.
[Process completed]
WINDOWS WORKS! BUT:)
I see it is working now on Windows, but it doesn’t react to faders it only swaps tracks after following order of buttons is being pressed:
CUE, PLAY/HOT CUE
This loads the track ID
It doesn’t matter whether the fader is up or down
If the CUE button is not pressed it won’t load the track ID
When new track is Loaded it changes the track ID for the loaded track
It doesn’t matter whether the fader is up or down
I think you are very CLOSE ,ate!
@DJDark Can you run this latest debug script on Windows and send over the output so we can get a better sense of what working output looks like here? Thanks!
Thanks for sending this over @ReOrderDJ!
My output on the Mac is:
panic: listen udp :51337: bind: address already in use
goroutine 1 [running]:
main.main()
/Users/erik.larson/Downloads/go-stagelinq-master 2/cmd/stagelinq-discover/main.go:237 +0xbdc
[Process completed]
And after a restart of the MacBook:
/Desktop/main ; exit;
2021/03/11 17:50:05 Listening for devices for 5s
2021/03/11 17:50:05 Discovery looping
2021/03/11 17:50:05 Started
2021/03/11 17:50:05 Discovery looping
2021/03/11 17:50:05 Bytes: 152, source: [::1]:62819, error: <nil>
2021/03/11 17:50:05 Checking IP:Port [::1]:62819
2021/03/11 17:50:05 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:50:05 Device was ourself
2021/03/11 17:50:06 Discovery looping
2021/03/11 17:50:06 Bytes: 152, source: [::1]:57764, error: <nil>
2021/03/11 17:50:06 Checking IP:Port [::1]:57764
2021/03/11 17:50:06 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:50:06 Device was ourself
2021/03/11 17:50:07 Discovery looping
2021/03/11 17:50:07 Bytes: 152, source: [::1]:57471, error: <nil>
2021/03/11 17:50:07 Checking IP:Port [::1]:57471
2021/03/11 17:50:07 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:50:07 Device was ourself
2021/03/11 17:50:08 Discovery looping
2021/03/11 17:50:08 Bytes: 152, source: [::1]:54756, error: <nil>
2021/03/11 17:50:08 Checking IP:Port [::1]:54756
2021/03/11 17:50:08 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:50:08 Device was ourself
2021/03/11 17:50:09 Discovery looping
2021/03/11 17:50:09 Bytes: 152, source: [::1]:59705, error: <nil>
2021/03/11 17:50:09 Checking IP:Port [::1]:59705
2021/03/11 17:50:09 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:50:09 Device was ourself
2021/03/11 17:50:10 Discovery looping
2021/03/11 17:50:10 Bytes: 0, source: <nil>, error: read udp [::]:51337: i/o timeout
2021/03/11 17:50:10 Timed out
2021/03/11 17:50:10 ::1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/11 17:50:10 Added this device: ::1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/11 17:50:10 Found devices: 1
[Process completed]
WINDOWS WORKS! BUT:)
I see it is working now on Windows, but it doesn’t react to faders it only swaps tracks after following order of buttons is being pressed:
CUE, PLAY/HOT CUE
This loads the track ID
It doesn’t matter whether the fader is up or down
If the CUE button is not pressed it won’t load the track ID
When new track is Loaded it changes the track ID for the loaded track
It doesn’t matter whether the fader is up or down
I think you are very CLOSE mate!
My results:
Last login: Thu Mar 11 16:46:09 on console
/Users/Wilks/Downloads/main ; exit;
Wilks@Chriss-MBP ~ % /Users/Wilks/Downloads/main ; exit;
2021/03/11 16:55:54 Listening for devices for 5s
2021/03/11 16:55:54 Discovery looping
2021/03/11 16:55:54 Started
2021/03/11 16:55:54 Discovery looping
2021/03/11 16:55:54 Bytes: 152, source: [::1]:60338, error: <nil>
2021/03/11 16:55:54 Checking IP:Port [::1]:60338
2021/03/11 16:55:54 Device from discovery Icedream StagelinQ Receiver
2021/03/11 16:55:54 Device was ourself
2021/03/11 16:55:55 Discovery looping
2021/03/11 16:55:55 Bytes: 152, source: [::1]:63432, error: <nil>
2021/03/11 16:55:55 Checking IP:Port [::1]:63432
2021/03/11 16:55:55 Device from discovery Icedream StagelinQ Receiver
2021/03/11 16:55:55 Device was ourself
2021/03/11 16:55:56 Discovery looping
2021/03/11 16:55:56 Bytes: 152, source: [::1]:64781, error: <nil>
2021/03/11 16:55:56 Checking IP:Port [::1]:64781
2021/03/11 16:55:56 Device from discovery Icedream StagelinQ Receiver
2021/03/11 16:55:56 Device was ourself
2021/03/11 16:55:57 Discovery looping
2021/03/11 16:55:57 Bytes: 152, source: [::1]:60785, error: <nil>
2021/03/11 16:55:57 Checking IP:Port [::1]:60785
2021/03/11 16:55:57 Device from discovery Icedream StagelinQ Receiver
2021/03/11 16:55:57 Device was ourself
2021/03/11 16:55:58 Discovery looping
2021/03/11 16:55:58 Bytes: 152, source: [::1]:60127, error: <nil>
2021/03/11 16:55:58 Checking IP:Port [::1]:60127
2021/03/11 16:55:58 Device from discovery Icedream StagelinQ Receiver
2021/03/11 16:55:58 Device was ourself
2021/03/11 16:55:59 Discovery looping
2021/03/11 16:55:59 Bytes: 0, source: <nil>, error: read udp [::]:51337: i/o timeout
2021/03/11 16:55:59 Timed out
2021/03/11 16:55:59 ::1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/11 16:55:59 Added this device: ::1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/11 16:55:59 Found devices: 1
[Process completed]
The interesting thing is that @icedream has a Prime 4 and his code works.
I thought that I would drop my configuration below just in case:
- MacBook Pro 15" (Mid-2012)
- Catalina 10.15.7
- 16GB RAM
- 2 x SanDisk Ultra SSD (480GB & 960GB)
- WiFi set to ON (both MacBook Pro & Prime 4)
- Connected via ethernet
Interesting, can you post the windows output here? The fader positions are output to the console so we should be able to see what’s going on here.
It works now after the second restart, but I discounted my USB-C Hub with my wired network as well.
I guess that might be an issue? Having two network cards to deal with ?
I tried with the MacBook Pro WiFi OFF and got “nil” this time:
Last login: Thu Mar 11 17:19:22 on ttys000
Wilks@Chriss-MBP ~ % /Users/Wilks/Downloads/main ; exit;
2021/03/11 17:19:22 Listening for devices for 5s
2021/03/11 17:19:22 Discovery looping
2021/03/11 17:19:22 Started
2021/03/11 17:19:22 Discovery looping
2021/03/11 17:19:22 Bytes: 152, source: [::1]:51889, error: <nil>
2021/03/11 17:19:22 Checking IP:Port [::1]:51889
2021/03/11 17:19:22 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:19:22 Device was ourself
2021/03/11 17:19:23 Discovery looping
2021/03/11 17:19:23 Bytes: 152, source: [::1]:64472, error: <nil>
2021/03/11 17:19:23 Checking IP:Port [::1]:64472
2021/03/11 17:19:23 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:19:23 Device was ourself
2021/03/11 17:19:24 Discovery looping
2021/03/11 17:19:24 Bytes: 152, source: [::1]:51970, error: <nil>
2021/03/11 17:19:24 Checking IP:Port [::1]:51970
2021/03/11 17:19:24 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:19:24 Device was ourself
2021/03/11 17:19:25 Discovery looping
2021/03/11 17:19:25 Bytes: 152, source: [::1]:52850, error: <nil>
2021/03/11 17:19:25 Checking IP:Port [::1]:52850
2021/03/11 17:19:25 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:19:25 Device was ourself
2021/03/11 17:19:26 Discovery looping
2021/03/11 17:19:26 Bytes: 152, source: [::1]:50606, error: <nil>
2021/03/11 17:19:26 Checking IP:Port [::1]:50606
2021/03/11 17:19:26 Device from discovery Icedream StagelinQ Receiver
2021/03/11 17:19:26 Device was ourself
2021/03/11 17:19:27 Discovery looping
2021/03/11 17:19:27 Bytes: 0, source: <nil>, error: read udp [::]:51337: i/o timeout
2021/03/11 17:19:27 Timed out
2021/03/11 17:19:27 ::1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/11 17:19:27 Added this device: ::1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/11 17:19:27 Found devices: 1
[Process completed]
Yeah that could be an issue, can you post the output of a successful connection here?
Here is the output with the software running, or should I close the software first?
panic: listen udp :51337: bind: address already in use
goroutine 1 [running]:
main.main()
/Users/erik.larson/Downloads/go-stagelinq-master 2/cmd/stagelinq-discover/main.go:237 +0xbdc
[Process completed]
I tested it, after a restart, just wifi connection, works as it should. As soon I plug in my hub it stops working. shows still the green light but doesn’t change the song names.
Another restart, wifi off, just the hub with a wired connection, works well.
Good to know, sounds like we need to handle multiple networks cards. So can you run the debug script and send us the output when it’s successful? Want to see what happens when a successful connection to your gear is made, I hope this can help us see where things fail haha