Apr 19, 2012 at 6:00 PM Post #586 of 680
 
Quote:
 
 
Thanks for the correction. Tried it through the D7 line out, no squeal. So that means it is not the DAC?
 
On a related note, how good is the amp section in the D7 anyway?
 

 
Yeah I would say this means the squeal comes from the amplifier itself. That's good news actually. At least the problem is not on the power rails. You can still use the D7 as a DAC without issues.
 
Apr 22, 2012 at 1:26 PM Post #587 of 680
I've got another newbie question, as it's my first time getting an external DAC..
After connecting the iem to the dac, is it normal to hear a 'pop' sound when switching on/off the DAC? Would it damage the iem?
 
If no, what is the correct procedure?
 
 
Apr 22, 2012 at 6:41 PM Post #588 of 680
I've got another newbie question, as it's my first time getting an external DAC..
After connecting the iem to the dac, is it normal to hear a 'pop' sound when switching on/off the DAC? Would it damage the iem?

If no, what is the correct procedure?


That is normal. It happens with many amps to a greater or lesser degree. It will not damage your IEM's, but if it is uncomfortable, you can just plug them in after turning on your D7.
 
Apr 22, 2012 at 8:56 PM Post #589 of 680
 
Quote:
That is normal. It happens with many amps to a greater or lesser degree. It will not damage your IEM's, but if it is uncomfortable, you can just plug them in after turning on your D7.

 
Or just not put them in until after you turn it on.
 
Apr 23, 2012 at 12:15 PM Post #590 of 680
Apr 27, 2012 at 11:07 AM Post #591 of 680
I just got my D7 yesterday and had the same driver issues a lot of people experienced (Code 10 error..hardware not installed properly).  I'm running XP Pro (SP3) on my work laptop and I couldn't get the iBasso driver to load.  There is an updated driver on iBasso's website dated 4/25/12, but it's a .raf file and I couldn't get it to run either.  Based on a couple suggestions in this thread, I downloaded CEntrance's driver and got my D7 to work this morning.  Their driver is a self-executing file and it loaded itself without issues. 
 
I only listened to the D7 for about a minute but it seemed to drive my HD600s pretty well on the low gain setting.  I only had the volume at 1 o'clock and was getting good spl with full, controlled bass. 
 
Looking forward to more listening...
 
Thanks to everyone for their help with the driver issues.  All seems to be working well with CEntrance's universal driver.
 
May 4, 2012 at 9:05 PM Post #592 of 680
I've just discovered a strange issue with my D7. Tried to search if anyone experienced something similar, but couldn't find anything...
 
The thing is that I've been using it for 2 months with my Senn 650, and its background noise is completely inaudible.
However, when I attach the line-out to my newly built Bottlehead Crack, the noise (most probably gathered from the PC through USB power) is quite noticable (even moving a mouse on a PC results in quiet but still audible "beeep"). I've tried with a self-powered USB hub, but the situation remained the same. And the problem is not on the Crack's side - when I short both channels with the ground on Crack - I can't hear a thing.
 
Now I assume I should build a USB isolator to fix this, but I'm really puzzled - how come that I don't hear such noise when using it as a DAC+AMP, but I can hear it very well when using it as a DAC only?
 
Any help is more than welcome!
 
May 5, 2012 at 11:53 AM Post #594 of 680
I'm using the D7 connected directly to my laptop and the line out is feeding a LD MKIII with the HD-650 plugged in and no hiss for me. Very quiet.
 
The background noise can come from lots of different source that is not easy to find. Tries to place the DAC differently, as far from the Crack, the PC. You should also use good audio cables (it does not mean very expensive). I think that tubes are also sensitive or they emit more electromagnetic field. I'm not sure in what sense.
 
May 5, 2012 at 3:26 PM Post #595 of 680
Yes, I can hear the same noise by plugging-in my earbuds into the line-out.
And if I connect D7 to a laptop, there is no line-out noise, probably since the laptop's USB port is battery powered.
D7 on a self-powered USB hub, without my HTPC connected as a host - no noise. As soon as I connect the host to the USB hub, the noise is back.
 
All this regardless if Crack is connected or not, if RCA cables are connected or not, etc.
 
So it's probably due to poor power supply unit of my HTPC, or interference  :(
 
Anyway, I'll order the USB isolator kit and try to fix the problem that way.
 
May 30, 2012 at 12:27 PM Post #597 of 680
Quote:
With the new driver I can now use the D7 with Windows 8!  Glad I didn't sell it (although I tried)!

biggrin.gif

 
Jun 11, 2012 at 11:52 PM Post #598 of 680
Quote:
Interesting--I just updated to OSX 10.7.3, and the problem seems to be fixed, for the most part:
  1. If I turn it off-and-on relatively close together (like 10 seconds or so) it occurs every other time, rather than every time.
  2. If I wait a minute or so before turning it on again, then it doesn't seem to happen at all.
 
OSX likely reserves and tallies the amount of required current on the bus, and it takes a minute or so to expire something disconnected.  This must have been broken before.  I only tested waiting over a minute--it could be less, but of course we aren't turning things off-and-on like that under normal use anyway, so I'd consider it fixed...
 

 
Hi All, Just got the D7, first time I plugged into my MacBook Pro, got "the" error message.  Is the only fix to upgrade to 10.7?  
Thanks !
 
Jun 14, 2012 at 5:13 PM Post #599 of 680
Just want to bump this thread to say I just ordered one and am very excited.  I've been loving my new Ultimate Ears Custom Reference Monitors, but the NuForce iDac2 I used them with feels like it's lacking.  Too much sibilance, which it sounds like the D7 will improve upon.  Can't wait!
 
Jun 17, 2012 at 12:53 AM Post #600 of 680
Quote:
 
Hi All, Just got the D7, first time I plugged into my MacBook Pro, got "the" error message.  Is the only fix to upgrade to 10.7?  
Thanks !

 
The update I did was only from 10.7.2 to 10.7.3, so it had nothing to do with upgrading to 10.7 in general.  In any case, the issue came-back just a couple days later, so the update didn't really do anything in the end, and it was apparently just a coincidence that it didn't occur for a day or so.
 

Users who are viewing this thread

Back
Top