Jump to content

midi and the roland d110


9 replies to this topic

#1
dylab

    SoundPunk Veteran

  • Members
  • PipPipPipPipPip
  • 878 posts
  • LocationMelbourne
i've begun using my d110 a bit more and would like to control the parameters of the parts in realtime
it can be done with a pg10 controller
the pg10 send the following data to control the parts (see attached image)
how would I go about getting this data out of my DAW if possible
or could I configure my bitstream 3.x to control this

#2
SilverStreak

    Gold Punk

  • Members
  • PipPipPipPip
  • 399 posts
Does midiquest work with the d110? I'll bet it does ;) .....and upon quick check indeed it does. Try the vst function. Never got that far with any of my kit but let me know how it goes...if you go this way anyway :P

#3
neo

    SoundPunk Veteran

  • Members
  • PipPipPipPipPip
  • 683 posts
That is SysEx data. You're on Ableton aren't you, dylab? Ableton doesn't support SysEx data natively but I had a quick look at MidiQuest what SS just mentioned and it looks like you'll be able to do automation. You'll need the XL version for that. SysEx data is inherently much more dense than CC data, this means that you may have higher resolution (although it doen't appear so looking at thos parameter ranges, slightly less actually) but automation won't be as smooth. CCs send very small amounts of data in comparison to long SysEx strings.

#4
dylab

    SoundPunk Veteran

  • Members
  • PipPipPipPipPip
  • 878 posts
  • LocationMelbourne
yeah im on ableton so am limited to sending out midi cc
i'll have a look at midi quest xl and see how that goes

my other thought was cc to sysex conversion with midi pipe but that looks like a world of pain

#5
dylab

    SoundPunk Veteran

  • Members
  • PipPipPipPipPip
  • 878 posts
  • LocationMelbourne
im guessing midiquest is abandonware much like motu unisyn
the vst side of things is not happening and i'm getting handshake timeouts with d110

#6
SilverStreak

    Gold Punk

  • Members
  • PipPipPipPip
  • 399 posts
midiquest will have a help file that will relate to the d110, and may have some handy info. I went through all this with my xl1t before I finally found out my os was to new and I couldn't revert to an older version. Even better was It wasnt till i read the Proteus help file to find the info for my xl1t...Yay :P

Q. Do you get the timeouts with patch edits or just the vst part?

#7
SilverStreak

    Gold Punk

  • Members
  • PipPipPipPip
  • 399 posts
Dude dunno if this helps but this is the fast tips for the d110 in mqxl10....may need a system reset.

* Patch - load a single Patch
* Patch Bank - load all 64 Patches

* Match D-110 Unit # to Comm Ch

* For the D-110, to obtain the ROM
  version for the D-110, hold down
  bottom 3 buttons right to left and
  turn instrument on

* We have seen situations where the
  D-110 unit failed to respond to SysX
  dump requests or responded improperly.
  The unit required asystem reset in order
  function as it should.

#8
dylab

    SoundPunk Veteran

  • Members
  • PipPipPipPipPip
  • 878 posts
  • LocationMelbourne
i'll give that a go - thanks for the help
its weird the d110 responds fine with sysex librarian and motu unisyn
but it doesnt seem to like midiquest
it could be a long night

#9
SilverStreak

    Gold Punk

  • Members
  • PipPipPipPip
  • 399 posts
Probly get it working on a patch edit level first. Save any precious patches of yours first via your other editors. Then do a factory reset on the d110 then try the handshake thing with MQ again. then when thats sorted, go for the vst function. And let us know how you go I'm interested in your results :P

#10
dylab

    SoundPunk Veteran

  • Members
  • PipPipPipPipPip
  • 878 posts
  • LocationMelbourne
it seems the handshaking error was due to my daisychain set up
reconnected it directly to ultralite and managed to get midiquest and d110 talking but vst seems to kill live





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users