XXHighEnd

Is it possible to mute the DAC 100% in all cases off not playing music?
Because it is very strange that the cracks come up when i am browsing a library??

You mean without playing music ???

Yes, this did not happen in previous versions.

When XX is idle and i click library (upper left) then suddenly the cracks starts and won't stop till i start a song again.
Weird behaviour..

Can you please check wheter this happens after normally pressing Stop ?
(which is probably what you already did, but I want to be sure)

Peter,

It happens random only when XX is in idle state. (not playing)

The exact moment the crack starts and why i can't figure out.
But it happens very often, so i hope you can solve this thing.

It seems like Eng#3 is triggered to start by something.
It feels like eng#3 is oscilating or something.


 

   

I think I said it before ?


(from your sig)

... but as I said elsewhere, I will try to explicitly more shutdown the DAC after playing. So maybe awaiten that before looking for things which can be solved by me anyway.

ok,

C-media or not it's caused by XX/Eng#3.
when i shutdown XX i don't happen.

But you will be able to tell me a few more things I think. Ok, you just told that if XX is not running it doesn't happen. That kind of things :swoon:.
If you can't tell anything else and it really is random, please buy another PC :yes:, no matter whether it's only happening when XX is there.

On the other questions, could you please put them in their own topic ?

Actually the most important for me would be whether you can copy the behaviour after the startup of XX, and never play anything.

As i can figure out untill now is that it not happens before XX has play a song with Eng#3. (restarted the pc and XX)
After playing a song with XX, even when closing XX, the crack random comes up, something when doing nothing with the pc.  Just idle, very strange! Sometimes the cracking of the DAC is a few seconds, sometimes without ending.
In idle state it can take 5 or more minutes when the DAC starts to tilt.
When load Foobar then and play een song and then exit Foobar The DAC stays quit.

So, can it be that when stopping/exit XX that the vista exclusive mode stays active in one way or another and that this causes the problem?

One thing is for sure now; this state of 'tilt' of my DAC has ruined my tweeter.
With a new DAC, new pc and new player (XX) it not easy to analyse whats exactly happens.
It is related with the use of XX (eng#3), because before using XX i never had this.
i hope we can figure it out

:scratching:

 :xx: :soundsgood:

Peter, I think you solved the problem with version u-5!
Excellent work!!

Since installing en playing around no mini loops or DAC Tilt's till now!
When strange behaviour occurs again, i will report it here.

Yesterday i closed XX and started Theatertek to watch a movie. At the moment i loaded Theatertek my DAC tilt's again. (Tilt; is that a good word?) 

Could it be a Vista bug that 'something' is 'not released right' after using it's exclusive mode? Because its only happening after the use of Eng#3.

But to be clear : Is it now indeed not happening anymore within XX itself ?

I had it once yesterday while starting a FLAC song in XX.
I dropped a song in the playlist and clicked play.
It took a long time (maybe 10 sec) untill the file was loaded. A lot of hdd activity.
In the meantime the slider walked like normal as a song is playing??
When the song was loaded the slider jumped back to startposition.
At that moment the DAC tilt's (heavy cracking)   
I clicked 'play' again and it stopped and the music started playing normal.
But u-5 is defenite an improvement over previous versions.

This brings me to a question.
Is the file loaded in memory before activating eng#3 when press play?
Why is the slider 'walking' when loading a song? 

It is good that you say this, because I noticed a (to me abonormally looking) long load time too, but wasn't sure. I can't think of reasons though, although things have changed slightly in that area. I will look into it.


This is normal for FLAC and MP3, but not intentional. Kind of difficult to solve (or better : kind of doesn't have priority and it is somewhat more difficult).


Litterally, no. After press play, yes.


Knowing what this theoretically can be (and this is not much at that stage of (not yet) playing), *and* combined with your TT story, I can only say something is wrong with the driver. So yes, I could solve something for you (which btw should not be needed -> something wrong in the base), but apparently I can't prevent everything. Example : if you'd kill the XXEngine3 process during playback, chances are high I think that your soundcard (!)/ DAC will be in the repeat loop again.

Please do yourself and me a favor. Reinstall the normal C-Media drivers and test again. And then ... please note that if nothing changes it still are the C-Media drivers being lousy (they just are).
Nor you, nor me should be bothered by an 18 euro solution endlessly, which can be solved by *another* 18 euro solution (buy whatever el cheapo soundcard just to test). BUT : If *I* could solve things for you, it is always better from my side. So it's not about that. What it is about (for me), is that I want to know what causes this. This is unrelated to solving it (ok, more or less).

Thanks,
Peter

The C-media site is down and, from what i have read, there are no good original vista drivers availible yet.

The C-media chipset came only in the picture because of the Dogber drivers. I don't trust soundcards in common sense of price<>digital quality. I have no problem buying a € 400,- euro soundcard if it is better.
But what do we need if we only want THE perfect interface between software and SPDIF? 
I don't see the difference in a cheap or expensive chipset. But that's what this thread is about. Maybe someone else has more knowledge about this.

One thing i know for sure; the C-media with Dogber driver sounds very, very Good.
One thing keeps my mind busy in this case. Why are the DAC tilt's gone after starting eng#1 or Foobar just once for a moment? Maybe you can analyse that and make some code to repeat that step when XX stops playing? Just to help me ;)   
 

ahum..  :cry: still waiting on my new tweeter..

The good news -for XX- is that i now quiet sure can say that the DAC cracks are involved with the use of Vista's exlusive mode.
Yesterday i played with a concurent player XMplay :innocent: with WASAPI (exclusive mode) output. The same cracks came up.

Now, what about "just the other" 18 euro solution ? :)

 ?  :scratching: ?

:) :)

For saving tweeters ?
If it sounds worse, obviously it won't be a real solution. But then at least you'll now there's a potential to the solution.

After loading a new playlist i pointed at the first song and clicked start.
At that moment there was a continous crack until the file was loaded.
After load was completed the songs started playing normally.
Could this be an XX related issue?
Dac is at 16/44.1 no OS, only invert
The effect is repeatable 

Ahh ... :swoon::swoon: I know now ...

This is related to the trick I apply to get Exclusive Mode let play modes it otherwise won't. But I didn't think of any 16 bit DAC (setting). :fool:

But to prove this ... what happens when you set DAC Is to 96/16 (!) and play the same file as before ?

DAC is 96/16 makes no difference.
Loading a playlist isn't the reason i found out.
It happens when starting a song AFTER the last song has played, ending with a 'no track data recieved' error.
A suggestion; is it possible to add code which checks a gap. So detect when a song is finished by its data. Then stop the player or fade out and go to the next song.   

So now your are saying that all the time you get these errors but never mentioned it ? Come on now please ... :scratching:

Normally i use 5 playlists of favourite songs which i play very often. I re-decoded these files to get rid of the 'no track data error' at the end of a song. The last few days i listened to new albums out of my big (FLAC) collection. I made a lot of new playlist's in XX. It was notable that the number of short 'DAC-cracks' increased and honesltly i didn't pay alot attention to it, because i'm using a pre-amp now. The concrete connection to 'no track data recieved' message didn't have my attention. Last evening i took some time to get it concrete. My girlfriend and daughter asked me if i has become crazy. Start-stop-start-stop-start-stop...
And don't get me wrong. Since you payed attention to this problem the mini-loops are history, DAC-cracks are a lot less. I suspect that the DAC crack issue has to do with the output drivers, not XX. But Dogber sounds so good!
I would appreciate any help preventing things through the code of XX.

I think you have quite some problems in your system, and the one I asked for several times now to eliminate (18 euro) JUST TO TEST, you won't even start trying.

As far as the status is now, you are asking me to solve Dogber's problems. UNTIL PROVED OTHERWISE. :)
Now please, shops are still open.

You do recognize that you are the only one, right ?

In the mean time, stop using FLACs, because THEY can be wrong as well. Then :

Please grab a normal WAV, look at the number of seconds it should run, take a stopwatch and look whether it plays as long as it should. Anyway, tell me how many tenths of a second it is off, okay ?

Btw, you might think I'm a little irritaded ... well, I'm not. But when you don't follow, say, "instructions", I just don't know what to do. Also, I don't link you can let me chase and solve a wronly working driver *if* that is so. And I don't say it is, but it has to be proved.
May you be afraid of indeed proving that, then I don't think I can do anything.

Ok ?

Hi hybride,

I assume you heard from Dogber that indeed his driver causes the problems you experience ?
It will be solved in the next release, he says.

That should make you happy !  :)

Dogber added a handler to his driver which stops a stream whenever it is unexpectedly closed.
So now it should be save for unwanted behaviour of audioplayers/streams.
I hope it will work for me so i can safely remove my pre-amp.
But now i will think twice to do that...