Hi guys,
I'm trying to get Wavelab to see my Pulsar 2's SPDIF input. All it says is available is Pulsar Rec 1, Pulsar Rec 2, or Windows MME.
I have connected the spdif modules (source and detsination) a few different ways with no success.
I'm sure I've had it working, but I can't for the life of me remember, and the manual is a haystack hiding a needle.
Thanks
Rick
Wavelab doesn't see SPDIF from Pulsar 2
-
Funktastico
- Posts: 82
- Joined: Tue Jun 26, 2001 4:00 pm
- Location: Finland
- Contact:
Connect the S/PDIF module in your pulsar project to Wave dest X (or to mixer and the mixer out to wave dest X).
Then you can record your S/PDIF input through Pulsar Rec X.
(X being number the of wave driver).
There's no way you can see S/PDIF input in Wavelab on it's own.
Toni L.
http://www.mp3.com/NativeAlien
Then you can record your S/PDIF input through Pulsar Rec X.
(X being number the of wave driver).
There's no way you can see S/PDIF input in Wavelab on it's own.
Toni L.
http://www.mp3.com/NativeAlien
-
Funktastico
- Posts: 82
- Joined: Tue Jun 26, 2001 4:00 pm
- Location: Finland
- Contact:
Thanks a lot Funk
That's what I has set up - I didn't realise that the Pulsar outputs show up as Pulsar Rec 1 or 2 regardless of whether it's analog or digital. I should have actually tried it out.
So how does the gear pick betwen, say, the analog input and the digital input if you've got them bith connected to the mixer in the project??
That's what I has set up - I didn't realise that the Pulsar outputs show up as Pulsar Rec 1 or 2 regardless of whether it's analog or digital. I should have actually tried it out.
So how does the gear pick betwen, say, the analog input and the digital input if you've got them bith connected to the mixer in the project??
-
Funktastico
- Posts: 82
- Joined: Tue Jun 26, 2001 4:00 pm
- Location: Finland
- Contact:
I've said it before, I'll say it again: RTFM
( = read the **kin' manual )
Wave destinations show up as Pulsar RECs in any recording application. You can't directly record analog inputs, you have to wire them (via a mixer or other ways) to wave destinations inside Pulsar, just like in a "real" studio.
Toni L.
http://www.mp3.com/NativeAlien
( = read the **kin' manual )
Wave destinations show up as Pulsar RECs in any recording application. You can't directly record analog inputs, you have to wire them (via a mixer or other ways) to wave destinations inside Pulsar, just like in a "real" studio.
Toni L.
http://www.mp3.com/NativeAlien
hehe you don't want to know how long the engineer and I spent searching through that annoying set of acrobat CD files....
Found plenty of references to connections which weren't what we wanted, but never found the golden phrase 'Pulsar inputs show up in all recording apps as Pulsar rec 1 and Pulsar rec 2'.
I'm sure it's there - we just missed it each time.
Found plenty of references to connections which weren't what we wanted, but never found the golden phrase 'Pulsar inputs show up in all recording apps as Pulsar rec 1 and Pulsar rec 2'.
I'm sure it's there - we just missed it each time.
Make sure you have virtual-wired I/O Correctly:
Pulsar2 SP-DIF source ---->> Wave DesX
Where X is 1 ~16 (You could have up to 16, just drag-N-Drop more in the project, then follow the instruction to re-Start windows and pulsar project).
Here is you could try to debug it:
1> Monitoring SPDIF: You could possibly monitor the in-coming SPDIF signal by connect it to the Bmixer in parallel with the Wave-DesX. If there is no signal, check the (2)
2> Samplerate Setting: The connection between SPDIF-I/O (pulsar is In and Ext-gear is Out this case), to make sure there is only one master clock setting. It meant that if the Ext-SPDIF-gear is set to master then the pulsar must be set to Slave or other way arround. Of cource they must be matched 44.1/48/96Khz (by default, pulsar is 44.1khz and ext-gear is 48khz). Tip for it is that you can verify the LED's activity in the Sample Rate Setting Window-Dialog: (1) LED is never ON: bad connection (2) LED is Blinking: samplerate is wrong or clock-setting is not sync. properly (3) LED is Completed ON: Good!
3> Conflicted MME driver issue: There could be some reasons that you were having other apps held up the Pulsar REC1 and REC2 drivers, so you might need to add more Wave Des3~16 as discussed earlier or it can be done in the System Property: Input/Out devices = 16, you should see in the Wavelab/MME all Pulsar Play/Rec1~16.
Summary:
Check Samplerate setting and check/add more in the windows and as well in the pulsar project Wave-SrcX/DestX.
Meaning:
Wave-Source = Pursar-Play
Wave-Dest = Pulsar REC
Hope this helps,
Long
Pulsar2 SP-DIF source ---->> Wave DesX
Where X is 1 ~16 (You could have up to 16, just drag-N-Drop more in the project, then follow the instruction to re-Start windows and pulsar project).
Here is you could try to debug it:
1> Monitoring SPDIF: You could possibly monitor the in-coming SPDIF signal by connect it to the Bmixer in parallel with the Wave-DesX. If there is no signal, check the (2)
2> Samplerate Setting: The connection between SPDIF-I/O (pulsar is In and Ext-gear is Out this case), to make sure there is only one master clock setting. It meant that if the Ext-SPDIF-gear is set to master then the pulsar must be set to Slave or other way arround. Of cource they must be matched 44.1/48/96Khz (by default, pulsar is 44.1khz and ext-gear is 48khz). Tip for it is that you can verify the LED's activity in the Sample Rate Setting Window-Dialog: (1) LED is never ON: bad connection (2) LED is Blinking: samplerate is wrong or clock-setting is not sync. properly (3) LED is Completed ON: Good!
3> Conflicted MME driver issue: There could be some reasons that you were having other apps held up the Pulsar REC1 and REC2 drivers, so you might need to add more Wave Des3~16 as discussed earlier or it can be done in the System Property: Input/Out devices = 16, you should see in the Wavelab/MME all Pulsar Play/Rec1~16.
Summary:
Check Samplerate setting and check/add more in the windows and as well in the pulsar project Wave-SrcX/DestX.
Meaning:
Wave-Source = Pursar-Play
Wave-Dest = Pulsar REC
Hope this helps,
Long
<font size=-1>[ This Message was edited by: LHong on 2001-11-14 13:35 ]</font>On 2001-11-14 12:20, Chadwick wrote:
hehe you don't want to know how long the engineer and I spent searching through that annoying set of acrobat CD files....
Found plenty of references to connections which weren't what we wanted, but never found the golden phrase 'Pulsar inputs show up in all recording apps as Pulsar rec 1 and Pulsar rec 2'.
I'm sure it's there - we just missed it each time.
Chadwick,
It seems that you might need to add more wave-Src/Dest devices in the pulsar project, which might be registered by wavelab/MME. Or filtering-out the wavelab audio-driver-setting that Only use the Pulsar-REC1 and REC2, which is already connected from the pulsar project. Try either way.
Long
It seems that you might need to add more wave-Src/Dest devices in the pulsar project, which might be registered by wavelab/MME. Or filtering-out the wavelab audio-driver-setting that Only use the Pulsar-REC1 and REC2, which is already connected from the pulsar project. Try either way.
Long