Tír Na HiFi

2.97 160 sounds very good. Getting odd crackle than I need to track down. Need more listening.

v2.94.1 abs:
buffer: 133
pointer1: 0x..80

goon-heaven wrote:2.97 160 sounds very good. Getting odd crackle than I need to track down. Need more listening.

v2.94.1 abs:
buffer: 133
pointer1: 0x..80

JC, goon-heaven, take pointers of 133, 160, 244, 256, 288. do this 2 times (second getting after restart of windows) to confirm that windows/wasapi doesn't change low 2 bytes in different its working sessons, because after restarting maybe these 2 bytes can be changed.
for example: my first result is
buffer size: 160
wasapi buffer pointer1: 0x00000.....0D80

2rd result after restart windows:
buffer size: 160
wasapi buffer pointer1: 0x00000.....0D80

always 0D08, it's multiple of 128.

JC's result: 0x....6240 for all sizes, is multiple of 64. with v2.97's method my number ...0D80 is better than JC's and my own version better than (even much better). my size 256 too good: 0x...0C00. maybe coz i use 4GB RAM. try set system memory capacity 4GB RAM, not sure can do this or not.

1st
buffer size: 133
wasapi buffer pointer1: 0x000000D57E4A6250
2nd
buffer size: 133
wasapi buffer pointer1: 0x000000EB864E6250

buffer size: 160
wasapi buffer pointer1: 0x000000A605626250
buffer size: 160
wasapi buffer pointer1: 0x000000AA81636250

buffer size: 244
wasapi buffer pointer1: 0x0000005724126250
buffer size: 244
wasapi buffer pointer1: 0x0000002396136250

buffer size: 256
wasapi buffer pointer1: 0x000000C7F0CD6250
buffer size: 256
wasapi buffer pointer1: 0x00000006D84D6250

buffer size: 288
wasapi buffer pointer1: 0x000000692EB86250
buffer size: 288
wasapi buffer pointer1: 0x00000058923E6250

sbgk wrote:I can't get it to work without getbuffer and releasebuffer, how is the event getting reset if you don't use these ?

unsigned char i=0;
getbuffer(...,160,&d);
releasebuffer(...,160,2);
d+=640;
AvSetMmThreadCharacteristicsA(...);
Start(...)

loop:
WaitForSingleObject(h,0xFFFFFFFF);
loaddata(d,...);
i^=1;
if(i>0)d-=640;else d+=640;
goto loop;

works for my laptop onboard souncard, but don't work for JC. will try fix, maybe bug in code. v2.97 use normally procedure (with getbuffer and releasebuffer in render loop).

jesuscheung wrote:uploaded
lekt.exe.manifest

just copy the file to same folder of lekt.exe.
SQ change should happen. experiment

was tired last night... didn't test properly

bad things less
but dry?

jesuscheung wrote:...
buffer size: 160
wasapi buffer pointer1: 0x000000A605626250
buffer size: 160
wasapi buffer pointer1: 0x000000AA81636250
...

weird, yesterday 0x...6240, today 0x...6250, system changed address. but v2.97 still works for you? think doesn't work today. will review code.

2.97 is working perfectly right now... listening...

let me restart windows...see what happens


----
restarted
2.97

pointer is shifted by +/- 1?
maybe something incorrect... sound is goood
not as good as last night
maybe spotlighted

-----
now
buffer size: 288
wasapi buffer pointer1: 0x0000007366806240

----
cannot test music in morning. always wrong hehe

jesuscheung wrote:let me restart windows...see what happens


----
restarted
2.97 works

seems v2.97 160 code usefull for pointer multiple of 16. ah now very difficult with mathematically logical/bitwise calculation, my pointer is 0x...0D80, if exists bug then also works for me, my pointer better usefull, hehe...

lekt wrote: ...
maybe buy cheap Sony for testing sound. im using cheap Senheisser MX400. in the old days tried cheap Sony, very natural sound, forgot this model... of course for listening need use expensive, hehe...

your MX400 looks like my old senheisser earphone... looks the same lol...
it beats my sony earphones i bought 2 years ago. x4 times the price...
got ripped off...