Hi @booss

Really appreciate having an alternate option to m8c, and your additional menu items for controls, etc. I have an issue rm8 for both my laptop (amd64) and handheld (Odroid Go Advanced - aarch64) where pulseaudio creates a 2s delay on the audio - see requested latency for pulseaudio output.

1 source output(s) available.
    index: 0
	driver: <protocol-native.c>
	flags: DONT_MOVE 
	state: RUNNING
	source: 1 <alsa_input.usb-DirtyWave_M8_11417570-02.analog-stereo>
	volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% / 0.00 dB
	        balance 0.00
	muted: no
	current latency: 0.00 ms
	requested latency: 2000.00 ms
	sample spec: s16le 2ch 44100Hz
	channel map: front-left,front-right
	             Stereo
	resample method: (null)
	owner module: 9
	client: 3 <rm8-audio>
	properties:
		media.name = "Simple DirectMedia Layer"
		application.name = "rm8-audio"
		native-protocol.peer = "UNIX socket client"
		native-protocol.version = "33"
		application.process.id = "2523"
		application.process.user = "ark"
		application.process.host = "rgb10"
		application.process.binary = "rm8-audio"
		application.language = "C"
		application.process.machine_id = "82b7b768bc7742e6a5f379cd3c48dd47"
		module-stream-restore.id = "source-output-by-application-name:rm8-audio"

I was able to get around this by commenting out anything relating to audio from the src and just using jackd or pulseaudio loopback instead which has no delay, but would love to see it working through your app. How can I help?

Caleb

This should resolve #3 on more devices.

On mac x86_64, I still don't get sound, but it does start and seem to work (which it didn't before.)

I can open quicktime player, and do an audio-recording (no need to record, just turn up monitor volume) and get output though, so it's at same feature-level as m8c on mac.

@booss I know you don't use rm8 as much, now that you have a real M8. I'd be happy to take over (share) maintaining it. rm8 is great, and is closer to working with audio on most platforms than m8c. I'd love to just get some PRs in around improving basic functionality, and compatibility, but otherwise keep it the same.

This will build several pre-compiled releases in Github CI (#6)

The idea is that it's triggered with a semver git-tag (like v0.0.1) but we can set it up some other way, if this is not convenient. For testing, I used dummy tags like vtest24. If you don't want to use semver, I think any tag could also trigger it, with a small change (so you can just tag your releases and it will generate a release for it.)

• Here is an example build
• Here is what that looks like, as a release.

Currently, it can build:

• linux (x86-64, arm64, arm32)
• mac (x86-64)
• windows (x86-64)

It will add a new tagged release with assets so users can download the built runtime for their platform (including some config examples and the README.)

This should have pi and handheld Anberinic devices (like this) covered, as well as windows, and older macs. I need to do more testing. I have a Mac M1, and an Intel-mac, and a few different platforms for linux, so I will try to get those all verified (and windows, in a vmachine.)

Linux cross-building is very slow, since it builds in qemu. I think we could improve this using rust's cross-building stuff, but it seems a bit tricky with SDL2/libudev native deps.

Main build-things left to do is mac arm64 (for M1/M2 apple silicone) and I can't seem to get it, but I made an issue over here asking for help. There is also currently an error trying to cross-build on linux spurious network error - Value too large for defined data type; class=Os (2) which I need to look into. It just started doing this, so maybe I need to adjust something in the docker-build.

I think for mac/linux, users will probly also need instructions for installing SDL, since it's dynamically-linked. For windows, I include a SDL2.dll in build.

# mac
brew install sdl2

# ubuntu/debian/etc
sudo apt update
sudo apt install libsdl2 libudev

# fedora/etc
sudo dnf install SDL2

# arch linux
sudo pacman -S sdl2

It would be handy to have a few Github action automatic release-builds for linux/arm (for use on pi and anbernic devices) and mac/win. It has so few system-deps (sdl2 is the only one one) it would make it very easy to install on just about everything (maybe just tell users to install SDL2.)

I'd be happy to PR for it. Generally, I set this up to happen on tag (I like semver, like v*.*.*) so to make a release you just tag & push. Alternately, non-tag/releases work too, if you set the "asset output" for the build, but it's a bit less convenient, since you have to dig through the builds to find the release.

I don't have a great deal of experience with rust cross-building, but I have a few C-based projects that do this kid of thing, and can try to figure it out. It seems much simpler with rust.

What targets should I set it up for? I am thinking these would be most useful:

• linux arm32
• linux arm64
• linux amd64
• windows amd64
• mac amd64
• mac arm64

For mac, normally I would suggest a "universal build" since it has good built-in support for "fat binaries", but I will need to research how to do it, a bit. Using cmake with C, I can do this on github action with a few env-vars, but I think it is different in rust. I found this which might be helpful. Basically, it seems like you build the 2 binaries separately, then use lipo to merge them into a fat-binary. Maybe a first step could be the basic targets that can be built with just cargo, then I can work on trying to get a universal binary.

Running on Rpi3B, running with and then without pulseaudio installed, I could never completely eliminate small pops and clicks every few seconds. Disabled wifi and bluetooth, same issue. With ALSA only (pulseaudio removed) I was getting ALSA 8545 buffer underrun errors. Increasing the -smp buffer setting didn't help, maybe made if worse at settings above 256.

I then used Jack to route the USB audio from the m8 to my soundcard according to https://github.com/laamaa/m8c/blob/main/AUDIOGUIDE.md and then run rm8 -noaudio In this case the audio runs clean with no pops.

I may have messed something up on my system, I am also having some low voltage issues, but audio is still clean with Jack.

Fresh install on Rpi 3b using latest Raspian OS Need to install Rust, (duh) and sudo apt-get install libudev-dev sudo apt install libsdl2-dev

Some compile warnings but builds after packages installed

Hello - I'm trying the app on my Win desktop to connect to M8 and I get an error about "No M8 audio device found". The app only runs if I specify -noaudio option, but then I lose ability to get audio through the desktop. If it matters, the M8 is connected via original USB cable, so that shouldn't be affecting it. Thanks.