elk-pi VS meyda

Just found Elk Audio OS. Looks exciting, but I'm struggling to understand exactly what it is and how it might be useful. Anyone using it? https://elk.audio/

That might not matter too much for you - if not then you're set. But if it does, using small buffers is hard with Linux (and non-realtime OSes), since the kernel has other things to balance, so you can occasionally miss your deadlines and have audio glitches if the buffers are too small. These guys offer a linux distro that's been well tuned for audio processing, as well as an engine that makes it easy to drop in your effects algorithm without having to deal with hardware support and making that engine: https://elk.audio/

There's https://elk.audio/

Overall there are JUCE embedded support.

If you need more bare bones there are some DSP only resources. Not sure if I saw there the RtAudio which is also very minimal -

I’ve run JUCE apps on embedded linux, a Raspberry Pi running maybe Elk Audio or Patchbox OS might be a good bet

Sounds like a job for web workers. Do you have any examples? I'd love to check them out. I've seen some sequencers but never a full-blown DAW attempt. I've been toying with a couple browser-based, realtime audio ML ideas lately (mostly porting some models to Tensorflow.js), so my interest is piqued.

As far as libraries go for analysis, the only solid option I've found so far is Meyda[0]. I was drawn to it mostly because it closely maps to librosa[1], and it seems fairly mature. Does anyone have any others that may come in handy for this kind of work? This is just free-time tinkering for me. I'm completely new to the space.

[0]: https://meyda.js.org/

It was pretty hacky really. There's a javascript library called Meyda that does audio processing and their front page has this visualization, i was just careful in my cropping. :). I should really give them credit in the description.

I recently published a beta build of Meyda to the npm registry, with the intention of having one of our longest running users test it out to make sure it worked in their project. I hadn't done a manual release in a long time, since we use semantic-release, so I skimmed the output of npm publish --help, and figured out what command I would run. I set the version field of package.json to 5.1.7-beta.0, as instructed built the bundle, ran our test suite, and ran npm publish . --dry-run, to verify that the manifest of files that would be published was correct. It was correct, and so I ran

If you're using Meyda to analyze audio that you load in this way, you will need to make sure that the sample rate of the audio matches the sample rate that Meyda is set to use. Otherwise you'll end up with audio features that are incorrect, and based on a skewed frequency scale. You can either match the Meyda sample rate to the wav sample rate, or you can resample the audio to fit a standard sample rate (i.e. 44,100hz, or 48,000hz). Resampling audio is a complicated topic beyond the scope of this article, but if you have trouble finding information online, let me know and I may find time to write an article.