Jump to content

Keeze

Members
  • Posts

    60
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by Keeze

    • Wilba Front
    • Front: 2 midi in / 2 midi uit
    • Back: 2 midi in / 6 midi uit
    • OSC
    • Including build-in 230V psu
    • Fits perfect in the desk I built (which is also for sale), but can be transformed to its original case.

    Why? I started playing guitar and I came to the conclusion that the guitar fits me more (played more guitar in a half year than synths in 5 years...)

    More info: Zolderverkoop | KC's Hobbyprojecten (vanhoekelen.nl) (Dutch)

    Also for sale: Mutable Instruments Ambika, Mutable Instruments Shruthi, PreenFM.

    overzicht.jpg

    mb-front.JPG

    mb-back.JPG

    original case.JPG

  1. 10 hours ago, Reubenclarke.jpg said:

    Hey Everyone. After following through the troubleshooting guide I think I'm having an issue with my midi->usb cable. I'm running windows 10, I tried both a no name cable and an M-Audio Uno. 

    Does anyone have any recomendations on cables that work well with windows 10?

     

    Thanks

    After some trial and error I had good luck with the Roland UM-ONE mk2 (YMMV).

     

    Cheers 

  2. Hi all, my first NG-project is alive ;) I build a switchable USB to 4 DIN midi port router. Al from parts I have laying around. After a evening digging this forum and trying, it just works. Now I can control my Volca's with a single USB midi keyboard (hurray).

    I don't get one thing: How do I get special characters on the display??

    For example in the next line I like to have a arrow instead off the >-sign (or the solid >)

    EVENT_SENDER  id=1   if_equal=Button:1:1  fwd_to_lcd=1  type=NoteOn chn=1   key=any  lcd_pos=1:32:1  label="> %e"  ports=00001000000000000000
    [17:36]

    Is this possible with NG?

     

    Cheers,

    Kees

    simple midirouter.jpg

  3. Hi all,

    I noticed that this forum has no encrypted connection https (anymore)… Has this always been so, or is this new. Since we all login over here, I think this is a bit of a security issue, since our passwords are transmitted in plain text.

    So especialy for those who use passwords on multiple sites (never a good idea) beware..

    Cheers, Kees

  4. So, finaly took the time and a PI3 I had laying around and installed the software.... The problem is that pyBLM can't find the Seq4:

    pi@pyblm:~ $ ./pyblm/pyBLM.py
    pyBLM launched.
    pyBLM init
    ERROR: Couldn't find the seq

    When checking for available midi-ports I get:

    pi@pyblm:~ $ amidi -l
    Dir Device    Name
    IO  hw:0,0,0  Launchpad Mini MIDI 1
    IO  hw:1,0,0  MIDIbox SEQ V4+ MIDI 1
    IO  hw:1,0,1  MIDIbox SEQ V4+ MIDI 2
    IO  hw:1,0,2  MIDIbox SEQ V4+ MIDI 3
    IO  hw:1,0,3  MIDIbox SEQ V4+ MIDI 4
    IO  hw:2,0,0  Launchpad Mini MIDI 1

    Output of mido.get_input_names() gives:

    MIDIbox SEQ V4+:MIDIbox SEQ V4+ MIDI 1 20:0
    MIDIbox SEQ V4+:MIDIbox SEQ V4+ MIDI 2 20:1
    MIDIbox SEQ V4+:MIDIbox SEQ V4+ MIDI 3 20:2
    MIDIbox SEQ V4+:MIDIbox SEQ V4+ MIDI 4 20:3

    Looks like the naming of the Seq4 ports has changed (I use firmware version 4.096). I tried to alter the seqregex function, but no luck :pout: .Since I don't understand a *** of regex and re.compile is used for finding the Seq4 I am a bit stuck. When I revert to an older version of the Seq4 firmware pyBLM starts to work. Can you give me a clue how to stay on the latest firmware and get the pyBLM to work as should? Thanks in advance :wink:

    Cheers, Kees

  5. 4 hours ago, Hawkeye said:

    The Atari 2600 was my first "computer", at age 5, the sounds from the TIA probably burned up a few neurons in my brain, it was a great time! :-)

    Yes, mine too, although I was a couple of years older....

    5 hours ago, Antichambre said:

    No, I just sent last PCB this morning, but i will get some other by the end of summer...
    I will remember you want it.

    Great, end of summer is ok!!

    ~Cheers,

    Kees

  6. 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..

    hardfault.thumb.jpg.afbba6a6165704b391cd

    Cheers,

    Kees

  7. 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:

    mios2.png.63f220e658a6aa6357b36e07b8c50d

    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 ;)):

    mios4.thumb.png.8b7615b92134e920f20a4ab6

    Cheers,

    Kees

  8. 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

     

×
×
  • Create New...