• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About weasel

  • Rank
    MIDIbox Newbie
  1. MidiBox DAW Controller

    Couple thoughts: great idea, i think it's quite feasible and will be worth the effort. will take longer and depending on your needs also not be cheaper than a commercial solution. all the buttons/pots/encoders in the world are no issue to connect obviously. i have some nice rotary encoders with fancy LED ringgs around them available if you want haha. one of the biggest issue i see with my limited knowledge is the DAW implementation. Does Nuendo allow to control the CURRENTLY SELECTED eq/dyn with a fixed CC or NRPN adress? or how are you thinking to realize the dynamic mapping? also sending out matching dynamic data from your DAW for your OLEDs, not sure if mackie control protocol supplies all this conveniently? oh also for that amount of OLEDs and input stuff you might need a couple more MCUs/core boards down the line i think? i though about doing something somewhat similar for ableton at some point, couple dynamically mappable input knobs with parameter name OLEDs. its easy there, if you use max4life, which i guess nuendo lacks..   maybe an alternative idea would be to buy an off-the-shelf controller for the basic motor faders and just build something smaller for all your custom shortcuts etc?
  2. Hey everybody, i was wondering how to split polyphonic keyboard input on several midi channels, depending on the voice number? I read through some  of the notestack source code but i can't see any implementation in NG via the scripts, right? I would have to write my own routines and recompile? Does midibox KB support this out of the box? Thinking of splitting my setup over two midiboxes anyways because together with a quite big amount of encoders my keyboard DIO matrix kinda overloads the SPI latency... so what i am trying to achieve is 6 voice polyphony to be spread over 2-3 midi channels, following the notestack rules/implementation. any advice would be greatly appreciated.
  3. Chain MIDIboxes

    Thanks man that helps a lot on where to start digging! Any background info as to why it has to be on the same PSU? would a common GND connection be enough maybe? Thats what i had to do between some other MCU boards..
  4. Chain MIDIboxes

    Hey, i also need to work on higher midi baudrates, was this somehow implemented in NG by now or do i have to compile wih my own adapted settings? @Zam would you mind shedding some light on your midi router/merger thing? i see you keep calling it USB midi, but if i just hijack the J11 pins to connect boards directly, it still is UART midi right? i would enable the second set of 4 midi ports in NG events? tried connecting PA2 or the j11 pins directly (and with pull up R) to the rx pin of my arduino, no signal. same connection works with optocoppler shields on bot sides of the cable..
  5. How did i manage to fry my STM32 disco board?

    Yeah ok thanks, will try now!   edit: thanks @latigid on, all back on track now!
  6. How did i manage to fry my STM32 disco board?

    Ok thanks. Having some other issue, i fail to save any settinsg in the mios bootloader? My NG software works fine, but once i load the bootloader via the blue button, i can't seem to save any (LCD) settings from mios command line. the mios studio query shows the corret bootloader, but neither the help nor any of the set commands give me any result, i tried storing at the end but it won't save any changed settingg booting up NG again.   any hints? probably another stupid mistake on my end..
  7. How did i manage to fry my STM32 disco board?

    Thanks a lot @latigid on. I feel stupid now because i actually read a line somewhere about some ST boards needing a firmware update but i though to myself "nah that doesn't pertain to me with my brand new board".   LED1 still blinking slowly, not sure if my old one did that? anyway, all seems to be working   EDIT actually no, while the ST now boots up properly and runs the NG program with only the midi USB connected, i can not access it via MIOS studio. Red COM LED1 keeps blinking slowly. i re-did firmaware updates twice and re-flashed bootloader after each time...     EDIT 2 as per usual after pluggging everything in and out 5 times, it now eems to reliably work. LED1 still blinking red, but everything works. shrug should emoji.   thanks guys
  8. How did i manage to fry my STM32 disco board?

    thanks phlatline well i gave up on the old one since not even the power led is coming up, new ones arrived today and i am having some weird behaviour after flashing the mios bootloader: right after flashing, still connected to the windows machine, the two midibox OPWM-led flashes came up. do that after every reset. but as soon as i disconnect the "programming" usb port, it just goes into a mode where the big red LED1 status led blinks slowly. the only way to get it going again is to connect the big USB portto a computer. just plugging them into a powersupply does not boot up properly either. it works flawless when i have both cables connect though. i do have PA9 and 5v connected.   edit - i can unplug the computer after successfull bootup and the disco board will keep runningg powered througgh the usb hub. i can now also unplug the "BIG" usb port cable and it keeps running on the midi usb. but i still will not boot up without a computer plugged into BIG usb port.
  9. you are getting me very excited for this.. yes i didn't really start going into mios code yet, just fiddling with NG configs. and i already realized i won't get a custom notestack w/o recompiling. it's one of the next 2-3 upcoming steps on my synth. and of course then i'll also hopefully get to look at your code and maybe contribute something to it! like, i'm good at adding hidden jokes in the comments. usually unfunny ones though.   for the poly/overlap, yeah my bad i only think of midi and poly synths, and ignore the eurorack needs. but you have it all figured out already!! CC/CV combination sounds deadly. i think a gap note 0 like you describe would be a great workaround. you should think about using that even for your regular arp, cause you can easily create much more complex rhythms with that as opposed to straight hammering 16ths lines... and let's be real who ever needs to play a C-2
  10. How did i manage to fry my STM32 disco board?

    thanks guys! the ws2812 chains were on 5v, while by design i had at most some GNDs connected between the different voltage parts, it probably was a short or misconnect somewhere along those lines... because the weird thingg to me was how it died whilei was using it, not patching or seriously moving anything. damn little breadboard patch cables...
  11. this would be so awesome! you could just use your piano roll, and map c1 to the first pressed key, c#1 to the second pressed key etc etc. or maybe a dynamic "force to scale" that limits any arp noe to the currently pressed keys. more of a "force to notes". does your arp currently support gaps/silent steps or only via velocity 0? since you have the full very impressive piano roll thing implemented. i think there's a huge potential for an arpeggio/step sequencer crossover like what that Arpegggio Designer does. Not sure if the midiphy SEQ does something like this @Hawkeye@latigid on? it would be more of a keyboarder arp function as opposed to an eurorack user i guess.   two more thoughts from a regular ableton arpeggio user: - gate values bigger than one step can be a lot of fun and create overlapping poly notes, or legato mono notes. ableton goes up to 200%, maybe even up to 4 steps length though? right now it looked like yours ends at one full step length w no overlaps. - i didn't fully understand your offset and delay parameters yet but combined with the resync they seem to add what looks like random timing jumps in the video? i LOVE that. having an option to add some kind of randomness/humanize to both timing and velocity is a very big feature of an arp . maybe think about a (hidden shift) function to add some random to velocity, or alternatively to the regen/target. i do this all the time on my arps in ableton. you could also implement this for the CV ins you are mentioning i guess, just CV control the delay time or the target velocity level with a random LFO, was that the idea you had for the CVs?   after 3 months of heavy almost full-time work and countless hours in this whole MCU music field i still can't even start to fathom how you pulled this off bruno. the piano roll programming is insanely good for a one man independent diy project. and the whole workflow and choice or parameters seems very well thought out judging from your video!   i also have some questions regarding general arpegggio/note stack functions, i need a notestack to spread out 6 poly voices to 3 duophonic synth boards. but i guess i have some reading up on that to do first and obv don't wanna derail your thread with this.
  12. Man this is absolutely amazing! Will definately get one if you make them available! I can only imaggine how much time nd effort went into this, incredible. I have one question which i couldn't answer watching the video: my favourite feature in an arp which unfortunately isn't realized in many is a melodic pattern relative to the pressed keys. there is a m4l plugin that does exactly this, http://www.maxforlive.com/library/device/3545/arpeggio-designer Does your arp support something like this? you have the piano roll and all in there so if not, i think it would be easy to add and make the arp even more unique? That way you can write a little rhymthmic sequence, monophonic or even polyphnic, and it will alway be adapted to exactly the keys you press. much more interesting than basic up/down/rnd functions, and makes it super easy and fun to write chord progressions and figure out voicings. The new native instruments kontrol keyboards also have something like this, calling it a "sequence" i think.
  13. yeah so while i was plugging some peripheral breadboard connections in and out earlier today, the moment it apparently died i was just playing on the keyboard and the encoders...   the connected OLED screen went black first, then i noticed all 3 LEDs on the disco board blinking at around 2-3Hz. I tried reseting and a cold restart with no change, back to blinking. started disconnecting all IDC cable that were connected, same behaviour. next i unplugged the power line of one of the ws2812 chains which somehow still was connected to the ST board (gnd or data) and the blinking frequency change dot about 1Hz. 10-20 seconds, one or two resets later it was all black and never came back since...   any idea what went wrong here so i can avoid doing the same with the next one? i think i was turning an encoder when it happened first, and there might have been a short somehwere on the kinda wonnky prototype setup i run?
  14. Alright, everybobdy stop whatever you are doing right now and gather to see what granddaddy Klose blessed us with: a little tease of the all new extended and improved WS2812 midibox driver: Gaze at currently 432 WS2812 controlled by a single J4 serial pin!  
  15. Ok guys, was away for a bit on family duties, here’s the final update before I put in the order within the next 2 days! I had @FantomXR change the LED Ring design to 32 instead of the prototypes 36 LEDs. That’s what I originally had planned too, for three reasons: 1. easier mathematical mapping of n^2 values 2. Better usage for rhythmic/timing use, ie. a 32 step circular sequencer (think Euclidean Circles module) 3. More space between the LEDs for possible masking solutions. The diameter of the ring will remain the same at 33mm. At the classic 80% perimeter encoder use (as shown in the demo videos with the bottom 5 LEDs blacked out), you will now have a 27 LED resolution instead of 31 on the prototype. The LED cross bleed which I was worried about for a while should be no issue with this updated version. Even without any masking or light pipes it is not that bad as you can see on all the demo videos. With the new LED distance it is quite easy to mill or print a little plastic masking ring if you want. And simple light pipes, even just hand cut from optical fibre, improve the quality a lot too. I will post pictures and videos of my results soon, but probably not in time before the order. Added SMD solder point for an optional power supply capacitor at the power supply pins of each LED board. Using WS2812C 2020 LEDs for much lower power consumption than the B variant. Added some extra pinouts on the encoder board for more efficient use of the 74HC165: on the prototype each 165 was filled with the 6 pins of two switchable encoders, wasting the 2 remaining pins. Now all 8 pins of the 165 have unique TH-solder points so empty pins of the 165 can easily be used for additional buttons. Eg. You can now connect 2 switch-less encoders and 4 pushbuttons to the same 165, or 1 switchable encoder and 5 pushbuttons, twice that per encoder PCB. Added a TH-solder point for the 165 Clock Enable pins so the boards can be used with bitbanging protocols instead of SPI only. Unfortunately due to some family emergencies over the last weeks I was not able to finalize the design in time for the afore mentioned manufacturer discount. I still managed to get a decent offer, and so far group orders including my own demand are at around 160 sets. That gives the following prices: Net manufacturing cost per fully assembled PCB set: 19-21 EUR (depending on the final numbers) Import taxes (VAT of 19% for EU, tbd for US and other countries) around 4 EUR per set Individual shipping to you (tbc, but probably 5-10 EUR per shipment, depending on destination country what shipping insurance etc you want) That equals to a roughly estimated overall sum of 30 EUR for 1 set, 50 EUR for 2 sets, 90 EUR for 4 sets, 170 EUR for 8 sets. plus/minus 5% i guess. This isn’t cheap but I am 100% sure it still is really good value for what you get. It's around the same price you pay for one single ALPS rotary encoder with a single color LED ring. The price is for a set of two PCBs, one with 4 RGB LED rings, and one for 4 rotary encoders. All SMD parts and the assembly is included, the actual rotary encoders and any through-hole solder pins are not included. Might be able to supply standard Bourns PEC11L if needed. I personally pay about 7 EUR more than this for every set, in my personal development/protoyping costs. So if you feel generous and support the cause, the net price per board would be 25-26 instead of 19-21 if I distributed the dev costs equally. Order will be put in this week, production and shipping will take approx 2-3 weeks, and then another week for testing and further shipping on my side. Expect it in your mailbox end of july. Also I am talking to a very popular US based modular DIY supplier who will eventually stock some boards in his webshop. Will confirm asap, pricing tbd.   And a summation of what I think is important information: This is a non commercial group buy of a pcb board. You buy the pcb board with all the SMD parts and assembly and nothing more. Of course I will take full personal responsibility in case something is fundamentally wrong or not working at all with the final product, based on a design mistake on my end. But other than that that’s all you get. No official support, no guarantees etc etc. That being said: I designed these for the MIDIbox platform originally and I also successfully tested and use them on Arduino boards and the Axoloti platform. They work perfectly. I will write basic functions and objects for all these platforms over the course of the next weeks and of course I will share all these with everybody. Also basic general control for ws2812 LEDs and 74HC165 rotary encoders is readily available for all platforms already. I’ll also throw together some basic quick start guides and assist with connection set-up problems, but I expect anybody getting in on this order to be able to set up their own serial communication on the right pins of their respective controller boards. Expect a hardware protocol limit of around 500 LEDs (3-4 4xLED boards) per serial line if you want to maintain a 60Hz refresh rate, as with any WS2812 application. Also the obviously the more 74HC165 you chain in series, the higher the latency will get. Both those programming libraries and the PCB design will be open sourced at some point. I don’t know when because I don’t want to do a half assed job on that and proper cleaning/optimizing and documentation might take a while. You will have to buy and solder your own rotary encoders. The boards are designed for and tested with the Bourns PEC11 and PEC16 range, I personally recommend PEC11L low profile encoders. The optional LED board SMD power input cap would have to be self supplied and hand soldered too but in most cases will not be necessary.     So yeah that’s about it. If I didn’t scare you away by now, please RSVP as soon as possible. Either here via a private message or via email at rgbledring at gmail dot com, then we can exchange personals and discuss details.     Also, in extremely exciting midibox news, a very special someone decided to start redesigning and expanding the WS2812 drivers. I will post updates as soon as we did some testing!