PlanetZ forums - scopeusers.com

trying to figure out how to set up sfp for use with wavelab- simply for wave editing and rendering to .wav

was going through the .pro presets to find one that would allow me to hear playback while in wavelab. Mastering.pro did the job.

had some .aiff samples that i wanted to edit and render to .wav. i could import the file and edit it. however, when i went to render to .wav, after the rendering process (where the new .wav file is displayed in front of the old .aiff) i would get the error "wavelab has encountered a problem and needs to close".

even though wavelab crashed, i could go to the folder i rendered to and view the created .wav file, even play it back.

switch sfp to the sequencing setup, fire up cubase..

figuring everything was ok, i used the King Blue sts creator to create an .sts duplicate of the .wav to use with the sts 3000. when trying to load the .sts file from the file browser, i get the message "file not found, do you want to search for the file?" searching for it found the file, but i could not hear the file playback. i was getting a midi signal into the sampler, had the level all the way up, but could not hear it. other .wavs that had not been rendered in wavelab imported fine, and i had playback.

just as a test, i tried rendering some .wavs to new wave files to see if it was the conversion from .aiff that was causing the crash. it crashed anyway...

i went back to Mastering.pro, and into wavelab. went to preferences and noticed that i was not using the scope drivers. when i switched to the scope drivers for recording and playback, i could no longer hear any wave that i opened in wavelab during playback.

when switching to the scope drivers, how should i configure sfp to hear playback?

will switching to the scope drivers stop wavelab from crashing when it renders?

i hope i explained myself well enough for someone to shed light on the subject...

what version of Wavelab are you using (3/4/demo etc)?

1. Rendering with the 'render' button is independant of soundcard driver as it should be an 'offline render'. Would be a wavelab issue.

2. Learning how to route the signal within SFP yourself using the various modules you can load would clear up any confusion you have using cubase and/or wavelab with SFP.

Cubase would almost always be best used with an ASIO in & out pair in SFP
Wavelab with either a wav in & out (if you will run cubase at the same time this makes it easier) or an ASIO in & out if you'll use wavelab directly for recording & editing independant of another application.

Once you have the i/o modules in place you can specify the number of channels they should carry into/out of your software (if applicable) and then load up the hardware inputs & outputs into SFP and cable cubase/wavelab to your physical outputs as needed, including any mixers & fx in the signal path you choose to use.

thanks for the response-

using 4.0g

i think it may be my sfp routing that was causing the crash. i will experiment with the setup when i get home.