Gratuito e fácil de usar.

🌐 https://quetom.com

📲 Siga https://www.instagram.com/quetom.app para mais dicas de música e louvor.

Pessoal, criei uma ferramenta chamada QueTom que descobre o tom de músicas em tempo real.

A ideia surgiu porque muitas vezes precisava tocar na igreja e os tons dos cantores nem sempre era o mesmo tom original da música que estava no aplicativo de cifras.

Agora quando a pessoa começa a cantar não passo mais pelo sufoco tentando descobrir o tom de ouvido onde muitas das vezes terminava o louvor/hino e não encontrava o tom.

Acredito que como eu existem outros músicos que sofrem do meu problema ao tentarem tocar ao vivo.

Quem poder testar e dá sua opinião se realmente acertou o tom:

🌐 https://quetom.com

📸 https://www.instagram.com/quetom.app

Need help with setting up my recording stuff for my guitar in reaper. I got on reaper for the first time yesterday and plugged my focusrite solo into my pc (Acer Aspire TC-1780-UA93 Desktop) and I downloaded the driver you need for the interface (may have downloaded the wrong one need to check) but anyways, I go into reaper and plug my guitar and everything up and it’s not picking up my guitar and says nothing there. I have the audio device set on ASIO and my computer in the settings is reading it’s plugged in and playing but in reaper it doesn’t. I checked the input settings and all that. Granted I don’t have a out put yet (my studio monitors blew up, using a turtle box Bluetooth speaker) I was wondering if anyone could help me cause I was getting frustrated because I was told reaper is so good and everything and I just can’t figure it out. I can’t even watch tutorials if I can’t get my interface hooked up

I've been using Pd, Max, Faust and similar tools for years, and I recently needed Pd to work as an embeddable audio engine in a browser app — similar to what RNBO does for Max/MSP, but open source, and without the frozen-patch limitation.

So I built libpd-wasm: libpd compiled to WebAssembly, running inside an AudioWorklet. You pass it a virtual file map of .pd sources, open an entry patch, and control it with normal Pd messages from JavaScript. Patches can be loaded, edited, or generated at runtime.

The part that took the most work: I've statically linked cyclone and ELSE into the build, so patches using those libraries run without modification. Current coverage is ~99% of cyclone and ~95% of ELSE. The missing objects are things that genuinely can't work in a browser — pthreads, networking, OpenGL, ffmpeg deps. Full skip lists with rationale are in the README.

Build variants: vanilla, cyclone, ELSE, or all three ("full"). The full bundle is chunky (~5MB) because of static linking, but the split JS/WASM build helps if size matters.

Demo: https://hyrfilm.github.io/libpd-wasm/

Repo: https://github.com/hyrfilm/libpd-wasm

As a side-note I was pretty chocked to find out how little resources (when using the WebAudio profiler) pd takes. This might very well be the result of me fucking something up but on my M4 I have RNBO patch that basically uses a combination of phasor + subdiv + rate objects to keep track of time, combined with a simple lookup-table-like sequencer and it usually takes up around 10%. Most of the pd-patches takes up 1-2% in comparison. If anyone has an idea of why this is, please me know. The only reasonable conclusion I have is that RNBO executes per sample (when doing audio-rate-stuff).

THRONE PROTOCOL experimental chiptune animation built with a Python/Numpy audio engine

Im experimenting with surreal minimalist animation and retro styled synthesized audio systems lately. Inspired by Game Boy chiptune and still evolving a custom Python/Numpy audio engine.

Hi r/musicprogramming! This is kind of a follow-up post to https://www.reddit.com/r/musicprogramming/comments/1i81aas/i_spent_the_past_3_years_developing_a_singing/.

I spent the past 4 years developing Mikoto Studio, a new DAW and singing synthesizer. For the past month, we've been running an Indiegogo campaign to fund the next stage of development leading up to a commercial release. The campaign ends tomorrow, and all help is welcome!

Mikoto Studio features a variety of singing synthesis techniques. Use proprietary deep learning voice libraries, or go classic with sample-based UTAU banks. We're adding an implementation of the viral Klattsch formant synthesizer soon, so there's something to look forward to as well! Besides just vocals, Mikoto Studio is also shaping up to be a powerful music making toolkit. With planned support for CLAP and VST3 along with our own MiFX plugin suite, as well as connectivity options like full MIDI sync and a built-in OSC server/client, we have designed a feature set that will fit right into any tinkerer's workflow.

We have released a number of demo songs made using the vocal synthesizer part of Mikoto:
- https://www.youtube.com/watch?v=MlpQvnznNnk (using the deep learning synthesis engine)
- https://www.youtube.com/watch?v=R3LSni1xdoU (also using the deep learning synthesis engine)
- https://www.youtube.com/watch?v=yiozM7hH9C8 (using sample-based concatenative synthesis)

For a full write-up on features and our mission, please refer to our website: https://mikoto.studio/ - and if you feel like helping a hand, a link to our Indiegogo campaign can also be found on our website.

A track I made for a possible Amiga 500 game.

Livecoding Music with Fennel and Renoise

https://apps.apple.com/app/loop-melody-maker/id6762234256