Glitch in audio when capturing to remix deck

Here's the latest I heard from NI on this matter.

Apparently the work-around is "First capture to the loop recorder, then to the remix deck". I don't know what this means. Does anyone else?

thanks for this detailled and well observed report. It is in fact a bug you are experiencing, and it has already been filed to our developers:

TP-11204 "loops captured from track deck get truncated (loops from loop recorder are fine)"

The error description already suggests the existing workaround: when capturing same noise to the loop recorder first, then to the remix deck, NO truncation takes place (so the bug only happens when capturing from a deck).

As soon as a fix for the issue is available, we will provide it in a future update. We apologize for the inconvenience.

 

Ok, trying to stay positive here. At least they acknowledge it and they are working on it. BUT IT TOOK MORE THAN A FSCING *** YEAR *** BEFORE THEY DID.

@canton I haven't tried, I never use the loop recorder, but what they seem to be saying is that you first make a recording/loop to the loop recorder, and from there to the remix decks. This is quite a elaborate work-around, and very cumbersome for users like me (S8) as this controller has no native buttons for the loop recorder. But it could work.

I hope they don't take another year for fixing this.

 

Still nothing... another year & some major updates later. So sad to see that a key feature for me is not working. It really killed a funfactor for me. The worst is: on the d2 there is no way of using the "workaround" .
Just my thoughts after reading the next patch notes today.
I lost hope it will happen soon.

 

How can we get some answers about this?

 

Hi there,

I had the same problem. It can easily be fixed; make sure that your remix deck is set as master when you capture a loop from the loop recorder or deck A/B. Works fine for me this way, check it out. If in some cases, there should still be an artefact/glitch at the end of the loop, you can try to divide it in half and the enoying noise will disappear.

By the way: If you capture directly from deck A/B, I think you have to make sure that the beat grid is set correctly, otherwise you risk to produce artefacts/glitches (because DC is maybe not at 0 at the end/beginning of the captured loop).

Let me know if this worked for you, too.

 

Hi Tierra!

Your solution does not work for me... i don´t work with master decks. I work with master tempo. So this is not my way of getting around it. But thank you for the really good idea. I tried a lot, but that i did not think about.
But anyway´s its a shame that the users need to find a way that software is running as advertised. (which it does not) And the worst is that the manufacturer is giving a solution that does not work with the "flaggships" D2 & S8. There simply are no buttons for the loop recorder... And i don´t want to map that thing... I bougth it so i don´t have to map a single knob. (coming from A&H midi controllers)
If it was possible i would like to give the hardware back for the price i payed.

 

Any update on this in 2.11.x? See also https://support.native-instruments....ds-glitches-pops-clicks-Worked-fine-in-2-1-x-

 

how is the new version? v3

 

Guess what "feature" is in the New Version? Anybody got a guess? No one? xD
I have the same sound glitches in Traktor Pro 3 as they were present in Traktor Pro 2.
I think this is here to stay. Anybody interested in buying 2 D2 with 1 serial for Traktor Pro2
which can be used as a discount upgrade xD

 

Regarding "TP-11204 loops captured from track deck get truncated (loops from loop recorder are fine)"

I chased support for an update with regards both TP 2.11.3 users and TP 3.0 users. After several chases over a period of 4 weeks, this is the final reply I got Friday night:

Dominick @ NI (Native Instruments)​

Oct 19, 23:15 CEST

Hello,

I have been working to get this bug to be looked at but unfortunately, it is a low priority for our Dev team at this current time. They are aware of this issue, but as of right now they are currently working on many other projects. We appreciate your understanding in this matter and we hope to have an update on this matter in the future.

I haven't quite decided my next step beyond finding the email address for Pedram Faghfouri - I have asked once for his contact details and on another occasion how to escalate issues past the support team (whose job I would not wish on anyone). As I got no answer to either question, I'm assuming support are under instructions to not disclose this information.

In trying to run forward with a new paint job for TP2 and a new flagship controller, NI may find themselves no better off because they are failing to address significant issues with existing (and sadly new) products, more people will move away, and their reputation just suffers more. It makes me sad when products go this way due to poor management.

 

Sadly NI is notorious for abandonware-treatment in a rush to constantly shoehorn new features that they will then abandon.