Clicks and pops on fades.. PLZ make them stop!!! (SOLVED?)

[beautypill]

The pop & click problem is not a problem for me anymore.
Plz read the treat to find the solutions. We´re talking about end and start-FADE pops. Not x-fade pops. X-fade pops occur when not making an optimal edit.

Yes, I have followed the instructions on the thread and so far, so good.

But I'm staying vigilant with close and careful listening, because [historically speaking] the problem has been sneaky and intermittent.

Iti's an unacceptable bug, regardless. You should never ever have to worry about clicks and pops coming into your audio with a professional digital audio editor! There is no setting that should produce that.

I'm glad [kinda] that this happened on my own music and not on a client's work. It's awful and embarrassing.

- c

[toodamnhip]

No to spoil the “yah it’s fixed” party, but I do not have multiplier. or any of the setting mentioned by KUBI and I have always found DPs crossfades subject to clicking after a merge. It is an inconsistent problem but is there nonetheless.

It has long been a work habit of mine to double check ALL merges as a result of this long time inconsistent bug in DP.

They have improved their crossfades significantly in Dp 8 though.
They used to mess up when crossfading over pitch corrections, now they don’t.
So keep up the good work MOTU but this area is still an area of weakness.

[beautypill]

This is completely depressing.

I'm a career-long user of DP and supporter of MOTU --- it's my favorite DAW by far --- but I can't accept this as a foible.

It's a huge, huge problem if you can't trust your own audio editing! You have to scrutinize your merged files now? Talk about anxiety!

- c

[Shooshie]

This is completely depressing.

I'm a career-long user of DP and supporter of MOTU --- it's my favorite DAW by far --- but I can't accept this as a foible.

It's a huge, huge problem if you can't trust your own audio editing! You have to scrutinize your merged files now? Talk about anxiety!

- c

Things come and go. And it's the same for all platforms. Each new version introduces bugs not present before, or brings them back. It's the nature of programming. But there will be future versions. If that is indeed a bug, MOTU will solve it one of these days.

[mikehalloran]

I have always found DPs crossfades subject to clicking after a merge.

I have never experienced this. In fact, before this thread, I had never heard of this issue.

[Pbing]

For what it's worth, I've had this problem commonly in the past and it seemed to me to only occur when I was fading over/between two soundbites who live both in the same sound file on disk.

For example, imagine if you are trying to make a seamless loop out of one section of a performance. You want to fade the audio just past the end of the loop with the audio just prior to the beginning of the loop. One way to do that is to cut out the loop with the pre- and post-roll included, copy it to two adjacent tracks, overlap the ends, and then log fade both sets of ends. This always resulted in clicks for me.

However, I have not tried the suggestions mentioned earlier in this thread w/r/t audio engine settings recently. I'm a little skeptical of those because this really seems to be something about how the fades are 'built' in memory, which as far as I know happens on the CPU/RAM entirely, before the audio hardware gets involved. But who knows really.

Posting just in case this info helps anyone else…