Search the Community

I am considering opening up the supplied metal case for the Allo USBridge to remove jumper J28 and allow the USBridge to be powered down separately from the Sparky. On the other hand, there are buttons on the case labelled RST and PWR, but I cannot find anything that tells me what they do. I am looking for a simpler way of shutting down the USBridge (and more importantly the linear power supply feeding it) without having to issue a shutdown command to DietPi. Thanks.

I want to experiment with a Roon Ready endpoint MQA enabled network streamer to listen to MQA selections from Tidal with Roon. MQA has been so hotly debated I want to pick up some gear and listen for myself rather than read endless online debates. I'm not interested in portable DACs or music fed directly from a computer. So, I'm inclined to shy away from the Meridian Explorer 2, Dragonfly Red or iFi Nano BL. I suspect that using the iFi Micro BL on a desktop is a waste of much of what that device has to offer. But perhaps I'm thinking of this the wrong way. Since Roon can now handle the decoding, I realize a renderer is all that I need, however, I don't feel compelled to ignore solutions that offer decoding and rendering. This particular system is very simple. It's a Naim Uniti Atom driving ProAc Tablette 10 speakers. The analog input is available. I've been pleased with the Allo USBRidge that I've deployed on one of my low budget systems and was thinking that pairing that device with a Pro-Ject Pre Box S2 would do the trick for about $580. An alternative would be the Bluesound Node 2 at about $500. I suspect that the USBRidge/Pro-Ject combo would yield better sound. However, the Bluesound would tie things up nicely with a single box. I'm not interested in any of the other features offer by Bluesound. Are there other alternatives you might suggest? How would you think about the two options I've mentioned? Just to put boundaries on this experiment, let's keep the budget below $750. Thanks, -- Rich

Has someone compared SQ of direct USB output from MBP/Audirvana to DAC vs. streaming to a device like Ultrarendu or USBridge with the same DAC and same USB cable ? Thanks Matt

I installed Dietpi on my Sarky and USBridge and got it to work. I can configure the software using the HDMI and a keyboard but I don’t get a GUI when I type dietpi.local. What software do I need select to install from the dietpi-config screen? thanks

https://www.allo.com/sparky/usbridge.html#specs Thinking of going with this. Presently running audio straight from pc to ddc to dac. What benefits can I expect? Will JRiver's DLNA interface with this thing or do I need the Volumio software? Thanks. I am a newbie with these things. PS and how does it connect? Ethernet and usb to computer then out to ddc?

Includes eMMC + reader and microSD memory. PSU and original boxes included. £90 + PayPal fees, including UK delivery. Can ship to Europe with delivery fee.

Just received a newly purchased USBridge. Am able to access the dashboard. Clicked View under Roon Bridge. Clicked enable; switches slide to the green side. Clicked Save Changes; then I get the spinning wheel, Successfully Updated, and then the switches slide back to red. Clicked Back, and I see that the Roon Bridge status is Inactive. What else do I need to do?

Unable to update USBridge from v6.18.14 to v6.21.1 Err:10 https://deb.debian.org/debian-security stretch/updates/contrib Translation-en BZ2_bzread: /var/lib/apt/lists/partial/deb.debian.org_debian-security_dists_stretch_updates_contrib_i18n_Translation-en.bz2 Read error (-5: DATA_ERROR_MAGIC) Not an issue with a second USBridge.

Hi there! I just got my Allo USB Wifi Dongle. It should be "Plug in, and start surfing! Includes easy to setup driver." Well, as a spoiled windows user, I thought it would be litterally "plug and play". However, the manual ist called "Quick_Start_Guide_for_Driver_Compilation_and_Installation" and is not at all easy for me... Can somebody help me step by step...? I don't have a screen on the USBridge, I just operate it by the allo web interface or by SSH over Putty... THANKS!

Hi! I got a new USBridge with DietPi, my intention is to use Squeezelite. My DAC is a Soekris 1101 USB DAC. I connect the DAC and power it on. It shows the 44khz - led while it waits for the source to connect. Then I power on USBBridge and wait until it boots up. The result is, that I don't get any sound at all: Squeezelite is "enabled" (which is a sign that somehow it recognizes that a DAC is connected, because without the DAC connected, Squeezelite stays "disabled"). However, Squeezelite refuses to play tracks. Prior to buy the USBridge, I got myself a Raspberry Pi 3 B+ and I installed PiCorePlayer in order to try out the compatibility of my DAC. It worked without problem. Given that I got it to work with a RPi, I thought I could buy a USBridge with no risk. Even more so, as the DAC is natively supportet by Linux according to the manufacturor. Some additional information: The power should not be the problem, as I connect the DAC through a device that cuts the USB power supply from USBridge and adds power from a clean (linear) source. If I connect the DAC directly, it does not power up (I suppose, USBridge does not deliver enough power). This setup works flawlessly with the Raspberry Pi 3 B+ and PiCorePlayer pCP4.1.0. While it boots, the 44khz-led switches off on the DAC. This is not a normal behaviour. Normaly, it remains on normally, or it switches to another value. This might indicate some issue on the communication between DAC und USBridge. Any possible solution??? And: I suppose that PiCorePlayer would not work properly on a USBridge, supporting the clean USB-port? Or would it? If yes, this would possibly resolve the issue for me. And if yes, how to... I am not familiar with eMMC - flashing... If it helps if I provide Log-Files or similar, please let me know how to get them, I am a complete newbie (I manage to SSH into DietPi with putty, but I have no idea where and how to find the log-files). THANKS INDEED in advance! Urs

Transport: Allo USBridge DAC: Schiit Yggdrasil OS: Volumio (newest available at the time of writing) Source file: Tidal playing via Volumio's native integration Every once in a while a dropout occurs. Music either stops completely (it shows as playing in Volumio GUI but there's only silence or there are a second long pauses). Issue occurs at random however I've noticed that on some tracks it occurs 100% of the time. Example track: link. Issue did not occur on RaspberryPi (also running Volumio) which is why I'm reporting it here. I'm okay with linux/ssh so if you need me to collect any logs just tell me where to look (there were no obvious errors in journalctl) Feb 01 19:15:11 volumio sudo[1947]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Feb 01 19:15:11 volumio sudo[1947]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:11 volumio sudo[1947]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:11 volumio sudo[1949]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:15:11 volumio sudo[1949]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:11 volumio sudo[1949]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:12 volumio volumio[743]: info: CoreCommandRouter::volumioGetBrowseSources Feb 01 19:15:12 volumio volumio[743]: info: CoreCommandRouter::volumioGetState Feb 01 19:15:12 volumio volumio[743]: info: CoreStateMachine::getState Feb 01 19:15:12 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: appearance , getUiSettings Feb 01 19:15:12 volumio sudo[1957]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:15:12 volumio sudo[1957]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:12 volumio sudo[1957]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:12 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: wizard , getShowWizard Feb 01 19:15:12 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: system , getShowWizard Feb 01 19:15:12 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom Feb 01 19:15:12 volumio sudo[1964]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:15:12 volumio sudo[1964]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:12 volumio volumio[743]: info: Listing playlists Feb 01 19:15:12 volumio sudo[1964]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:13 volumio volumio[743]: info: CoreCommandRouter::volumioGetQueue Feb 01 19:15:13 volumio volumio[743]: info: CoreStateMachine::getQueue Feb 01 19:15:13 volumio volumio[743]: info: CorePlayQueue::getQueue Feb 01 19:15:14 volumio volumio[743]: info: No input data Feb 01 19:15:14 volumio volumio[743]: info: No input data Feb 01 19:15:15 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: streaming_services , handleBrowseUri Feb 01 19:15:21 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: streaming_services , handleBrowseUri Feb 01 19:15:22 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: streaming_services , handleBrowseUri Feb 01 19:15:22 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: streaming_services , handleBrowseUri Feb 01 19:15:28 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: streaming_services , handleBrowseUri Feb 01 19:15:32 volumio volumio[743]: info: CoreCommandRouter::volumioAddQueueItems Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::addQueueItems Feb 01 19:15:32 volumio volumio[743]: info: CorePlayQueue::addQueueItems Feb 01 19:15:32 volumio volumio[743]: info: Adding Item to queue: tidal://song/100794834 Feb 01 19:15:32 volumio volumio[743]: info: Exploding uri tidal://song/100794834 in service streaming_services Feb 01 19:15:32 volumio volumio[743]: info: CorePlayQueue::saveQueue Feb 01 19:15:32 volumio volumio[743]: info: CoreCommandRouter::volumioPushQueue Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::updateTrackBlock Feb 01 19:15:32 volumio volumio[743]: info: CorePlayQueue::getTrackBlock Feb 01 19:15:32 volumio volumio[743]: info: CoreCommandRouter::volumioPlay Feb 01 19:15:32 volumio volumio[743]: UNSET VOLATILE Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::play index 6 Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::setConsumeUpdateService undefined Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::stop Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::setConsumeUpdateService undefined Feb 01 19:15:32 volumio volumio[743]: UNSET VOLATILE Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::play index undefined Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::setConsumeUpdateService undefined Feb 01 19:15:32 volumio volumio[743]: info: CorePlayQueue::getTrack 6 Feb 01 19:15:32 volumio volumio[743]: info: CoreStateMachine::startPlaybackTimer Feb 01 19:15:32 volumio volumio[743]: info: CorePlayQueue::getTrack 6 Feb 01 19:15:32 volumio volumio[743]: info: [1549048532974] streamingServices::clearAddPlayTrack Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand stop Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand clear Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: Feb 01 19:15:33 volumio volumio[743]: ---------------------------- MPD announces system playlist update Feb 01 19:15:33 volumio volumio[743]: info: Ignoring MPD Status Update Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand load "http://ab-pr-ak.audio.tidal.com/a97c414 Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: Feb 01 19:15:33 volumio volumio[743]: info: ------------------------------ 9ms Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand add "http://ab-pr-ak.audio.tidal.com/a97c4149 Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: Feb 01 19:15:33 volumio volumio[743]: ---------------------------- MPD announces system playlist update Feb 01 19:15:33 volumio volumio[743]: info: Ignoring MPD Status Update Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: CoreStateMachine::setConsumeUpdateService mpd Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand play Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: ------------------------------ 10ms Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: Feb 01 19:15:33 volumio volumio[743]: ---------------------------- MPD announces state update: player Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::getState Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand status Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio kernel: iso_packets:0, bInterval:1, urb_interval:1, reg_con:0x4 Feb 01 19:15:33 volumio kernel: iso_packets:0, bInterval:4, urb_interval:8, reg_con:0x4 Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::parseState Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand playlistinfo Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: Feb 01 19:15:33 volumio volumio[743]: ---------------------------- MPD announces state update: player Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::getState Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand status Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::parseTrackInfo Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::pushState Feb 01 19:15:33 volumio volumio[743]: info: CoreCommandRouter::servicePushState Feb 01 19:15:33 volumio volumio[743]: info: CoreStateMachine::syncState Feb 01 19:15:33 volumio volumio[743]: info: CorePlayQueue::getTrack 6 Feb 01 19:15:33 volumio volumio[743]: info: STATE SERVICE {"status":"play","position":0,"seek":0,"duration":218,"sample Feb 01 19:15:33 volumio volumio[743]: info: CURRENT POSITION 6 Feb 01 19:15:33 volumio volumio[743]: info: CoreStateMachine::syncState stateService play Feb 01 19:15:33 volumio volumio[743]: info: CoreStateMachine::syncState currentStatus stop Feb 01 19:15:33 volumio volumio[743]: info: CoreStateMachine::pushState Feb 01 19:15:33 volumio volumio[743]: info: CoreStateMachine::getState Feb 01 19:15:33 volumio volumio[743]: info: CoreCommandRouter::volumioPushState Feb 01 19:15:33 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Feb 01 19:15:33 volumio volumio[743]: info: ------------------------------ 110ms Feb 01 19:15:33 volumio volumio[743]: info: parsing response... Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::parseState Feb 01 19:15:33 volumio sudo[1997]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:15:33 volumio sudo[1997]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:33 volumio volumio[743]: info: ControllerMpd::sendMpdCommand playlistinfo Feb 01 19:15:33 volumio volumio[743]: info: sending command... Feb 01 19:15:33 volumio volumio[743]: info: MyVolumio status changed Feb 01 19:15:34 volumio volumio[743]: info: MyVolumio status changed Feb 01 19:15:34 volumio sudo[1997]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:34 volumio volumio[743]: info: parsing response... Feb 01 19:15:34 volumio volumio[743]: info: ControllerMpd::parseTrackInfo Feb 01 19:15:34 volumio volumio[743]: info: ControllerMpd::pushState Feb 01 19:15:34 volumio volumio[743]: info: CoreCommandRouter::servicePushState Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::syncState Feb 01 19:15:34 volumio volumio[743]: info: CorePlayQueue::getTrack 6 Feb 01 19:15:34 volumio volumio[743]: info: STATE SERVICE {"status":"play","position":0,"seek":464,"duration":218,"samp Feb 01 19:15:34 volumio volumio[743]: info: CURRENT POSITION 6 Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::syncState stateService play Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::syncState currentStatus play Feb 01 19:15:34 volumio volumio[743]: info: Received an update from plugin. extracting info from payload Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::pushState Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::getState Feb 01 19:15:34 volumio volumio[743]: info: CoreCommandRouter::volumioPushState Feb 01 19:15:34 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::pushState Feb 01 19:15:34 volumio volumio[743]: info: CoreStateMachine::getState Feb 01 19:15:34 volumio volumio[743]: info: CoreCommandRouter::volumioPushState Feb 01 19:15:34 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Feb 01 19:15:34 volumio sudo[2004]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:15:34 volumio sudo[2004]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:34 volumio volumio[743]: info: ------------------------------ 308ms Feb 01 19:15:34 volumio sudo[2007]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:15:34 volumio sudo[2004]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:34 volumio sudo[2007]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:15:34 volumio sudo[2007]: pam_unix(sudo:session): session closed for user root Feb 01 19:15:34 volumio volumio[743]: info: MyVolumio status changed Feb 01 19:15:34 volumio volumio[743]: info: MyVolumio status changed Feb 01 19:17:12 volumio systemd[1]: Starting Cleanup of Temporary Directories... Feb 01 19:17:12 volumio systemd[1]: Started Cleanup of Temporary Directories. Feb 01 19:17:55 volumio kernel: atc260x-rtc atc2603c-rtc.0: atc260x_rtc_settime(): 2019-02-01 19:17:55 Feb 01 19:19:05 volumio volumio[743]: info: CoreCommandRouter::volumioPause Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::pause Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::stPlaybackTimer Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::servicePause Feb 01 19:19:05 volumio volumio[743]: info: CorePlayQueue::getTrack 6 Feb 01 19:19:05 volumio volumio[743]: info: CoreCommandRouter::servicePause Feb 01 19:19:05 volumio volumio[743]: info: [1549048745864] streamingServices::pause Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::setConsumeUpdateService mpd Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::pause Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::sendMpdCommand pause Feb 01 19:19:05 volumio volumio[743]: info: sending command... Feb 01 19:19:05 volumio volumio[743]: info: parsing response... Feb 01 19:19:05 volumio volumio[743]: info: Feb 01 19:19:05 volumio volumio[743]: ---------------------------- MPD announces state update: player Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::getState Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::sendMpdCommand status Feb 01 19:19:05 volumio volumio[743]: info: sending command... Feb 01 19:19:05 volumio volumio[743]: info: parsing response... Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::parseState Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::sendMpdCommand playlistinfo Feb 01 19:19:05 volumio volumio[743]: info: sending command... Feb 01 19:19:05 volumio volumio[743]: info: parsing response... Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::parseTrackInfo Feb 01 19:19:05 volumio volumio[743]: info: ControllerMpd::pushState Feb 01 19:19:05 volumio volumio[743]: info: CoreCommandRouter::servicePushState Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::syncState Feb 01 19:19:05 volumio volumio[743]: info: CorePlayQueue::getTrack 6 Feb 01 19:19:05 volumio volumio[743]: info: STATE SERVICE {"status":"pause","position":0,"seek":195953,"duration":218," Feb 01 19:19:05 volumio volumio[743]: info: CURRENT POSITION 6 Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::syncState stateService pause Feb 01 19:19:05 volumio kernel: aotg_hub_endpoint_disable Feb 01 19:19:05 volumio kernel: aotg_hcd aotg_hcd.1: <EP DISABLE> ep5 index 1 from ep [out] Feb 01 19:19:05 volumio kernel: aotg_hub_endpoint_disable Feb 01 19:19:05 volumio kernel: aotg_hcd aotg_hcd.1: <EP DISABLE> ep5 index 4 from ep [in] Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::syncState currentStatus pause Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::pushState Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::getState Feb 01 19:19:05 volumio volumio[743]: info: CoreCommandRouter::volumioPushState Feb 01 19:19:05 volumio volumio[743]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Feb 01 19:19:05 volumio volumio[743]: info: CoreStateMachine::stPlaybackTimer Feb 01 19:19:05 volumio volumio[743]: info: ------------------------------ 58ms Feb 01 19:19:05 volumio sudo[2245]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Feb 01 19:19:05 volumio sudo[2245]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 01 19:19:05 volumio sudo[2245]: pam_unix(sudo:session): session closed for user root Feb 01 19:19:05 volumio volumio[743]: info: MyVolumio status changed Feb 01 19:19:05 volumio volumio[743]: info: MyVolumio status changed Feb 01 19:19:12 volumio sshd[2255]: Accepted password for volumio from 192.168.0.13 port 44274 ssh2 Feb 01 19:19:12 volumio sshd[2255]: pam_unix(sshd:session): session opened for user volumio by (uid=0) Feb 01 19:19:12 volumio systemd[1]: Starting user-1000.slice. Feb 01 19:19:12 volumio systemd[1]: Created slice user-1000.slice. Feb 01 19:19:12 volumio systemd[1]: Starting User Manager for UID 1000... Feb 01 19:19:12 volumio systemd[1]: Starting Session 2 of user volumio. Feb 01 19:19:12 volumio systemd-logind[516]: New session 2 of user volumio. Feb 01 19:19:12 volumio systemd[1]: Started Session 2 of user volumio. Feb 01 19:19:12 volumio systemd[2260]: pam_unix(systemd-user:session): session opened for user volumio by (uid=0) Feb 01 19:19:12 volumio systemd[2260]: Starting Paths. Feb 01 19:19:12 volumio systemd[2260]: Reached target Paths. Feb 01 19:19:12 volumio systemd[2260]: Starting Timers. Feb 01 19:19:12 volumio systemd[2260]: Reached target Timers. Feb 01 19:19:12 volumio systemd[2260]: Starting Sockets. Feb 01 19:19:12 volumio systemd[2260]: Reached target Sockets. Feb 01 19:19:12 volumio systemd[2260]: Starting Basic System. Feb 01 19:19:12 volumio systemd[2260]: Reached target Basic System. Feb 01 19:19:12 volumio systemd[2260]: Starting Default. Feb 01 19:19:12 volumio systemd[2260]: Reached target Default. Feb 01 19:19:12 volumio systemd[2260]: Startup finished in 26ms. Feb 01 19:19:12 volumio systemd[1]: Started User Manager for UID 1000. Feb 01 19:19:12 volumio sshd[2255]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Feb 01 19:19:12 volumio sshd[2255]: lastlog_openseek: Couldn't stat /var/log/lastlog: No such file or directory Feb 01 19:19:17 volumio sudo[2274]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl -e Feb 01 19:19:17 volumio sudo[2274]: pam_unix(sudo:session): session opened for user root by volumio(uid=0) Feb 01 19:20:10 volumio sudo[2274]: pam_unix(sudo:session): session closed for user root Feb 01 19:20:12 volumio sudo[2335]: volumio : TTY=pts/0 ; PWD=/home/volumio ; USER=root ; COMMAND=/bin/journalctl Feb 01 19:20:12 volumio sudo[2335]: pam_unix(sudo:session): session opened for user root by volumio(uid=0)

Currently, I'm using an Amazon Fire Stick 4K with BubbleUPnP (Tidal), it outputs the album art and replay info nicely via HDMI (see attached picture). I want to replace the Fire Stick with an USBridge Sig though, and keep using BubbleUPnP. The USBridge has an HDMI-Output, what will it display?

Hello, about to embark on RP audio streaming for a naim dac-v1 and have settled on a USBridge. I have read of people using 2 power supplies for the main board and the other for the HAT. Anyone experiment here? also considering an Ifi Purifier 2? Thanks for any input ! Cheers John

I have being using USBridge for a (+/-) month. USBridge is streaming music from a Synology NAS (1817+), through "Volumio" to a dCS Debussy DAC. After a while USBridge is losing connection to the network. If source of music is directly connected (usb) to the sparky, the playlist is run to its end. If source is the Synology music stops playing. The only solution is to reboot the system through the command line but it again for a very short lifecycle. Any idea for a possible solution?

Hello, I just received my USBridge. It connects to the network fine using the onboard ethernet. When I try to use the gigabyte dongle purchased from ALLO, it fails to power up from any of the sparky ports. I tried it on my PC and it powers up just fine. Please advise.

Hi Are Allo still working on their own player for the Usbridge Sig ? MoOde 6.5.2 is useless with my Chord Dacs. Regards

I am wanting to take the jumper out to separately power my Allo Usbridge.. I realize the rechargeable LifeP0 18650 x 4 work but what about a power bank like this? Could this be used? Could i use adapter for USB C to then power upper unit of Usbridge? Seems like this would be much easier than constantly recharging the 4 LifePo batteries. Possibly better more stable current delivery to Allo as well? https://www.amazon.com/gp/product/B07KS5Z8GL/ref=ox_sc_act_title_2?smid=A2KUZVNQ9LP7N9&psc=1 USB C Portable Charger RAVPower 20100mAh PD 3.0 45W Power Delivery Power Bank (USB-C Input, 45W Type-C Output) updated USB-C power Delivery charges almost all devices at a huge 45W output, highly compatible with the majority of Type-C devices, such as MacBook, MacBook Air, macbookpro etc. Parallel power: recharge 2 devices at a time with the USB A and USB C outputs; Please note that laptops can only be charged alone via the USB C port Ultra-fast recharge: get a full recharge in just 3.5 hours with the 30W USB C port, Micro-USB QC charges at 18W in just 6 hours, standard 2.4a charges in just 9.5 hours USB C Powerbank.docx

Hi everybody, I'd been fighting with the config of my allo usbridge unit for a while and when I finally thought everything was set up properly I couldn't get any sound from it. Apparently, my dac Topping d10 doesn't seem to be powered by the clean output of the Usbridge board whereas it is perfectly powered by the other Usb connections. But of course, That's not why I bought the Usbridge. Is it a problem of compatibility? The dac Topping d10 is a usb powered dac, it hasn't got an external power supply. Is there an easy solution to that? Thanks in advance for your help, Raul

Has anybody compared the new USBridge Sig to a standard RPi3 (or RPi4) as a host system for the DigiOne Signature? Are there obvious advantages/disadvantages using an USBridge Sig instead of a RPi? Thanks, nbpf

Hi... I've been using an Regen/idac2 combination with the USBridge just fine. I'm using the standard USBridge PS powering both the Sparky and the hat. idac2 is USB powered, and is NOT on the list of compatible DACS. Last night, I removed the Regen, and plugged the idac2 directly into the USBridge. No lights on the DAC, a quiet, clicking sound from the USBridge...and no sound of course. Restored the Regen and all is well again. Questions: Since it works with the Regen in place, and therefore powering the DAC, might the problem be that the current requirements of the DAC exceed what the USBridge can supply? I see, though, from the compatibility list that the ifi idsd IS compatible, and it similarly contains a headphone amp, so I would guess that the current requirements are similar. Given that the USB data from the USBridge is so clean, I'd like to at least try it without the Regen. Any suggestions as to how I can accomplish this would be appreciated. I'd be happy to get a separate PS (probably an iPower) for the USBridge, if that will address the problem. Many thanks... Michael

Hello, I am a total newbie to the Allo products. I bought a USBridge and plugged in a monitor, keyboard, mouse and ethernet cable. Then I plugged in the power cord to the DC 5V input. Then...nada, nothing! No LEDs lighting up, no monitor image, nothing. I do see some red lights on when I peer down into the unit past the SD card slot and some blue lights when I peer in beside the USB 3.0 slot. But no colours at the LEDs. I have waited upwards of 10 minutes and I have unplugged and plugged in the unit 5 times now. I have looked over the scant FAQ and tried to search here for a similar topic but I am coming up empty on suggestions for my next diagnostic steps. I would appreciate any pointers for what I should do next. Cheers, James

Hello, I have been using usbridge for almost a year with my Auralic Polaris (usb-dac) and Squeezelite. I control my system with iPeng. Dietpi v6.6 was installed in the headless version. After the update to 6.8, there was an issue. Usbridge has no sound output. I reinstalled Dietpi with allo gui (version 6.6). Sound was back. After an update to 6.8 again no sound output. Does anyone know this behavior? What could be the reason? Thank you