SJS-ONE is an 8-bit synth that you add to an Arduino board, making it ideal for hardware and firmware tinkerers and lovers of unique monosynths. But we’ll give it bonus points for two other reasons. First, it has some really bizarre cases available as add-ons, which look a bit like punk birdhouses. (Birdhouse squats? Hot rodded bird tenant buildings?) Second, in a really clever move, they help you troubleshoot hardware issues with a Flash animation. It could make it clear even to a complete beginner how to use a multimeter (a measuring device that checks electrical connections).

The Arduino design is significant, because it makes firmware modification easy for people familiar with that environment. (We’re not letting 2012 end without some tutorials on how to do this with direct AVR programming on our MeeBlip, but I definitely see some appeal to working with Arduino.) To be clear, the way this works is, you can use the Arduino to configure patches on the SJS – so you’re not programming an Arduino synth, directly. You also do need an Arduino Uno in order to use the SJS-ONE.

The real draw to me is the quirky sonic character of the thing. On the sound side, they have a nice approach to the multi-function filter. The whole thing is, indeed, grungy and squelchy. This thing sounds completely mad, defying the typical rules of synth engineering, good behavior, and sound “fidelity.”

Here’s what the developers have to say:

SJS-ONE is a software defined 8-bit mono synthesizer with a dual (series) MAX261, switch-cap filter, which we are, as far as we know, the only ones to use at this point in a DIY-synthesizer. The filter can be programmed to work as low-pass, band-pass, high-pass, all-pass or a combination of filter modes.

The synth works as an Arduino shield, meaning that people can hack and modify the firmware at will. At the moment we have two firmwares finished, one paraphonic, supersaw synth, and one drummachine/sfx synth. More firmwares are in development!

All aspects of the synth can be fully controlled by designing your own custom firmware and we sincerely hope that people will share their firmware in the spirit of the open source and hardware that inspired us to drive this project from idea to final product.

The synthesizer has some interesting history that has certainly colored its development and ultimately its sound. The initial version was developed as an instructional workshop for a synth-event called SyltJam in 2011. The workshop idea was to show people how quickly you can design the basic hardware and software required to produce a platform for versatile audio and music generation.

As it turned out, people liked its sound so much that we decided to refine the design – which more or less involved adding peripheral components to increase configurability and improve on stability and ESD, ground-mismatch and noise sensitivity while keeping the actual design minimal and simplistic.

It’s beginnings are as humble as its production – less than 50 of these have been made available, and all parts are hand-assembled and hand-soldered, while the manual is hand-drawn and cases hand-painted.

Host board: Arduino Uno
ATmega328 16MHz
2KB RAM
32KB Flash ROM
Power supply: USB-B 5V DC
2.1mm center-positive barrel 6-12V DC
Output circuitry: 8-bit R-2R ladder DAC
Filter: MAX261
Analog output: ±2.5V signal level (external amplifier required)
Software defined parameters: Waveform
Filter modes
Filter resonance
Filter cutoff
Filter connection (LP, BP, HP)
Filter bypass
You can purchase the SJS-ONE from the DevSound Shop.

Side note on licensing:

It’s also open source hardware, licensed under a Creative Commons license, with all schematics and code available on GitHub. I should say “open source hardware” in lowercase, because unfortunately, they’ve chosen a non-commercial license. The reason the Open Source Hardware definition requires that that commercial use strings remain out of the license is simple: it’s difficult to define what constitutes a “commercial” project, making confusion for users. It also means incompatibility with projects that work with GPL licenses for software or otherwise comply with open source hardware definitions by eliminating those commercial restrictions.

I can say as a hardware maker with some skin in the game that I strongly encourage use of the ShareAlike restriction. I absolutely understand a desire not to see your work used in a closed project or in a way that doesn’t give back to your effort. But you can use clear branding requirements to avoid confusion between your work and others, and you can use ShareAlike (and software licenses like GPLv3) to ensure that people who do use or modify your project share their work, too.

(If anyone would like to see me do a longer post on licensing, I’m happy to do so!)

it’s a terrific project, though, license quibbles aside. And having some license is still much clearer than the many projects that lack one at all.

Here’s a link to that nice Flash-based troubleshooter:

http://devsound.se/files/SJS1Shooter.swf

“The troubleshooter will show you exactly what you should expect at every single point in the circuit. Note that oscilloscopes may display things slightly different or have different settings from those displayed in the troubleshooter. It may be a good idea to have someone who knows oscilloscopes around to help if you are unsure.

• Steps 1 to 4 can be performed with a multimeter (and any firmware)
• After this you have to download the troubleshooting SyltFirmware and reprogram your SJS-ONE using this sketch.
• Then, for step 5 and onward, you will need an oscilloscope! Sorry, a multimeter just won’t cut it, but if you absolutely can not gain access to an oscilloscope, consider trying something like ZelScope.”

On GitHub: https://github.com/stg/SyltJamSynth2011
Product page: http://devsound.se/products-page/sjs1

  • Pakir

    Sorry for the mix-up with the licencing!
    It’s supposed to be a ShareAlike licence… (by-nc-sa)

    Everyone is welcome to hack, modify and get inspired our stuf :D

    • retroz

      So it’s a non-commercial license?

    • Pakir

       Indeed. If you’d like to use the code or hardware for commercial purposes, just talk to us.. We’re pretty friendly people. If you’d like to use the code or hardware for non-commercial purposes, you are equally welcome to talk to us, but you’re not required to.

      From Creative Commons FAQ:
      “If someone else wants to use your work commercially and you have
      applied an NC license to your work, they must first get your permission.”

      So.. The doors aren’t closed if someone wants to make a clone of the SJS-ONE or something like that, as I said, just talk to us :)

    • STG

       Yes, what Pakir said.

      The first time we even thought about applying a license was yesterday, when we were requested to add one. Since we have yet to properly discuss the issue, BY-NC-SA seemed like a good starting point.

      Even the slightest hint of bureaucracy tends to make me cringe and as such, licensing is not something I often give much thought to – I release everything I can openly and without a license (copyright default?) because I believe sharing information is orders of magnitude more important than anything else – and that I can do without concerning myself with licenses.

      Personally I like non-NC, SA licenses, but depending on your viewpoint there can certainly be problems with these licenses.

      There are many large companies selling open source products today, adopting strategies designed to exploit peoples will to share. They have enough financial backing and market exposure to mass produce products at a much, much lower price leaving the designer with nothing more his name on a product page. This is of course only an issue when trying to make a living off designs that happens to have enough mainstream appeal to warrant mass production. Money aside and more importantly – it can really break your spirit.

      (Should you, Peter Kirn, decide to write an article regarding licensing I would really appreciate some discussion regarding this – it seems to be a growing issue for makers trying to turn their hobbies into a living, yet one rarely mentioned)

      That being said, we will take another look at the license as soon as we can get together and discuss it properly. This may lead to the NC attribute being removed.

      Until then, a solution for any license conflicts is only an email away.

    • retroz

      (just realized it’s not clear who I am from this goofy comment account – this is James from the Meeblip project).

      We used a cc-by-sa license in an attempt to comply with the Open Source Hardware Definition, and because open source isn’t really “open” if it has strings attached.

      The simple truth is that a good idea can easily be copied, improved and commercialized (I haven’t looked at your hardware design, but I’m guessing you’re using the two stages of the MAX261 cascaded to create a fourth-order Butterworth low pass filter). Most development in the music industry is simply duplicating existing work — coding ADSR envelopes, LFOs, oscillators, and so on. We’re always standing on the shoulders of those who came before us. 

      I encourage you to take the jump and remove the non-commercial restriction.

      While it’s remotely possible that a shady company might clone your product, but they they most certainly wouldn’t gain the support of the DIY community in the process, and you still have just the same ability to develop new designs in the future.

      Good luck with the SJS-ONE — I hope you sell lots and your success leads to many cool instruments in the future.

  • ruipenha

    “If anyone would like to see me do a longer post on licensing, I’m happy to do so!” – I’d really like to read that!

    • http://twitter.com/d0gbl0g d0gbl0g

      ditto!

  • Humphrey

    yes – what STG said. The problem i have with the complete open hardware specification is the danger of bigger companies selling the design for a much cheaper price. See all the trouble the midibox platform had to deal with ;)

  • Ben

    Can the SJS-One be used with an Arduino Duemilanove (ATmega328) board?
    Without having dug very far, I get the impression that the main
    difference between the UNO and the Duemilanove lies in the USB-serial
    chip used.

    • Pakir

       It’s been tested successfully with Uno and Diecimile.
      It hasn’t been tested with Duemilanove, but it should work.

  • WinstonSmith2012

    This synth sounds perfect for the reproduction of classic game soundtracks.