KVR Audio

The Chase · Post by **The Chase** » Tue Jun 06, 2006 4:18 am

[rant]was working with plugs that have never given me problems on what is probably my best song/project ever...Cloned a sampler channel and the new one loaded all screwy (bursts of random glitchy noise throughout) and when I tried to reload the sample in the sampler channel to fix it I got my windows error sound and an error window with bunch of numbers (access error XXXXXXXXXX) followed by a proper lock-up.

So I restarted and pulled the last saved project thingy out of the trash bin folder, and like the original project file, it's f**ked too, saving it as another project or not (which leads me to believe that whatever the problem's source is, it happened a while before i tried to clone the sampler channel.

The projects will open, but the sampler channels in it are screwy. They reload as glithiness and some of them inconsistantly load the wrong wave files (files that have no simular names).

I'm tired of this. It's like randomly tearing up painted canvases. And nOOOoOOo, this didnt have to happen on stupid crunk-rap drum beat #969546437378 that I make out of boredom...always has to happen on either my heaviest track yet or 7 minute long epics.

I just wish FL6 would work like version 5 without the priority settings and all that (who the hell asked for that?).

Cheers, all. I'm probvably going to export all the mixer tracks and load them in a new project and try to work that way (cock bitch ass f**k barbera bush fellatio is how I feel right now).[/rant]

[friendlier tone] any idea how I could possibly solve this? is there any image line service that debunks funky project files?[/friendlier tone]

The Chase · Post by **The Chase** » Tue Jun 06, 2006 4:23 am

I have the most roller coastery love/hate relationship with FL Studio ever.

Here is the track in case anyone is curious:
www.carothers.info/chase/Rips_f**k.mp3

koolkeys · Post by **koolkeys** » Tue Jun 06, 2006 4:27 am

Tell us how you really feel.........

grymmjack · Post by **grymmjack** » Tue Jun 06, 2006 4:46 am

Chase; send the FLP with your official bug report to IL. They can't fix what they don't know is broken, etc.

This of course assumes it is a bug with the software

I dunno though. What plugs are in use?

The Chase · Post by **The Chase** » Tue Jun 06, 2006 5:00 am

grymmjack wrote:Chase; send the FLP with your official bug report to IL. They can't fix what they don't know is broken, etc.

Every time I've gone to IL with a problem they've looked at the diagnostic results and the error windows and they basically went "huh, that's odd" and then disappear out of the thread. FL6 just doesnt like my computer. I take hardcore care of my computer. I keep my compy cleaner and tighter than a dolphin's anus and FL6 is the only app I've ever had problems with. I might try to go to tech support one last time.

This of course assumes it is a bug with the software I dunno though. What plugs are in use?

To list front-to-back:

Smart Electronix Fre(a)koscope
Smart Electronix S(M)exoscope
Gvst GGain (2x)
Kjaerhus Classic Flanger (2x)
Camel Audio Camelphatfree (10x

)
Buzzroom GeneComp3
Gvst Gclip (5x)
Kjaerhus Classic Compressor (5x)
E-Phonic LOFI (2x)
MDA Bandistro
Tls Saturated Driver (5x)
kjaerhus Classic chorus (3x)
kjaerhus classic delay

All the synths are synth1 except for the ambient noise at the beginning and end of the clip coming from H. G. Fortune's Swamp.

ouroboros · Post by **ouroboros** » Tue Jun 06, 2006 5:26 am

I hate to say it, but I bet the offending plug is TL's Sat. Limiter or the MDA distro: I've had odd problems with TL's stuff since the update, and froze on the band distro.

arguru · Post by **arguru** » Tue Jun 06, 2006 5:37 am

That's like VST 37 instances of different without counting instruments... mmm.

I would not be surprised if my computer causes a fission thermonuclear explosion if I attempt to load such stack of VST plugins.

I agree that probably the problem is not FL related.

adamatic · Post by **adamatic** » Tue Jun 06, 2006 5:38 am

This is why you always save with CTRL+N. That way you can keep a series of backups so if you make a mistake or the computer shits on your project you can roll back to the previous revision. Personally I've only lost projects in fl to similar glitches 2-3 times over the years and yeah its usually with projects with alot of shit going on in the them.

You might also want to grab memtest from http://www.memtest86.com/ it could be bad ram or something of that nature thats causing your weirdness. Overheating / bad memory can cause weird shit to happen.

Another thought is that I've personally experienced crashes/instability from using multiple instances of TLS plugs in fl before. You might want to check that out, I've found more than a couple plugs over the years that can take down the host or cause weirdness if you start loading up multiple instances.

Its usually a combination of different problems and murphys law that causes data loss like your describing, ie your computer was running slightly hot from increased cpu of all the plugs running, you were trying to save while the sound was audibly glitching so i'm assuming your computer was lagging a bit, plugins not playing nicely and allocating the same memory as fl is trying to write the save to, solar flares corrupting memory, and big foot all smash into a train wreck together and cause data loss. This is why backing up projects is so important.

Shit, human error is scarier, ie opening up a project and tweaking the mix until it sucks and accidentally saving over the original mix.

The Chase · Post by **The Chase** » Tue Jun 06, 2006 5:45 am

arguru wrote:That's like VST 37 instances of different without counting instruments... mmm.

I would not be surprised if my computer causes a fission thermonuclear explosion if I attempt to load such stack of VST plugins.

I've had more than twice that with more experimental music.

The Chase · Post by **The Chase** » Tue Jun 06, 2006 5:46 am

I've never had a problem with any of the given plugs. I've had problems with MDA's degrade plug-in but never the multibandistro thingie. I've used the Tls saturator on seriously more than 100 projects without flaw. And plug-in problems are usually not like this at all. I can't imagine sampler channel mis-behavior being the product of a bad plug or two.

ouroboros · Post by **ouroboros** » Tue Jun 06, 2006 6:05 am

just reread your post re:sampler channel. Weird.
makes me wonder if it was a bad kernel/cluster on the hard drive the wav was saved on.

Left Headphone · Post by **Left Headphone** » Tue Jun 06, 2006 6:07 am

Well don't switch to Sonar. It crash on me four time tonight. I'm having to move all of my Sonar midi files into FLS6.

The Chase · Post by **The Chase** » Tue Jun 06, 2006 6:18 am

ouroboros wrote:just reread your post re:sampler channel. Weird.
makes me wonder if it was a bad kernel/cluster on the hard drive the wav was saved on.

I so hope not. I dont have any budget for a new hard drive.

Debutante · Post by **Debutante** » Tue Jun 06, 2006 6:39 am

I think it may be GVST's plugin. I had a little problem with the chorus once on a project and later found that all almost all his plugs did the same thing.

MINDYOU, he did a complete plugin update maybe amonth or two ago for the lot, and I haven't had any problems with them since I updated them. So if you haven't gotten the updates within the last four months it could be GVST. I really love his very simple plugins and was glad to be able to continue using them after the updates.

This was my short thread about the GVST problem:

http://www.kvraudio.com/forum/viewtopic ... highlight=

Travito · Post by **Travito** » Tue Jun 06, 2006 8:16 am

back when i redid MIDI's for fun and only knew how to run FL studio 4 with the basic plugins, i pushed over 100 polys on a STOCK, COMPAQ.

talk about killing a computer.

Pissed at FL Studio 6 again