|
|
Post by The History Kid on Aug 22, 2016 16:42:32 GMT -5
Wanted to bump with this question, since I never did get a definite yes or no. One question based off of what another member said, are there any cons to using Tosslink? I use up to 192 kHz outputs with the DAC now, does Tosslink support that rate, and would I notice any shortcomings? The PC does have a standard Optic out, and I still have one free on the DAC. |
|
|
|
Post by gzubeck on Sept 4, 2016 14:21:52 GMT -5
Wanted to bump with this question, since I never did get a definite yes or no. One question based off of what another member said, are there any cons to using Tosslink? I use up to 192 kHz outputs with the DAC now, does Tosslink support that rate, and would I notice any shortcomings? The PC does have a standard Optic out, and I still have one free on the DAC. No. Toslink and coaxial do the same. There should be no difference. Also, you need to understand that after any updates there are chances that drivers can be corrupted. Ive had multiple instances where graphics drivers and basic audio drivers get corrupted after changes or updates. The quickest way to find out problems is to uninstall a driver and then reinstall it. This will remove doubt that it's a driver problem and not a malfunctioning unit. When things go south you have to troubleshoot a bit. It's always fun when a motherboard or some part on a computer goes bad because it can take a whole day to find the problem on a PC. |
|
|
|
Post by The History Kid on Sept 4, 2016 14:45:39 GMT -5
I get that, what others aren't getting is there was no rhyme or reason to the DAC working again. Nothing fixed the problem.
As for Toslink, most of what I've seen so far states that it is limited to 48 kHz, 24 bits...
|
|
|
|
Post by gzubeck on Sept 4, 2016 15:44:01 GMT -5
I get that, what others aren't getting is there was no rhyme or reason to the DAC working again. Nothing fixed the problem. As for Toslink, most of what I've seen so far states that it is limited to 48 kHz, 24 bits... No. If there's a limitation it's based on your output device. Toslink and coaxial are usually identical. If your output device is limited then your dac can only receive what it receives. The intermittency with your dac can mean that sometimes your driver loads and sometimes it doesn't. Also there could be conflicts in your computer's registry files. That why you have to clean out as much as you can and reinstall drivers. |
|
|
|
Post by The History Kid on Sept 4, 2016 21:09:46 GMT -5
On the Toslink note: got it. I will give it a go then. Windows should be able to support at least 96/24.
As for the random working/not working issue - I had checked all of that too, made sure drivers were running, etc. I don't discount it may have been a computer issue, it is an Asus...but it was still odd.
Also...sorry if my replies seem short or snarky. They're not meant to be...it's a disadvantage of phone posting. Haha.
|
|
|
|
Post by Percussionista on Sept 8, 2016 14:28:15 GMT -5
The short answer is that I have no idea...... The ONLY references I have been able to find to that command involve disabling DSE. (However, trying to figure out Windows security is a moving target at best.... ) Thanks for this info! A lot easier than the first method, requiring several arcane reboots and boot-level menus. I have one question though - does this affect any other features other than driver signing? The flag "nointegritychecks" is kind of all-inclusive sounding. UPDATE... I've now also refurbed my "old" computer with some new hardware for better gaming, and have Windows anniversary edition installed and was not able to use this method to disable DSE. Tried over and over, rebooted, etc. I went back to the original method involving several reboots with the reboot menu options and this worked first time. Go figure. ;-) |
|
KeithL
Administrator 
Posts: 10,271
|
Post by KeithL on Sept 8, 2016 14:54:26 GMT -5
In theory Coax and Toslink should be the same. I have heard of instances where the Toslink outputs on some older devices were limited to 24/96k (and the Coax went up to 24/192k)... but only a few. Toslink is electrically isolated, so it is immune to ground hum and stuff like that (Coax may or may not be isolated). Some people claim that Toslink has higher jitter, or doesn't sound as good (I've never noticed any difference). If you're having driver problems there is one very important difference between Toslink and Coax - and USB. Windows loads the driver for a USB device when it detects that you've connected the device. This means that you won't see the driver when the device isn't connected; it also means that the load and negotiation process occurs when you plug in or turn on the DAC. Note there that Windows can in fact tell when something is plugged in, even if it isn't turned on... so unplugging and reconnecting something can make a difference EVEN IF IT'S TURNED OFF. This also means tat turning the DAC off and on again is NOT exactly the same as unplugging the wire...... In contrast to USB, both Toslink and Coax are "dumb" interfaces..... with either, the computer doesn't "know or care" whether the DAC is connected, or whether it's working. Therefore, if Toslink or Coax drivers fail to load, it has nothing at all to do with the DAC... it's strictly a Windows issue. You can even disconnect and reconnect either while music is playing and you shouldn't get an error on the computer......... I get that, what others aren't getting is there was no rhyme or reason to the DAC working again. Nothing fixed the problem. As for Toslink, most of what I've seen so far states that it is limited to 48 kHz, 24 bits... |
|
KeithL
Administrator
Posts: 10,271
|
Post by KeithL on Sept 8, 2016 15:02:09 GMT -5
A few other notes about Toslink..... 1) Toslink is an OPTICAL signal... the red light you see in the window is the signal.... If the little window in the end of the wire gets dirty it can interfere with the signal..... (so try wiping it). 2) It's also not uncommon for a piece of dust or lint to find its way into the connector and block the light. Try pushing the door open and blowing into the connector to clean it. 3) Toslink cables can be BROKEN The fiber is either glass or plastic, and both are sort of brittle. The fiber is thin and somewhat flexible, but, if you bend a Toslink cable too sharply, you can break the fiber.... and then it won't work any more. 4) Most Toslink connectors seem to be a bit loose, and fall out quite easily.... 5) There's also a sort of length limit with Toslink.... I've never heard a number, and it seems to vary, but some outputs will only work with relatively short cables. (Others work over relatively long cables.... you won't find out until you try.) Note that there are fancy glass cables that are supposed to work over slightly longer distances with a given output. On the Toslink note: got it. I will give it a go then. Windows should be able to support at least 96/24. As for the random working/not working issue - I had checked all of that too, made sure drivers were running, etc. I don't discount it may have been a computer issue, it is an Asus...but it was still odd. Also...sorry if my replies seem short or snarky. They're not meant to be...it's a disadvantage of phone posting. Haha. |
|
|
|
Post by The History Kid on Sept 8, 2016 16:09:52 GMT -5
Thanks for the info Keith.
Funnily enough, I have to reboot my DAC every time I want to use it after my computer has been asleep, because windows won't find it otherwise. Even then it may not work and I have to unplug and reconnect the cable.
Think I really need to consider the optic, if only for testing reasons. The computer treats optic as a totally separate device, so that may so be helpful.
|
|
|
|
Post by Percussionista on Sept 8, 2016 17:07:45 GMT -5
So wouldn't Windows notice the USB device when it's booting up (especially if it's turned on)? I shouldn't have to unplug and replug in the USB cable! When I tried to disable DSE via the admin command line prompt, the system had previously told me before that it saw the DC-1 device, but it didn't have a driver for it. I just couldn't get passed the DSE check via this command line bcdedit method to install the driver. The old reboot with startup options method worked like a charm. If you're having driver problems there is one very important difference between Toslink and Coax - and USB. Windows loads the driver for a USB device when it detects that you've connected the device. This means that you won't see the driver when the device isn't connected; it also means that the load and negotiation process occurs when you plug in or turn on the DAC.... |
|
One question based off of what another member said, are there any cons to using Tosslink? I use up to 192 kHz outputs with the DAC now, does Tosslink support that rate, and would I notice any shortcomings? The PC does have a standard Optic out, and I still have one free on the DAC.
