Page 2 of 2

Posted: Sun May 18, 2008 6:12 pm
by siriusbliss
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

Posted: Sun May 18, 2008 9:02 pm
by garyb
13ms latency minimum for a pulsar1......

nothing can be done about that for external synths, but for scope synths, no reason not to connect directly throught he card's midi port. that would be near zero latency....

Posted: Sun May 18, 2008 11:22 pm
by Nebukadneser
If you are using Cubase, buying a seconhand Steinberg Midex 8 MIDI interface is the best way to go to improve MIDI timing and accuracy in general.

As for the Scope synths - the ULLI settings is the only way to lower latency. 13ms is the lowest a Pulsar 1 can go.

Neb

Posted: Mon May 19, 2008 12:12 am
by braincell
I bought the Emagic interface because I was going to switch from Cubase to Logic but exactly one month later Apple bought Emagic and dropped Windows users. That is one reason of the many reasons I hate Apple. This is on a second computer. I will stick with the Novation. The latency setting is fine when using the Novation so for whatever reason, the Pulsar midi interface just sucks; end of discussion. It was probably just stuck on there so they could advertise another feature. A latency of 13 ms is perfectly fine, as long as I am not using the Pulsar midi interface, that seems to be what I am getting.

Posted: Mon May 19, 2008 12:38 am
by garyb
garyb wrote:13ms latency minimum for a pulsar1......

nothing can be done about that for external synths, but for scope synths, no reason not to connect directly throught he card's midi port. that would be near zero latency....
wow, that came out wrong....

nothing can be done about this for vsts. when you route through the sequencer, your audio latency setting applies to midi. but for scope synths, no reason not to connect directly throught he card's midi port. that would be near zero latency. you can still route to and from cubase to record and playback midi on that synth.

Posted: Thu May 22, 2008 4:49 am
by Fede
braincell wrote: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.
Cubase and Windows NT are long-date well-known midi problem generators, aren't you addressing your hate to the wrong recipients (S|C, Apple)?

cheers
Fede

Posted: Fri May 23, 2008 10:14 am
by Neutron
I have a novation xiosynth sitting on the shelf unused now. it has USB midi. as soon as i send it anything everything else in my system (scope synths and hardware on the scope midi ports) get completely out of whack.

That does not even happen with behringer bcf2000 which i sometimes need as an extra midi port.

maybe the problem is with novation.