Hello,
I tried to use the MIDI in on my Pulsar I but it is too slow. What's the deal with that?
MIDI I/O on Pulsar I Too Slow
Re: MIDI I/O on Pulsar I Too Slow
To play what?braincell wrote:Hello,
I tried to use the MIDI in on my Pulsar I but it is too slow. What's the deal with that?
Direct to the Creamware synths routing it through Cubase 4 using the Novation Remote 25 as a controller. It doesn't really matter since I can use the USB on the Novation instead of a MIDI cable. I was just noticing that the latency was so poor, I wonder why they even bothered to include MIDI in the Pulsar. Is it the same problem on Scope cards?
Never seen that on Pulsar1, Pulsar2 or Scope cards.
If you really think it's a problem, how about actually quantifying it by doing a latency test to see what the measurable latency is?
How about eliminating all other factors, like the host (Cubase) for example.
Of course this is all moot, because it's fairly obvious you're just trolling again
If you really think it's a problem, how about actually quantifying it by doing a latency test to see what the measurable latency is?
How about eliminating all other factors, like the host (Cubase) for example.
Of course this is all moot, because it's fairly obvious you're just trolling again
FWIW, I have one of the really old Pulsar 1 cards, and I used it for years with SoftStep and ArtWonk, two algorithmic MIDI pumpers that can produce MIDI much faster and denser than human hands or feet or whatever. I never had a problem with MIDI on that card, nor do I have a problem with the big Scope cards that replaced it. Scope MIDI works great. So whatever the problem, it's not coming from from the Pulsar.
Well I'm not sure why I'm even bothering to help given your rude and belligerent attitude, but what the hell... maybe you'll learn some social skills some day. Try googling 'Cubase emulated MIDI ports', it's a pretty well-documented problem. I'm not a Cubase user, so there's likely even more settings to look at inside Cubase. The best place to seek help for this is probably cubase.net
Obviously before you pursue these solutions, you should actually do a test to see what the latency is, and also try another host to narrow down the problem. This is basic troubleshooting practice.
Obviously before you pursue these solutions, you should actually do a test to see what the latency is, and also try another host to narrow down the problem. This is basic troubleshooting practice.
you might be a drummerdarkrezin wrote:Well I'm not sure why I'm even bothering to help given your rude and belligerent attitude, but what the hell...
anyway, I have a few Pulsar Ones, too - and I never had a problem flooding the Pulsar midi port with active sensing from my old Kawai K4 under Win98
in XP you can immediately crash the machine with that method - now who's to blame ?
adipose code like Cubase isn't really worth commenting
Cubase is quite good now. I don't have any problem with it. I wish I had a dual core Pentium but it's very stable for me until my projects get very large. I hated it for years but now it works fine. I don't use Logic because Apple screwed Emagic users by dropping pc versions. For this reason I hate Apple and because Apple users generally are a-holes with Steve Jobs leading the way.
there is a tiny bit of latency introduced by the keyboard, another one by the Novation Midi driver, next is Cubase communicating with that Midi input, and finally the output to the Scope Midi driver.braincell wrote:Direct to the Creamware synths routing it through Cubase 4 using the Novation Remote 25 as a controller. ... I was just noticing that the latency was so poor, I wonder why they even bothered to include MIDI in the Pulsar...
direct would be the keyboard connected to the Scope card...
Midi (in it's original form) is a fairly slow protocol - even a pure hardware 'through' connection can have 5ms of latency.
cheers, Tom
-
FrancisHarmany
- Posts: 1078
- Joined: Sun Jun 02, 2002 4:00 pm
- Location: Haarmania
-
siriusbliss
- Posts: 3118
- Joined: Fri Apr 06, 2001 4:00 pm
- Location: Cupertino, California US
- Contact:
Been running all kinds of MIDI configurations on my old Pulsar I (going back to before I got the Scope Pro), and never had problems with latency - in fact I tend to prefer it's response to my older PC's running even Soundblasters 
.
Suspect is having too many layers of drivers and/or possibly even an IRQ conflict with the stupid USB. If you're going in via MIDI, then the other layers are possibly suspect - although they shouldn't be. If you're going THROUGH Cubase, then that's another suspect layer - but not sure.
Yeah, test the controller direct into Pulsar I with maybe a simple Scope synth and see what happens.
It shouldn't make any difference, but you can try changing the latency settings in Pulsar configuration.
Greg
.Suspect is having too many layers of drivers and/or possibly even an IRQ conflict with the stupid USB. If you're going in via MIDI, then the other layers are possibly suspect - although they shouldn't be. If you're going THROUGH Cubase, then that's another suspect layer - but not sure.
Yeah, test the controller direct into Pulsar I with maybe a simple Scope synth and see what happens.
It shouldn't make any difference, but you can try changing the latency settings in Pulsar configuration.
Greg
Xite rig - ADK laptop - i7 975 3.33 GHz Quad w/HT 8meg cache /MDR3-4G/1066SODIMM / VD-GGTX280M nVidia GeForce GTX 280M w/1GB DDR3