Keeze

You are exactly right! My apologies for the confusion. Cheers, Kees

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

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: http://opensoundcontrol.org/spec-1_0 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

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

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

So, what made it run? (You don't need lib32gmp3-dev, if you have libgmp3-dev btw)

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 http://www.midibox.org/dokuwiki/doku.php?id=linux_mios32_toolchain_core with exception of the command above... Everything compiles without any errors...

Like it! You could consider cutting the gear for the dataweel also from wood, two layers with a small steel notch for easy turning ;)

Any news about the pictures not showing...?

Double post ....

Hi, Can I still sign in for a kit without the case, LCD/Leds? Cheers, Kees

And working :)

Found the datasheet... 10 to 32 pF, so 22 should do the trick

That were my thoughts to, but always worth to check, tnx ;)

Good point, good feedback. Thanks!

Hi all, In the schematic for the Quad IIC Midi board, I find 15pF caps for running the crystal. I have only 22pF laying around (and used to use these with 16/20 Mhz crystals). Is there a specific reason to use 15pF or would 22pF do? Cheers, Kees

Hi all, Now the build of my Seq-4 is coming to an end I have one question which I can't find here in the forum. Do or Don't I remove the detent from the middle encoder (the one with the big datawheel). What did you do and what are the experiences. I am curious about your thoughts. Cheers, Kees