|
help me, I'm desperate... Albino 2 kills my sound output
|
View this Thread in Original format
| cybernetica |
Hiya,
I've been working on a new track with multiple instances of Albino (and lots and lots of FX plugins) in FL Studio 5. It has CPU loads of 70-90% and higher, but that's kinda usual for my tracks.
Anyway, when I'm playing back that tune in FL Studio, everything is fine, until it reaches a dense layering of Albino sounds. Then it suddenly "pops", the levels turn red (= maximum) and then the audio stops. Although the track is still playing, I cant hear anything now anymore.
Exactly the same happens when trying to render the track! When rendering is complete, I'm getting a wav/mp3 file with like 2 minutes of the track, then the "pop" sound, and then I get 8 minutes of silence.
I often have this problem with Albino as CPU load gets heavy and the Albino sounds get much more layered and complex. Also, Albino reacts very sensitive to certain knob tweakings. This "sound output killing" seems to happen rather at random, I cant really locate whats the reason for this.
Do I have too many instances? - i have reduced the number of albino plugins to 2. Thats the minimum, I need these sounds, they are necessary to make the track breath, and I cant use any other plugin for them, not at all. I tried to reduce the complexity of the Albino sounds already: less waveforms, FX, and LFO action. But nothing helped me here...
Bouncing to wav? - That is possible, but since there is some complex LFO action and automation on the sounds, rendering only a few bars would result in repetitiveness. If I'm trying to render the whole tracks channel output to wav (would be a nice 100 megs wav file)... guess what... I'm getting again like 2 minutes of the sounds, and 8 minutes of silence.
What else can I try?
I think this track I got is really good and I'm gonna send it to labels... thats not the point here of course but this track is so damn important to me... please help me, somehow :/ |
|
|
| djlogik |
| I wish I could help you out, but I'm going to post to bump the thread for you. |
|
|
| armanivespucci |
| Weird problems like this frequently have to do with your audio settings. For instance, changing from ASIO 24 bit to 16 bit as my sound driver once saved one of my tracks- I just had to cleverly bounce half of the entire track to audio and then re-import it to finish the song, since my entire computer was shutting down and restarting every time I opened the track in Fruity. I changed the driver back to 24-bit for export, rendered the whole thing, and voila, it worked out fine. |
|
|
| cybernetica |
Thanks. Seemed to be a problem with the ASIO driver too... However I tried to change my sound driver too, but it didnt help me. 22Hz, 44Hz, either way, it didnt help.
However I seemed to have found a solution for this. I deleted all channels except ONE albino channel, deleted all FX channels, then I bounced the complete Albino channel output to wav, and it worked that time. Not really locating the problem, but at least I can carry on now. :) |
|
|
| 4am |
| This has happened to me a few times. Usually when I was overloading a signal (a harsh noise would play like a blast of air and then my meters would 'peak out'). It usually happened when using ALOT of instances of the same plug-in at the same time like you're talking about. To fix it, I'd just mute some of the plugs on the FX channel that was 'over-loading' and continue my work. :) |
|
|
| GreenLight |
| Bounce to audio ... audio tracks do not use nearly as much CPU load as lets say the same sound pumped out from a certain VSTi in real - time in MIDI . |
|
|
| The Drow |
| quote: | Originally posted by GreenLight
Bounce to audio ... audio tracks do not use nearly as much CPU load as lets say the same sound pumped out from a certain VSTi in real - time in MIDI . |
but then it gets too hard to sync. |
|
|
|
|
