Sonar & Wavelab Q

  • Thread starter Thread starter ChorazaiM
  • Start date Start date
C

ChorazaiM

New member
here's the scenario : I record a mono wav in Cakewalk. If I then send this wav to Soundforge (via the tools dropdown) and convert the wav into stereo, it renders the stereo wav as the same temporary file, allowing Cakewalk to import this back without problems - but when I try to do the exact same thing in Wavelab, it generates a new temporary file which isn't linked to the original as far as Sonar is concerned, hence when I flip back to Sonar, it doesn't ask about loading any changes as there are none. I can't be the only person in the world (and hopefully not the only one on this board) using both Sonar & Wavelab combined - so does anyone have a solution to this?
 
ChorazaiM - I'm not at my DAW now, so I can't check this out. However, I think you need to save the modified file in Wavelab first. After that, when you exit back to Sonar it will notify you of a change to the file and ask if want to use the modified file.

At least that's what I remember. Let me know if that doesn't work.
 
dachay2tnr - actually, that's how I discovered this *doesn't* work ;] I would send the (mono) file to Wavelab, use some stereo effects filter, it would render a new wav, and I would then save it. Problem is, when I flipped back to Sonar (after saving both waves), it didn't notice any changes to the original wav as Wavelab was working on a copy of that file - at least, that's my only explination of why it wouldn't work, whereas it works fine in Soundforge which actually converts the same wave to stereo versus generating a new wav). It sounds like you've gotten this to work though - does Wavelab also generate a new wave file on your end, or does it render the effect to the same temporary file? The scenario you describe below with saving the wav and then Sonar prompting you to use the modified versions *does* happen when i work in Soundforge - just not in Wavelab :/ Excuse any typos btw - damn hot here today so I can't think/spell straight...
 
y would u wanna go back to Sonar after exporting to wavelab...its supposed to a "Mastering" Program hence the final step...y cant u do the minor efx in Sonar? or is it because the efx u want are only available in wavelab?...i'ma try it out anyway and see if i can get it to work
 
Choraz - Sorry, the answer I was giving you was for general editing using Wavelab. Now that I've had a chance to try it, I see what you mean. However, it is appears to be specific to the mono-to-stereo conversion you are trying to do.

If, for example, you process the clip in another way - say normalizing or pitch correction - Wavelab will apply the change to the open file. Then when you save it and go back to Sonar you will get the "file changed" message.

However, as you said, when processing the wave from mono to stereo, Wavelab actually creates a second file. Since the original file has not been modified, you don't get the "changed file" notice when you return Sonar.

Can't help you out, except to confirm that mine is working exactly like yours is. However, it seems to be just for that particular process. Other edits in Wavelab behave as you would expect them to.

A suggested workaround would be to save the "second file" (stereo) and then import it into Sonar using the File -> Import Audio command. It's an extra step - plus you have to line it up - but it should work.

Teacher - Wavelab can serve as a wave editor in addition to being a great Mastering program. It has some features and functions you can not find in Sonar (such as a drawing tool which allows you to edit the actual waveform to remove a glitch for example). You would in this case use it to edit a clip within a Sonar track, and then return to Sonar to finish mixing. They work well together, and Wavelab actually appears on the Tool menu of Sonar. You just highlight the clip, and use the menu to launch Wavelab with the clip already loaded.

Once you have finished mixing your project and export a final stereo wave file, you can use Wavelab to master it. Here, of course, you would not want to return the file to Sonar.

PS I don't work for Wavelab (or Steinberg); however, any renumeration would be gladly accepted. :)
 
Thanks dachay2tnr - at least I know this isn't something specific with my system now. I've tried looking for some sort of option / setting in Wavelab to force it to generate within the same temporary file, but so far no luck. In the meantime, I'll stick to my current work around which is to apply the effect, save the wave seperatly, and then to avoid having to try to lie it up perfectly in Sonar, I simply re-send the original file to Soundforge, which I then convert to stereo and paste the new versions into - an extra step, but easier (IMO) than lining things up perfectly. Oh well - it's too bad, as I'm dump Soundforge completely if it weren't for this one particular "feature" (well, that and the fact I like Soundforge's normalization quite a bit)...thanks for your replies, and excuse any and all typos ;]
 
any renumeration would be gladly accepted
Sorry, that was meant to be remuneration (MONEY!).

I agree with you, Choraz. I very much prefer Wavelab to Sound Forge and don't really see the need for both. However, every program tends to have a couple of features that are great. For example, the Wave Hammer in SF beats anything that comes with Wavelab (however, it doesn't beat the Waves L1 :) )

BTW, I was able to find a way in Wavelab to convert to stereo without creating a new file. If you do a Save As of the clip in Wavlab, you will see that you can change File Properties from Mono to Stereo (as well as the bit and sample rate). However, even if you save it under the same name, it still has no effect on the clip within Sonar.

Sounds like you just can't get there from here.
 
Back
Top