valada weldon dorathy

0 views

Skip to first unread message

Latrina Mosely

unread,

Aug 2, 2024, 9:17:24 AM8/2/24

to poiriforco

I have a Panasonic Blu-ray player that has Netflix on it. I set it up a few months ago and it has worked fine for streaming movies and viewing my Netflix instant queue. But recently I've started getting error messages when trying to access Netflix. "Cannot connect to netflix, please try again."

Occasionally a Netflix client such as a Blu-ray player or TV can get "confused" about its account authorization. When this happens, you may start getting error messages when you attempt to access Netflix on a device that was previously working fine. This can happen on an LG or Sony or Panasonic or Samsung or VIZIO Blu-ray player or web-enabled TV, or on the ROKU streaming box or Apple TV (among others). The message you get can vary but may be one of these:

This procedure is also helpful if you are getting rid of a Blu-ray player or TV that you've previously set up for Netflix and you want to remove your account from the device. It used to be possible to manage devices online in your Netflix account but they've since disabled that feature. Currently if you want to remove a device from your Netflix account online, you have to disable *ALL* of the devices and add them back in one at a time.

But there is a way to break the link to your Netflix account from the actual device itself. To do so, get into the Netflix screen on that device (or the Netflix error screen, as the case may be), then using your device's remote, hit the following buttons:

Go back into Netflix on that device again and you will then need to re-authorize the device with your Netflix account. This may require an activation code and a trip to www.netflix.com/activate to enter that activation code, or it might just entail logging into Netflix from the device using your account e-mail address and password. The procedure for activating a new device for Netflix varies a bit from device to device. But once it has been re-authorized, the error messages should be gone and the device should work properly again.

6/14/13 - happening again: big surge in interest in this topic suggest a Netflix network outage. I can confirm the same problem trying to access Netflix from my phone. A Netflix network outage is likely culprit.

So I am using both the USB and i2S inputs with my May. However my i2S source is inferior to my USB source and not my critical listening path. I am basically using a inexpensive Ebay sourced USB to i2S Converter on my Nvidia Shield output so that I can have two USB output devices connected to the May.

The May has some issues locking to that i2S signal, it takes it about 15 seconds when switching to lock. The NVidia outputs everything to 192K, but sometimes the May switches to 48K when I open some apps like Netflix. My previous dacs never switched from 192K (though did take a while to connect), so I suspect its a PLL issue caused by Mays tight PLL tolerances, as stated by others in this thread. I also think this is more about the cheap i2S converter than about the May.

Tldr: may pll makes the source a bit of a non-issue. I'd say use a streamer for galvanic isolation regardless cause why not, but I just use usb because of the instant locking, and unlike on the spring 2 (where i2s vs usb is quite noticeable), the may just does brilliantly from any source you throw at it

USB doesn't need any PLL because the clocking is at DAC side. PLL is only needed when DAC needs to regenerate clocks from external source (S/PDIF, AES or optionally I2S). Which is not the case with USB where clock is solely at the DAC side...

Hi everyone - wonder if you can help? I have just received my Holo May and have got everything up and running, but with one significant omission: I can't get PCM 1.5 Mhz to work (nor can I get above DSD256, but that's not my main concern). I can get 705.6 kHz and 768 kHz running, but no higher. I have tried from a Sonictransporter via ethernet to a uRrendu (1.5, running 2.8 build); I have tried with a direct USB cable from the May to the Sonictransporter; I have tried with HQPlayer Desktop running on my laptop (Mac, running Big Sur) and a straight USB connection to the DAC, all to no avail. Music plays fine at lower rates in all cases, but not at 1.4/1.5 Mhz; nothing seems to make the source connections, however configured, to run at the highest rates. (And yes, I tested source files in differing base rates - same result). When directly connected to my Mac Pro laptop the Audi Midi panel reports the Holo May as offering all formats at 16 and 24 bits up to and including 768 kHz, but no more. Similarly, when attached to the Sonictransport and looking at what the uRendu says (it has a DAC diagnostic app) it, too, reports 768k as the maximum.

Is your playback software taking 'Exclusive Control' of your DAC's USB driver preventing Hqplayer from actually applying your 1.4112mhz or 1.536mhz setting? (If you're using HQplayer by itself and no other audio software is on then this won't be your issue.) (It may not even be a Mac audio issue, but it perplexed me when I used Roon (in ASIO EXCLUSIVE MODE) while streaming to HQPLAYER software as an ASIO endpoint which was in fact problematic.

Regarding the other scenarios you mentioned it's likely you are being capped by the limitations of that hardware/software. I can only go to 768khz via USB with Roon's internal upscaling and there's definitely limitations over a network connection with DSD using Roon I believe capped at DSD256, and definitely DSD512 via USB.

Lastly, this could possibly be a USB Port related issue. I was unable to use my JCAT Femto clock USB pcie card to achieve maximum throughput rates simply because the antiquated USB chip and driver were not able to support it whereas I had no issue using my Sigao custom media server albeit with very new Internal USB 2/3 ports on a very current motherboard.

Thanks for that - all good questions! Yes, when running directly from the laptop, HQP has full access (the whole ASIO, exclusivity thing isn't an issue on Mac OS, at least as far as I am aware). Hardware limitations might indeed be playing into the uRendu and directly from the Sonictransporter situations, which is why I tried using a laptop and removing all those constraints. I do not know if the hardware on my MacBook is an issue or not .. it could be, given its vintage (late 2013) but maybe others have some insights?

I was able to select 1.536 MHz when directly attached to the laptop, but it never played. I am also able to select 1536 as a maximum bit rate on the HQP embedded configuration page on the Sonictransporter, but it never pushes out anything except at the 705/768 rates.

Thanks - the May reports that it's running v 1.20. Any idea which version that might be? Given that none of the USB probes come back with anything above 768 kHz, you may be onto something. (As for the uRendu supporting it, I've seen a response saying "no reason not, but not tested", so ... that's a "maybe" I guess!)

Theoretically, it "should" support this rate, but we actually do not know as no one at Sonore has ever had access to a DAC which supports this rate for testing. There are very, very few DACs which support this rate. As mentioned, there are also a lot of different firmwares for the Holo Audio USB input, so that is the first thing to investigate with Tim. Note that Jussi has recommended testing first with MoBo USB outputs to confirm it works before trying other USB sources (like ultraRendu, or "high end" USB cards, etc).

SO/ROON/HQPe: DSD 512-Sonore opticalModuleDeluxe-Signature Rendu optical with Well Tempered Clock--DIY DSC-2 DAC with SC Pure Clock--DIY Purifi Amplifier-Focus Audio FS888 speakers-JL E 112 sub-Nordost Tyr USB, DIY EventHorizon AC cables, Iconoclast XLR & speaker cables, Synergistic Purple Fuses, Spacetime system clarifiers. ISOAcoustics Oreas footers.