Roadmap to 1.0

[melody-rs]

• Fix documentation issues
  • Fix doc warnings
  • Fix doc links
  • Fix weird formatting
• Add support for FMOD 2.0.3
• More platform support (MacOS, ARM)
  • wasm-bindgen support Not planned
  • HTML5 with wasm32-unknown-unknown
  • HTML5 with wasm32-unknown-emscripten
  • MacOS
  • ARM
• Go over all uses of Utf8CStr(ing)::from_utf8_unchecked and friends
• Better userdata
  • Investigate setting userdata to a *mut T instead of *mut c_void*
• Write tests
• Better DSP system
  • Figure out DSP data parameter types
  • Provide DSP data parameter types
  • Data parameter validation
• Custom filesystem
• Anything missing from COVERAGE.md

[caspark]

I investigated 5 Rust FMOD wrapper crates, and this one is my favourite: it works on Linux and Windows (haven't tried MacOS), supports Studio, uses bindgen as I'd expect. And, it has a Rust-y API that hews closely to the C API but is still mostly safe, while still accepting that system creation & shutdown is rare enough that it's not really worth trying to make it safe!

I integrated it into my game last week and it's working well. So, firstly, thank you for making it!

Secondly, are you still using it in tandem with your game as you wrote in the readme, and hence expect to cut new releases for crates.io as they make sense? (Or have you moved on to other things? No judgement if so)

[melody-rs]

Thank you!! 💟

It's kinda complicated. I had 2 projects that were using this crate- wormhole and libfmod.
I ended up canning wormhole a while ago, and I'm not actively using libfmod.
It's meant to replace all the audio code for another project, and for various reasons that hasn't come to fruition yet. libfmod is kinda a mess right now, there's lots of weird deadlocks and I'm pretty sure I'm doing an undefined behavior somewhere because the Ruby GC keeps segfaulting. Instead of focusing on rewriting out all the audio code, I've been focusing on finishing a massive content update we've been working on for a few years. That effort ended up turning into the exact thing I was trying to avoid, and I ended up rewriting a large part of the codebase. Twice.
I am starting to work on a bevy game with some friends, if that goes anywhere we'd 100% be using this crate!!

Despite all that I do want to keep this project up to date and publish new releases to crates.io!