Step Sequencer - REALLY bad audio quality???

Patch

I've created a mapping for Launchpad mini for the Step Sequencer. Took me bloody ages.

BUT - the audio quality of the samples when they are triggered is all over the place! Sometimes, the same sample can trigger 4 times in a row, and sound completely different every time.

It's wild. I can't work it out. These are hi quality drum hits from paid for sample packs that I use in Ableton Live all the time. Something weird is going on. Could it be due to the size of the mapping? It's 1000+ lines long…

Still using Traktor Pro 3.

Sûlherokhh

1. Does it happen when you manually trigger the samples via launchpad (and mapping)?
2. Does it happen when you manually trigger the samples via GUI+mouse or any other way?
3. And finally, does it happen when the samples are automatically triggered after setting a sequence/pattern and having it active?

If 1) is true and 2) & 3) are not, it may be the mapping.

@Stevan: You have the most experience with really big mappings of anybody i know. Has this happened to you before?

Stevan

I would also close Ableton or try to delete Lunchpad from the Remote Scripts folder if you use Ableton alongside Traktor. Performance should not be affected no matter how many devices or commands are in the menu though. Not even if you have 100K commands (try duplicating any existing bigger mappings)

I have Launchpad Mini MK3 and I know it defaults to Ableton control once the Live is opened no matter what app you used it with before that. Also check for multiple ports and test both options, mine has two inputs and outputs for MIDI. Not sure if MK2 is the same deal?

Patch

1. Does it happen when you manually trigger the samples via launchpad (and mapping)?

No it does not.

1. Does it happen when you manually trigger the samples via GUI+mouse or any other way?

No it does not.

1. And finally, does it happen when the samples are automatically triggered after setting a sequence/pattern and having it active?

Yes, it does. 😢

I’m only running Traktor. Live is not open. Looks like the mk2 only has one input and one output port.

Something very odd is going on.

Sûlherokhh

Which version of TP3 are you using? So we can try to reproduce. The good news is that it's not your mapping or your launchpad! :)

Patch

3.4.0 (237).

It shouldn’t be the mapping. I remapped the official F1 Step Sequencer mapping…

Sûlherokhh

Perfect. I got the installer in my archive and have a go at it. I'll use one of the NI sequencer remix sets to test in a bit and tell you how it works.

What swing value are you using when the problems happen? Maybe reducing it to zero would be an explanation, if the gridmarker that identifies the sample's start time is a bit off.

Patch

Thanks. I've not changed the swing amount yet.

I'm using paid for samples (by Featurecast) that work fine in Ableton Live.

Sûlherokhh

https://community.native-instruments.com/discussion/comment/174055#Comment_174055

I'll be installing 3.4 in jamming with the step sequencer on various settings. Will get feedback afterward. Do you have all samples set to trigger type 'latched' and as one-shots?

Patch

Yes sir, I do. 😀

Sûlherokhh

https://community.native-instruments.com/discussion/comment/174524#Comment_174524

So far i had no trouble with the NI step sequencer remix set samples. Do you have trouble with all samples or with specific samples? If it's the latter, would you mind uploading the troublesome samples in a pm to me so i can test those specifically?