simonklp Posted September 9, 2018 Share Posted September 9, 2018 On Friday, September 07, 2018 at 9:15 PM, jabbr said: Its not just the CPU utilization but the amount of noise in your PC ... the NAA is a cheap and very effective way to isolate your PC from your DAC. Wholeheartedly agree. Link to comment
simonklp Posted September 9, 2018 Share Posted September 9, 2018 On Friday, September 07, 2018 at 9:11 PM, jabbr said: The SQ is surprisingly good given my very limited expectations. What it tells me is that low power eg 5-10W and complete galvanic isolation may be the most important factors (but not enough data to be conclusive) ... in any case Although I also don't have sufficient data, I have the same opinion as you. Thanks for your sharing. Link to comment
asdf1000 Posted September 11, 2018 Share Posted September 11, 2018 On 8/19/2018 at 7:02 PM, Miska said: his is hardware I use for NAA at the moment: https://up-shop.org/home/81-up-gws01w4g-memory32g-emmc-boardwo-vesa-plate.html (also works fine for HQPlayer Embedded doing upsampling to PCM output) I picked up one of these, ordered direct from Up. I first checked it's running the latest BIOS update and it is. It's happily powered by a USB3.0 port in my Startech USB3.0 7-port hub (with grounded DC plug power supply...). My iFi Pro iDSD DACs USB interface is not 5 V bus powered though. I use this 22 AWG USB to 5.5 x 2.1mm DC power cable: https://www.spacehifi.com.au/cables-and-connectors/usb-cables/usb-to-5.5mm-x-2.1mm-power-cable Very happy indeed. For ultra critical listening (like on the weekend) I can use the same USB-DC power cable to power Up with a Mophie USB powerbank.. Link to comment
jabbr Posted September 11, 2018 Share Posted September 11, 2018 Consider me a Windows newbie, but I have a weird problem with trying to run Windows 10 as wireless NAA. Note I have 2 other NAA, one a wired linux and the other a wireless linux and both are working. I just got a Minix Neo Z83-4 Cherry Trail NUC (Windows 10) Wifi 802.11ac that I;m trying to use as NAA. When I run networkaudiod.exe, the HQPlayer NAA recognition stops working entirely -- for my other NAA as well. I tried running wireshark on my linux laptop (also Wifi) to see if there is a broadcast storm etc but I'm not having luck ... any ideas? Custom room treatments for headphone users. Link to comment
Miska Posted September 11, 2018 Share Posted September 11, 2018 19 minutes ago, jabbr said: Consider me a Windows newbie, but I have a weird problem with trying to run Windows 10 as wireless NAA. Note I have 2 other NAA, one a wired linux and the other a wireless linux and both are working. I just got a Minix Neo Z83-4 Cherry Trail NUC (Windows 10) Wifi 802.11ac that I;m trying to use as NAA. When I run networkaudiod.exe, the HQPlayer NAA recognition stops working entirely -- for my other NAA as well. I tried running wireshark on my linux laptop (also Wifi) to see if there is a broadcast storm etc but I'm not having luck ... any ideas? Just make sure each NAA have at least different name, otherwise HQPlayer will certainly become confused... Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
jabbr Posted September 11, 2018 Share Posted September 11, 2018 17 minutes ago, Miska said: Just make sure each NAA have at least different name, otherwise HQPlayer will certainly become confused... Tried running the networkaudiod_name.bat, and can't even any IPs to show up in the network naming option ... Custom room treatments for headphone users. Link to comment
shadowlight Posted September 11, 2018 Share Posted September 11, 2018 @jabbr, try the following from command prompt to see if you are seeing any errors set NETWORKAUDIOD_NAME=jabbr-win-naa (give it any old name that you want) networkdaudiod See if you are seeing any error messages. Is you Windows OS x64 or regular x86? Make sure to run the networkaudiod command from the appropriate directory. Other thing to confirm is IPv6 support on the Win system. Does wired connection also knock's off the other NAA? jabbr 1 Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 [networkaudiod] (456): networkaudiod Copyright (C) 2011-2018 Jussi Laako / Signalyst. All rights reserved. [networkaudiod] (456): ASIO Technology by Steinberg Media Technologies GmbH. [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:57380 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:57380 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:57380 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:57380 [networkaudiod] (456): connection from [::ffff:192.168.1.21]:56901 [networkaudiod] (456): Network QoS functionality not available [networkaudiod] (456): protocol error: clASIOMiniEngine::DeviceLookup(): lDrvs < 0 [networkaudiod] (456): begin disconnection [networkaudiod] (456): disconnected [::ffff:192.168.1.21]:56901 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:50593 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:50593 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:50593 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:50593 [networkaudiod] (456): connection from [::ffff:192.168.1.21]:56903 [networkaudiod] (456): Network QoS functionality not available [networkaudiod] (456): protocol error: clASIOMiniEngine::DeviceLookup(): lDrvs < 0 [networkaudiod] (456): begin disconnection [networkaudiod] (456): disconnected [::ffff:192.168.1.21]:56903 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:62600 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:62600 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:62600 [networkaudiod] (456): discovery from [::ffff:192.168.1.21]:62600 [networkaudiod] (456): connection from [::ffff:192.168.1.21]:56907 [networkaudiod] (456): Network QoS functionality not available [networkaudiod] (456): protocol error: clASIOMiniEngine::DeviceLookup(): lDrvs < 0 [networkaudiod] (456): begin disconnection [networkaudiod] (456): disconnected [::ffff:192.168.1.21]:56907 This is what I get with wireless. I set NETWORKAUDIOD_NAME=minix-w10 and then ran from command line. Custom room treatments for headphone users. Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 Success, it was a flaky Thesycon driver on Windows that needed to be reinstalled ... interesting that that took out the whole NAA network :shrug: If I put the device in the right spot to get a strong Wifi signal, I can do DSD512 no problem, otherwise dropouts. Custom room treatments for headphone users. Link to comment
shadowlight Posted September 12, 2018 Share Posted September 12, 2018 Congrats on getting it to work. Did you optimize the win is (assuming win 10 home). I remember running into something similar where I had two Naa instance on the system and HQPe did not like that. Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 I have 3 sometimes 4 NAA on the network at the same time (testing various configs, mostly linux) -- so wasn't expecting that particular issue when the DAC wasn't recognized (no driver). Haven't optimized Win 10 yet... I am working on getting 802.11ac working with my Espressobin (network optimized ARM board) but need a new Wifi card -- the two I got didn't work ... so that's tomorrow's project, at least I got DSD512 working with the Topping DX7s finally! Custom room treatments for headphone users. Link to comment
shadowlight Posted September 12, 2018 Share Posted September 12, 2018 Yeah, I have the same thing. The first thing that I do is give it a different name for the NAA. I have a celeron based linux (Debian, celeron based Win10 Pro optimized using the thread on CA and a RPi 3. I have successfully used the Linux and Win10 system to stream DSD512 via wireless and I have not tried using the RPi for DSD but I have successfully used it to 384k PCM stream. I also have a Beaglebone Black that I am planning to leverage with the DSC2 DSD only DAC (group buy on diyaudio) to pull the i2s signal directly off the Cronus/Hermes setup onto the DSC2 bypassing the USB completely. jabbr 1 Link to comment
asdf1000 Posted September 12, 2018 Share Posted September 12, 2018 Hi @Miska Does your latest naa-355-x64 image support the RTL8812AU wifi chipset driver? For USB-WiFi adapter? If not, possible to patch it in? Thinking of using NAA in a 3rd system which doesn't have ethernet cable access. Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 Regardless of WiFi kernel drivers would be the issue of trying to config WiFi at all with his images — best to use a mainline kernel — 4.18 has new DSD mods and can be patched for RT Custom room treatments for headphone users. Link to comment
asdf1000 Posted September 12, 2018 Share Posted September 12, 2018 20 minutes ago, jabbr said: Regardless of WiFi kernel drivers would be the issue of trying to config WiFi at all with his images — best to use a mainline kernel — 4.18 has new DSD mods and can be patched for RT Ah yes, I forgot about that - the next steps like selecting the WiFi network and entering the network's password. In another system I already have the Allo USBridge NAA doing DSD512 over WiFi ac, using the Asus USB-AC56 adapter (DietPi). I do prefer Jussi's NAA image though - there's no 'surprises' on headphones... Would love his NAA image running on a 'low noise' NAA device, like USBridge, microRendu etc. Those only support NAA via DietPi OS and sonicOrbiter OS etc. You can't always get what you want I guess ? All Link to comment
Miska Posted September 12, 2018 Share Posted September 12, 2018 2 hours ago, jabbr said: Regardless of WiFi kernel drivers would be the issue of trying to config WiFi at all with his images — best to use a mainline kernel — 4.18 has new DSD mods and can be patched for RT My x64 images contain RT kernel with all DSD support... 2 hours ago, Em2016 said: Ah yes, I forgot about that - the next steps like selecting the WiFi network and entering the network's password. I have thought and examined possibility of adding WiFi support to the images, but have not yet found a satisfactory way to deal with these. Now network is managed by systemd-networkd, but that doesn't really have a nice way to deal with wlans... There are other options too, but each have some down side. asdf1000 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
amolan Posted September 12, 2018 Share Posted September 12, 2018 Hi Miska, Are these images available for us ? Thanks, Alexandre. Link to comment
Miska Posted September 12, 2018 Share Posted September 12, 2018 34 minutes ago, amolan said: Are these images available for us ? Those are available to everyone! You can find all the images if you go to download NAA from the web page, all images are under the "images" sub-folder. Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
amolan Posted September 12, 2018 Share Posted September 12, 2018 Thanks Miska, I will take a look. Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 6 hours ago, Miska said: My x64 images contain RT kernel with all DSD support... Certainly. I’d be very happy for you to support all the devices I’m using! Seriously x64 is one thing as you say, WiFi is a whole ‘nuther level of complexity and ARM with multiple SoCs each needing kernel support yet another level of complexity, that providing images for all options would be a lot of work... I’m glad to see these devices now merged into mainline which should mean that as new DSD devices get introduced there can be one place to get updates. It would have been better to do device detection somewhere else than the kernel so that eg changes to quirks.c could be distributed independently. Oh well. ATM I can build the armbian image, burn to SD, open and edit both /etc/network/interfaces and then /etc/wpa_supplicant/wpa_supplicant.conf pop the SD into the device, power on and then SSH in to install networkaudiod.deb (I’m sure I can figure out how to preinstall networkaudiod.deb into my image..,) Custom room treatments for headphone users. Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 Hmm ... something to consider would be a DTB that contained all the info for the USB DSD devices — quirks.c could read on startup and build a table ... Custom room treatments for headphone users. Link to comment
Miska Posted September 12, 2018 Share Posted September 12, 2018 13 minutes ago, jabbr said: Hmm ... something to consider would be a DTB that contained all the info for the USB DSD devices — quirks.c could read on startup and build a table ... DTB is non-x86, on x86 there's ACPI table from BIOS which does better job. But generally DTB or ACPI is not used for devices behind USB bus, because it is hot-plug. But overall, this driver stuff is not specific to DSD support or audio, there's plenty of similar things for network interfaces and other hardware, regardless if it is PCIe or USB. Quote ATM I can build the armbian image, burn to SD, open and edit both /etc/network/interfaces and then /etc/wpa_supplicant/wpa_supplicant.conf I can experimentally put wpa_supplicant and WiFi support on some images. But I doubt if it ends up being walk in the park in practice for people trying to use it... asdf1000 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
jabbr Posted September 12, 2018 Share Posted September 12, 2018 1 hour ago, Miska said: DTB is non-x86, on x86 there's ACPI table from BIOS which does better job. But generally DTB or ACPI is not used for devices behind USB bus, because it is hot-plug. Ugh ... so nothing device independent. I just see a bunch of audio os vendors who are reinventing the wheel to add DSD support because they are on 3.x kernels etc... and having tried to compile 4.18 for RPi myself ... I’m sure I messed something up ... would be great to update a package just for ALSA to reconfigure the USB quirks ... 1 hour ago, Miska said: But overall, this driver stuff is not specific to DSD support or audio, there's plenty of similar things for network interfaces and other hardware, regardless if it is PCIe or USB. Yeah DKMS works great for example adding/customizing the IXGBE Ethernet driver. 1 hour ago, Miska said: I can experimentally put wpa_supplicant and WiFi support on some images. But I doubt if it ends up being walk in the park in practice for people trying to use it... That would be great. At least something. I’m having good success with it. Custom room treatments for headphone users. Link to comment
Miska Posted September 12, 2018 Share Posted September 12, 2018 2 hours ago, jabbr said: Ugh ... so nothing device independent. I just see a bunch of audio os vendors who are reinventing the wheel to add DSD support because they are on 3.x kernels etc... and having tried to compile 4.18 for RPi myself ... I’m sure I messed something up ... would be great to update a package just for ALSA to reconfigure the USB quirks ... Some vendors will do kernel maintenance wrong and get locked into some ancient kernel version, Android being one of such... 2 hours ago, jabbr said: Yeah DKMS works great for example adding/customizing the IXGBE Ethernet driver. You can use DKMS also for recompiling UAC driver module, no problem... But you will need to have a fork of the driver, same as for the IXGBE, etc. jabbr 1 Signalyst - Developer of HQPlayer Pulse & Fidelity - Software Defined Amplifiers Link to comment
jabbr Posted September 15, 2018 Share Posted September 15, 2018 Espressobin as NAA: I've compiled 4.18.7 with RT5 patches (realtime) and enabled the ALSA drivers (not default in the armbian download), as well as WiFi up and running. Success with networkaudiod-arm64 with PCM. DSD not enabled Still trying to get the Topping DX7s working with DSD (quirks.c says it should): /proc/asound/card0/stream0 jon@espressobin:~$ sudo cat /proc/asound/card0/stream0 Topping DX7s at usb-d0058000.usb-1, high speed : USB Audio Playback: Status: Stop Interface 1 Altset 1 Format: S32_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000 Data packet interval: 125 us Interface 1 Altset 2 Format: S32_LE Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000 Data packet interval: 125 us Interface 1 Altset 3 Format: SPECIAL Channels: 2 Endpoint: 1 OUT (ASYNC) Rates: 44100, 48000, 88200, 96000, 176400, 192000, 352800, 384000, 705600, 768000 Data packet interval: 125 us and the relevant part of syslog: Sep 15 01:04:09 localhost kernel: [ 742.132289] usb 2-1: new high-speed USB device number 6 using xhci-hcd Sep 15 01:04:09 localhost kernel: [ 742.246313] usb 2-1: Device not responding to setup address. Sep 15 01:04:09 localhost kernel: [ 742.449292] usb 2-1: Device not responding to setup address. Sep 15 01:04:09 localhost kernel: [ 742.657124] usb 2-1: device not accepting address 6, error -71 Sep 15 01:04:09 localhost kernel: [ 742.771137] usb 2-1: new high-speed USB device number 7 using xhci-hcd Sep 15 01:04:09 localhost kernel: [ 742.885163] usb 2-1: device descriptor read/64, error -71 Sep 15 01:04:10 localhost kernel: [ 743.119658] usb 2-1: New USB device found, idVendor=152a, idProduct=8750, bcdDevice= 6.f2 Sep 15 01:04:10 localhost kernel: [ 743.119672] usb 2-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0 Sep 15 01:04:10 localhost kernel: [ 743.119680] usb 2-1: Product: DX7s Sep 15 01:04:10 localhost kernel: [ 743.119686] usb 2-1: Manufacturer: Topping Sep 15 01:04:10 localhost kernel: [ 743.158804] usb 2-1: 1:3 : unsupported format bits 0x100000000 Sep 15 01:04:53 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): discovery from [::ffff:192.168.1.21]:57965 Sep 15 01:04:53 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): discovery from [::ffff:192.168.1.21]:57965 Sep 15 01:04:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): connection from [::ffff:192.168.1.21]:60730 Sep 15 01:04:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): Found ALSA device: hw:CARD=DX7s,DEV=0 - DX7s: USB Audio Sep 15 01:04:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): begin disconnection Sep 15 01:04:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA backend uninitialized Sep 15 01:04:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): disconnected [::ffff:192.168.1.21]:60730 Sep 15 01:05:01 localhost CRON[3100]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1) Sep 15 01:06:52 localhost systemd[1]: Starting Cleanup of Temporary Directories... Sep 15 01:06:53 localhost systemd[1]: Started Cleanup of Temporary Directories. Sep 15 01:06:53 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): discovery from [::ffff:192.168.1.21]:58712 Sep 15 01:06:53 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): discovery from [::ffff:192.168.1.21]:58712 Sep 15 01:06:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): connection from [::ffff:192.168.1.21]:60743 Sep 15 01:06:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): Found ALSA device: hw:CARD=DX7s,DEV=0 - DX7s: USB Audio Sep 15 01:06:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): begin disconnection Sep 15 01:06:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA backend uninitialized Sep 15 01:06:54 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): disconnected [::ffff:192.168.1.21]:60743 Sep 15 01:07:02 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): discovery from [::ffff:192.168.1.21]:58540 Sep 15 01:07:02 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): discovery from [::ffff:192.168.1.21]:58540 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): connection from [::ffff:192.168.1.21]:60748 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): Found ALSA device: hw:CARD=DX7s,DEV=0 - DX7s: USB Audio Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): begin disconnection Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA backend uninitialized Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): disconnected [::ffff:192.168.1.21]:60748 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): connection from [::ffff:192.168.1.21]:60750 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA backend uninitialized Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): Set channels: 2 (2) Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA device: hw:CARD=DX7s,DEV=0 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA access mode: 3 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format: S32_LE Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM bits: 32 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM physical width: 32 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM rates: 44100 - 768000 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA DSD not supported Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 44100 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 48000 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 88200 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 96000 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 176400 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 192000 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 352800 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 384000 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 705600 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA rate available: 768000 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA backend initialized Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 44100/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 48000/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 88200/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 96000/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 176400/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 192000/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 352800/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 384000/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 705600/32/2 Sep 15 01:07:03 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA PCM format available: 768000/32/2 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): start 384000/32/2 [pcm] Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): Set channels: 2 (2) Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): Set sampling rate: 384000 (384000) Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA engine starting... Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA channels: 2 - 2 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA active channels: 2 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA number of periods: 4 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA period times: 125 - 85334 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA period sizes: 48 - 32768 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA period time: 85333 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA period size: 32768 Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA engine started at: 384000 (384000) Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): ALSA engine running... Sep 15 01:07:11 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): enter streaming mode Sep 15 01:07:13 localhost kernel: [ 926.604350] NOHZ: local_softirq_pending 80 Sep 15 01:07:45 localhost kernel: [ 958.240038] NOHZ: local_softirq_pending 80 Sep 15 01:08:39 localhost networkaudiod[2646]: [/usr/sbin/networkaudiod] (2646): leave streaming mode Jonathan Custom room treatments for headphone users. Link to comment
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now