bpa wrote:
> I'm not backing the cable - I'm curious about possible Pi4 h/w issues.
> I have aPi4 where the Wifi will drop after a few hours if screen
> resolution is set too high - a bug which apparently has been fixed yet
> still happens on my Pi4.
We know you are not bacxking the cable
d6jg wrote:
> That is true but us Earthlings would just pull another £5 cable from our
> box of cables and move on. Spending $350+ on a cable is IMO obscene.
> Send it back, buy one for $5 and give the money saved to the local food
> bank.
I'm not backing the cable - I'm curious about possible
bpa wrote:
> The "Maybe the cable is bad" seems to have appeared for other Pi4 users
> with ordinary cables - so it might be an ordinary issue as well as a
> Audiophile one.
That is true but us Earthlings would just pull another £5 cable from our
box of cables and move on. Spending $350+ on a
jeroen2 wrote:
> I love the fact that you guys are even discussing this. :cool: But I
> would think it's up to the person selling $500 USB cables to explain why
> sometimes it works and sometimes it doesn't Surely they must have a
> much deeper understanding of the inner workings of USB
chill wrote:
> But it works on the Macbook. I wonder if different chipsets handle the
> link negotiation differently. Maybe the Pi uses only a fixed data rate,
> whereas the Macbook might do some sort of adaptive rate? Is that
> possible?
I love the fact that you guys are even discussing
There are a number of "Maybe the USB cable is bad?" posts on various Pi
forums.
A few of them seem to be fixed by either upgrading s/w (especially
firmware) or downgrading from Buster.
bpa's Profile:
chill wrote:
> But it works on the Macbook. I wonder if different chipsets handle the
> link negotiation differently. Maybe the Pi uses only a fixed data rate,
> whereas the Macbook might do some sort of adaptive rate? Is that
> possible?
Yes - the loose +5v wired seemed to be the obvious
bpa wrote:
> They route the +5v on the outside the signal cable - perhaps it is
> broken ?
But it works on the Macbook. I wonder if different chipsets handle the
link negotiation differently. Maybe the Pi uses only a fixed data rate,
whereas the Macbook might do some sort of adaptive rate?
Greg Erskine wrote:
> How can a couple of connectors with a few wires between them not work?
They route the +5v on the outside the signal cable - perhaps it is
broken ?
bpa's Profile:
Greg Erskine wrote:
> How can a couple of connectors with a few wires between them not work?Maybe
> the cable deemed the Raspberry Pi not worthy. [emoji3]
Sent from my Pixel 3a using Tapatalk
slartibartfast's
Greg Erskine wrote:
> How can a couple of connectors with a few wires between them not work?
Maybe the ultra-clean, perfectly-timed data bits are just too much for
the Raspberry pi to cope with :)
chill's Profile:
How can a couple of connectors with a few wires between them not work?
Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403
View this thread: http://forums.slimdevices.com/showthread.php?t=113997
scslite wrote:
> ... Curious got back to me and their assessment is that their cable is
> just incompatible with the RPi platform.
Out of curiousity (no pun intended) I had a look at their website. These
guys are, like lots of boutique audiophile companies, a bunch of
charlatans.
If Curious
I just wanted to update this post and put a closure to it. Not the
outcome that I was hoping for but alas Curious got back to me and their
assessment is that their cable is just incompatible with the RPi
platform. I would hope that they will investigate this and add as a
disclosure on their
Good luck with the Return/Exchange. I think Curious has a 30-day full
satisfaction period so should be straightforward to send back...
This is not the proper place to discuss, but since a window of
opportunity opened for a full refund...
If you are determined to utilise RPi/PcP, there are
and I think it could be one of the first things Curious suggests is done
before agreeing to replace since it is in their FAQ and they might not
have experience of pCP/TinyCore.
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france (fip etc), kcrw,
slartibartfast wrote:
> If other cables work with your Pi then changing the OS isn't going to
> help.
I agree it doesn't seem logical but trying an different OS at least
eliminates the possibility of some sort of weird chip initialisation or
timing issue which is only apparent with the problem
scslite wrote:
> Yes squeezlite works with the generic cable and another USB cable I have
> which is a BBQ Full Rack similar design to the Curious with an isolated
> power line.
>
> The logs do show something with the Curious is bad but what? I have not
> tried another OS on the RPi but may
scslite wrote:
> "enable monitor udev actions/triggers with udevadm"
command at shell prompt
UDEVADM MONITOR
Do a test by plugging and unplugging a "good" device to see messages
appear, then try the problem device. If no messages then problem is at
a lower level of USB interfacing which
chill wrote:
> I don't think this has anything to do with Squeezelite. The Pi isn't
> enabling the Qutest with this cable. Did Squeezelite work with the
> generic cable? I would send Curious the two log file snippets that I
> posted above. I would hope that they'll stand by their product
scslite wrote:
> I'll try to test as suggested by LifePO4 and report back later. The
> fact that the cable works perfectly when plugged into my MBA means
> there's some signal that's not on the RPi USB that Squeezlite is not
> recognizing the Qutest..
It is is not squeezelite but from log at
scslite wrote:
> I'll try to test as suggested by LifePO4 and report back later. The
> fact that the cable works perfectly when plugged into my MBA means
> there's some signal that's not on the RPi USB that Squeezlite is not
> recognizing the Qutest.
>
> Another thought is does the Qobuz
I'll try to test as suggested by LifePO4 and report back later. The
fact that the cable works perfectly when plugged into my MBA means
there's some signal that's not on the RPi USB that Squeezlite is not
recognizing the Qutest.
Another thought is does the Qobuz plugin require Squeezlite or is
Man in a van wrote:
> I know hot plugging can sometimes stir things up but at the OP's own
> risk
I wouldn't go as far as messing with hot pluggin but OP could try enable
monitor udev actions/triggers with udevadm and see if anything show up.
However from the log I think the issue is before
LiFePO4 wrote:
> I have zero experience with pcp on the USB side. I only use optical
> solutions, so just making a suggestion. I wasn't even aware there is a
> Qutest USB setting. I thought USB Audio is the only option on the
> dropdown box for USB DACs, so total noob here.
>
> My
scslite wrote:
> Logs attached. Also tried to make sure pins have good contact.
>From the generic cable:
Code:
[1.131641] usb 1-1: new high-speed USB device number 2 using xhci_hcd\
[1.314285] usb 1-1: New USB device found, idVendor=2109, idProduct=3431,
I have zero experience with pcp on the USB side. I only use optical
solutions, so just making a suggestion. I wasn't even aware there is a
Qutest USB setting. I thought USB Audio is the only option on the
dropdown box for USB DACs, so total noob here.
My suggestion is try powering on the
Logs attached. Also tried to make sure pins have good contact.
+---+
|Filename: CuriusUSBCableLogs.zip |
|Download: http://forums.slimdevices.com/attachment.php?attachmentid=33506|
I have a USB type A socket on a PC where some cables work and some don't
- I think it is just a mechanical issue where tolerance are just out or
have become worn or perhaps the "springiness" of the contacts has gone.
I see those cables are a mere $350 for 0.8m. I guess if you can afford
to pay that much for a bit of wire then you can afford to pay that much
for one that doesnt work!
VB2.4[/B] STORAGE *QNAP TS419P (NFS)
[B]Living Room* Joggler & Pi4/Khadas -> Onkyo TXNR686 -> Celestion F20s
*Office*
scslite wrote:
> Will see if I can figure out to log as well as suggested in my rather
> rudimentary expertise on this at the moment.
>
>
pCP Main Page > Diagnostics > Logs
Man in a van's Profile:
Paul Webster wrote:
> Also - other content of their FAQ makes me think that this should be in
> the Audiophiles area.
>
Yes, looks like it. Maybe the Curious cable became conditioned to your
Macbook already.
jeroen2's
I'm using the USB 2.0 on the Pi and tried both of them but no dice. Ok
i read the Curious site FAQ closely this time and will try to go over
some of the tips there tomorrow even though some are rather vague in
what to do. Will see if I can figure out to log as well as suggested in
my rather
In my opinion all usb cables are the same, if they are complient with
the respective standard
Are you using the usb2 or usb 3 sockets on the pi
I would suggest a couple of logs to start with, boot and dmesg
One set with a certified usb cable (and hopefully working dac)
One set with the
I see their FAQ has something in it that suggests this is a known
issue.
Also - other content of their FAQ makes me think that this should be in
the Audiophiles area.
https://curiouscables.com/faq
Paul Webster
http://dabdig.blogspot.com
author of \"now playing\" plugins covering radio france
Hi all,
New to the forum and wanted to see if anyone here has by chance
encountered the same issue I'm having with a Curious USB cable.
Set up is an RPi4B with latest Picoreplayer via the onboard USB output
hooked up to a Chord Qutest DAC.
I'm having problems when I plug in a Curious USB
36 matches
Mail list logo
