Dubstepforum.com

@Eridu and dididub, thanks a lot, I appreciate it.

how do i pitch vocals up and down without changing the speed (i know you can do it in fruity slicer but im talking about individual samples)? i know the new FL has some vst that does it but im on 9. cheers

In the sampler under the time stretching part of the SMP tab, twiddle the pitch knob.

It's in the manual.

http://www.image-line.com/support/FLHel ... ampler.htm

crunkedxup wrote:how do i pitch vocals up and down without changing the speed (i know you can do it in fruity slicer but im talking about individual samples)? i know the new FL has some vst that does it but im on 9. cheers

load it in granulizerr

nice one for the replies lads/ladettes.

crunkedxup wrote:how do i pitch vocals up and down without changing the speed (i know you can do it in fruity slicer but im talking about individual samples)? i know the new FL has some vst that does it but im on 9. cheers

Alter the pitch knob in the time stretching portion of the sampler window, not the one at the top.

I have a question regarding basslines in fl studio and following the track.

I understand the basics, that on a typical song you just follow the melodies, it sounds fairly good. However, I have sampled a piano melody in via slicer - meaning I just have 'notes' which aren't really related to any 'note' if that makes sense, they're merely just markers. This means I can't attach my bassline to the main melody; as I don't 'know' the main melody, unlike when I don't sample.

I've tried adding the bassline with my kick drums, a technique which has made my bassline sound awful...it just doesn't fit. So what gives?!

Even if it's a sliced up sample they'll still be some kind of rhythm there to lock it in with.

If its not working with the kicks maybe try playin the bass on the offbeat that works sometimes.

Thanks, I know there's a rhythm on the sample, but how do I find it?!

Okay guys, I consider myself to be fairly competent in FL but today I ran into something new. My latest project has managed to fill up the entire memory (all 4 gb). I've never had this happened before, so I tried to clean up in the memory by keeping all the audio on the disk, removing all unused plugins and switching smart disable, but that barely made any difference. Can I somehow see what's eating my memory? I've got a LOT of automation clips, and I made many of them unique, same with samples. I guess this takes up more memory, but can it really be that much? As a result of this my project is beginning to act really strange, any tips on how to resolve this?

Edit: Totally forgot about bridged mode, toggled my 20 or so instances of massive to this and managed to free up some. Anyone know if there are any drawbacks to running them like this? I got a pretty powerful computer, would it be best to run more or less everything in bridged just to free up some memory in FL?

mrdii wrote:Thanks, I know there's a rhythm on the sample, but how do I find it?!

just listen closely to it, loop the sample and just play key bass for a bit while you get a feel for it.

Maxxan wrote:Okay guys, I consider myself to be fairly competent in FL but today I ran into something new. My latest project has managed to fill up the entire memory (all 4 gb). I've never had this happened before, so I tried to clean up in the memory by keeping all the audio on the disk, removing all unused plugins and switching smart disable, but that barely made any difference. Can I somehow see what's eating my memory? I've got a LOT of automation clips, and I made many of them unique, same with samples. I guess this takes up more memory, but can it really be that much? As a result of this my project is beginning to act really strange, any tips on how to resolve this?

Edit: Totally forgot about bridged mode, toggled my 20 or so instances of massive to this and managed to free up some. Anyone know if there are any drawbacks to running them like this? I got a pretty powerful computer, would it be best to run more or less everything in bridged just to free up some memory in FL?

Bounce your synth patches to audio

webstarr wrote:

Maxxan wrote:Okay guys, I consider myself to be fairly competent in FL but today I ran into something new. My latest project has managed to fill up the entire memory (all 4 gb). I've never had this happened before, so I tried to clean up in the memory by keeping all the audio on the disk, removing all unused plugins and switching smart disable, but that barely made any difference. Can I somehow see what's eating my memory? I've got a LOT of automation clips, and I made many of them unique, same with samples. I guess this takes up more memory, but can it really be that much? As a result of this my project is beginning to act really strange, any tips on how to resolve this?

Edit: Totally forgot about bridged mode, toggled my 20 or so instances of massive to this and managed to free up some. Anyone know if there are any drawbacks to running them like this? I got a pretty powerful computer, would it be best to run more or less everything in bridged just to free up some memory in FL?

Bounce your synth patches to audio

It's not cpu power, it's memory. Even when they're not playing the memory is full, so I don't think this helps unless I delete the synth patches after but that's not really an option for me.

http://www.youtube.com/watch?v=mXhjOW0E20s

the "bass" at 0:25 trying to make this in 3xOsc, aint going well. is it possible? sounds simple as anything but cant get it on point.


@Maxxan have you checked for background processes that might be running? had a major problem with that on some windows pc's. although 20 instances of Massive does seem like a lot so maybe it's understandable

crunkedxup wrote:http://www.youtube.com/watch?v=mXhjOW0E20s

the "bass" at 0:25 trying to make this in 3xOsc, aint going well. is it possible? sounds simple as anything but cant get it on point.


@Maxxan have you checked for background processes that might be running? had a major problem with that on some windows pc's. although 20 instances of Massive does seem like a lot so maybe it's understandable

thats a simple sound man, try messing with saw and square waves together, maybe some slight detuning

crunkedxup wrote:
@Maxxan have you checked for background processes that might be running? had a major problem with that on some windows pc's. although 20 instances of Massive does seem like a lot so maybe it's understandable

Yeah like I said it's not my CPU bottlenecking, I got a load of processing power and 16 gb of RAM so the memory in FL caps (32 bit crap) long before I run out of physical memory. So background processes got nothing to do with it, SOMETHING is taking up all the memory in my project but I can't find what. I got a lot of stuff going but running each massive in bridged mode only frees up like 50 MB tops, so it can't be just that. Must be something else, I'm thinking probably re-pitching of some of the samples since each time I do that it cries about no memory. But I don't know how to get around that other than maybe bouncing all the samples post-pitching and then deleting the originals, but that seems a bit tedious and TBH I don't see how a couple of 2-sec clips can eat up 4 gigs of RAM. It's a god damn mystery.

hmm you got any expensive effects plug-ins running? that is a bit of a mystery. let us know if you find out what it is

If you have a series of effects that use oversampling linked together on different channels it tends to to eat your computer in general. Maybe that could be your problem.

Hm, I don't know if they use oversampling or not (got a ton of EQ:s and stuff though so I guess a lot of them do) but I've got pretty messed up effect chains and mixer channels linked together, guess that could be it. Not sure why it would eat memory though, but obviously something is that shouldn't so might very well be that. I managed to free up enough to (probably and hopefully) finish the track, I'll try to keep an eye on the memory bar in my next project and try to figure out when it spikes. God, don't even wanna think about what would happen if it maxes out mid-project. I'm surprised it never happened to anyone else though.

Mah productionz b so next level

Okay, finally figured this thing out. Feeling a bit stupid now tbh, but the culprit was a bunch of HQ WAV audio stems. I was glitching them up pretty good so I had a lot of them as unique audio clips in the playlist to be able to process them separately, but I hadn't used make unique as sample, simply make unique. So I had a whole bunch of 5 minute WAV files loaded, each taking a few hundred MB ram. I bounced them all to samples and then purged my audio. Man it's running smoother now.

So if you're working with big samples, dont forget to make unique as samples unless you plan on using all of it. Helps a LOT.