KVR Audio

BERFAB · Post by **BERFAB** » Tue Sep 12, 2006 2:01 am

When loading some projects in FLS 6 on my new really-fast-big-memory desktop pc (Win XP Pro) it crashes on some of the larger projects.

This leaves me scratching my head because the same projects load with no problem in FLS 6 on my little $499 Circuit City special laptop (also Win XP Pro).

BTW, my HUGE honkin' projects in Cubase SX3 run great on the new DAW, so I know it's not the machine.

Any suggestions? Are there known issues/bugs I should know about?

Oh--the DAW uses a Tascam US-122. The laptop uses whatever soundcard came in it.

Thoughts?

Thanks
-B

Hink · Post by **Hink** » Tue Sep 12, 2006 2:30 am

dude I think you might find fl doesn't like the tascam...I know it worked before....but I have seen many 122/fl issues at looptalk

Jason Brian Merrill · Post by **Jason Brian Merrill** » Tue Sep 12, 2006 2:36 am

did this happen with your old pc/122?

experimental.crow · Post by **experimental.crow** » Tue Sep 12, 2006 3:13 am

BERFAB wrote:When loading some projects in FLS 6 on my new really-fast-big-memory desktop pc (Win XP Pro) it crashes on some of the larger projects.

This leaves me scratching my head because the same projects load with no problem in FLS 6 on my little $499 Circuit City special laptop (also Win XP Pro).

BTW, my HUGE honkin' projects in Cubase SX3 run great on the new DAW, so I know it's not the machine.

Any suggestions? Are there known issues/bugs I should know about?

Oh--the DAW uses a Tascam US-122. The laptop uses whatever soundcard came in it.

Thoughts?

Thanks
-B

first thing i would check ...

make sure that the FLS audio settings > sample rate matches the sample rate of your sound card ...

Debutante · Post by **Debutante** » Tue Sep 12, 2006 5:44 am

If your project is large and loaded with plugins, sometimes it's a single plugin that causes the crash. Quite some time ago I had a similar experience and was able to isolate what plugin it was and everything was great after that. I simply started removing my most recent plugin additions from the VST folder until the crashing stopped in order to determine which one was the culprit. Third time was a charm...

Under most circumstances I think you will find in consensus that FL is an extremely stable VST host, even with people who don't really like it. There are some plugins, however that it doesn't seem to like. I can't get Tassman active for very long...

BERFAB · Post by **BERFAB** » Tue Sep 12, 2006 1:34 pm

Debutante wrote:If your project is large and loaded with plugins, sometimes it's a single plugin that causes the crash. Quite some time ago I had a similar experience and was able to isolate what plugin it was and everything was great after that. I simply started removing my most recent plugin additions from the VST folder until the crashing stopped in order to determine which one was the culprit. Third time was a charm...

Under most circumstances I think you will find in consensus that FL is an extremely stable VST host, even with people who don't really like it. There are some plugins, however that it doesn't seem to like. I can't get Tassman active for very long...

So how do I eliminate plugins from the project if I can't open it without crashing?

I do like FLS a lot. It's great on the laptop for sketching out ideas and loops. And, I have never experienced a crash on the laptop with it. But transferring the projects to my main DAW is a big headache.

I should have mentioned that on rebooting the DAW after a crash I will get a message saying that FLS was unable to set to a 44100 sample rate (or something like that). When I go into the settings page for the US-122 (through FLS, not Cubase) I notice that the sample rate actually flickers--I've never seen this behaviour before. WTF?

Also, note that I use FLS quite a bit as a VST in Cubase. So far, no problems there.

And to answer JBM's question, I never used FLS on my old DAW.

Is there a known incompatibility with the Tascam? Is there a workaround?

BTW-I'd check looptalk, but who the heck can figure out how that interface is supposed to work? You've got to be an engineer to navigate their board...

thanks to all for your help.

-B

Jason Brian Merrill · Post by **Jason Brian Merrill** » Tue Sep 12, 2006 2:43 pm

you cant navigate looptalk?

wow.

Hink · Post by **Hink** » Tue Sep 12, 2006 2:57 pm

did yah try unplugging the 122 and opening it?

BERFAB · Post by **BERFAB** » Tue Sep 12, 2006 4:09 pm

Hink wrote:did yah try unplugging the 122 and opening it?

I'm not sure if you're being sarcastic here. Unless there's a big on/off switch on "off," opening it isn't going to be of much benefit.

-B

BERFAB · Post by **BERFAB** » Tue Sep 12, 2006 4:11 pm

Jason Brian Merrill wrote:you cant navigate looptalk?

wow.

I could, but I choose not to. I'm not the only one critical of their interface.

-B

popmoney · Post by **popmoney** » Tue Sep 12, 2006 4:39 pm

So how do I eliminate plugins from the project if I can't open it without crashing?

Hi there
You can move the plugins into another folder which Fl doesn't have access to.Or open a new project and start adding synths and effects and see what might be crashing it.
cheers

Hink · Post by **Hink** » Tue Sep 12, 2006 4:40 pm

BERFAB wrote:
Hink wrote:did yah try unplugging the 122 and opening it?
I'm not sure if you're being sarcastic here. Unless there's a big on/off switch on "off," opening it isn't going to be of much benefit.

-B

no I mean have you tried opening FL with the 122 disconnected and tbh if I were trouble shooting the problem and with the fact crashes most often are hardware related, that would be my first test...no sarcasm intended, but yes I seem to remember a lot of FLs usrers having problems with the 122 and FL before I got fed up with looptalk too...

BERFAB · Post by **BERFAB** » Tue Sep 12, 2006 5:51 pm

Hink wrote:
BERFAB wrote:
Hink wrote:did yah try unplugging the 122 and opening it?
I'm not sure if you're being sarcastic here. Unless there's a big on/off switch on "off," opening it isn't going to be of much benefit.

-B
no I mean have you tried opening FL with the 122 disconnected and tbh if I were trouble shooting the problem and with the fact crashes most often are hardware related, that would be my first test...no sarcasm intended, but yes I seem to remember a lot of FLs usrers having problems with the 122 and FL before I got fed up with looptalk too...

Hink-
That's actually pretty funny. I re-read the posts and clearly I missed what you were getting at, as I was picturing actually cracking open the 122, not FLS.

No, I didn't try that.

Popmoney-
Good suggestion.

Unfortunately, I have a feeling I may just have to switch cards. I'm due for an upgrade--perhaps something that supports USB 2.0. Any suggestions?

Thanks all.
-B

Modeler · Post by **Modeler** » Tue Sep 12, 2006 5:55 pm

BERFAB wrote:Oh--the DAW uses a Tascam US-122.

Therein lies the problem.

I bought a Tascam US-122 and very rarely use it with FL as it's unstable as f**k. According to IL it's a Tascam issue. According to Tascam it's "La la la I'm not listening"...

BERFAB · Post by **BERFAB** » Tue Sep 12, 2006 5:59 pm

Danny Darko wrote:I bought a Tascam US-122 and very rarely use it with FL as it's unstable as f**k. According to IL it's a Tascam issue. According to Tascam it's "La la la I'm not listening"...

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

FL Studio 6 Crashes my new supercharged DAW