XXHighEnd

Hi,

I'am trying xxhighend in demo mode for a week now on a M2TECH hiface If i play 44.1 Khz files upsampled to 192 it works in 09z-2 but not with 09z-3. I have turned on option '96K or 192 only' but it gives in 09z-3 error message 'Illegal sample rate or bit depth conversion implied' and don't play. I have tried all possible play options like special, adaptive, arcpredict, antiImage latency settings etc., but no way to play 192K in 09z-3.  I don't like 09z-2 because of missing SFS settings. 44.1, 88.1 and 96 and 176 play well in both versions. My dac don't features 176 playback. It give some static distortion so that's a no go.

Hope somebody have a solution for this?
Could it be a bug in 09z-3?

Thanks,

Looks to me like a bug indeed !
Will solve it. And sorry for the inconveniency. I guess not many people use this, or otherwise I would have heard it before ...

Thanks,
Peter

Thanks Peter, hope you can find the bug. I'll wait for a new updated version than.

Hi Peter,

I've tried 09-z4 in the hope the 192K upsampling will play right now, but no succes. It even gets worse, now i also can't play 96K. Both give same message. Illigale sample rate or bit depth conversion implied... Don't know if you did look already to that bug, but for now it doesn't work at all.

Hope this info can help you by get rid of that bug. Didn't have time to do a good listen to the 09-z4 version already so can't comment on the sound quality right now.

Keep up you good work! 

96k with 9z-4 works here; my Jkenny is a modified hiface. Sound is damn good too! No suggestion on a solution assuming your "Dac Is" setting matches your dac?

I am sorry but this bug has not been addressed in 0.9z-4-0 yet.

Upsampling to 96 still works, but most probably you did not activate the fx button after the upgrade ?
(that this is needed is a bug within itself :yes: ... but I think in 0.9z-3 it was the same)

Peter

Sorry, i checked it yesterday night rapidly, forgot to tick the fx checkbox. So 96K is working, i will wait for correcting the bug in a newer version.

09-z4 sounds very good, but so many options to try... so i'll keep experimenting.

P.S. Other thing happend very often is this message: 'Engine 4 did not start in the expected time'. Sometimes after that it still plays but also happened that playback did not start. By retrying play button it eventualy works. But ik happens also inbetween tracks. It looks like it has nothing to do with 'Demo mode'. Could it be something with system requirements (Notebook Core2Duo 2,1GHz, 2GB Ram, Windows 7 SP1 (32 bit). I have tried all kind of setting changes but it looks like it keeps on happening. I played with Latency settings, Q1, Adaptive, Special ect. but all make no difference. It happened with 09-z2, z3 and z4 all in the same frequeny.

Any ideas?

Yes, that will be the conversion process from 44.1 to your wanted 96. There are 14 seconds to do this, and it can go in 5 or so seconds for a 10 minute track.

But not on a notebook like this ...

So, when the 14 seconds have past, that message will appear.
By coincidence playback can just have started though, so that's when the message is there when playback is there also.

Shortening the SFS may help, because that too (reading into memory) takes time.

In the very end you should use Arc Prediction to upsample, but then your DAC should be able to do 88.2. And I assume it can't ?
Anyway, then this whole "pre-conversion" won't be there, and only some other stuff will take time. Btw, FLAC conversion also belongs to such pre-processes, and that too can take long on a notebook (should go in 1 second for a 10 minute track on a somewhat more fast system).

Peter

Thanks for the info, i'll try some of your tips. I can do 88.1K only problem with dac is playback of 176K.

P.S.: You can maybe make an option (for slower computers) for longer time out duration or time out duration by the user adjustable?

Greetz,
Martijn

I've tried 44.1 file with a audio length of more than an hour upsampled to 96k and no time out. And sometimes a file of a single length of only five minutes can give time outs. How is that possible if it has to do with processor power. Is it divided in to different parts and that one single part can give this time out or is this 14 sec. time out period for the processing of the total file?

It is per part, and the part is determined by the SFS.

But also think about spun down disks ... If they spin down within one minute, and your part takes longer than that, the disks needs to spinup and that alone may take 10 seconds ...
This by itself will be avoided by an SSD or RAMDisk ...

Start TaskManager, bring forward the CPU graph, and see how the peaks imply the parts loading. Just try to "learn" from that, and see how settings may vary it. Or, how Appointment Schemes vary the CPU load itself (which is about after the "pre-processing").

Peter
(but keep asking where necessary)

I'll also try smaller SFS size then. But for proper functioning i have to go to a much more powerful system. For simple tweaking/updating, i think RamDisk is no option with only 2GB memory, maybe sdd memory but i think it's also expensive. But i keep on experimenting to find most optimized options.

Thanks for all the info!

Martijn