W2K & Midi

marcuspocus · Post by **marcuspocus** » Mon Jul 30, 2001 7:36 pm

Hi people!

Did anyone had succes with midi in pulsar for w2k? I mean, are you able to have more than one midi port? I know from the 'readme' that there's only 2 sequencer dest&src available, but are you able to make them work? at all?

Logic do see the Creamware DSP Midi 1, but doesn't receive anything from it, in pulsar OS, if I monitor Pulsar MIDI source, i see that it's working, but when routed thru Sequencer Midi dest 1, nothing reach Logic, nor FruityLoop, nor Reaktor or WaveLab...

Even if i put Sequencer Midi source & destination 2, the port doesn't appear in any of those programs.

Any one ?

Thanks.

_________________
Marcus Pocus
The king is ALIVE!

[ This Message was edited by: marcuspocus on 2001-07-30 20:38 ]

Zork · Post by **Zork** » Wed Aug 01, 2001 1:03 am

Same here.
When trying to use Sonar with a Pulsar I, I can see 2 midi ports, but none of them receive any data from my keyboard.

When I connect Midi source -> Bluesynth, blusynth -> BM -> analog out I can hear the synth play (from within my projectwindow).

When I connect sequencer source -> Bluesynth, connect Midi source -> sequencer dest & connect bluesynth output -> BM -> analog out, I am able to hear bluesynth play from within Sonar by using the piano roll editor.
Really vague, huh?

marcuspocus · Post by **marcuspocus** » Wed Aug 01, 2001 3:52 am

Well, it's still better than me, I don't see 2 midi port. But Hardware Midi source is working, as i can monitor it in pulsar, or play a synth directly as you... It's the sequencer source/dest that are not working.

And only 1 appears in any soft.

_________________
Marcus Pocus
The king is ALIVE!

[ This Message was edited by: marcuspocus on 2001-08-01 06:24 ]

subhuman · Post by **subhuman** » Wed Aug 01, 2001 7:33 am

I use the hardware port anyway myself; I never need more than 16 MIDI channels for Pulsar my projects. Try using the hardware port off your MIDI interface like Pulsar is just another module as a work around until the software ports are implemented. (Next public beta or OS3) Alternatively, stick with 98SE or ME until then, everything works pretty good except Windows can burst at the seams if you've got too much stuff going on outside Logic & Pulsar.

Zork · Post by **Zork** » Wed Aug 01, 2001 8:02 am

Thanx for the tip, Subhuman!
Will give it a try, since I don't need more than 16 channels either.

Zork

marcuspocus · Post by **marcuspocus** » Wed Aug 01, 2001 8:51 am

Would be nice to record what you play...

If sequencer in or OUT for that matter don't work, how can you record midi to logic?
And if you use STSX000 (which take all 16 cha.) how can you play any synth at all?

Well, the driver seem promising for performance but i'll go back in ME for now. Good thing i've made a Ghost before!

Can't wait for 3.0!
_________________
Marcus Pocus
The king is ALIVE!

[ This Message was edited by: marcuspocus on 2001-08-01 09:52 ]

subhuman · Post by **subhuman** » Wed Aug 01, 2001 9:10 am

If you use all 16 channels for the STS, then yeah, that can be a problem.

As far as recording the MIDI - it's quite simple really, the MIDI is coming into the sequencer, which in turn sends the MIDI to Pulsar (it shows up as "Pulsar Midi Source" inside the Pulsar Routing Window), you simply press record on the sequencer. --At least if you control everything with external hardware. If you're trying to record mouse-movements of knobs, then Pulsar is sending MIDI which you will need to capture, but again, cable the Pulsar Hardware MIDI Out Port to your Midi Interface and inside the software route the Midi Outs you need to record via mousemovements to "Pulsar MIDI Destination" -- it'll go out the MIDI cable and into your sequencer for recording.

When I get the STS5000 I may end up using more than 16 channels, so I'll probably change back to the software MIDI drivers... the moral of the story is we need 3.0