melatonin_audio_sparklines
juce-toys
Our great sponsors
| melatonin_audio_sparklines | juce-toys | |
|---|---|---|
| 2 | 1 | |
| 90 | 108 | |
| - | - | |
| 3.6 | 0.0 | |
| 8 months ago | about 1 year ago | |
| Python | HTML | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
melatonin_audio_sparklines
-
Audio Sparklines
You found the Achilles' heel of my project! I don't mind the fonts being different sizes or not monospaced, but the fact that there's a difference in height in the font rendering between ⎺ and ‾ on different platforms is a bummer. I have a flag in the C++ implementation so they can still be rendered "correctly" in IDEs like Xcode [1].
I felt doomed to Unicode in this case because of the number of places I wanted them to show up (CLion lldb integration, GitHub actions output, terminal). I would have loved to actually render graphics! I actually never thought about how they would render on a blog article, I wouldn't generally wouldn't use them for blogging...
1. https://github.com/sudara/melatonin_audio_sparklines/blob/ma...
-
Using ASCII waveforms to test real-time audio code
Nice! I became obsessed with rendering sparkline representations of chunks of audio for the same reason: to inspect failures when writing tests / refactoring. https://github.com/sudara/melatonin_audio_sparklines
juce-toys
-
Audio Sparklines
STK is cool! I'm building a synth plugin, so that's why I'm in JUCE...
I want to hear more about the remote visualizer! I was using Jim Credland's buffer debugger (again, JUCE)[1]. It pops open a window, making it fairly easy to visualize buffers with one caveat: you actually have to tell it about the buffers you care about visualizing and then recompile. This means debugging can't really be on the fly (unless you only always care about the same buffer or two).
The other issue I ran into was viewing audio from my tests. I'd love to hear about the shared memory approach — real waveforms would be ideal!
1. https://github.com/jcredland/juce-toys/blob/master/jcf_debug...
What are some alternatives?
FFmpeg-SIXEL - Experimental fork git://source.ffmpeg.org/ffmpeg.git
stk - The Synthesis ToolKit in C++ (STK) is a set of open source audio signal processing and algorithmic synthesis classes written in the C++ programming language.
sixel-tmux - sixel-tmux is a fork of tmux, with just one goal: having the most reliable support of graphics
visual_debugger - debug data over a shared memory connection to an OpenGL ImGUI window
Gin - A few extras for juce
SampledSignals.jl - Core types for regularly-sampled multichannel signals like Audio, RADAR and Software-Defined Radio
notcurses - blingful character graphics/TUI library. definitely not curses.
FYampaSynth - Modular Synthesizer Programming in F#