Yet another reastream puzzle!

[papagirafe]

Hi,

I am puzzled with Reastream. About 6 weeks ago I did a series of tests on audio/midi transmission between various machines on my "home #2" network and it was working as expected with local broadcast and specific IP adresses. Unfortunately I did not save the test project at that time.

Now I am setting up a new test at my "home #2" (with the same computer) that requires specific IP adresses and it just doesn't work anymore. Even the loopback address 127.0.0.1 that was initially working doesn't work anymore. I disabled the windows firewall completely but no luck. I tried an network ip loopback on a different micro router but no luck.

Since the initial tests, 3 things have changed: the main router is not the same, windows 10 went through 4 or 5 updates, reaper was updated twice...

Any ideas? What are exactly the ports and protocols to clear on the network?

[jrk]

Hmmm, localhost or 127.0.0.1 doesn't work?

1. You should be able to ping 127.0.0.1 - to rule out anything deeply weird.

That works I guess?

2. Can you ping the target IP from the source machine?

I believe the port for ReaStream is 58710.

3.Maybe try netstat to see if something's sitting on it?

Although that shouldn't be a problem.

[papagirafe]

Ok

1- yes, 127.0.0.1 works again along with local broadcast
2- all pings to any destination are working fine
3- Interestingly, Netstat did not reveal any UDP connection at the moment of my tests or anything on port 58710. I repeated the test with and without the firewall with same results. I also had disactivated all other unused network interfaces to leave just one and disabled ipv6 at the same time. Nothing changed...
So i am still puzzled :-(

Originally Posted by jrk

Hmmm, localhost or 127.0.0.1 doesn't work?

1. You should be able to ping 127.0.0.1 - to rule out anything deeply weird.

That works I guess?

2. Can you ping the target IP from the source machine?

I believe the port for ReaStream is 58710.

3.Maybe try netstat to see if something's sitting on it?

Although that shouldn't be a problem.

thanks for the suggestions!

[jrk]

All I can say is Good Luck - I'm sure there's someone on here who can help.

[papagirafe]

Finally! JRK I found the culprit!

All my recent tests were done using one track sending sound or midi "externally" to a second track within the same reaper on the same machine because I did not have access to two computers (kids on-line school). I finally tested with 2 physical machines and it just works as expected.

This is a bit of a surprise since a lot of computer programs I have worked with in the past supported "external ip" loopback. I have some idea why this is a restriction (port is already occupied ?) but it's not such a problem after all....

[jrk]

Glad you figured it out. I'll file this away in my mental crap hoard. I'm on win7 and ReaStreaming to the machines own address works just fine.