0 Members and 1 Guest are viewing this topic. Read 20431 times.
As of today, I run single PC. I run an intel server motherboard with a XEON low TDP processor, 4GB of low latency RAM, and a Paul Pang v2 USB output card. For power, I currently run a wide input picoPSU with a FSP SMPS (19V, 6A), and a battery powering my OS SSD. For software, I run WS2012 R2, AudiophileOptimizer, and J.River 19. I can't decide whether or not JPLAY is an improvement to the sound or not with this setup, but on my CAPS v3 Lagoon running WS2012 and Phil's early optimizer, JPLAY was a must for me. I can't explain this.
Did you configure this on your own or is there an online guide/discussion that you followed?
It's what my next pc will be, as I stated in the other thread. Most of what Terry has built into that pc is based on AudioPhil's experimentation (creator of AudioOptimizer). However, Terry tweaked it a little cuz he wanted the FC8 case, etc.
Kenreau, assuming you still have your mac-mini and a PC computer, you might download JRiver MC19 and have a shoot out between the two setups. If they are not equivalent in sound quality and the Mac-mini sounds better this would tell what kind performance gap you have to bridge via the build quality of the PC. JRiver MC19 is also available for Mac computers. Scotty
thinking about getting this for my play back as well. wondering if I can install it on multiple computers that i will use?Does anyone know?
Ted,You are using JRiver on one system and JPlay on another for your dual pc setup? Can you use JRiver on both pc? If yes, any pointers/links on how to set it up?
No, not exactly. JRIver is the client and runs on the controlpc. It talks to the Jplay ASIO driver (bitstreamiong set to "DSD"). Jplay then passes the music across the ethernet link to the audiopc where it hands off the music to the kernel streaming dac driver. So..you use JRiver for everything and in the back end Jplay is simply the engine. So...Jremote is used on the ipad for browsing, playing, etc. Jplay settings show the KS driver for the DAC (in my case Chord or now Meitner). A nice benefit is that when you change DACs the JRiver settings don't change. It's still the JPlay ASIO driver as far as JRiver is concerned. Then Jplay, on the audiopc, sees the new KS driver.
No, not exactly. JRIver is the client and runs on the controlpc. It talks to the Jplay ASIO driver (bitstreamiong set to "DSD"). Jplay then passes the music across the ethernet link to the audiopc where it hands off the music to the kernel streaming dac driver.