All faders were down mate. I am using 2 and 3 for my setup.
I don’t understand why it worked few days back and now it isn’t lol
Yeah weird not sure, when I’m back at my computer I’ll send over a new debug script that pulls down the mixer channel faders instead of the deck volume variables. This way we can see if the faders in your setup follow those variables, and just use those instead. I’ll post the script here when I have it written up.
Thanks for continuing to test this out, we’re so close haha
Thanks man! Hope we crack this soon;)
1 Like
Here’s the latest debug script, it will look at the mixer fader variables and log those out so we can see if that’s what your setup is using. Can you run this and post your output here, thanks! main.exe.zip (1.7 MB)
Have to pack it into dropbox. Because the readout have more lines, that we are allowed to post.
1 Like
Thanks! Looks like these variables can be used, just need to confirm they work with @ReOrderDJ’s setup
this is all that happens
C:\Users\PC>"C:\Users\PC\Downloads\main.exe (2)\main.exe"
2021/03/15 21:04:53 Listening for devices for 5s
2021/03/15 21:04:53 Discovery looping
2021/03/15 21:04:53 Started
2021/03/15 21:04:58 127.0.0.1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/15 21:04:58 Added this device: 127.0.0.1 "OBS_Plug" "Icedream StagelinQ Receiver" "0.0.0"
2021/03/15 21:04:58 Found devices: 1I have the same log. Using Prime 2 and Windows 10.
Interesting it seems like your device isn’t discoverable again, any changes with your network setup?
but it is green on unbox app mate, should I run it while ubox is running?
No you should keep unbox closed while this debug script is running, that could be the issue. Lmk if that works, I think it will.
it was off and after restart
tried main.exe again, after pc restart it looks the same 
when Run unvox it turns green and responds to play/hot cue as usual
Hmmm try this @ReOrderDJ @DrLastContaQt, modified the print statements a bit, idk why it stopped working though given it worked for @DJDark: main.exe.zip (1.7 MB)
I’m reading with interest but I’m not up for any testing at the moment. I’m currently in bed with COVID and have been since Saturday morning. I’ve sheltered this last 12 months and not even been out of the house in over two and a half weeks but it has infiltrated our walls and now I’m feeling super crappy. Great.
Keep up the good work guys. I’m reading with great interest and loving the progress!
Stay safe people x
1 Like
Damn sorry to hear this @MrWilks, feel better soon! We’ll definitely keep at it!
1 Like
Thanks @erikrichardlarson . A family member who still has to work accidentally brought it in and while I dodged it for over a week, it finally caught me and felt it starting Friday. Oh well. I’m a statistic now.
Loving the work though! 
1 Like
same result unfortunatelly
I will test it later today. Last time Prime 2 was connected to WiFi but not directly to router. It was connected do AP (with repeater on) which is connected via power line to main router. I will connect Prime 2 (via WiFi) and PC (via LAN) directly to main router today and let you know the results.
mi latest error
Last login: Tue Mar 16 09:29:54 on ttys000 /Users/enriquefernandezcenteno/Desktop/unbox-mac/unbox.app/Contents/MacOS/unbox ; exit; MBPdeEnrique13:~ enriquefernandezcenteno$ /Users/enriquefernandezcenteno/Desktop/unbox-mac/unbox.app/Contents/MacOS/unbox ; exit; Error: Command failed: ./unbox_denon_poller 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:249 +0xbdc
at ChildProcess.exithandler (child_process.js:304:12)
at ChildProcess.emit (events.js:223:5)
at maybeClose (internal/child_process.js:1021:16)
at Socket.<anonymous> (internal/child_process.js:430:11)
at Socket.emit (events.js:223:5)
at Pipe.<anonymous> (net.js:664:12) {
killed: false, code: 2, signal: null, cmd: ‘./unbox_denon_poller’ }