S4 Cue Points 'popping' on release

S4 Cue Points ‘popping’ on release

I’m stoked about my new S4; been working at it for a few days to get the hang things.

One thing I noticed is when I set Cue Points, or ‘Hot Cues’ ~ and retrigger them, WITHOUT the track playing (basically using them as ‘gated triggers’,) they POP when I release the cue button.

Example…
Say I’m doing a beat, and I’ve cued the kick on one, and the snare on another - I DON’T have the track playing, I’m simply going to use the cue points to help me sample the sounds - I press the snare (for instance,) !! It comes in a little late, missing the initial attack, and it POPS when I let go…

Not cool. Anyone else? Perhaps someone could aid me in fixing the issue??
=Z

Sounds like your grid is off. Make sure that the grid lines up at the exact point of the kick/snare

Having snap on will set your cue exactly on the grid so if your grid is off your cue will be off. Since this is happening while a track is not playing I don’t thing quantize has anything to do with this.

Both of you are right - but the problem persists. I’m finding it only pops when there is a ‘tail’ …like reverb in the recording, so when I’m letting go of the button it pops, because the audio is suddenly cutting out. Sadly Traktor doesn’t have a ‘quick fade’ built in to avoid the POP.

I think why it was coming in late, missing the attack, is because the ‘sync’ button was on… if you miss the beat as set by the internal clock, it tries to put you in time (even with quantize off.) I’m not using a reference backup beat track, so I have no idea where the metronome is in time. With sync off, it’s always punchy, never missing the attack - however if you let go suddenly, in the middle of a waveform, it will pop due to the sudden cut off of the audio.

hmmmmmmmm,

you could try and edit the sample in a DAW and make it a “quick fade” in the end, then press the button untill you’re past the fade and you should be fine

It’s one of the first things I noticed when I got the S-4 running. Quickfade should be on the priority list.

Thanks for the idea, but I have one word to respond: boo. That rids the entire idea the S4 was suppose to introduce; spontaneous high quality mixing in a plug and play solution. I’m an advanced audio engineer, and I’m well aware of workarounds I could do in OTHER software. That’s completely missing the point. Sorry dude… I had to dick on you a little. Just a little.

Got the same problem. Can’t it be fixed in the software with an update. I asume NI is aware of the problem…?

I would hope so, but I wouldn’t assume so… you’re absolutely right though, and it’s good news: it would only need a software update as it is not a hardware issue.

Come ooooooon NI - go team go!

turn sync off, make sure your grids are correct, turn snap off. It has to be one of those options

It’s not any of these things - thanks though. I’ve tried all combinations, but as discussed earlier in this thread:

When audio is cut off abruptly it POPS. So when you let go of the cue button in the middle of an audio wave, when the track isn’t playing and you are just sampling; you get a strong popping sound. What Traktor needs is a built in ‘quick fade’ for when the cue button is released.

In other audio editing software: it used to be, you had to do quick fades manually if you cut an audio file in the middle of a wave. Now most of them do that fade automatically to avoid the pop, and save you the hassle. Traktor needs this feature.

Did you or anybody posted this problem at NI?

your sample deck is probably synced to the master clock
so even when no track is playing there is still a beat count happening in the background (turn on the “tick” option and you’ll hear it)
this causes samples to be triggered with a delay or sometimes to be cut off a little bit to match the master clock
I don’t like the way NI implemented that feature, but it is what it is
under the conditions described above, turning off “sync” should help

Increase latency in settings?

I didn’t yet… but that’s a great idea (DJTT is such a great community, this is the first place I came!)

Thanks - indeed that is what I concluded about ‘missing the attack’ of the shots I was triggering. Taking sync off fixed that issue, and of course so did ‘playing to the internal clock’ :stuck_out_tongue:

I don’t think latency has any thing to do with this issue. Thanks though.

Nope, it’s obviously the auto-fade problem and the pop is coming from the sample being cut off at a non zero-point, not from latency issues

This doesn’t happen on the Mac version

Really… I have a MBP, and it is certainly an issue.

Here is a great example ~ when this guy starts playing, he begins by triggering a kick drum: every time it POPS when he releases adding extra (unwanted, and unflattering,) rhythm.

I heard the pops! he doesn’t seem to care, don’t like his style but he gave me some nice ideas :slight_smile: