PlanetZ forums - scopeusers.com

hi ,

I have a problem with my pulsar II midi module .. ( maybe it's me the problem)

I don't succed to pilot my sequencer's with the creamware midi interface .

my routing is : pulsar2 midi A source -------------sequencer midi dest 1

it used to work like this ... but now, no signal received in my sequencer Ableton live 8 ,
In ableton live, creamware midi in out are well reconized and activeted ...

Maybe i'm confused on some points .. i need your help ..

thank you for your help

i think you need to activate in Live where it says Output: Creamware MIDI input/output1.

stardust wrote:And it might be good to add a Sequencer source module to the routing window.

Actually, you need to load up all Wave and MIDI drivers as set up in Device Manager > Scope > Driver properties. Some apps seem to have issues when the project doesn't contain them all, so throw them in your default project!

hello !!
thank you for your answers ...

i tried this routing ... and it's ok for midi out, it runs well, i can synchronize my mpc for exemple ..... but still not for midi in




do you have any idea ..

may it comes from scope installation ?

Attach a MIDI Monitor to Pulsar2 A MIDI Source and see if there's anything there.

this is my results with this routing ...

it no seems to be good !!

That doesn't look good. What source are you feeding to the hardware MIDI in on Pulsar (ie. keyboard model?).

i'm using an mpc or midi keyboard !!

ok, so there's some kind of reset message constantly sent from the mpc, what happens when you hit a pad? you should see a note on and note off message(or at least note on). are you sure you have the proper port assigned in the mpc(it has 2 ports, no?)?

yes the information come from mpc's play button .. but nothing happen when I push a pad ./ the mpc works well because i'm using it with a midi mate usually ( midi-> usb) and i have no problem /

thanks again for your help

if nothing happens when you push a pad, are the pads assigned to the proper output on the mpc?