Forum Replies Created

Viewing 15 posts - 1 through 15 (of 23 total)
  • Author
  • in reply to: For easier patching. . . . #4165


    Brilliant idea!

    in reply to: Nanosynth/Teensy idea #3796


    Well my preliminary googling indicates that the Teensy 3.6 board can only handle 3.3 volts – but the 3.5 board (which has most of the same functionality) can handle the full 0v to 5v range. So I ordered one.

    Since the Leonardo board is simply present on the NS1, and does not actually support any of its other functions (if I understand correctly), it seems to me that if you want to add Teensy functionality to your modular NS1 system, you do the following:

    1. Get a Teensy 3.5 board for $28.25. Get the one with pins, shown here.
    2. Attach it to a breadboard and power it with a USB cable.
    3. Place it next to your NS1.

    If this is true (and I’ll be trying it when my Teensy 3.5 arrives) then it doesn’t matter what board is or isn’t included in future Nanosynths. And, any future revolutionary Teensy hardware or software can be integrated into your growing nanomodular in the same way – just make sure you stick with an option that can handle 5v.

    I’m guessing here. If anybody knows for sure, or has already tried this, please let us know. Thanks.

    in reply to: Nanosynth/Teensy idea #3786


    Wow donturner that looks like an amazing system! I had no idea that Teensy had a visual connect-the-wires programming GUI. Having a soundmachines synth (or any kind of setup) that incorporated it would be fantastic.

    However, would a Teensy 3.6 product or board be compatible with the Nanosynth – specifically, the 0v to 5v voltage range? Do you know? Is any arduino-type board inherently compatible with that range? The info available on Teensy is kind of overwhelming, but I think this is the key compatibility question. If they’re not compatible, the units could blow each other out. (I assume that many of us would probably want to be able to connect any future nano to our NS1’s, to have an integrated setup.)

    If other users are aware of additional compatibility issues, other than the voltage ranges, please let us know. If these systems are inherently compatible, might that mean that any future Teensy based product would be NS1-compatible, whether or not Davide decides to use Teensy?

    I have a related question for current NS1 users. Is having a Leonardo board in any future Soundmachines micromodular product important to you? Would you be open to having different boards or systems incorporated in future nanosynths, as Arduino and other sound synthesis systems continue to be developed? (I would. But maybe some people feel differently.)

    Of course, all of this is separate from whether Davide himself is open to the idea. We can brainstorm and share ideas here, but (in my view anyway) Davide can do whatever he wants, it’s his vision and his company. I think the Soundmachines NS1 is an amazing achievement (I have two of them) and a gift to our community, and I want to respect his process and his preferences. If he loves the Leonardo board and wants to keep using it, I’m not going to argue with him. I also want to respect the fact that Davide may have already done considerable work on developing a new product that may be Leonardo based. I am sure we will treasure anything he does, no matter what it’s based on (although I would hope it would be compatible with the NS1).


    I have 3 questions for Davide and other people on this board.

    1. Are Leonardo and Teensy compatible? I don’t mean software-wise, I mean in terms of the voltages they generate and control. (If the answer is no, perhaps the discussion ends here.)

    2. Would users be open to seeing different boards in different Soundmachines jumper-cable-style products, or would they prefer Leonardo all the way?

    3. Would Davide like to share his thoughts about Leonardo vs other emerging Arduino related audio approaches?

    Maybe there are other questions. Of course there are. Thanks everybody.


    in reply to: Polyphonic Nanosynth v1.0 #3767


    Davide you have made my day! All best wishes. Take care. I’m sure we all look forward to your new creations.


    in reply to: Multiple ns1s and power supply #3613


    Hi Paul, for storing and carrying my ns1 I use a clear plastic hobby/tool box with tiered trays that are just right for all the little cables. I lined the bottom with bubble wrap and it’s a perfect fit for the ns1.

    As for power supply for multiple ns1’s, I think you need to run a USB cable or power cable into each ns1. I have two. You need to connect a 0v from one to an 0v on the other to ground and equalize them. I find that pins on the right side of the ns1 work well for that. But I don’t think you can power the whole thing that way.

    I too would love a 3 tiered case. However, I found that a folding book stand like this one makes a perfect stand for two ns1’s, stacked one above the other.

    The other advantage of a stand like this is that you can use it to hold a cookbook, or tablet, when you’re not making music.

    I do not intend to endorse amazon, I’m sure you can find similar items in many places.

    If other people have other good ideas please let us know.

    in reply to: learning resources for arduino for ns1? #3447


    Niklas that’s cool!

    I’ve said it elsewhere but I’ll say it again, Niklas’ step by step instructions here made my setup work, and made it possible for me to compile and upload sketches successfully. I am grateful for that. Anyone who is scratching their heads should go there first.

    And, just a reminder… the arduino part of the NS1 is optional! You can just plain ignore it if you feel like it! It’s up to you.


    in reply to: Obligatory noob question #3432


    Hi clarepiper

    Like you, I get modular patching, and I don’t understand how to code on the Arduino at all. I am a noob only slightly less noo than you. BUT I have managed to install programs into my nano’s Arduino board. It took some trial and error (and was frustrating at times), but it was worth it.

    The idea is that the Arduino chip can extend the functionality of your nano by doing various additional kinds of DSP (digital signal processing). What the pins on the left side of the board do depends on the code.

    Usually detailed instructions will be provided in the “readme” on the github repository and also in the first part of the program (or “sketch” as they are called in Arduino). Keep a copy of those in front of you when you are using a given sketch.

    Rather than trying many different kinds of sketch, you might want to pick one and explore what you can do with it.

    Detailed instructions for installing sketches are in this thread . I am the noob who says “OMG OMG OMG” a lot on that thread. Niklas gives great detailed advice, and Matthew Freidrichs uses the Arduino to provide something I wish the nano had: a modulatable LFO.

    That’s the whole point of the Arduino: it can be coded to do things that the original synth can’t do. The sky is the limit. But since each sketch can use the pins in a completely different way, you have to pay close attention to the comments and instructions on the sketch you are using.

    The other general comment I want to make (which is not very clearly spelled out in the documentation I have seen) is that the code available to the Arduino can be extended by adding various libraries to the IDE on your computer. Some sketches, perhaps many, rely on those additional libraries, and if you haven’t installed those libraries on your PC, Arduino will complain when you try to compile and then upload (which means ‘load into your nano’) the sketch.

    Niklas’ instructions will help you add the necessary libraries.

    With all that said, if you are happy with the “hard” modules on the nano, there is no obligation to use the Arduino side of the board at all. Just do what you enjoy. There is so much to explore – nobody could cover all of it!


    in reply to: Who is active? #3057


    Hi Niklas. I joined the Facebook group and I hope everyone else will too.

    I don’t know how github works. Can anybody upload a file to an existing github directory?

    Pulling all the firmware sketches together in one place sounds like a good idea if people are OK with that.

    Maybe Davide can tell us if he intended to be a place just for official firmwares, or if he wanted everyone’s contributions to live there.

    in reply to: What if I want the original firmware back #3055


    Here is the “error” message I got but the code compiled anyway and I was able to upload and run it on my NS1. Do not worry if you see this. Maybe somebody could tell me what I could do differently, but as I say it’s running fine.

    WARNING: Category '' in library EEPROM is not valid. Setting to 'Uncategorized'
    WARNING: Category '' in library SPI is not valid. Setting to 'Uncategorized'
    WARNING: Category '' in library SoftwareSerial is not valid. Setting to 'Uncategorized'
    WARNING: Category '' in library Wire is not valid. Setting to 'Uncategorized'
    Warning: platform.txt from core 'Leonardo & Micro MIDI-USB (arcore)' contains deprecated"{compiler.path}{}" {} {} "{build.path}/{archive_file}" "{object_file}", automatically converted to"{compiler.path}{}" {} {} "{archive_file_path}" "{object_file}". Consider upgrading this core.
    Archiving built core (caching) in: C:\Users\CHRIST~1\AppData\Local\Temp\arduino_cache_920771\core\core_arcore_avr_leonardo_5112aca257bfec713bd9d7a38edbbb58.a
    Bootloader file specified but missing: C:\Users\Christian\AppData\Local\Arduino15\packages\arcore\hardware\avr\1.0.0\bootloaders\caterina\Caterina-Leonardo.hex
    Sketch uses 15470 bytes (53%) of program storage space. Maximum is 28672 bytes.
    Global variables use 955 bytes (37%) of dynamic memory, leaving 1605 bytes for local variables. Maximum is 2560 bytes.
    in reply to: MODLFO firmware for NS1 #3039


    A tribute track paying homage to the NS1 and the MODLFO.

    in reply to: MODLFO firmware for NS1 #3022


    @matthew Sorry for confusion, my bad. I was like “whaaaat? How can my NS1 not have a MCP49xx DAC?” but I’m stunned and grateful that you actually looked through my error messages and tried to help. Your Reaktor blocks are amazing also. I have sent you a little paypal present. Have a good weekend.

    in reply to: MODLFO firmware for NS1 #3016


    Matthew, OMG I finally managed to upload your gorgeous MODLFO. It is so wonderful. My nano is a crazed chaos machine and I haven’t even brought the envelopes and attenuators into play. OMG.

    Paul and everybody who may have had trouble compiling and uploading: Niklas has blessed us with step by step guidance here that provided all the missing pieces that I was missing.

    When I compiled the MODLFO sketch after following Niklas’ instructions, I got some things that looked like error messages, but they must have been minor, because I hit UPLOAD anyway and it WORKED. (I guess if the errors were bad it would have refused to upload.)

    Anyway thanks so much to Matthew and Niklas, and I hope everybody finds the path to nanomodular joy. Let us know how it goes. And thanks Davide for such a wonderful box of miracles. Please make more! Please make a west coast sibling! And may all your dreams come true!


    in reply to: What if I want the original firmware back #3014


    @Niklas OMG OMG OMG it worked it worked your instructions worked! THANK YOU.

    @zingus, follow the Niklas road and you will arrive at happiness.

    I was able to compile and upload the magical MODLFO by Matthew Friedrichs

    I got some error messages but I clicked UPLOAD ANYWAY and it WORKED.

    Just forge ahead, and you will likely see the magical words UPLOAD DONE.

    Let us know!

    in reply to: Who is active? #3012


    Hi Niklas, I’m here, I don’t know a lot about coding but I’m trying to learn.

    I think the Nanosynth is amazing. A huge amount of modules and possibilities in a very small footprint – and price.

    I would never have thought of buying some of these modules if I were building my own modular.

    As an example, I have used the AND gate with 2 square LFOs to make varying rhythmic patterns by pinging the filter – FUN.

    I used the Sensor Blocks to wire up light sensors to control the filter cutoff, and then I waved my hands around. FUN.

    The S&H, the mults, the mixers, the sumsubs, the looping envelope. FUN.

    I just got a second nano. So many possibilities. FUN.

    in reply to: VCO – Patch 1 – not producing sound #3010


    Abstrkt, I don’t work for Soundmachines either. I was able to do the patches in the manual with no problem. I assume you have played with all the knobs, turning the VOLUME OUT and INITIAL up, turning the filter FREQ up, and so on. You are able to hear the filter self oscillate, so the sound output is getting out okay.

    My one thought is that sometimes it’s hard to tell which pin is which. Maybe you connected the oscillator to the CV of the filter? That’s something I could imagine myself doing. See my post “Make your nanosynth easier to patch” for how I marked the pins to make it easier to see what’s what – for me, anyway. Or look at my avatar.

    Good luck. Maybe it is a hardware problem. I hope you get yours working, or get one that works.


Viewing 15 posts - 1 through 15 (of 23 total)