FL Studio 6 Crashes my new supercharged DAW

[Modeler]

Well, isn't THAT special. Given that I've run my Cubase SX2/SX3 exclusively through the 122 without ANY issues, I would say its an FLS issue, not a Tascam issue.

Thanks DD

-B

TBH I'm inclined to side with IL. I E-mailed Tascam about this in January 2005, shortly after the v3.30 drivers were released and made no difference whatsoever. I never received a response, Tascam never updated the drivers again and have since discontinued the unit.

I'll never buy anything made by Tascam / Teac again.

[BERFAB]

So what did you replace it with, if you did replace it?

[Modeler]

So what did you replace it with, if you did replace it?

I haven't replaced it, still use it on the odd occasion (with extreme care). If I open a big project with it selected as the audio device, it more often than not blue screens.

I'm going to revisit this at the FL forum, bearing in mind I never got to the bottom of it. I'll let you know what happens.

[experimental.crow]

i mentioned this early , in the thread , and can't see that you have checked this ...

what sample rate is your card set to ?...
use the cards ASIO panel to determine ...

what sample rate is FLS set to , under audio settings ?...

incompatable settings herein could cause the problem you describe ...

[Modeler]

BERFAB - just a thought but are you plugging the US-122 into a front USB slot (usually extended from the motherboard by a cable) or directly into the back? I've just changed mine to a 'real' USB port and it hasn't crashed since.

EDIT: Never mind, it's just gone again - arse.

[Modeler]

From Buckskin on the FL Tech Support fourm:

This is a known problem with the Tascam drivers. It also affects the US-224 and 428. FLS fixed this in the 5.? release, but it ended up causing more problems for everyone else other than Tascam users, so it was changed back. It's a Tascam driver issue and as I have been in direct contact with the driver developer and they are not going to fix it. All you can do is switch your audio driver to direct sound when loading a large project or one that has sample missing in it and switch back to asio drivers after load. asio4all works to prevent this, but for me it had a whole other set of problems. But you should try it.

This is pretty much as I understood it. For some reason it only causes problems for FL, so it was obviously never a priority for Tascam to fix. Bastards...

Sorry that doesn't help much but it might be worth giving ASIO4ALL a go.

[BERFAB]

From Buckskin on the FL Tech Support fourm:

This is a known problem with the Tascam drivers. It also affects the US-224 and 428. FLS fixed this in the 5.? release, but it ended up causing more problems for everyone else other than Tascam users, so it was changed back. It's a Tascam driver issue and as I have been in direct contact with the driver developer and they are not going to fix it. All you can do is switch your audio driver to direct sound when loading a large project or one that has sample missing in it and switch back to asio drivers after load. asio4all works to prevent this, but for me it had a whole other set of problems. But you should try it.

This is pretty much as I understood it. For some reason it only causes problems for FL, so it was obviously never a priority for Tascam to fix. Bastards...

Sorry that doesn't help much but it might be worth giving ASIO4ALL a go.

DD-
Thanks for the research. I figured that it might be a driver problem and I was wondering if ASIO4ALL might solve it. Good to know that there's a solution.

'preciate the help.

-B