pulsar II & xtc mode: some troubles 'n questions

An area for people to discuss Scope related problems, issues, etc.

Moderators: valis, garyb

Post Reply
therm
Posts: 6
Joined: Sun Oct 13, 2002 4:00 pm

Post by therm »

Hi

I'm just posting this message everywhere as to get an
answer quickly. So you might already have seen this
post. If so, there has been something added in the end
in respect to a post of at0mic I read and that might
explain some of my problems.

Anyway, my list of troubles.

Motherboard: Asus P4B266SE (with latest BIOS version)
CPU: Intel P4 1800Mhz
Memory: 512MB
OS: Windows ME
Graphical Card: Riva TnT 32MB
Sequencer: Cubase VST 5.0
Creamware product: Pulsar II with Classic I/O (used in
XTC mode!)

1. When I try to assign a midi controller, it does not
work. Specifically:
I try to hook up
the cut off 1 of the Prisma to midi controller no.20,
but Cubase does not
take it, which
shows in the fact I cannot draw anything in the editor
window of that
controller. The
only controller which seems to work is velocity. I've
also tried to
identify the right
controller by first assigning it (to no.20, as stated
above) and then
record while I tweak
the rotary knob of the cut off. It doesn't record
anything.

2. I can click on the value of the midi clock and
change it, but after
that, it's not
possible anymore to type a change. Same goes for the
Coarse function in
the different
synths. I'm able to change it once, but after that I
cannot type it
anymore and need to
use the rotary knob.

3. I cannot always set my delay time with the Dual
Delay S or Delay S fx
module. I can
change it for some time, but after a couple of
changes, the module refuses
to put it on
e.g. 1/2T or 1/1

4. Lastly, but definitely not the least, I have
several problems with
recording. I
understand I cannot just bounce my synths to an audio
track in Cubase. I
do think this
is a big flaw, as this would save me a huge amount of
time. But anyhow, I
have to use
the merge function, which I do. The problem, however,
is that when I use
XTC fx while
recording (including the delay function within a synth
like the
Lightwave), I get serious
audio clicks. I do NOT have these clicks during
playback, though! I have
tried to
change my ULLI settings, but they don't seem to affect
this. On the
contrary, when I
put my ULLI on the highest latency value, I get too
much latency to record
properly
(definitely more latency than the 25ms which is being
said, if one
considers that only
from 40ms on, latency is audible for the human ear and
I hear some clear
latency at
25ms - and I don't have superears or something like
that). Please let me
assure you
this is a huge problem. If I want to record everything
to a single audio
track to put
things on CD, I cannot include XTC effects without
having clicks, unless I
use an
external device to record the thing and then pull the
soundfile back
in...not really an
elegant and user-friendly solution, hey?
A second problem which occurred recently, is that I
try to record a midi
track, but VST
says the recording is too short to use it. When I
record the exact same
thing a second
time, there doesn't seem to be a problem.
Thirdly, I have a question: is it possible with the
merge-function to
record more than
one midi-track at a time, as to record all midi-tracks
to one audio-track
at once, or do I
really need to convert all my midi tracks to audio
seperately before I can
make a final
single audio file?

To sum things up, I'm very happy with the sounds the
Pulsar produces, but
I think it' s
one of the most user-unfriendly pieces of equipment I
have encountered in
my life.
The fact that the manual is not all that great and
hardly mentions the
XTC-mode of the
Pulsar II might have something to do with it. All I
know is that this card
has already
given me more headaches than joy, which is not my idea
of musical
pleasure...

Especially the recording-troubles are a pain in the
@rs# (pardon my french
:wink:. Is it
possible this problem relates to my OS? I have heard
from several people
that ME is
not the most stable system, but still...

There is a little thingie, though, that I read in a
post of at0mic and which might explain some of my
problems. The passage is the following one:

---
From SFP on, you can't set XTC project properties in
Cubase. Open SFP, and open
SFPAppXTCAppXTCProject.pro
You can set ULLI, IO's, midi etc. here.
---

Hmm... in the Asio control panel with the audio setup
option in Cubase, I can set IO, ULLI, etc. but the pic
at0mix refers to is something I didn't know you had to
use in order to run XTC mode properly... Can someone
explain me the meaning/importance of this and how I
should set things up in order to have as few problems
as possible?

Cheers,

Therm.
User avatar
at0m
Posts: 4743
Joined: Sat Jun 30, 2001 4:00 pm
Location: Bubble Metropolis
Contact:

Post by at0m »

1° You have to set ULLI for XTC as for OS mode, in the cset.ini. Gonzoft pointed me to the page at CW's list
Under [XTC-config], add the line "intBlkSize=x" so it looks like

[XTC-Config]
intBlkSize=256
DirectPlayO...

with:
x=512->13ms latency->Cubase shows plugins latency of 1154
256->7->642
128->4->386
64->3->...


2° Tip, to record every track at once: Select Master Mix Out, in Cubase, and set it to port 'Merge' instead of ie. 'Analog Out'.
Dolphin
Posts: 81
Joined: Sat Mar 23, 2002 4:00 pm
Location: Germany, Munich

Post by Dolphin »

I tried that on my system (XP with Cubase SX) and found out:

1. If I bounce a single instrument (Pulsar or VST or Sampler ...) without (!!!) any effect, it works just fine. Perfect sound.

2. If I bounce a single instrument with a Cubase or DirectX-effect, it works fine too. Perfect sound again.

3. If I bounce a single instrument (or the whole mix) with just one Pulsar effect (insert or send) I get serious clicks, drops, crackling, etc. It sounds like heavy stuttering. The stuttering is about twice as loud as the original signal. I used the Merge-Out to do this.

I never did bounce any instrument or mix before, so I did not encounter this before. But after this experience I wonder if there is a major bug.

Can you check this out, please?

Thanks,
Uwe
therm
Posts: 6
Joined: Sun Oct 13, 2002 4:00 pm

Post by therm »

I have mailed the same list to the support service of Creamware, but reading the users comments, customer service by Creamware is not that bright at all. I do think this is a major flaw and it should not happen! The only way to record a midi track to audio with XTC fx would thus be the use of an external device with the additional analog 'detoriation' of the signal if it's not a digital device.

My friend has a Pulsar XTC and he has bounced already a Creamware synth using the export function (which is obvious, as he can't merge as far as I know) and with him it's working fine. Now why the hell wouldn't that be possible with a Pulsar II card?

Sad things happen with these cards. They create awesome sounds, are budget friendly, but a pain in the ass to learn and work with. Have you noticed how the problemsolving forum is the most visited of all? And no, it's not a small difference with the second in number of posts...

Anywayz, if I receive something, I will notify you and everyone else through the board.

Cheers for taking the time to read the whole list I posted!
therm
Posts: 6
Joined: Sun Oct 13, 2002 4:00 pm

Post by therm »

Okay, I received a mail from Ingo Raven at the Creamware support center. Here's his answer to my question.

1. The reason why I couldn't change the controllers, is because I wasn't able to send a controller live through a midi keyboard. I got myself a midi keyboard now and everything seems to work fine.

2. Apparently, this is some sort of bug. Ingo has forwarded it to the right people to take care of it.

3. Not all note values are possible... Hmmm, I won't go into his answer, coz' I don't really get it. Or to say it otherwise, Ingo didn't really get the situation which I meant. Which is no big deal, as I haven't encountered the problem since.

4. Set the PCI Latency Timer to a higher value (128 or 255). If you still experience problems, try different PCI slots or IRQ's.

therm
Post Reply