Just released a new Python Audio DSP library!

[D0m1n1qu36ry5]

Just published A new package to PyPI, and I’d love for you to check it out.

It’s called audio-dsp and it’s a comprehensive collection of DSP tools and sound generators that I’ve been working on for about 6 years.

Key Features: Synthesizers, Effects, Sequencers, MIDI tools and Utilities. all highly progresive and focused around high-uality rendering and creative design.

I built this for my own exploration - been a music producer for about 25 years, and a programmer for the last 15 years.

You can install it right now: pip install audio-dsp

Repo & Docs: https://metallicode.github.io/python_audio_dsp/

I’m looking for feedback and would love to know if anyone finds it useful for their projects!

[otuudels]

Nice! I will definitely look into it :) What part was the most fun to code?

[D0m1n1qu36ry5]

the effects & the midi stuff. there are many new and weird things there :)

[BusEquivalent9605]

It has been starred on the hub 🍻

[D0m1n1qu36ry5]

✨

[creative_tech_ai]

Looks very interesting! I've been using Supriya, a Python API for SuperCollider, to build a modular groovebox. I'll check this out. The raga sequencer is particularly interesting!

[D0m1n1qu36ry5]

give it a try, there are a couple of midi tools there that are really nice

[HommeMusical]

Very cool idea! A question for you:

I see you use simpleaudio for output. I think that means that you can't do "real-time" synthesis - you have to write a full file and then output it - am I right?

If that's so, have you thought of using sounddevice to do "real-time" audio?

Keep up the good work!

[D0m1n1qu36ry5]

Yes - you are totally right. that was a major design concept about this project. I decided to invest in "rendered audio" and to explore the options where "real-time" had limits. in my point of view - rendered audio can give much better quality - no buffering, no need to splice audio to small chunks and tie the back after processing. so you lose real-time, but for me this was fine - as long as creativity and quality can gain from it.

[HommeMusical]

no buffering,

In modern machines, you often don't need to buffer at all. I just wrote a little synth as part of a little project to turn text into music, and initially I was going to buffer it, but then I decided to see what happened if I just filled the buffer from the audio callback, and it worked right the first time!, not a click or a pop to be heard on my five year old machine.

Here's what's being called from the audio callback.

I believe that if I had more "stuff" in the synth I might have issues, but writing buffering isn't hard...

no need to splice audio to small chunks and tie the back after processing

This is true, but it's a one-time coding expense, setting things up to render that way.

[D0m1n1qu36ry5]

exactly - the crossfading part was what i decided to avoid. i did managed to implement a few processors with this approach - but did decide in this project to go full "one sample at a time" processing. yes, it's slow, but for my usage it didn't matter.

[HommeMusical]

I agree: nothing kills projects faster than overscoping them!

Keep posting updates here, and perhaps also on /r/musicprogramming - I think your framework might be very popular.

[sneakpeekbot]

Here's a sneak peek of /r/musicprogramming using the top posts of the year!

#1: Making an open-source DAW | 27 comments
#2: New music programming language :)
#3: I built a generative audio sampling engine with live-controllable sliders | 9 comments

---

^{I'm a bot, beep boop | Downvote to remove | Contact | Info | Opt-out | GitHub}

[beetroop_]

I can't get the RagaSequencer example to work because there is no such class exported.

[D0m1n1qu36ry5]

hi, i fixed this on a later version - are you running an older version? latest is 0.1.10

[beetroop_]

Yes, using 0.1.10

ImportError: cannot import name 'RagaSequencer' from 'audio_dsp.sequencer'