i cant hear anything!
i use my pulsar already for some months but all suddenly (after (de-)installing some programs) my card doesnt make any sounds anymore. even a clean OS with fresh installed pulsarsoftware didnt work.
i use the pulsar midi source, a synthie and the analog out. midi works, the output too.
so... what could be the problem?
i really need help, it's frustrating
i use the pulsar midi source, a synthie and the analog out. midi works, the output too.
so... what could be the problem?
i really need help, it's frustrating
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
Tried a lot of presets in the Poison? Check the volume button on the Poison as well
I don't have it. Maybe there's something in there that doesn't compute but I don't think so( a synth is a synth is a synth...)
Have you tried other synths?
<font size=-1>[ This Message was edited by: paulrmartin on 2002-01-03 10:38 ]</font>
<font size=-1>[ This Message was edited by: paulrmartin on 2002-01-03 10:39 ]</font>
I don't have it. Maybe there's something in there that doesn't compute but I don't think so( a synth is a synth is a synth...)
Have you tried other synths?
<font size=-1>[ This Message was edited by: paulrmartin on 2002-01-03 10:38 ]</font>
<font size=-1>[ This Message was edited by: paulrmartin on 2002-01-03 10:39 ]</font>
modular, poison, inferno... all quiet, the volume is up though.
ok.. maybe midi IS the problem; i routed pulsar midi source to sequencer dest, then sequencer source to synthesizer. cubase says it gets a signal (the red "in" bar flashes) and after recording and playback a miditrack the green bar flashes, but i cant see anything when i want to edit the midi track.
aah! i got the problem: i cant record midi! but why? the midi monitor, even vst receives signals (synthie is ok, it reacts when i edit and play a midi track via mouse in vst)
<font size=-1>[ This Message was edited by: musquash on 2002-01-03 12:09 ]</font>
ok.. maybe midi IS the problem; i routed pulsar midi source to sequencer dest, then sequencer source to synthesizer. cubase says it gets a signal (the red "in" bar flashes) and after recording and playback a miditrack the green bar flashes, but i cant see anything when i want to edit the midi track.
aah! i got the problem: i cant record midi! but why? the midi monitor, even vst receives signals (synthie is ok, it reacts when i edit and play a midi track via mouse in vst)
<font size=-1>[ This Message was edited by: musquash on 2002-01-03 12:09 ]</font>
- paulrmartin
- Posts: 2445
- Joined: Sun May 20, 2001 4:00 pm
- Location: Montreal, Canada
-
- Posts: 2464
- Joined: Tue Jun 05, 2001 4:00 pm
- Location: Warsaw to Szczecin, Poland
- Contact:
hi,
AUDIO:
Forget about cubase for a while - try to connect your Poison out through any mixer (say, micromixer) and watch the level-meters. If the signal is present it means there is something wrong with your sound drivers (if you have a PC Ican't help you in that matter because I'm a Mac user and I know it's more complicated to get Pulsar audio driver (to update it or just to install) to work properly on a PC than on a Mac.
MIDI:
And once more, Cubase is different on Mac and PC but I think our friends here would help you better if they knew your set-up details: what cubase, what mobo, ram, win, etc. If you say the red bar flashes - try to discover (using midi monitor module) what kind of midi messages go to cubase and go from cubase to your synths. Perhaps there is something wrong with your midi controller (you moved a slider, changed configuration or so in the same time you clean-installed pulsar? Sometimes the most stupid things happen to an advanced user so try to notice it
AUDIO:
Forget about cubase for a while - try to connect your Poison out through any mixer (say, micromixer) and watch the level-meters. If the signal is present it means there is something wrong with your sound drivers (if you have a PC Ican't help you in that matter because I'm a Mac user and I know it's more complicated to get Pulsar audio driver (to update it or just to install) to work properly on a PC than on a Mac.
MIDI:
And once more, Cubase is different on Mac and PC but I think our friends here would help you better if they knew your set-up details: what cubase, what mobo, ram, win, etc. If you say the red bar flashes - try to discover (using midi monitor module) what kind of midi messages go to cubase and go from cubase to your synths. Perhaps there is something wrong with your midi controller (you moved a slider, changed configuration or so in the same time you clean-installed pulsar? Sometimes the most stupid things happen to an advanced user so try to notice it
Have you got midi thru enabled in Cubase?
Is the synth midi track (in Cubase) sending on Creamware Midi Out 1? Is it the active track?
Is the synth (in Pulsar) receiving midi? Is the channel set to omni?
That's all I can think of for now - we should be able to get this working.
/dave
<font size=-1>[ This Message was edited by: dbmac on 2002-01-03 13:34 ]</font>
Is the synth midi track (in Cubase) sending on Creamware Midi Out 1? Is it the active track?
Is the synth (in Pulsar) receiving midi? Is the channel set to omni?
That's all I can think of for now - we should be able to get this working.
/dave
<font size=-1>[ This Message was edited by: dbmac on 2002-01-03 13:34 ]</font>
@dbmac: yes, yes, yes, yes and yes
i used midi monitors at pulsar midi out and seq. midi out, both receive same values. creating a midi track in cubase to "simulate" my keyboard sends same values, too. so it's.. confusing
btw: the "midi learn" function works well; i am able to use the midi controller on the keyboard to manipulate the synthie
i used midi monitors at pulsar midi out and seq. midi out, both receive same values. creating a midi track in cubase to "simulate" my keyboard sends same values, too. so it's.. confusing
btw: the "midi learn" function works well; i am able to use the midi controller on the keyboard to manipulate the synthie
It's starting to look like an audio problem -like Samplaire suggested, try connecting a small mixer to the synth output to check for audio signal.(I use the Channel.dev for inspecting audio signal flow - tiny, minimal connections/dsp). If there's audio activity inside Pulsar, well you're just about there.
Just for reference, does Pulsar produce any audio from any other source - wave or asio?
/dave
Just for reference, does Pulsar produce any audio from any other source - wave or asio?
/dave
yes, other sources work (at least wave or the background project), the synthies work, too - just not with my keyboard.
i dont get a signal at the mixer (the volume meter)if i try to use the keyboard, but i DO get a signal if i route a midi track (made with mouse and this editor) from cubase to midi-in of the synthie.
i dont get a signal at the mixer (the volume meter)if i try to use the keyboard, but i DO get a signal if i route a midi track (made with mouse and this editor) from cubase to midi-in of the synthie.
oh, i didnt try vsti's yet... ok here we go
no, vst makes the same problem: keyboard is recognized but has no effect, only a pre-edited midi track affects the vsti's
if i directly connect the pulsar midi source with the synth midi in, then the orange lamp (right beside "omni") reacts, but no sound at all...
no, vst makes the same problem: keyboard is recognized but has no effect, only a pre-edited midi track affects the vsti's
if i directly connect the pulsar midi source with the synth midi in, then the orange lamp (right beside "omni") reacts, but no sound at all...
Hope you remember the difference between "Pulsar Midi Source" (hardware midi port on your Pulsar) and "Sequencer Midi Source" (software midi driver)...? If you don't get audio at the mixer, it seems to be a midi problem, or a corrupt Poison maybe (try redownloading from "Creamware - My Page" on http://www.creamware.com)
poison was just an example, it could also be any other synthie.
yes, i know the difference between pulsar and sequencer.
i will try the gameport for midi later and new midi-cables next week or maybe not... i just got an error message after booting that pulsar couldnt create the background project because it cant find pulsar midi source. maybe i have a buggy installation (though i dont think so)
yes, i know the difference between pulsar and sequencer.
i will try the gameport for midi later and new midi-cables next week or maybe not... i just got an error message after booting that pulsar couldnt create the background project because it cant find pulsar midi source. maybe i have a buggy installation (though i dont think so)
Pulsar's OS is very easily corruptible, especially if you've installed any plugins using *.oxe files, or even placing *.dsp files into the directory. Matter of fact, every time I install a plugin, whether third party or CW shop, I have to re-run the latest installation to repair Pulsar. This has occurred literally dozens of times, going back to version 2.
I just bought and installed the PsyQ plugin, and after a "successful installation" the same thing happens - Pulsar shows weird behaviour, asks for registration for things like the Micro Mixer (?), displays strange error messages, becomes unusable. Re-running v3.01 fixes it. I've never encountered a bad midi source before, but whenever Pulsar exhibits any strangeness I go for the reinstall. I'm amazed I don't see more reference to this peculiarity in these forums, it couldn't be only my problem. I've had this happen with Pulsar on three different computers and numerous clean Win98 installations.
Try it.
/dave
I just bought and installed the PsyQ plugin, and after a "successful installation" the same thing happens - Pulsar shows weird behaviour, asks for registration for things like the Micro Mixer (?), displays strange error messages, becomes unusable. Re-running v3.01 fixes it. I've never encountered a bad midi source before, but whenever Pulsar exhibits any strangeness I go for the reinstall. I'm amazed I don't see more reference to this peculiarity in these forums, it couldn't be only my problem. I've had this happen with Pulsar on three different computers and numerous clean Win98 installations.
Try it.
/dave