XXHighEnd

Hello Peter,

A couple times now using 2.08d,  I've had a burst of high volume static come through the speakers. It seems to happen when playing only one or two songs on a playlist and the noise comes in at about 5 to 10 second after the music starts and scares the heck out of me. I have to quickly turn off the amp and stop XXHighEnd.

The static sound is the same which would happen on XXHighEnd a couple of years ago when repeatedly pressing down the volume to quickly.

I did not have this happen on 2.07.  Do you have any ideas what could cause this?

Best regards,

David

Hi David,

I recall I had this one time maybe 2 months ago. But then it happens maybe once a year to begin with.

I am positive this is because you do something in advance of which you can see or feel it ain't right. Example : Press Stop - change your mind and press Play again within half of a second. This is only an example.

So carefully think what you might have done in advance of this, and tell me so I can look into it.
It should be coincidence but thus may depend on your "workflow". Like you said it yourself from previous times : change the volume fast. I know that if we do this today, sound will stop. Or worse ... O I taught mysef to not change the volume fast. But then this is not necessary any more.

Notice that with Alt-s (see XXOSK.exe and the S on it) the music stops instantly. So always have that on screen (you should anyway), and now you can stop the possible noise as fast as you are yourself.

If you use a quite random SFS number (and not a calculated one for your own reasons) then you can add/subtract 0.1 to.from it. This does matter, as all is relatively fragile inside for things coming together which should not. So if you just changed something regarding (all) these settings, it easily can be bad luck on the combination.

I hope I am clear enough on wanting to solve this, instead of you being able to deal with this ... But it needs the example !

Best regards,
Peter

OK, I just had it myself. This was the sequence :

I played a 24/96 (actually an MQA but I regard this unimportant) which ended by itself because of the end of the album (this could be crucial).

I put on a next album of 16/44.1 and selected 4 tracks (I don't think this is important, but mentioning it just in case).

With my SFS of 0.9 I estimate that the 3rd buffer of that ended up in a burst of noise. But only during the length of that buffer (which should be 0.8 seconds or so (at 705600 samples per second). After that all went back to normal.
Side note : I recognize that it can happen during the length of one SFS buffer size only - for years by now. Also : the shorter/smaller the SFS, the shorter the noise lasts.

I stopped and restarted playback of the same selection, just because I was curious.
Nothing happened this time.
This latter proves to me that it should be related to what happened prior to the issue.

Peter

Hi Peter,

I can't say I have been too interested in trying to replicate this but it has  seemed to only happen when trying to play a 1 to 3 song playlist in Unattended (always Redbook). I have not  had a problem with a full album.

I think one time the static happened at the beginning of the second song in unattended.  Today, I have only been playing albums so everything has worked perfect and btw, I am using your settings with the .9 SFS.

I know this is not too informative, but I wanted to post in case it happens to someone else.

David

Hi David,


If you are sure it was the second track and not just the first, then think (consider) of something in your PC not responding fast enough. But combine this with your experience of the lower SFS setting. So have you had this lower before then this shouldn't be the issue (so let me know what you used for lower for a longer period of time (like weeks)).

Also look at the length of this first track you played; was this considerably longer than average, you can have ran into the situation that too much in the PC fell asleep (not the whole PC of course). And now with the small SFS of 0.9, it does not wake up in time. This should not result in the noise, but by accidental combinations of matters, it could.

Best regards,
Peter

Hi Peter,

Had the same issue of burst of noise now 2 times with 2.08a.
The first time it was 2 bursts after each other. The second time was just one burst.
The second time (I do not recall the first time) the music stopped after the burst.
I just restarted the track and no issues.

It is a bit scary. Any clues on this issue? I have never heard this kind of noise burst before. I know of cracks and other short ticks but this is different.
My SFS is at 2 so not long but also not ultra short. Should it be longer, but the burst will be longer too. Or shorter?

regards, Arjan

Arjan,

Hmm ...

In any event the shorter the SFS the sorther the burst. Coincidentally I changed mine from 0.9 to 1.5 yesterday, so maybe I can recognize it starts to happen to me too (it did once for 2.08 but I have it 1-2 times per year anyway (1 time will be closer to the truth)).

What is your Q1/xQ1 ? (mine is 14/1)

Peter

Hi Peter,

I use the same Q1/xQ1 setting. Changed to SFS 1.5, from 2.

Last 2 days no burst of noise. But it was also more regular listening to complete albums.

It might have to do with using Alt-X and testing different parts of tracks.
Because when it happened I was testing the SQ for different tubes in the power amp. And I did that by playing parts of different tracks of albums. I select a track, use end after track and start unattended play. When the music starts I use Alt-X to get back into the UI so I can use the sliders to set the volume or stop playing. But then again the burst of noise only happens 2 times....... so it is rare and difficult to reproduce.
To be honest I also do not want to reproduce this, because it is scary.
So hopefully when it happens again I remember the scenario that led to this.

Regards, Arjan

Hi Arjan,

Maybe it is not the best idea to cange the volume by means of XXHighEnd in that (Unattended) fashion. So if it happens you you like that only, then we can bet it is that (for your situation). Also, this is never tested of course. Also not by me and as you actually just told, when I'd try 10 times of course nothing goes wrong. So it should be used by a 100 people each day 20 times, and then we'd have a nice test base. But I am afraid you are the only one ...

Regards,
Peter

Just upgraded to 2.08d.  After playing several albums with no issue (all Attended), I just loaded another album and as I started the first track (also in Attended mode) experienced my first "burst of noise" incident.  Short.  I have NEVER experienced this with XXHE in all the years of use.  So my guess is that something has changed with 2.08d.  My current settings are in my signature. 

Not sure if there is something to be done.  I will report if this happens again, and then perhaps try different SFS.

Ramesh

Ramesh, did you all these years play Attendedly so regularly ?

Peter

Peter,

I played in Attended mode a lot, especially when experimenting with albums to see if I liked them or not. 

I think I may have found the sequence that causes the burst--not 100% sure.  Load the album, then select the first track again in the playlist, then play.  Happened twice, and I suspect it is this sequence.

Ramesh

Hi Ramesh,


Can you eleborate on this please ?
So supposed the first track is automatically selected (is it ?), select it "again" would un-select it.

Thanks,
Peter

What I noticed myself yesterday at changing the volume after the GUI has been brought up (Unattended Playback commencing), was that clearly I ended up in another part of the track (maybe only 1 second further or earlier, but not "adjacent" as should). So this already looks dangerous to me ...

Peter

Hi Peter,

Please excuse my ignorance about all this but on other previous versions of XXHE, the burst of noise would only happen for me if I rapidly adjusted the volume in unattended, say if the phone rang or something and I tried to quickly turn it down.

I don't know how you implemented the instant volume and track changes with the new hotkeys, but is there any way they can be related? It seems the trouble happens with only one or two tracks in a playlist and not really with full albums.  Is there a too quick "turn around" which happens during a quick loading of one or two tracks which does not happen when the computer takes it's time loading an album worth of tracks?

By the way, I never received the burst of  noise when adjusting the SFS, even to extremes. I would just get clicks and such.

Hi David - Thank you for your suggestions.

Your mentioned (too quick turn around) could only (theoretically) be related to Unattended; in Attended it's just track per track anyway.

It almost definitely is related to the new Volume (change) setup. And for example, with the really small SFS (like 0.1) the volume change itself hardly works and sound most of the time just stops (as I recall it).

It looks like possibly Ramesh as a way to mimick it. So I seriously hope he can !

Thank you all,
Peter

Hi Peter,

Just had the burst of noise again, 2 times at the beginning of a track. After that the track went on without any issues.

I was running unattended a track from an album. After it stops I selected the last track of the album and started again unattended. The music started and directly burst of noise 2 times with small amount of sound in between.

My current settings are in my signature.

regards, Arjan

Arjan,

a. Do you have the Always Clear Proxy button active (in Settings) ?

b. If Yes, do you (some times) use the [C] button near the bottom of the main screen ?

c. Can you dig up the resolution/sampling rates and HDCD state (possibly MQA state if you are using that) of the last track played and this new one ?

d. Can you describe this more thoroughly for me :


because no track stops unless it is the last track (hence the same you restarted payback for) or you used Alt-K (stop after track), or something else I can't think of.

Thank you !
Peter

Hi Peter,

To answer d.
When I just play one track I always click, stop after track, button below unattended button. So it just runs only one track unattended and after the track has ended the UI comes back again.
So I did that for one track of the album and after that I selected the last track (and because it is the last track the stop after track ended is not needed) and started play again. Then the burst of noise came.

I use the stop after track button, never Alt-K!

Maybe important: I tried Alt-U but music just stopped..... Although Alt-X to go back to UI works fine.

Will look into the other questions this evening.

regards, Arjan

Maybe I was confusing. Alt-K is the same as that Stop After Track button and I really did not put any value in the difference (but good to know now anyway). If we use a remote (and I think we do) we can't even use Alt-K.
Otoh, you could be using the XXOSK and imply Alt-K from there (I do that some times).

Peter

Yes, this is important. Are you using the Coverart Wallpaper ?

And are you using Alt-U all the time, but this one time it did not work ?
or ?

Hi Peter,

A bit late my reaction, but was to busy.
I use now the same settings as in your signature.
And maybe this is another topic.....but.

With coverart Alt-U is working fine both with keys and the XXOSK.

Without coverart the music stops when using Alt-U (Alt-D seems not to work...) both with keys and XXOSK.

But no burst of noise yet.

To answer your question, I was not using Alt-U before, and I never used coverart. Only sometimes.....

regards, Arjan

Hi Arjan,

I am not sure whether I already mentioned it in this topic, but see the Release Notes for how to solve Alt-U and such. So in there, I describe what you just also did ...

Best regards and thanks,
Peter

Thanks Peter,

RTFM for me! We call this a PICNIC, problem in chair not in computer.
I will use no coverart with the xxosk or alt-keys. See if the burst of noise will show again.

Regards, Arjan

Came home from a work trip last night and had just a few minutes to play some music. I loaded the tracks from Abdullah Ibrahim's "Sotho Blue" CD into the playlist area. I grabbed the first track, Calypso Minor (Fantastic if you haven't heard it!) and dragged it to the bottom of the playlist. So track 1 was now the last track which I then selected and hit play. After about a minute I had the burst of noise which scared the sh*t out of me. Until now, I had been playing 2.09 since its release without any issues.

With the burst of noise came the following error message:

"Check File Format
24 bit second stage Crack Detect >455"

The track is 16/44 not hi-res. I was playing with a SFS of 2 at the time. Hope this helps solve this issue.

Brian

Hi Brian - Thank you very much for your description.

Did exactly what you described, but of course nothing.
What seems to recur is that people select tracks one way or the other. And something did change in that area. So I think I start to grasp what could be happening. But still, I do this so often myself.
Great track btw.

And did Ibrahim did the cover design together with Carsie ?
:whistle:
Regards,
Peter

Sure looks like it!

Brian

Hi there,

maybe I can contribute a bit finding the reason for this burst of noise.
I had this problem a few times about one and a half years ago, right after I got my new audio PC, NOS1-a and XXHE running for the first time.
Peter, as I remember, I reported it to you in some emails.
I remember that it also happened with highres files (maybe with 16/44 files too, what I don't remember).

Later on, for some still unknown reasons, I never had this burst of noise problem again for about 16 month. Not even once.

Recently, since about two weeks only, I got it back. It happened 3 times that this burst of noise frightened me, always for just about 1 second only and music stopped playing right after it. In my case it happened when playing a whole album in the e.g. during the 5th track being played.

So, what did I change recently:
1) Mid of September I began using my 3G upgraded NOS1-a. But that's too long ago. Therefore I don't believe that this is the reason.
2) About two weeks ago I installed release 2.9
3) About two weeks ago I changed the Q settings pretty much.

It seems logical that 2) or/and 3) probably have caused the reincarnation of "burst of noise" in my system.

Ad 3): my changes of the Q settings:
My old settings during the 16 month without this problem had been (more or less never changed much):
Q1: between 14x1 and 14x10, Q3/Q4/Q5: 1/1/0, SFS: between 20 and 120, Clockres: 0.5ms, Coustom Filter: High (2nd in the list).

My new settings now are:
Q1: 14x40, Q3/Q4/Q5: 0/0/0, SFS: between 0.7 and 2.6, Clockres: 1ms, Coustom Filter: High (2nd in the list).

The biggest difference between those two sets of settings are:
- Buffer size Q1xQ1x
- SFS

Maybe that helps to find the culprit...
Kind regards
Richard

Thank you very much Richard.

Yes, as I told ... people will have been encouraged by my own lower buffer settings and just like I calculated (in the other topic) how a 30x40 is 85 times larger than 14x1 for that buffer alone, there's a 85 higher chance that something goes wrong - thus minimum, other highered settings left out.

Kind regards,
Peter

Just got this again.  Adding some information hoping it helps, have not been able to reliably reproduce the problem.

Playing with Peter's new settings: Q1: 30/40; Q3,4,5: 1; SFS 120; Clock 15ms; do nothing with cover art

Attended mode.

The sequence was as follows.
- Drag folder over to play list; first track selected
- Hit Play; waited a while, nothing seemed to be happening
- Hit Stop;
- Hit Play again, fairly soon after Stop
- Track begins very briefly; Alert pops up (the Crack 24 alert);
- Burst of noise;
- Album stops;
- Clear playlist; drag folder over to playlist; first track selected; hit Play again; all is well

I must say that now when I hit Play after selecting an album, I always tense up just a bit!!

Ramesh

Dear Ramesh,


Justified. And I set myself to solve it (today).

The culprit is this one :


Meaning : if one doesn't have the "senses" that this may end up in misery, then, well, it will.  :) And btw, this should trigger the alarm bells :


So if I see this, I will think "uh-oh" and next be in control (like quitting XXHighEnd would be the best solution, but which I do not do because I want to run into the issue (learning from it, so to speak).


If it would always be accompanied by this message, I would definitely have solved it soon. But people are telling that they don't see the message (after playback stopped !) so I better don't believe those people or otherwise I don't know where to start. And mind you please, this is completely different from the situation that playback continues after the noise.

Btw Ramesh :


There are two errors in that.  ;)

Thank you for your clear description !
Peter

Edit, Nov 15, 2011 : Mentioned download of XXEngine3-209-X1.rar has been replaced by the X2 version in this post (http://www.phasure.com/index.php?topic=3900.msg42102#msg42102).

Dear people,

I found an issue with the determination of a wrong byte order (this is what causes the burst of noise). And the thinking error (or maybe race-incident) which has been in there is quite unbelievable;

Ever back the analysis of the correct byte order was applied on the more native music data. Later, when more of filtering applied and which processing can all end up wrongly, this analysis was moved more "down" so the filtering processing would be caught just the same. Small problem : the code more down incorporates the digital attenuation. And since the analysis comprises of "detect too high difference values from sample to sample", the attenuation "squeezes" that.

Then I found that the analysis (deliberately) does not work over SFS (Split File Size) boundaries. But, the effect of that was never noticed : the smaller the SFS the less chance too many too high deviating values would be detected. This is hard to explain, but ever back (like 9 years) I determined that more anomalies had to happen in sequence before further playback would be rejected. A kind of : one tick is fine, but not 200 in a row.
*That* idea I now have abandoned;

The version of XXEngine3.exe you find below, trips with a "Crack Detect" message after 3 subsequent relatively wrong samples. This allows one glitch (of one sample !), a next to go back to normal levels, and not more. So if right after this "coming back" a next sample appears to go sky high (for deviation), something is regarded to be wrong and playback stops right away.

Regarding the latter, things vastly changed;
Previously the current buffer (which already could contain wrong sample data) played empty and the next one - the one with the detected wrong samples, was not further offered for playback. Sadly, a buffer can easily play for 30 seconds and even many minutes for "only" 16/44.1 (48) capable DACs. From of now, when the filling of a buffer detects wrong samples, playback is stopped immediately (but it will still depend on some amount of internal buffer). The difference thus is that playback is now explicitly stopped, while previously it played until the main buffer was empty (this is the SFS buffer).

Remark : We will "obviously" see that a 100 people (probably including myself) will have many occasions of the Crack Detect message occuring, while they think it is false alarm. Well, it won't be really, but it depends on how wrong things really are, and we can not know that in advance. What I am talking about is ripping glitches (envision you hear them as scratches) and the Crack Detect routine may trip on that now easily, if only close to the maximum voltage span is covered from sample to sample, and if only that happens 3 times within one SFS buffer. So indeed, when you play at a sampling rate of 705600 and imply an SFS of 30 seconds, then all this time actyally nothing is allowed to go wrong and a poor rip will let it go wrong. Do notice that a poor rip includes scratches on the CD and if these imply mentioned voltage span, then bad luck; playback will stop.

Of course everybody is going to report about their experiences and the tripping can be made less tight. But as we now know, when too loose we are going to hear it and we don't like that.

Anyway, it is good to realize that from 3 dimensions or so, the noise now is attacked and the most important one is the not thinking of the attenution in there; Nothing tripped forever, if only the attenuation was large enough. This also explains the not even occurring of the Crack Detect message, because the anomaly was not detected (in continuous form).

Lastly, when you receive too many stops (with mind you, most probably hardly audible anything at all - maybe a little LP-tick) then before reporting it, you should try to repeat the situation; Is it repeatable "on the second" (you can drag the time slider button to right before the happening, press Pause and next Play) ? then it will be a scratch in the CD *or* a for real too high transient. Is it not repeatable, then you ran into the real thing and the purpose of this topic ...

So let's have it !
Peter

PS: Kill XXEngine3.exe (click blue led in right hand border of XXHighEnd), unzip the below to your XX folder and start listening again.

Hi Peter,

Since 2009, when I first started using XXHE, I have never experienced this burst of sound or crack detect. For the first time after updating Engine3, I got a crack detect msg, on a playlist which I generally listen to at least twice a week.

Call it Murphy’s law!!

Best regards,

Arvind

Hi Arvind,

No no, we need some stronger cases for Murphy's law. Like my own case from yesterday :

I did something, heard something which did not belong, put my hand on my ears - the rest of the family thus doing that too and ... bingo. With a large set buffer somewhere it lasted for 10 seconds or so and I just held on, quickly thinking how in the world this could avoid my newly made "tripping" code. Then music started again and when that played for 10 seconds, the noise started again. There I stopped playback.
A few minutes later Murphy's law told me that where I had my regular share of 1 - 2 times per year, BUT challenging for it with the larger buffer (not yet in 2.09) ... I had forgotten to install the XXEngine3-209-X1 on my own audio PC.

Nice eh ?

I actually also wasted 3 hours of time in discovering myself whether the tripping would be too soon. Which ...
I told you would happen.

So Arvind, I talked about that. Please read back on it and respond adequately because I must solve this if there is something to solve. OK ?
If it really is repeatable I'd even like to receive the track (via FileMail etc.).

Thanks !
Peter

PS: The great thing is that while I intended to test matters on the Audio PC and had switched on my Logging on it, but thus never did any testing over there starting with not even putting the program to it, the Logging remained on and I had log data of the happening. If I can find where it happened of course.

Hi Peter,

The crack detect occurs at the same point (3 attempts). This playlist has 5 tracks totally, from 3 different albums. The first 3 tracks play just fine. Right at the end of the 4th track, just when it is moving to the last track, playback stops & crack detect msg appears.

I tried to reduce SFS from 20/20 to 0.9/120 but the same result.

Sending you the 4th & 5th track by file mail.

Best regards,

Arvind

Arvind - great, thank you.
I am looking into it. When I changed something I will but up a next XXEngine3.exe in this topic (probably today). This will happen as long as needed and after that it will be final.

Regards,
Peter

Today I have got this burst of noise again, scaring loud and this time it didn't stop itsself until I pressed the stop button.
I was playing the same song, the last one in the playlist, like 4 or 5 times before it occured.

Yesterday I had another phenomeon: After selecting new songs in the playlist and pressing "play" the last seconds of the previous song were played (out of the buffer?) and playback stopped after this without any error message.

As reported I didn't have any of these problems for aboit 16 month before I upgraded t o 2.09 and changed the Q settings a lot.

Kind regards
Richard

Hello Richard,

It was the idea that you downloaded XXEngine3-209-X1.rar and use that. See a couple of posts back. Did you do that ?

Thanks,
Peter

Richard, that is the one I had too and once you hear that, better press stop.

An hour ago, coincidentally I could reason out what this should cause (something replays from an already played buffer) and I should be able to solve that one.
Btw the underlaying cause is that we use the huge Q1 (x  xQ1) - in my yesterday's case even 48x50 (you can't do that yet).

But please let ke know ASAP whether you used the new XXEngine3 or not, because if Yes, it apparently does not help for this situation (which is sort of logical).

Regards,
Peter

Peter, I now downloaded XXEngine3-209-X1.rar.
After I had copied this new XXEngine3 exe, in XXHE the output device is not found any more. Under setup this field then is empty and there is nothing to choose.
I tried it one more time after a reboot and got the same result. When I copy the older 2.09 engine3 exe over it, it's working fine again.

Kind regards
Richard

Richard, no idea. To me it looks like you are the only one with this. Maybe you now are bothered by the Blocked File thing ? See the properties of the file.

Peter

Hey, I found a situation where I can incur for the noise. Actually thanks to the new tripping + logging of it, I saw it happening while actually trying something else (with amplifiers off :)).

Do not use End After Track
or Kill XXEngine3 (click blue led in right hand border) when you did after all.

Peter

Here is a new XXEngine3.exe which does not trip so fast as the previous one. At least it solves the situation of Arvind (which btw only happened with native Arc Prediction).

Edit Nov 17, 2017 : This is now here (http://www.phasure.com/index.php?topic=3900.msg42116#msg42116).

Anyone gets the Crack Detect message unjustified ? please let me know.
(unjustified is when you can repeat it at the same point in a track or a ttrack boundaries)

Regards,
Peter

Peter, yes, it was the blocked file problem. It's working now (version X1). I could have known that myself.

Yes, I am using the "End" button pretty often. I will avoid it now and see if burst of noise still happens.

Kind regards
Richard

I could incur for it myself last night (in this case by pressing Next (XXOSK) in Unattended which failed - but with Q1 of 48x50) and while the "51 cracks"  were reported on-screen, totally nothing was audible of it.

51 is the maximum which can occur but it will be caught before pushed out and 16 is the maximum which could be pushed out, hence what can slip through before it is detected. This counts for all sampling rates, so at the lowest rate of 44100/sec we'd have 0.00036 seconds of burst. You won't hear that. :) At 16x upsampling this duration is 16 times shorter. Etc.
Notice that in the sofar posted "beta solution" (2.09-X2) 44100 (1x upsampling of 16/44100) is not covered for but in the final solution it will.

Regards,
Peter

Hi Peter,

The X2 upgrade patch has sorted out my problem.

Thank you very much.

Best regards,

Arvind

Which version of Engine 3 should I replace?

X1 or X2?

I have the scary noise here also once in a while and if this is the tweak to cure that then my heart will be thankfull!

Bert

X2. I will remove the X1 upload. Sorry for the confsion !

Peter

Hi all,

This should be the final one (download it below).
Now not only the issue is covered for when it happens (as in the X2 version) but also the cause has been found and taken out. This cause has been in there forever (since the last 0.9z version), but was challenged for because of a 80 second time window where things could go wrong which window previously was way shorter (think a few seconds). All related to how playback stopped (implicitly would incur for the wrong situation) and how fast a new Play was issued.
The noise could happen fairly soon when the new Play was issued, but also at the second track of that when the first was shorter than 80 seconds (minus how fast you could re-issue Play).

Thank you all for your help on this one !

Peter

Sort of a strange situation here. Never had a burst of noise problem with 2.07; however, since I reverted back to 2.07 from 2.09, I've now had the problem 3 times. Two of the three times the burst only lasted a second or two then music played. One time music stopped completely and I had to reboot. That I would get the burst followed by music is likely due to my small SFS with 2.07, which is .02. With 2.09 my SFS was 1.0. At some point I may try 2.09 again but I started hearing a bit of harshness with it that is absent in 2.07. Perhaps some saved file from 2.09 was preserved when I switched back to 2.07 from 2.09?

Hi Brian - You mean some saved file which now causes the "buts of noise" in 2.07 for you ? nah. I would bet that this is the smaller SFS. I mean, I simply know it has always been there and I also know what I solved in the XXEngin3-X3 version. However, it *is* related to a relation between Stop and Start (Playback) and how one can do something unexpectedly (for the program) which or goes wrong within the second (depending on the SFS size) or goes wrong at the start of the 2nd track (after pressing Play). And then it is also related to the Q3,4,5 settings.

I hope you can make something of this !
Peter

Thanks Peter, I play around with some settings.

Brian

Hi Peter,

For the first time after the X3 upgrade patch to Engine 3, I got crack detect msg. I have sent you the music file by FileMail.

Hope you can make something out of it.

Best regards,

Arvind

Arvind, Yes, this (see below).

Just not right for the period of 0.1 second (so that is theoretically 441 subsequent base samples which are wrong.
It exactly this what the "Crack Detect" trips on.

It is not your rip. It is just in the master of this.

If you play this with the Custom filter, it will pass (I checked). No idea what you will hear for this small period of time.
Theoretically this is a close to 22.05KHz tone without anything else (it is safer to think it is ~11KHz). But it also clips, so this really is not right.

Best regards,
Peter

Hi Peter

I've applied this over 2.09 with no problems.  Is it okay to apply it over 2.01?

Charlie

Hi there Charlie,



Sadly, No ! Sorry ...
First one would be 2.07.

Regards,
Peter