I recently bought a GMKtec G5 N97. The ROCK installation went smoothly. Because I have a bunch of Internet “appliances” upstairs and down, my network setup is as follows: Cable modem in bridge mode Ethernet-cabled to an upstairs Apple Time Capsule router that acts as the DHCP server - the Time Capsule is Ethernet-cabled to a downstairs AirPort Extreme router in bridge mode (its DHCP serving is off) - the AirPort Extreme is Ethernet-cabled to the N97 ROCK/MOCK.
I can access the N97 ROCK server, using its IP address (which I told the Airport router to never change) from a browser on a Win 11 PC, on an iMac, and from my iPhone. The Roon library was successfully populated from a few “trial” music files on an external drive connected to the N97 via USB. The Roon app on all of the above can see the library on the N97 and play songs to the devices the Roon app sees (so I can listen on the PC, Mac, or iPhone). I’ve checked, and the N97 and all devices running the Roon app, are on the same network subnet.
The problem is that the Roon app (whether run on the PC, Mac or iPhone) does not see (i.e., does not list under Audio devices) the SMSL D300 DAC that I’ve plugged into the the N97’s USB port (I’ve tried all 3 N97 USB-A ports; the DAC itself has a USB-B port, so I’ve used a USB 2.0 USB-A to USB-B cable).
The SMSL DAC does seem like its communicating with the N97 ROCK because the DAC’s front LCD panel shows DSD512 (whereas when I connect it to my iPhone and other things it shows PCM). I also tried plugging the N97 into the Unison USB port on my Schiit Bifrost DAC but the Roon app doesn’t see that, either (although I understand that Schiit DACs want PCM).
I’ve tried a few of the troubleshooting steps I’ve seen: restarting ROCK, rebooting the N97 then restarting ROCK, uninstalling and reinstalling the Roon app on the computers/iPhone, deleting the RAAT folder and having it re-created (only did this on the PC, which was Ethernet-cabled to the AirPort Extreme). Still no joy.
Hi @Kevin_Hogg
I have done a fast test with my spare GMKTek G5 N97 MOCK. I cannot connect my S.M.S.L. Sanskrit via the USB-ports of the N97 MOCK. The DAC is not recognized.
I assume the USB-drivers of the ROCK-installation are not correct for the GMKTek G5 N97.
I have two remarks: it is a MOCK, so that means that the hardware is not officially supported. So one have to live with the restrictions of such a MOCK.
Second remark: it is never a good idea to connect a DAC directly to the ROCK Core. It is always better practice to connect it via a network Roon Bridge. That does not have to be expansive: a Raspberry Pi on which you install RoPieee is always a good start and is working perfectly. RoPieee is a free software, but is always appreciated if you give a donation to @spockfish when you are pleased with his hard work.
I hope I was able to help you with this answer.
Kind regards, Frank.
Thanks, Frank. Very helpful. I suppose the following is somewhat irrelevant since it’s advisable to get a Bridge, but I noticed (after stopping Rock, deleting the RoonServer folder in its Data directory, restarting Rock, and running the Roon app on my Mac) that the SMSL DAC is detected - as shown in the screen capture below. But, when I try to enable it, the SMSL DAC entry disappears (as do the other entries that follow that entry). [hmm, not sure whether I’m adding the screenshot correctly]
Hi Kevin,
That is exactly the same comportment I had. The Roon Core tries to connect, but is not able to, so it removes the DAC from the list.
Kind regards, Frank.
I have a GMKtec G2 Plus and G3 Nucbox, both set up as Roon cores via MOCK (ROCK) and running in relatives homes very successfully with reasonable size libraries. I never tried to direct connect a DAC, since I run everything via Raspberry Pi’s (mix of pi zero w 2’s, pi4’s, and pi3b’s) mostly on RooExtend and some on Ropieee (because I want PlexAmp). I’d strongly suggest getting an RPi and installing Ropieee for general hassle avoidance (though your network will enter the equation - if both GMKtec and RPi are Ethernet connected it’s likely to be fine). If you’re literally using this as just a RoonBridge, you can use an older model of RPi if you have one lying around or can buy one inexpensively.
Thanks, CryGi. I looked at a few posts re Dietpi with RoonServer, and from what I gleaned both would be installed on the N97 instead of ROCK. If that would allow me to reliably connect my SMSL DAC directly to the N97 then I’d be all for it. But I’m a lightweight, and didn’t see any “tutorials for lightweights” on how to do it, so I’d probably be unable to get that up and running. I did see the very recent post re a DietPi-related early release candidate but didn’t really understand what the significance was.
Thanks, Johnny (I’d address this to Frank, too, but don’t know how to reply to two people at once). I think I understand the function of a Raspberry Pi as an intermediary. From what you said it’s also my understanding that the Raspberry Pi would be connected to the DAC with USB, and connected to the AirPort Extreme with an Ethernet cable (if so, I assume I could move the N97 next to the Airport, and connect it to the Airport with a short Ethernet cable). Is that correct?
One more thing: I’d also like to be able to connect my iPhone 15 to the DAC with a USB cable (I’ve done it and it works), so would there be any problem if I unplug the Raspberry Pi from the DAC from time to time? Or would it be better to get a Raspberry Pi that has a Toslink output that I could keep connected to the DAC optically?
It’s been a long time since I’ve used an AirPort Extreme. I don’t know how its performance as a switch is, but it should theoretically be fine.
If your AirPort Extreme is acting as your core switch (meaning the switch that is at the center of your network) then your core should definitely be attached to it directly via Ethernet no matter what.
[If any of this causes issues, you can always get a $15 dumb 5 port switch from Amazon or 8 port if you prefer and plug it into the AirPort Extreme with Ethernet cable and plug the core and the DAC each into it. This has the advantage that you can place the switch on your desk or wherever you want the DAC. Over reasonable distances, the length of Cat 5e or Cat 6 Ethernet cables don’t matter, so getting each device where you want it is a consideration. But if you want a different switch to act as your primary switch because of location, performance, or both, just get one and plug it into the AirPort Extreme and then plug everything into that and then your AirPort Extreme would just be acting as a router, not as a switch so long as the only thing plugged into it is your switch and your internet connection. Not trying to make things more complex, just give you the context.]
Ok let’s assume your core is plugged into your core switch with Ethernet - which it should be, whether your core switch is your AirPort Extreme or another switch.
So, if you have an RPi running Ropieee connected via USB and you unplug the DAC from it, the zone should just “disappear” from Roon, and should just “reappear” when you plug it back in. But I don’t want to promise anything. You might have to reboot the RPi or something could go wrong. I don’t know your model of DAC - it might get confused and not present correctly to the RoonBridge on the RPi. But most of the time, what you want to happen will happen.
Also - if I’m talking over your head, don’t hesitate to ask. There’s no such thing as a stupid question.
Get a gigabit dumb switch, whether you get 5 port or 8 port. But TPLink or Netgear are both fine. Just make sure it’s dumb - unmanaged - and fast (1GB). In the US, the TL-SG105 is a good option, or the LS1005G is $9.99 right now.
And in the future, you ideally want other endpoints in your house to be wired back to that switch with a “home run” - a single straight shot of cat 5e (or 6 but that’s overkill for most people) Ethernet cable. Not to say that WiFi definitely won’t work, but if you’ve made the investment here it’s better to keep things this way consistently. Depending on your living situation that can be a royal pain in the butt. Good luck!
As an FYI, in the Roon Networking Best Practices it does say…
Finally, we strongly recommend against using Apple network devices such as the Apple Airport Extreme and Airport Express (note: it’s fine to use the Airport Express as an Airplay device). To ensure the best performance, we recommend against using these devices.
Ugh, then I take it all back. Proceed with caution / low expectations. You need a router that Roon likes. I don’t know why it’s on that list, but if it’s on that list, they probably mean it. Especially if they say “strongly”
I guess I should read more documentation more carefully. That said, it’s unclear to me whether the concern relates to Airports’ performance over WiFi or whether the concern includes their performance as routers etc over Ethernet. That, that, said, there are posts indicating that the Airports should work fine. I’ll give them a try, as I am a penny-pinching person of Scottish descent!
I did not indicate or suggest that the Airport Express was in any way part of your current issue. Just letting you know about a potential issue, hence the “FYI”.
Perhaps not related to your issue, but my recently purchased SMSL D6-S was incredibly finnicky about the usb cable I used to communicate with anything (Roon server or roonbridge). We have a house full of these cables (18 to be exact) and I could only find two that function with the SMSL.
Unfortunately, I cannot tell you why they work and the others did not. Also, they are unbranded cables, so I am not sure where I got them. Most interesting to me: the cable supplied with the SMSL did NOT function either. Maybe something with the USB C protocol and older USB ports?
Very interesting, Papi. I saw some advice re trying other cables, but I only had two close at hand. Your experience makes me think I need to root through some boxes to see whether I can dig up a few more. My N97 mini-pc, though, just has USB-A ports (and the DAC is USB-B) - I’ve read about different USB-C cables having different sets of active pins (some have them all active, some just a subset I think) but don’t know whether that is also true of USB-A and B. First thing I’ll dig out is my multimeter to test my cables for that. Thanks!
Hi @Kevin_Hogg and @Papi_Chulo,
I have done the test on my GMKtec G5 N97 with the same USB-cables that I use without problem for connecting that S.L.S.L-DAC on a Raspberry Pi with RoPieee. So, in my case, I don’t think that the cables could be faulty. That doesn’t mean that changing USB-cables cannot be a solution in other cases, but in my case it isn’t. @Papi_Chulo thank you for the tip.
Kind regards, Frank.
Thanks again, Frank. Really appreciate all the advice. That does make sense, and I figured that the chance of the cable being the culprit was slim since it’s apparent that the DAC is communicating with the N97. I’ve ordered a Raspberry Pi and have my fingers crossed that it with RoPieee will work with the SMSL D300. There does seem to be a bit of an issue with the firmware on that particular DAC as it relates to DSD. Apparently, the v1.0 firmware I have does not support DSD DoP, but while the updated firmware supports DoP it also leads to unwanted clicks and pops so I don’t want to update. I hope that the DoP issue will not create a problem with Ropieee and the Pi.
