• Welcome to ASR. There are many reviews of audio hardware and expert members to help answer your questions. Click here to have your audio equipment measured for free!

TOPPING HS02 coming

Looks like the above statement is device/driver/software dependent. Under linux+rew loopback measurement is fine, no bouncing at all. (souncard was EMU0404 USB)
How does this path compare to the loopback without the HS02?

- Rich
 
:cool:
 

Attachments

  • 335033100_250412660650566_5702173670467629445_n.jpg
    335033100_250412660650566_5702173670467629445_n.jpg
    202.1 KB · Views: 892
  • 336012549_604689421674864_6568120670384945030_n.jpg
    336012549_604689421674864_6568120670384945030_n.jpg
    425.7 KB · Views: 1,295
  • 336158600_777102480220969_5083138137622537082_n.jpg
    336158600_777102480220969_5083138137622537082_n.jpg
    312.2 KB · Views: 974
Looks like the above statement is device/driver/software dependent. Under linux+rew loopback measurement is fine, no bouncing at all. (souncard was EMU0404 USB)
Can you share the measurement on Linux with loopback ?
 

Nice, thanks for the photos. They have removed the markings on the isolator chip. But the pinout looks like its an analog device usb isolator. ITs also a newer model that allows a crystal clock input. Cool
 
Last edited:
You have to trust me, I know what I'm doing. I have enough experience with measuring. :cool:
The pictures show my equipment.

So the exact same physical layout and connections perform differently on Windows vs Linux?
 
Yes.
PC_WIN10<->HS02<->XFi_HD(with loopback)
PC_LINUX<->HS02<->EMU0404(with loopback)

One problem is that EMU does not have WIN10 driver and XFi_HD works under linux in usb1.1 mode only. So I can't test the same sound card under linux and windows.
 
so it is not the exact same layout and connections then.

2 different interfaces

So 2 different variables (OS and interface)

But I understand your point that you can't use one on both Win10 and Linux
 
This fact is important to me :

PC_WIN10<->XFi_HD_LOOPBACK_MODE ======== OK
PC_WIN10<->HS02<->XFi_HD_LOOPBACK_MODE == NOT_OK

PC_WIN10<--XFi_HD<--VIKTOR1K ======== OK
PC_WIN10<--HS02<--XFi_HD<--VIKTOR1K == NOT_OK

(most time I use win10 and xfi, xfi is modded for better thd)
 
Last edited:
I guess it is his own modification - changing Rubycon YXJ capacitors with hybrid poymer Nichicon FPcap with additional film caps. There shouldn't be any difference as Rubycons are already high quality Japanese capacitors and using even lower ESR caps with film bypass can cause some ringing/instability in power supply.
 
I guess it is his own modification - changing Rubycon YXJ capacitors with hybrid poymer Nichicon FPcap with additional film caps. There shouldn't be any difference as Rubycons are already high quality Japanese capacitors and using even lower ESR caps with film bypass can cause some ringing/instability in power supply.

That‘s what I thought, too, although the silk screen on the board seems to indicate 2x 2 electrolytics.

Either way, the HS20 seems like a bit of a bargain compared to this:

Which I believe is basically the same with a regulated 5V power supply added on.
 
It was already alarming using (selectable) filters that mimic tube and SS distortion in one of their devices ;)
How is that snake oil? Its called marketing. Addressing a market demand. With it you can address both markets. Those that want measurements and those that could care less.
 
How is that snake oil? Its called marketing. Addressing a market demand. With it you can address both markets. Those that want measurements and those that could care less.
Oh,I'm all in for people to make money but in our case when someone is suppose to carry the flag of objectivity choices like this spoils it a little,doesn't it?
I mean why pay 800$,you can get a nice little real tube amp or a tube buffer for a LOT less if you're into that kind of thing.

The image alone is odd,notice that the word "distortion" is strategically absent,subsituded by the word "performance"(!) to describe the ~40ish SINAD,


5918360.jpg



Nice try,but...
 
Indeed different internals.

Strange for such a new product , a change so early.
USB 2.0 specs state that the upstream Vbus capacitor must not be larger that 10uF to limit inrush current and associated voltage sag at the host which could upset already attached devices. Larger caps are only allowed when some sort of soft-start is provided.
The downstream Vbus buffer shall be at least 120uF for the exact same reason.

As far as I can see, we have 470uF (or 330uF for the second unit) here on both sides which would violate the upstream-side spec. One might get away with this most of the times but sometimes there can be issues and I have seen such in the past occasionally.
 
but sometimes there can be issues and I have seen such in the past occasionally.
How do these issues appear?

As a short temporary drop out in audio ?

Or a complete disconnection from DAC?

And is it a bigger issue the faster the transfer speed?

So not a problem for audio? Which is < 100 MBps at worst usually? (multichannel)
 
Too big voltage sag at other USB ports in hub during connection of out-of-spec device can potentially cause resetting connection of other devices.
But don't make assumptions yet - it is possible to have huge capacitance in USB device with USB power management IC. It limits current draw to USB spec and acts like soft-start.
We don't know HS02 schematic, maybe Topping solved this potential issue.
 
Too big voltage sag at other USB ports in hub during connection of out-of-spec device can potentially cause resetting connection of other devices.
But don't make assumptions yet - it is possible to have huge capacitance in USB device with USB power management IC. It limits current draw to USB spec and acts like soft-start.
We don't know HS02 schematic, maybe Topping solved this potential issue.
I noticed HS02 user manual says they recommend direct PC connection, not using with a hub.
 
There is no difference between external hub or internal "hub" on your motherboard.
 
Back
Top Bottom