Dan -
I've had consistantly good electrical results from the fairly cheap Amazon 'Basics' USB cables, available in various combinations of mini, micro, 'A' connectors:
https://www.amazon.com/gp/aw/d/B00NH13LSM/ref=mp_s_a_1_6?ie=UTF8&qid=1470059860&sr=8-
6&pi=AC_SX236_SY340_QL65&keywords=amazon+basics+usb+cable&dpPl=1&dpID=4155w1oQZDL&ref=plSrch
This URL from Heck gets you a 3' micro - mini cable for a little under four prunes delivered to your door, which even has a useful bump to indicate the wide side of the cursed micro USB connector.
Recently, I dissected and re-purposed one of these cables as a low-noise (or more correctly, a noise-rejecting) input cable for the home-brew amps driving my Martian-Logan electrostats.
The problem was that the amp's 6" of UTP input lead was picking up both internal AC hum from the amps PSU and an irritating amount of noise from the M-L's 4800VDC panel charge circuit. - the last time I've heard this much 'frying bacon,' I was at a Baptist picnic....
The Amazon cable has a decent outer sheath that seems uniformly thick and well sized to the shield (cheap cables can pretty sloppy), it had a tighly woven braid layer with excellent coverage (cheap cables use looser weave braids with a lower percentage of coverage), the inner foil shield was reasonably thick, tighly wrapped around the wires, and had a bare 'drain' wire embedded within it - this is a nice feature, creating a solid electrical bond between the connector shells and additional mechanical support for the cable.
There were 4 internal wires arranged as red/black and white/green, the red/black pair was thicker than the white/green which I assume was for better charging efficiency. The wires were multi-stranded and felt like they were teflon insulated - and at 3' showed almost imperceptable capacitance on my Fluke meter.
I wired the cable with white & red as the L/R hot, green & black as the returns - the cable shield was wired to chassis ground at the input end, and left floating at the board connection.
Sonically, the hum + hash dropped from clearly audible at 5' to barely audible with ear-to-speaker, a worthwile improvement - and otherwise I didn't sense any other significant changes - the cable added no other warts, but neither did it rain down sonic manna and hoseannas either.
These cables seem well-made, they perform well at USB 2 AND USB 3 speeds, and I was quite pleased that I could use one as an analog input cable too.
Cheers
Jim
What, don't understand. If the wire is not part of the current loop then no electrons will drift....
Drift velocity, they just jiggle about a bit but never travel far, a lot of problems with audio (and other areas of electronics though not anywhere as near) are based on the view of electrons running round a train track like carriages, they dont they wiggle past a point due to the influence of the elctro-magnetic waves.
I am still trying to work out if it makes sense. But the loop rule can be violated, for instance when charging a battery, many/few/some/almost all?? electrons go through the battery but some are used to reduce a pole of the cell. So electrons in is not electrons out in that case.
That tells me that at least one of the connection interfaces is not operating correctly.
You would do better trying to make the interface work correctly in the presence of interference.
Or that the claim is complete nonsense. Other than data dropouts (gross errors), think of what has to happen to make the sound change. That's a remarkably sophisticated interface! 😀
The cable used is perfectly fine, the difference is that filters are fitted, or not.
Study up on 'flash memory' as used in SD cards, phone memory, thumb drives etc.
Dan.
Study up on 'flash memory' as used in SD cards, phone memory, thumb drives etc.
Dan.
Last edited:
Yes, that must be it, I need to "study up on 'flash memory' as used in SD cards, phone memory, thumb drives etc" so I can reach your level of understanding. This will help prevent the problems I've seen with copies of photographs sent over USB making me look older and fatter.
Sadly, that appears to be the case.vladimirb0b said:
I'm not sure what you are saying - a battery maintains a fairly stable potential difference? True, but unremarkable.
No. Connect just one side of a battery and all you have is a piece of conductor, shaped like a battery but no longer doing any useful work as a battery.
Thank you for confirming that you don't understand how electricity works.
Sorry, which electron are we talking about? Unless it is being charged, current generally flow into the negative terminal of a battery i.e. electrons come out (if there is a circuit loop). In the case of BGT there is no loop so the battery has no function apart from being a lump of conductor. Similarly, the capacitor across the battery has no function apart from being a lump of conductor. Like a potato, or some damp earth in a very expensive box.
When you charge a battery the number of electrons entering the negative terminal are exactly balanced by the number leaving the positive terminal. This must be true, as otherwise the circuit charging the battery would violate physics: charge conservation to be precise. It may be that you are confusing two different meanings of 'charge':vladimirb0b said:
1. move some ions etc. around in a battery - electrochemistry
2. move some electrons around in a conductor - electrostatics
Been playing with flash memory for years and years now, whats the problem.... Oh they are also used in SSD's and anything with a processor, FPGA etc. is likely to have a flash memory device on the board.....
Puzzled further about this because if all you are doing is reading the data from the flash (which is exactly what you are doing during music replay) then non of the elevated erase and programming voltages are active....
Please enlighten.....
Please enlighten.....
From what I read, the memory cells are 3 bit (8 voltage level states) and as the geometry is reducing, the number of electrons required to charge each cell to the designated state is reducing also.
This makes this storage system prone to system noise during the 'write' cycle.
Data (voltage level) errors during read and write operations are expected, and 'repaired' by error detection and correction strategies.
Data correction is handled internally, and it may be that data readout timing variation caused by extra (or less) processing is behind the changes that I and others readily hear.
Dan.
Nah, chasing Bybees again, all this is sorted before the data is spat out of the memory device into the next buffer on its way to the DAC, all these operations work at different rates and burst of data are to be expected as FIFO and other types of data buffers are used to package the data ready for transmission.
All this stuff regarding digital data transfer is getting a bit strange, its like we are forgetting the rise of digital signal transfer and how far it has developed and how much of it happens without anybody noticing and without any problems for 100 - 0.0000000000000000000000000001% of the time.
And jitter only really concerns us at the point of conversion.....
All this stuff regarding digital data transfer is getting a bit strange, its like we are forgetting the rise of digital signal transfer and how far it has developed and how much of it happens without anybody noticing and without any problems for 100 - 0.0000000000000000000000000001% of the time.
And jitter only really concerns us at the point of conversion.....
We are getting into the SankyK area of discussion here, where claims were made of bit perfect files sounding different due to PSU used at the time of writing the data to disk and HDD sounding different to SSD playback, isolated for noise purposes, this did lead to the discovery of "Dark Bits", these are random non-bits that reside in the intercises between the normal bits, that under certain circumstances can change state to normal bits causing bit perfect transmission of data to in certain circumstances to sound or look different. The timing of these dark bits is also problematic as they like to tootle along at the same frequency as the universal cosmos clock so also play havoc with time based interfaces.
- Status
- Not open for further replies.