I brought up the aircraft carrier in a conversation with a Frenchman while our daughters played in his apartment off the Champs-Élysées some months ago. He said: "Yes, it was very expensive and we don't take it anywhere." ; )
IIRC the operational plan involved having two of those as projection is much more limited (and notably cannot be continuous due to docked maintenance periods) with only one.
I use S3 with the DEEP_ARCHIVE storage class for disaster recovery. Costs go up if you have many thousands of files so careful there. Hopefully will never need to access the objects and it's the cheapest I could find.
Great project! I've been using mididings for similar purposes. Main draw of this for me is customization in go instead of cpp. How would you say it compares otherwise?
Hi, Thanks for your response. I have to admit I was unaware of mididings even
though I did a search for similar projects last year. Somehow mididings did not
pop up. Looking at their website it does have a lot of overlap with Pigiron.
The Harmonizer and scenes features look nice though I doubt I would use them
myself. I like the idea of being able to execute arbitrary shell commands,
that opens up a lot of possibilities.
Pigiron is actually an evolution of a previous (unreleased) project I wrote years
ago in Java. It had a similar structure of linked nodes, each specialized for a
specific task. One of the things it had that Pigiron so far does not, are sysex
editors, specifically for the DX7 and Oberheim Matrix synths. At some point
I'll probably write a client app for the DX7 and maybe a more general sysex
editor. Sadly the Oberheim has died. Another idea I want to investigate is
integrating basic synthesis blocks that can be linked directly into the Pigiron
tree. I want to keep it relatively simple though.
