Search results

E.g. https://www.parkytowers.me.uk/thin/hp/t630/ refurbished costs about 50EUR + shipping on ebay e.g. https://www.ebay.com/itm/185756340161 . The wifi M.2 PCI-e slot can be used for other PCI-e boards, like http://www.miccet.se/2023/01/11/extra-nic-on-the-hp-thin-client-t630/ . I believe (not...

I was thinking about PCI-e controllers which would allow building PCI-e soundcard hats, to integrate with the RPi format. For standard PCIe cards the x86 world offers countless options, with decent price comparable to RPi (refurbished thin clients), reasonable consumption, original quality power...

Recently I played with Radxa Rock 3 with RK3568, both 8ch TDM (48kHz) and 8ch 4x I2S_DO (up to 384kHz) work fine. If you are not dependent on some RPi-only project like moode (which hard-codes configuration hacks specifically for RPi) and debian 12 with the latest kernel would suffice, it's viable.

The HDMI block of RPi is in the proprietary VideoCore block of the Broadcom SoC, unrelated to I2S. 8ch 24bit HDMI on RPi4 should work, the HW supports it, the drivers do support it as well, e.g. https://github.com/raspberrypi/linux/issues/4204 . I have never tested as I have no 8ch HDMI receiver.

We will see parameters of the new Pi. No specs of their RP1 southbridge have been released, we do not know if only 2ch I2S or 8ch like basically all other arm SBCs. My guess is 2ch as so far. I am afraid the 16nm process will not allow full long-run power without active cooling. What...

IIUC you are looking for a splitter to power your RPi while using the USB-C as a gadget (that's the subject of this topic). If so, the splitter would have to present the device side of the USB connection.

That USB3 (i.e. data) connector is female (i.e. host side). You need a device side connector, to be plugged into a host.

Some time ago I played with USB-IP, it seemed to work OK over ethernet. Even the USB-IP client for windows worked (when made to work). Wifi is a very different beast, randomly hitting larger pings, much less reliable, much higher latencies and jitter. This is a nice paper which shows the...

Yes, IME very often the problem is in the descriptors which do not fit the picky requirements of the closed-source black-box drivers (which are almost never properly documented, making it tedious trial/error). Maybe iOS logs could tell why the driver rejects the device...

I wonder what changed in IOS 17 support for the UAC2 protocol, any details?

@dualazmak: While I just skimmed your very informative posts (but too long for me to read in detail, sorry)... You have two USB audio devices. One is async (Okto using XMOS), the other I do not know (I could not find any relevant info for the Korg). Each of the devices consumes samples at its...

Well, we do not know what the acceptable latencies are in this particular case. IIUC Ableton does not support wasapi, that means FlexASIO between Ableton (ASIO) and the windows audio subsystem (wasapi shared). That means extra buffers (= latency) in FlexASIO + what is latency of the windows...

IMO it's important to analyze the details of what goes on in your computer when playing audio. I find Etienne's https://github.com/dechamps/FlexASIO/blob/master/BACKENDS.md#flexasio-backends one of the best writeups on windows audio internals. First very few audio devices support hardware...

This is an example of systemd-style integration of udev with the linux usb gadget https://www.collabora.com/news-and-blog/blog/2019/02/18/modern-usb-gadget-on-linux-and-how-to-integrate-it-with-systemd-part-1/ - upon appearance of the device the gadget configuration gets called. You should be...

Maybe using the SYSTEMD_WANTS property would be more systemd-isch than the hack with at. It is mentioned also in the manpage and commonly used for running units when a device appears. Also telling systemd to start a unit directly would be an alternative, as in...

Thanks. IIUC, none of the boards populate the USB-C port of RPi4, only HDMIs. The USB-C data pins are not available through the RPi GPIO header. For the gadget mode the USB-C connector of RPi must be used.

@stenmag: Congrats to solving the issue. Please post the cases involved so that people can see. Thanks.

IIUC MiniDSP Flex uses Sharc DSP chip. This DSP always resamples asynchronously the incoming signal to its internal 96kHz sample clock, e.g. https://www.minidsp.com/forum/minidsp-for-newbies/20859-can-i-bypass-the-dac-oversamplingfilter That would be the reason why every run the resampled...

If your USB host (any OS, not only linux) can detect other USB devices, it should detect your gadget. That's easy to check with any other USB device. Best to use the same working cable then - they trick me surprisingly often. But your RPi must be configured correctly to become a USB device.

IMO it's better to start troubleshooting with the g_audio module as it's much easier to configure than the composite configfs. Of course dwc must be switched to the gadget mode in config.txt. I always power rpi4 through the GPIO pins, have no experience with USB-C power in the gadget mode.