Jump to content

gyurek

Members
  • Posts

    5
  • Joined

  • Last visited

    Never

Posts posted by gyurek

  1. Hi syamajala,

    I have edrum and mbfm and mbsid both :) see my homepage at http://web.t-online.hu/gyurek

    I prefer mbfm for use with edrum, but fm drums sounds very poor for me.

    I started to build a drum synthesizer/sampler, based on

    - an old 486 mainboard (fanless - noiseless)

    - Sound Blaster AWE soundcard - the only card with onboard ram for sample playback, onboard fm sound, reverb/chorus, spdif digital output for noiseless recording, and midi i/o

    - 512 MB Compactflash card (for os and drum samples)

    - 16x2 lcd connected to lpt port

    - 4 buttons and 4 pots connected to game port

    - os based on dos with original sb drivers

    - will fit on a 2U rack

    Still work-in-progess, but sounds much better for drums.

    Cheers,

    Gyurek

  2. Hello,

    I'm in the middle of building my own Midibox DIY synth. Both SID and FM modules works fine, so I deciced to build them together.

    My current config looks like this:

    Midi In --> Core1 (for SID) --> MBLink --> Core2 (for FM) --> Midi Out

    Almost everything works (ordinary midi messaged are processed well), except sysex messages. Core2 can be accessed fine with sysex, I can upload patches, firmware. Core1 does not work, when I try to reload firmware, I get "Received unexpected MIOS SysEx message = 00007E40020E0B00F7  expected = 00007E4001" message.

    Core1 configured to MBLink forward point, device id 1, and Core2 configured to link endpoint and device id 2.

    Am I missed something important?

    Thanks.

    Regards,

    Gyurek

×
×
  • Create New...