Version 0.14 has arrived, with grid support. Update to this new version through Maiden at http://norns.local. If you installed the script through the project manager (recommended) then find Loud Numbers in the list and hit the “update” button. Easy. If you installed it manually (with the ;install command), then delete your Loud Numbers folder (save any csv data you want to save first) and reinstall through the project manager.
Changelog
Get a visualization of your data by plugging in a grid
Should support grids of any size and hot-plugging, but let me know if you run into difficulties. The Norns display will match the number of columns on any grid plugged in.
I haven’t tested on non-Monome grids. Would love user reports on whether they work.
Todo
Figure out why the ordering of the columns in the CSV file is not preserved on load (contributions welcome!)
Ask and ye shall receive! I’ve just pushed an update that should add basic MIDI support. It should play notes, and send start/stop signals when you press play and stop. I don’t have a whole lot of ability to test MIDI so I would appreciate any bug reports and feature requests you have. I won’t increment the version number until we’ve ironed everything out
Update through Maiden and you should get the new version.
Okay, no-one is telling me things are broken, so I’m officially incrementing the version number. Welcome to v0.15, which comes with full(?) MIDI support. Thanks for @swhic for prompting me to make this happen!
As usual, update to this new version through Maiden at http://norns.local. If you installed the script through the project manager (recommended) then find Loud Numbers in the list and hit the “update” button. Easy. If you installed it manually (with the ;install command), then delete your Loud Numbers folder (save any csv data you want to save first) and reinstall through the project manager.
Changelog
Loud Numbers will send MIDI notes to the first connected MIDI device in the list. It should also send start and stop signals when starting and stopping.
You can change which MIDI channel it uses in the parameters, as well as adjusting the length of the MIDI note.
You can now also adjust the length of Crow notes in the parameters too, which were previously fixed. Big thanks to @eigen and @zbs for helping me fix a troublesome bug on that.
Still todo
Figure out why the ordering of the columns in the CSV file is not preserved on load.
I was inspired to check this out by your other post. Really happy that I did, I have a ready source of data created by my blood glucose monitor, a freestyle libre 2 sending data to nightscout which is accessible as JSON.
I am currently listening to the 8508 entries I have for January this year. Happily it’s mostly very similar notes.
The fact that it was naturally drone like got me thinking about the possibility of using another engine or exposing more of the engine parameters to play into that. Really low bmp and long attack/decay.
I also thought about the possibility of selecting multiple columns of data to play simultaneous with polyphony.
I like the narrative juxtaposition that would be possible with time synced data sets. In my case that might be bassline of blood glucose, lead of pulse rate.
Wow, what a great dataset! Strong emotional resonance with that one, for sure.
You’ve definitely identified some features I’d love to add to the script. If you’re handy with script coding, then I’d absolutely welcome a pull request (or even a fork aimed at more advanced users). You might also like to check out my sonification VCV Rack module, which was just submitted to the official VCV library today so should appear there before too long - might be easier to try out some of the polyphony/drone ideas there.
The Loud Numbers script has been updated to version 0.16!
Changelog:
Switched graphics to use @markeats’ lib.Graph library, rather than my hand-coded bar chart thing.
Support for custom csv separators - Europeans rejoice. Change line 31 (the sep variable) if you’re not using comma-separated values.
File and column names are now alphabetically ordered in menus, giving more consistency than the random ordering that came before. If you want a particular file or column to load automatically when the script is loaded, add an underscore (_) to the beginning of the file or column name.
As usual, update to this new version through Maiden at http://norns.local. If you installed the script through the project manager (recommended) then find Loud Numbers in the list and hit the “update” button. If you installed it manually (with the ;install command), then delete your Loud Numbers folder (save any csv data you want to save first) and reinstall through the project manager.
I think the problem here is that OWID sometimes provides long data, but loudnumbers expects wide data. It just means it needs a little reformatting in a spreadsheet first, using a pivot table.
I’ve gone ahead and done it for you in this spreadsheet - the first tab is long, the second one is wide. You should be able to download a csv of the wide version in the file menu, but let me know if you have any issues and I’ll be happy to help
I’ve pushed a small v0.17 update, which moves the storage for CSV files from the we/code/loudnumbers_norns/data folder to the we/data/loudnumbers_norns/csv folder. You’ll need to run the script once after updating to move the default _temperatures.csv file to its new home.
This has the big benefit of you not losing your CSV files when you update the script! So that’s nice.
Big thanks to @infinitedigits for helping me out with this at the Stockholm Habitus workshop!
It also adds some beta capabilities around sending MIDI CC values too - try that out and let me know if you hit any bugs.
Just FYI, the ‘new’ csv folder was empty for me on a fresh install via maiden (I ran the script multiple times and restarted as it wouldn’t load anything).
Everything was fine after moving the csv manually.
Huh. Interesting. Thanks for the bug report! Did you get any error in Maiden at all? It should create the folder and move the file automatically the first time you run the script.
@92pabrew I’ve pushed a small update that should fix the issue. Could you remove all traces of the script from your Norns (in both code and data) and do a fresh install and see if it behaves itself now?
