Dubstepforum.com

so, i've been working on this one project for about a week now. and now just out of nowhere I noticed my kicks weren't on beat. I hadn't touched them in forever, or anything having to do with them, or any of their patterns. It's not the samples, i've tried different ones. I've also tried making new patterns with them. no luck. and the thing is it's ONLY kicks, every other drum is hitting where it should. AND it's not happening in a new project with the same kick samples. i screenshotted and did a shitty ms paint drawing to help explain this.


What is going on!?!?

Check your sampler, mixer channel and pattern blocks

Try a different sample and see if it does the same thing. A sample from a whole different library btw.

checked it all, no luck.

either gonna go ahead and finish the thing and then do the kicks in a separate project or go back to a little older version of the same project which is fine

thanks though guys

It could be that you hit a weird knob or something in the sample window. To test, insert a sampler and duplicate the sequencer layout, mute the strange one and see if they line up. Also, did you inadvertently assign the sample to a mixer track that is using some effect that could cause this?

yeah I thought about that but I don't know what effect could make something hit before it's ever supposed to. the one in the picture i posted is the very first instance of it in the whole song and I didn't do any weird reversed effects or anything.

I'm gonna have to level with ya bud, as far as all the rational explanations go, FL studio does gimp out from time to time with no explanation. An example of which would be a phantom sound that seems to play at a certain point even if your entire playlist is blank, happened to me with a very loud obnoxious gong sample at the start of one of my tunes, was going to treat it and then decided to scrap it, but it still played it everytime the song started even if i deleted the whole playlist wasnt anywhere.

But my point is that, although it is a very rare occurance, FL does have a tendancy to just gimp out without any explanation. Could just be one of those times.

/sigh. first time i've ever had a problem with it. I guess it could be worse right?

on the bright side, I did have another copy of it saved and everything seems to be working, and for whatever reason i'm flying through this tune now that I got over that little bump

@congo jack it was probably a pattern block

has to be somethn in the sampler window or fx

benjaminC wrote:@congo jack it was probably a pattern block

i haven't touched a pattern block since the day fl10 was released

mikeyp wrote:

benjaminC wrote:@congo jack it was probably a pattern block

i haven't touched a pattern block since the day fl10 was released

Ive never used them,much prefer working in the playlist

benjaminC wrote:

mikeyp wrote:

benjaminC wrote:@congo jack it was probably a pattern block

i haven't touched a pattern block since the day fl10 was released

Ive never used them,much prefer working in the playlist

Dont use em either, ah FL is fantastic but it has got a few bugs under the bonnet without a doubt. Thankfully after 10 editions, they finally discovered the utility of an autosave function

benjaminC wrote:

mikeyp wrote:

benjaminC wrote:@congo jack it was probably a pattern block

i haven't touched a pattern block since the day fl10 was released

Ive never used them,much prefer working in the playlist

back in my noob days I didnt even know about the playlist, it was always hidden lol
i'm glad I figured that one out

This is just a graphic fault with some of the newer versions of FL unless you can hear a problem, I think Ive seen exactly what your talking about... stuff youve sequenced in the step looks slightly before or after the line when you look at those little blips in the playlist pattern blocks, right? Yeah seen this, never heard it, and rendered audio was perfectly on time, asked on i.l.'s forum, was told its a graphic issue.

Kinda like why audacity waveforms are 2 different colors on some pc's

benjaminC wrote:@congo jack it was probably a pattern block

or an instance of edison or newtone in slave mode.

ZOOM that shit ALL THE WAY in. Make sure it's on the grid. It could be off by microscopic amount. ( your pattern clips)

This always happens to me...
In the mixer, uncheck Automatic Plug-in Delay Compensation from the drop down menu. Then left click the clock symbol in the kick's channel (right under volume slider and above floppy-disk icon) and click reset.
Stupid FL Studio.