lekt player

Anything to do with computer audio, hardware, software etc.
nige2000
Posts: 4253
Joined: Thu Feb 14, 2013 10:47 am
Location: meath

Re: lekt player

Post by nige2000 »

lekt wrote:uploaded lekt.exe v2.94 abs

for all buffer sizes. user can input buffer size which he wants by edit .bat file, for example:
@echo off
Title LEKT MUSIC PLAYER
lekt.exe 160 "C:\music\abc.wav"
lekt.exe 128 "C:\music\abc.wav"
lekt.exe 144 "C:\music\abc.wav"

so then can get minimal buffer size of sound card, correctly size. try test and compare.
interesting, this testing version even better than other. haha...
balance, vibration, bass,... OK. simple algorithm. hmm... seems provocation of compiler, JC.

well come goon-heaven author of this thread coming back now !
is it looking like the lowest buffer acceptable for any dac is the best for sound quality?
sd card player, modded soekris dac, class a lifepo4 amp or gb class a/b amp, diy open baffle speakers based on project audio mundorf trio 10's
User avatar
goon-heaven
Posts: 312
Joined: Sun Sep 15, 2013 9:38 pm

Re: lekt player

Post by goon-heaven »

lekt wrote:uploaded lekt.exe v2.94 abs
....
well come goon-heaven author of this thread coming back now !
Thanks. I'm notching more come-backs than Gary Glitter. LOL.

Lowest I can play lekt is 133. Much more listening to determine best WASAPI SQ - buffer size.

Hey JC: Explain what to do to get to 132?
lekt
Posts: 1102
Joined: Thu Oct 10, 2013 4:52 am

Re: lekt player

Post by lekt »

lekt.exe getminsize is too old version, maybe not correctly calculate min size, will review its code.
OK, now better use v2.94 abs for determine good buffer size, and min size also (do this manually).

goon-heaven, i've never seen 133 size, always even numbers as 160/256/224/..., not odd numbers.
weird.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: lekt player

Post by jesuscheung »

goon-heaven wrote:
lekt wrote:uploaded lekt.exe v2.94 abs
....
well come goon-heaven author of this thread coming back now !
Thanks. I'm notching more come-backs than Gary Glitter. LOL.

Lowest I can play lekt is 133. Much more listening to determine best WASAPI SQ - buffer size.

Hey JC: Explain what to do to get to 132?
me too is 133.

testing clockrate=133/44100... vs 132/44100 with 128, 1ms, 2m buffers
132 has the magic
(i am running too many programs... i could be misjudging... 132 and 133 sounds similar. difference is in earaches)

buffer > 132 i can feel tension.
< 132 just feels right.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: lekt player

Post by jesuscheung »

lekt wrote:lekt.exe getminsize is too old version, maybe not correctly calculate min size, will review its code.
OK, now better use v2.94 abs for determine good buffer size, and min size also (do this manually).

goon-heaven, i've never seen 133 size, always even numbers as 160/256/224/..., not odd numbers.
weird.
until you figure it out... i am sticking to clockrate=132/44100... haha best SQ EVER
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: lekt player

Post by jesuscheung »

how come i can play 128 with asio4all?
not with wasapi?
lekt
Posts: 1102
Joined: Thu Oct 10, 2013 4:52 am

Re: lekt player

Post by lekt »

nige2000 wrote:is it looking like the lowest buffer acceptable for any dac is the best for sound quality?
don't remeber, i've read in MSDN, think that. do testing manually for each size, only need change clockrate in windows registry for each case or not. maybe let it 10000 always by default.

by theory transfer small pakage of data better/faster/regularly than large pakage.
for example, transfer via wifi/internet better than via USB. pakage size smaller. but how can write good application for this task, not easy. i think that.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: lekt player

Post by jesuscheung »

128 buffer + 132 clockrate = losses little resolution. ~zero earaches.

8ms buffer + 8ms clockrate = ~zero lost in resolution. more earaches.

not perfect. ok for now

132*1/44100=good
132*2/44100=better
132*3/44100=89796 best
132*4//44100 -> goes bad

clockrate is biggest puzzle of windows hifi
lekt
Posts: 1102
Joined: Thu Oct 10, 2013 4:52 am

Re: lekt player

Post by lekt »

jesuscheung wrote:me too is 133.

testing clockrate=133/44100... vs 132/44100 with 128, 1ms, 2m buffers
132 has the magic
(i am running too many programs... i could be misjudging... 132 and 133 sounds similar. difference is in earaches)

buffer > 132 i can feel tension.
< 132 just feels right.
132 and 133 works for you, size 32 works and what is min size of your PCIe card?

need correctly rounded number for clockrate, JC. i use as following:
10000000 * 352 / 44100 + 0.5 = 79819.09410430839
10000000 * 160 / 44100 + 0.5 = 36281.679138322
and take five digits from left. rounded number must be more correctly.
jesuscheung
Posts: 2491
Joined: Mon Oct 07, 2013 11:09 pm

Re: lekt player

Post by jesuscheung »

lekt wrote:
jesuscheung wrote:me too is 133.

testing clockrate=133/44100... vs 132/44100 with 128, 1ms, 2m buffers
132 has the magic
(i am running too many programs... i could be misjudging... 132 and 133 sounds similar. difference is in earaches)

buffer > 132 i can feel tension.
< 132 just feels right.
132 and 133 works for you, size 32 works and what is min size of your PCIe card?

need correctly rounded number for clockrate, JC. i use as following:
10000000 * 352 / 44100 + 0.5 = 79819.09410430839
10000000 * 160 / 44100 + 0.5 = 36281.679138322
and take five digits from left. rounded number must be more correctly.
in asio4all, the min size is 64. i can play it.

in asus native asio driver, i can select 1ms. i can play it too.

UPDATE
so far in asio4all, 128 sounds best.
64 is getting dry.
144 is getting tense.
Last edited by jesuscheung on Thu Jul 03, 2014 3:57 am, edited 1 time in total.
Post Reply