• Content count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Keeze

  • Rank
    MIDIbox Newbie

Profile Information

  • Gender Male
  • Location Brabant

Recent Profile Visitors

406 profile views
  1. Button Seq4 height

    From the album KC's pictures

  2. MIDIbox TIA - Atari 2600 Synth

    Great, end of summer is ok!! ~Cheers, Kees
  3. MIDIbox TIA - Atari 2600 Synth

    Hi Antichambre, I am also interested in a PCB and TIA chip... Still got some? Cheers, Kees  
  4. MIDIbox SEQ V4 Release + Feedback

    A W E S O M E ! ! I tried to get a hard fault, even turned the LPK in a 32th note arp... No !! HARD FAULTS !! any more. Thank you very much TK. Cheers, Kees  
  5. MIDIbox SEQ V4 Release + Feedback

    Hey TK., This works! So the order is correct. Now I have to find out why I get !! HARD FAULTS !! after some time (20 to 30 seconds of playing) Setup: Akai LPK25 -> via usb -> RPi B+ -> via osc -> SEQ4 -> routed to Midi out1 -> Shruthi The address location is different every time.. Cheers, Kees
  6. MIDIbox SEQ V4 Release + Feedback

    Hi Tk, Tnx again! When I send to SEQ4, the midi monitor on the SEQ4 recognizes sysex. I route the incoming OSC to USB1 and MIOS Studio gives me: While I send: matches found: midimessage ( 144, 60, 116 ) -> /midi1 ,m MIDI [0x00 0x90 0x3c 0x74] matches found: midimessage ( 128, 60, 127 ) -> /midi1 ,m MIDI [0x00 0x80 0x3c 0x7f] These are the last two messages. and should give: 90 3c 74 80 3c 7f Same messages sent to OSC tool (velocity changes due to real keyboard used ;)): Cheers, Kees
  7. MIDIbox SEQ V4 Release + Feedback

    You are exactly right! My apologies for the confusion. Cheers, Kees
  8. MIDIbox SEQ V4 Release + Feedback

    Hi TK. Thanks! But... With the original version of OSC2MIDI When I send from my SEQ4 to my osc2midi thingie and I route the incoming message to an usb->midi port to an syntbox it plays everything correct! When I send from my osc2midi device to my SEQ4 it recognizes it as a SYSEX message. When I switch to the alternative compiled version of OSC2MIDI Midibox recognizes the incoming message and play it (routed to a midiport) OSC2MIDI does not recognize the incoming message. Conclusion Outgoing messages from SEQ4 to osc2midithingie works, the other way around not yet. There must be a second place where incoming messages are translated? Perhaps Lines 446 - 462 in mios32_osc.c? Thanks, Kees  
  9. MIDIbox SEQ V4 Release + Feedback

    In a separate topic I asked a question about OSC in the Seq4 and ik looks like there something with the implementation of OSC in the software. Ik looks like that the parsing of the Midi data type is shifted. Instead of /midi1 ,m MIDI [0x00 0x90 0x3c 0x39] My SEQ4 sends: /midi1 ,m MIDI [0x90 0x3c 0x39 0x00] The first is compliant with the standard found here:  Problem is that when the SEQ4 receives a compliant message, it does not parse is right. Am I right and if so, can it be fixed? Cheers, Kees  
  10. SEQ4 and OSC (Midi usb router)

    After recompiling osc2midi with changed parsing of the m-datatype I have got it working. Ik looks like that the Midibox implementation is non-compliant. @TK. , any chance this can be fixed? Another problem is that I got a !! Hard Fault !! at PC=0x0805c7f6 several times when sending data. The Ethernet module is a ENC28J60 Ethernet LAN Network Module, which is connected since summer 2016, but used for the first time these days. I use the boards from Tim (SmashTV), a STM32F4 with firmware 4.092. What can that be? Cheers, Kees    
  11. Hello all, I want to connect more than one USB midi device to my SEQ4, without connecting a full-blown computer. So I have some spare Raspberry Pi's laying around. Model B+, so 4 USB ports. I already tinkered some things and I ended with a program called osc2midi (and back). I can send to my SEQ4 and I can also receive from the SEQ4 thus communication is established. Now I run into formatting problems. With help from the creator of osc2midi I found out I have to use the m-datatype in the conversion, but it look like the data is interpreted different. SEQ4 OSC is set to Midi-messages. Then I send from SEQ4 to osc2midi I receive: /midi1 m, MIDI [0x90 0x3c 0x35 0x00] When I sent from osc2midi, it sends: /midi1 ,m MIDI [0x00 0x90 0x3c 0x39] Osc2midi uses a single variable, so I can't change is easely. Osc2midi uses map-files and the mapping for this statement is: /midi1 m, msg : midimessage( msg ); So, one of the machines has the output shifted. And how to find out which one... Can someone shed some light over this subject..   Edit   Looks like the midibox code got an error:   Cheers, Kees
  12. My SEQV4 - Finished electronics !!!

    So, what made it run? (You don't need lib32gmp3-dev, if you have libgmp3-dev btw)  
  13. My SEQV4 - Finished electronics !!!

    Perhaps try to download the toolchain again in /usr/local and than unzip it with tar -xvfj gcc-arm-none-eabi-xxxxxx.tar.bz2. I have a VM with LUbuntu, and followed with exception of the command above... Everything compiles without any errors...  
  14. Seq V4 case....I think I've become...

    Like it! You could consider cutting the gear for the dataweel also from wood, two layers with a small steel notch for easy turning ;)
  15. YAS4B (Yet Another Seq4 Build) ;)

    From the album KC's pictures

    Fully functioning \o/