The objectively expensive cable is any cable that cost the most. That would be the 5 meter cable William had his friend Gordon (really nice guy BTW) make. But it only spec’d to CAT5.
The objectively best performing cable is the BJC cable since they come with validation of their adherence to the standards body that writes the spec.
I’m keeping in mind this is a singular session but it was using their equipment. When I had my two machines setup for client server and running JRiver I was randomly swapping while playing back and showing William that. This moved the conversation forward because we were able to talk about 1. Are we actually listening to the cable 2. Or are we listening to cached data?
The conversation went something along the lines that, from Williams POV, that you’ve transferred data with a good or bad cable then the stored data is only that good or bad. I posited then what happens if I setup two folders and transfer a 24/192 file over using one cable and then another cable. Would the files sound different or the same. I think he opened up to the reality, and yes it IS reality, that if they hash out to the same MD5 then they are indeed the same.
I discussed with him how CRC32 works and even on his own laptop, even though we’ve been swapping out cables while playing, that with the NETSTAT -e his laptop had received well over 4GB of data, 0 receive errors and 13 send errors, and 0 discards.
The objectively best performing cable is the BJC cable since they come with validation of their adherence to the standards body that writes the spec.
I’m keeping in mind this is a singular session but it was using their equipment. When I had my two machines setup for client server and running JRiver I was randomly swapping while playing back and showing William that. This moved the conversation forward because we were able to talk about 1. Are we actually listening to the cable 2. Or are we listening to cached data?
The conversation went something along the lines that, from Williams POV, that you’ve transferred data with a good or bad cable then the stored data is only that good or bad. I posited then what happens if I setup two folders and transfer a 24/192 file over using one cable and then another cable. Would the files sound different or the same. I think he opened up to the reality, and yes it IS reality, that if they hash out to the same MD5 then they are indeed the same.
I discussed with him how CRC32 works and even on his own laptop, even though we’ve been swapping out cables while playing, that with the NETSTAT -e his laptop had received well over 4GB of data, 0 receive errors and 13 send errors, and 0 discards.