More > JRiver Media Center 24 for Windows
NEW: Zone Sync 2 [Old instructions]
mattkhan:
I don't think I have the hardware to test this personally until either asio or linux is supported but I'll ask anyway, are there any particular scenarios that should be tested? or any test signals to use? or do you just want it used day to day to see what happens?
Does the "MCWS web service" translate, in practice, as "we assume you have configured all your hosts correctly with respect to time sync so will just make calls to the system clock and expect to get answers that are in sync"? if so, I don't see the relevance of the main zone having an ntp server on it.
JohnT:
--- Quote from: mattkhan on March 14, 2018, 04:36:00 am ---I don't think I have the hardware to test this personally until either asio or linux is supported but I'll ask anyway, are there any particular scenarios that should be tested? or any test signals to use? or do you just want it used day to day to see what happens?
can you expand on this pls?
--- End quote ---
It's working well on Linux for us, so when the next Linux build is posted, give it a try. You can just test it with your music collection. Something with prominent percussion, bass hits, piano, etc. makes it easier to tell quickly if it's in good sync. The "timing adjust" option on the context menu for zones is working in the new system so you can use that to tweak the sync manually if it's off. Just let us know how much it's off and what audio sub-system you're using (e.g. ALSA on Linux, and what kind of output: USB, analog, which DAC, etc.).
--- Quote ---Does the "MCWS web service" translate, in practice, as "we assume you have configured all your hosts correctly with respect to time sync so will just make calls to the system clock and expect to get answers that are in sync"? if so, I don't see the relevance of the main zone having an ntp server on it.
--- End quote ---
The main computer acts as the time server for all zones. They are provided with a URL to call so they can synchronize themselves to the main computer's clock.
If you have an NTP server running on the main computer, it will provide its NTP time server URL to the zones. Otherwise it will provide an MCWS url pointing to its own web service.
It should just work out of the box for all Media Center zones running the latest software. We added a custom DLNA call which asks if a DLNA zone supports our JRiver DLNA sync protocol and only zones running the latest Media Center software will answer in the affirmative.
JimH:
--- Quote from: mattkhan on March 14, 2018, 04:36:00 am ---I don't think I have the hardware to test this personally until either asio or linux is supported ...
--- End quote ---
ASIO might work. Linux should be supported by the end of this week.
JohnT:
By default, Windows only runs an NTP client, not server. It's easy to enable the server though, I think I used the instructions on this page to do it:
https://www.interfacett.com/blogs/creating-standalone-ntp-server-windows/
It's pretty trivial on Linux/Mac also.
You may have to re-boot afterwards, not sure. It's not necessary to run an NTP server to use the new sync system. If NTP is not available, it will instead use a new MCWS web service "Time" call (e.g. http://localhost:52199/MCWS/v1/Time). The Time function returns a 64 bit integer compatible with the "timeval" struct representing the current system time. At the client end, offsetting by half the network round-trip time gives a "close enough" value for good sync unless the network is VERY slow and the send/receive timings are very asymmetrical.
AndrewFG:
Can you please give me the details of your “custom DLNA call(s)” and the underlying architecture of how you set the clocks?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version