I think this is the most fun I’ve ever seen people have playing classical music
I think this is the most fun I’ve ever seen people have playing classical music
Experimenting with some computational musicology on a vast corpus of traditional music compiled by a friend. Extrapolating from the last few hours, I anticipate the first complete analysis will take 2.5 days to complete on my macbook. Plenty of time to research how to build a raspberry pi parallel computing cluster…
I have been waiting for this one, and it was worth it
Sacred Harp is some of the most exciting music I’ve come across in years, but, being polyphony, you need a group of people to properly enjoy it. Sometimes, once a week really isn’t enough, and an evening in front of a multitrack recorder has to suffice…
EDIT: I couldn’t resist also recording this parody version. 50% of Sacred Harp is a bunch of biblical and religious stuff but most of the rest, including 209, is pure, unadultered memento mori.
Found this nice ISMLP category page while starting research for a new project, containing enough baroque French gurdy scores to keep anyone busy for a while imslp.org/wiki/Category:Scores_featuring_the_vielle
There’s all sorts of interesting stuff if you poke around a bit — for example, in Bordet’s Méthode raisonnée pour apprendre la musique there’s a summary of the hurdy gurdy which suggests that extended keyboards beyond the usual two-octaves-minus-high-F# existed, but were “extraordinaire, et peu usité:”
After missing the crowdfunding campaign, I was happy to finally be able to buy a copy of Tobie Miller’s excellent Bach solo hurdy gurdy CD at Chateau d’Ars last week. I couldn’t find any official album artwork on the web yet, so here is a quick scan of the cover, for anyone else who got a copy already.
It is possible, if somewhat awkward, to update the Mooer Ocean Machine firmware on a mac using Wine and a cheap USB MIDI cable.
WARNING: if the firmware update doesn’t complete successfully, it will not permanently brick your unit (as the update can always be attempted again) but the pedal will not work until a firmware is successfully installed! Attempt at your own risk, and definitely not 10 minutes before a gig.
First, download the update from the Mooer website. The update and update software comes in a .rar archive, so you’ll need something like The Unarchiver to unpack it.
You’ll need the latest version of Wine for Mac from winehq.org. I successfully installed the firmware update using 3.0.2. Using version 2.0 consistently failed.
Power on the Ocean Machine in firmware update mode and plug in your USB MIDI cable as specified by the update readme. Check in Audio MIDI Setup that it’s working and recognised. Then, launch the updater using Wine. Select the firmware update file, then click “Update”. You might get a popup window helpfully saying “MIDI Device Error!!”. Try pressing Update again, if you’re lucky it will work. If not, open Terminal and try the following solution.
The problem with (old versions of) Windows, Wine and this updater program is that they rely on the “MIDI device mapper” utility to decide which MIDI device to use. This would be fine, but under Wine for Mac there’s no easy way of seeing a list of devices or configuring which device to use.
It is possible to change the default MIDI device used by the MIDI mapper, by creating a text file with the following code:
REGEDIT4 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Multimedia\MIDIMap] "CurrentInstrument"="#1"
#0 is the default device, so start at #1.
I saved mine in MMap.ini. Then, run the following command:
wine regedit MMap.ini
and re-open the update app. If after two presses of Update you still get “MIDI Device Error!!”, then quit the updater, change #1 to #2, run
wine regedit MMap.ini and try again. Repeat until successful. Yes, the update process sucks.
Recently scanned some album covers I couldn’t find on the web. Here they are, to save the work for any other fans of similarly obscure music:
Tanz', Duo Haertel Wascher
Eetu Klemetti - Kampi-Klemetin nuottikirja
Gregory Jolivet - Alt'o solo
Marylin Tucker & Paul Wilson - On The Tide
Marylin Tucker & Paul Wilson and friends - Dead Maid’s Land
The Cornwall Songwriters - The Cry of Tin
I built an Ambika to join my family of Walnut Mutables!
I messed up the LED holes in this one, but the laser engraved front panel graphics and text came out really well. The back panel is acrylic so I can admire my electronics handiwork and Olivier’s amazing design any time.
I took the opportunity to give my Shruthi a knob upgrade, too.
FREE: ATmega1284p TQFN to DIP adapter boards available for Shruthi/Ambika/open source work!
TL, dr; I had a batch of adapter boards for the ATmega1284P (a pin-compatible upgrade to the ATmega644 used in the Mutable Instruments Shruthi and Ambika open source synthesizers) built which enable an SMD version of the chip to be inserted into the DIP socket on the MI boards. I now have loads of them and am giving these boards away for free to people who want to work on open source Shruthi/Ambika firmware! I’m also happy to assemble them for a few euros.
Why the ATmega1284P?
This chip is a drop-in, pin-compatible upgrade to the ATmega644 used in the original Ambika and Shruthi designs, which provides twice the flash available in the 644p. This is particularly important for Ambika firmware development because the stock firmware, and YAM, uses up almost all the space.
Why not just use a DIP ATmega1284p, if they’re pin-compatible?
As previously discussed on the Mutable Instruments forums, the DIP ATmega1284p chips have a hardware fault related to the UART used for MIDI functionality which can cause the chip to crash. The SMD version of the chip apparently doesn’t have this fault, and therefore using the SMD chip via an adapter board should fix the problem and act as a drop-in replacement without having to totally redesign the synth.
I designed this board last month and now have 44 of them. I’m sending some to the developer of the excellent YAM firmware, and will experiment with a few myself, but I have no need for so many.
So, if anyone’s interested in doing firmware development work on Ambika or Shruthi, or using these for any other open-source purposes email me email@example.com your address, paypal me the shipping costs if it’s going to be more than a couple of euros, and I’ll send you some boards!
I’m also happy to assemble the boards with headers and ATmega chip for €8 + P&P per board, if anyone wants.
Disclaimer: the boards are untested, and I personally have not tested them with the shruthi hardware or firmware! I may not have time to do so but will post my experiences here when I get round to it. Point is, these boards are strictly experimental with no guarantee they actually work!
Boards in stock as of 2017-11-18: 32
Software upgrade for the MI Shruthi: Visual Sequencer
One particularly cool feature of the Shruthi is being able to set the mixer mode to seqmix and have the control values in the step sequencer determine which sound sources are active on each step. The problem with this is (or, was!) that, even with the clever binary-based approach for determining how combinations of sound sources map to hexadecimal (0-15) values, it’s incredibly hard to remember the mappings.
I spent an hour or so trawling through the synth code, and documentation for the LCD module, before managing to create a version of the software which, when the mixer operator is set to seqmix, replaces the 0-f step sequencer view with a two-line visual step sequencer, where the four lines from bottom to top represent osc2, osc1, sub and noise*
The controls for the view are exactly the same as before, i.e. pretty unintuitive, but this visualisation of the sequence data makes designing patterns way easier than before.
Here’s the software, as .hex and .syx for flashing or SYSEX dumping:
I originally wanted to have this view all on one line, by creating sixteen custom characters, one representing each combination of sound sources by a bar of pixels. Unfortunately, the HD44780 LCD module only supports eight custom characters, and the Shruthi already defines all of them. I got around this by spreading the display over two lines, reducing the number of characters needed to four, and taking advantage of the “=” default character as the “11” character, and the blank space as the “00” character. I then replaced the two decorative custom characters used on the Shruthi splash screen with single bar characters based on the “=” for “01” and “10”. Finally, in the Editor::DisplayStepSequencerPage function in editor.cc, I made a conditional block based on the state of
part.patch().osc.option (the non-intuitive location of the mixer operator), displaying the two-line visual view if it’s set to
This is the first of several UI upgrades I plan on making to the Shruthi firmware, depending on how much I can tolerate working on old embedded code in a language I barely know!
*according to the shruthi manual, osc1 and osc2 should be the other way round, but that’s how it ends up working so I accepted it as it is.
I built a Shruthi XT!
The circuit boards and panel were group bought with the Pusherman facebook group, I ordered the components from Mouser, and built the case myself out of walnut left over from a dulcimer build.
I used the BOM from the Shruthi XT build page, with Mouser’s BOM import tool. Generally everything worked fine with a couple of caveats: it auto-detected the wrong encoder (the horizontal mounting version of the same model) so I had to order another one. The MIDI sockets it found were also different, and had a metal spring on the outside which I had to remove in order to get them to fit the case.
Watch out when soldering the board-to-board connectors! I put them on the wrong way round the first time and had to remove them, which was tedious.
On my future MI builds I’m going to try using Bourns PTV09 potentiometers instead of the Alps ones on the BOM, as they cost significantly less and should be approximately the same quality.
I built the SMR4 MkII filter board but am going to upgrade to the 4 Pole Mission as soon as I get the board and components for it (along with boards for an Ambika, and a normal size Shruthi to inherit the SMR4…)
Overall I’m very impressed with the synth! It sounds great and is a lot of fun to make sounds with, although it’ll take me a little while longer to get to grips with all the features and wavetables.
If you want to get into DIY synths, but skip past the “circuit which makes bleeping sounds” straight to “professionally usable synthesizer” I’d definitely recommend building a Shruthi.
Future improvements planned: upgrade to a 4 Pole Mission filter board, make a laser-etched walnut front panel, more UI improvements in the software, maybe a built in battery and USB port for powering MIDI controllers.