Exception in thread, Traceback and unable to assign requested address

jms5194 / Digico-Reaper-Link

Small Python application that links a Digico console and Reaper, handling automatic marker insertion and tracking.

MIT License

24 stars 1 forks source link

Exception in thread, Traceback and unable to assign requested address #4

Closed monikeraudio closed 2 days ago

monikeraudio commented 2 years ago

Have installed dependencies and running todays updated script - I admit to not being very well versed in programming but can trace OSC packets and they are leaving the console and not being received on the loopback address.

jms5194 commented 2 years ago

Hi!

What OS are you running on? If you are running on MacOS, please use the compiled application that you can download from the releases page on the right hand side of the page. If you want the new features I've added today (repeater for ipad support), you may need to wait a couple days for me to push a release.

Otherwise, that error stack doesn't really look like an error per say, just looks like it couldn't connect to the remote device. Are your settings correct in the preferences window in terms of remote IPs and ports?

monikeraudio commented 2 years ago

Hi,

Great to be in touch - I'm testing on both PC and OSX. With my lack of knowledge in Python I'm tracing packets in Wireshark. I can trace the OSC into the host from the console, but can't see anything coming out on the loopback address.

The screenshot was from when I was offline, and that last error line goes away when connected properly. Would any of the other notes regarding the socketserver be a cause of messages not passing through to the loopback, or is this normal?

jms5194 commented 2 years ago

When all of the IP configuration is correct, you shouldn't see any of those log messages. It should just say "Reaper OSC Server started", "Digico OSC Server Started" "Repeater OSC Server Started".

Can you send me pictures of your "External Controls" window on the console, your preferences window in Digico-Reaper Link, and your Control/OSC/Web preference page in Reaper?

monikeraudio commented 2 years ago

OK - i tried a different approach and edited the default IP address in IDLE to the IP addresses I needed instead of using the preferences. I found that the same errors would occur when updating the preferences, and then when re-loading the program the addresses had returned to default.

Now I get a clean load as you outline above, unfortunately still not receiving communication in REAPER. Settings attached below...

jms5194 commented 2 years ago

Ok, thanks for this. I'm seeing a couple issues here now. I have never tested the configuration storage portion of this in Windows, I'm working in MacOS, so let me take a look at this this evening on a windows machine and see what happens there. It seems that it is not storing the configuration persistently on Windows. Everything else looks good to me. So this is probably a problem in the code as it relates to Windows. Let me try and take a look at this tonight and I'll get back to you.

jms5194 commented 2 years ago

Can you please try and download the code again? I think you may have caught a commit that was right inbetween versions. I think you have the most current main.py but an older UI.py.

jms5194 commented 2 years ago

That doesn't solve your preferences issue, but might fix your problems with connectivity.

jms5194 commented 2 years ago

I think this should be solved now. Can you grab new versions of the script and test on your side? I'll build a windows install version if it works for you now.

ccampbelltt26 commented 2 years ago

Interested if the Windows installer has been made?

jms5194 commented 1 week ago

Hi- there is now an actual Windows version in releases- https://github.com/jms5194/Digico-Reaper-Link/releases/latest.

I'm testing it right now on a windows machine and it seems good so far. The only gotcha was that I had to manually let it though Windows Defender to allow it to communicate with the Digico. Let me know how things are looking for you now.

jms5194 commented 2 days ago

I'm going to close this issue now since I've been testing the Windows version for myself the past couple weeks and it seems to working well for me. But let me know if you continue to experience any issues with the newest windows version!