Crack Detect message after Pause ?

[arvind]

HI Peter,

Another problem faced by me is when I pause the track for say more than 2 mins & the click play then I get the following windows:

Engine #3 did not start within the expected time.
24 bit format stage crack detect >112
44100/176400/40941264/50000000.

Arvind

[PeterSt]

Hi Arvind,

Well, it may surprise you, but nothing of the kind here; I just tried 16/44.1 and 24/96 BUT this is on a "DAC Needs 32 bits" DAC. And there may be a difference according to that.

On the other hand, I really can't get how this would emerge. So, to me it looks like you possibly are doing something different in between ?
Can you please tell me :

1. What file format you are playing in this case;
2. Whether this is Attended or Unattended;
3. The exact sequence of activities.

Example of 3 I just applied :

Select a track - Press Play and let play for 10 or so seconds - Press Pause - wait 2:10 minutes - Press Play - ... plays.

Please re-do this at answering 3, so there is no doubt you did it differently (already for yourself).

And oh, never hesitate to bring up such things, and the more you all mention, the more will be solved. Even if you did something wrong (to your own findings), these kind of things just shouldn't happen !

Thanks,
Peter

[Calibrator]

This following may have some relevance here.

Earlier today I was playing some DTS encoded tracks and naturally had to tick the 'disable crack detect' box. As expected the warning box came up which I then duly acknowledged by clicking on the OK button.

When playing in UNattended mode I was unable to use the Alt-N to get to the next track. When I used Alt-X the crack detect warning box reappeared ( prior to the GUI coming back ), and it was not until I had clicked the OK button on the message that the GUI came back.

I don't recall it happening like this in previous versions.

I've been converting some multichannel DTS Master Audio from Blu-Ray's into 24_96 DTS wav's and they sound fabulous here

Cheers,

Russ
 

[arvind]

Hi Peter,

I went through the same sequence again & evrything worked fine. Maybe I did something differently at that time.
Just for your info file format is 16/44.1 WAV.
Attended

If this happens again I will memorise the sequence accurately.

Arvind

[PeterSt]

Arvind, I am fairly sure something happened indeed. You shouldn't get that message anyway, so ...
So indeed it is a matter of quite exactly knowing what happened.

See Russ's post as well. Looks very normal to me, if it would happen to me I'd say "o yeah, that one", but in the mean time you out there will never be able to guess even closely what happened.

Will look into that Rips-Russ. Ehh, when time permits.

Peter