PlanetZ forums - scopeusers.com

Hi
It really doesn't take much to crash scope asio. One wrong call and it hangs requiring a sfp reboot. Very annoying when a client is waiting! Does someone have a solution?

eg.
I use Sound Forge 8d and I want to record and playback using asio: very troublesome.

If I open the record window while asio drivers are selected but my last session ended in a 44.1 khz file (either as a result of a previous rate conversion or if there is a 44.1 file in focus from before) then the rec file properties are 44.1/16. Just this one call to sfp asio when it is in a 48k project will crash it. Requiring a reboot.

Another... if I am previewing in the open wav window of sound forge and accidentally hit a 44.1 file when in a 48k session, bang it crashes asio...reboot

sfp asio doesnt like sample mismatches at all!!

Using WDM or microsoft mapper doesnt cause a crash but the sound quality is very poor on the way in recording. If we could record in asio but playback thru the mapper or wdm it would solved but NO app does this.

These hangs also happen in wavelab, logic, vegas, live etc

DEVICE REQUEST: Is it possible to make a sample rate module that will change an asio source output to the project rate and aviod this hanging?

Does anyone have some words of wisdom here? Thanx

I have tried all types of asio destination modules, the same problem. I am currentlly using ASIO2 64 Dest module and recording in SF in 48k/32bit. Running XP and scope 4.5 with sync plate, I tried patching the clock output of the sync plate module into the asio dest module.

i've tried to open and preview 48 khz files from a 44.1 khz session and i've had not problems using nuendo and the application asked me to convert the file.

I know that soundforge is not that good with asio drivers and it could be the real problem.

When working in digital world, there must be one only samplerate source for all cards you are using and the software must be synchronized with the card's word clock.

There are many soundforge 8 users with problems related to asio, so i suggest you to switch to another application.

Best Regards

Sal

I'd have to say - keep different rates in different folders, as a rule.

Are you doing film work? Why 48k?

As djmicron said, steinberg apps have no problem with that - my old cubase 5 just plays them at the wrong speed, if i remember.

Anyway, you're in Perth, no? I live near the city, if ya ever need to talk scope, pm me

Hi Wayne
Yes I do film work and even my other music I keep at 48k. I used to use 44.1k but I truley did notice a significant difference.

I figure if the project isn't important enough to master professionally down to 44.1k then my optimaster mastering and sf rate conversions will suffice. I still think dsp and summing sound better at 48k.

If I get it mastered professionally then I provide a 48k/32bit file for them to put through their prism/? da's and high end analog chain. Since it inevitably goes analog, keeping it as highest res is best. Then they capture back at 44.1k and dither.

Yep I'm in Perth...aloha. Will do.

...But there were still asio crashes in Wavelab etc as I said.

Is there really no way of making a device to solve this issue and still use asio?

Cheers.

Not sure why you're using asio in a wave editor - please explain?

i think it's not strictly related to the card's driver, but it should be solved from the software side.

I've tried it with :

nuendo (ok preview, ok open, ok playpack (automatic conversion))

samplitude 8 (no preview, ok open, no playback until samplerate conversion)

bcslaam wrote: Another... if I am previewing in the open wav window of sound forge and accidentally hit a 44.1 file when in a 48k session, bang it crashes asio...reboot

sfp asio doesnt like sample mismatches at all!!

Sorry, but you should *really* be expecting that behaviour. You should work in realtime with only one samplerate, full stop.

As for SF8, I'm not so sure about it's ASIO implementation. We use SF6 via WAV source & destination modules occasionally for recording live sketches & it works flawlessly 98/99% of the time (the other 1-2% we get the occasional unwanted crackle)

it's crashing because you can't do that.

if you change the samplerate or the type or size of the asio modules you must shut down your sequencer or host first.

changing those things with the asio app open will cause a reload of dsps which will effectively pull the chair out from under the app. it's not scope crashing, it's your sequencer and it's an expected behavior(falling to the floor and hurting itself because there's no loger a chair to support it). it's not hard to close and reopen the app to change sample rates, just 2 or 3 minutes out of your life.

or use a function like 'Disable audio' during the operation, like Cubase 5 offers
even then you can't close SFP, you just can change project or ASIO elements in the project.

I use asio instead of wav because I always seem to get stuttering or clicks and pops in wav and I also can notice an improvement in quality.

But the show stopper is the stuttering. It happens 95% of the time for me. I always have a masterverb pro or two loaded. I have 25dsp 3 card system, 1GB ram, 1.7khz cpu, intel 865 motherboard, only other card i have is a nic but there was no activity during (never been a prob with asio and heavy activity), video is nvidia 5600 dual agp. The only function of the machine is to run sfp and record mixes to soundforge. I have all the standard xp tweaks. Separate irqs etc

Anyway much appreciated for your feedback I guess I'll have to stick with asio and its stuborness. I might email sony bout it...fat lot of difference it will make tho ey.

ASIO with Samplitude 9 is stable here, (but I HAVE noticed increase in DSP between Samp. 8.31 and 9).

I got rid of most of my crackles, etc. by upgrading power supply and adding another fan inside the computer blowing directly on the cards - but then I presume you've already done these tweaks.

Try changing all 3 cards to same IRQ?
Add more RAM?

Just some thoughts.

Greg

Sound Forge 8 ASIO implementation in my experience is simply bad.... I've never had problems with the CW ASIO driver with any decently written host. The WAV driver could be a lot better, but that's another story...