I have some indication that Microsoft actually passes bitstreams as-is when they are not flagged properly, even if this is not documented anywhere. Second, Windows is not an option, as both Windows sound sub-system, and AMD/NVidia/Intel HDMI drivers are closed source. Then you connect that to something like Apogee's Big Ben, and laugh. Sounds familiar?Īudio professionals have a field day with this stuff, as every pro DAC ever made, has a separate clock input for this exact reason. If often helps to remember that marketing guys like solutions they can sell, and they do there best to find problems this solutions can then "solve". Perhaps they prefer to sell you extra 1000$ worth of special USB interface and cables instead - model "SuperSnakeOil 5000 Ultra XL". Certainly, there is "some" cost involved. Weather the manufacturer of the commercial DAC product chooses to use it, is another matter. Pretty much any DAC chip, with pretensions to audiophile quality, made in last 10 years or so, has an input for external clock, and FIFO buffer is a necessity of most DAC designs - DSD or PCM. This is called re-clocking, and is a very simple form of FIFO buffer - where the FO part is under control of high precision local clock source. What can be done with it, is to replace significant jitter that occurs in transmission (USB,HDMI.let's not talk about TCP/IP), with insignificant jitter that is inherent to high-precision clock source. To respond to concerns/questions (and a rant on subject of Jitter cannot be "bypassed". He hasn't done so (yet), he has only banned the account.Not exactly an overwhelming response, but better some interest then none :) to remove my account and posts or 'anonymize' my account from his forum after the first thread was removed. Remember JRiver sponsors his new CAPS 4 project in full and is also an advertiser on CA. to be nothing else than pure censorship to protect his friend Jim, his own financial interests, or both. Personally I consider the removal of both threads by Chris C. We did learn in this second thread (JRiver's Jim replied again here) that Chris C. That thread has been deleted later as well, again without any statement or notice. I opened a second one with the same first post. There hasn't been any statement or notice of the removal. Like Marcin says, the thread I started has indeed been deleted by Chris C. There was an interesting thread about this at Computer Audiophile in the Software forum but it now appears to be gone. It does indeed restore JPlay functionality in 20.0.44. (personal opinion: not very likely, it's most likely a childish revenge thingy) PS: For those that still want to use both JRiver and JPlay let's hope it's just another bug that crept into their software, ready to be fixed in their next release. JPlay driver not showing in JRiver 20.0.44 | JPLAY | Forum | JPLAY - hi-end audio player for Windows And if you're not a customer yet of JRiver but want to use JPlay don't buy JRiver but use something like Foobar or any of the other players that support ASIO out, listed here: The Well-Tempered Computer You could also write a Facebook review on JRiver or respond to them on their forum (although they're known to censor all references to JPlay from their forum to "protect their customers"). He has already refunded me, so if he denies a refund refer to that. Last version that works in conjunction with JPlay is 20.0.41.Īlso don't forget to send an email to jimh at to tell him what you think about this and/or request a refund. So a warning to all JPlay/Jriver MC users don't upgrade to 20.0.44. See Poll: should JRiver remove the JPlay is a hoax warnings from their JRMC product? for some background information. Jim Hillegras already threatened to remove the JPlay support completely from JRMC if we took the 'remove the JPlay hoax warning' discussion much further and while Chris Connaker closed the topic it nonetheless seems he has decided to sabotage JPlay fully starting from version 20.0.44. I found out about this while visiting the JPlay forum. Since JPlay is nothing but a virtual ASIO output device to JRiver this most likely means they have chosen to deliberately sabotage JPlay. 44 the JPlay ASIO driver is now no longer available for selection. Well it looks like the devil has taken a full hold over the boys at JRiver.Īfter the installation of. Just saw your post and I tested it as well and indeed it no longer works.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |