lekt player
-
- Posts: 2491
- Joined: Mon Oct 07, 2013 11:09 pm
Re: lekt player
pointer of WASAPI data buffer 1:
618442154544
pointer of WASAPI data buffer 2:
618442155568
pointer of app data memory:
616328200192
(I HAVE 16GB)
618442154544
pointer of WASAPI data buffer 2:
618442155568
pointer of app data memory:
616328200192
(I HAVE 16GB)
Re: lekt player
thx, goon-heaven.goon-heaven wrote:pointer of wasapi data buffer 1:
24279408512
pointer of wasapi data buffer 2:
24279409536
pointer of app data memory:
24303697920
reason have found.
your pointer of wasapi data buffer is not like as mine, can not use in this algorithm. maybe 8GB or OS version, my is win8pro.
but pointer of app data memory is OK for this task. will make it. wait for me...
Re: lekt player
also as goon-heaven's, not as mine. seems 16GB maping is difference. but pointer of app data memory also OK for manipulation. i think can fix it.jesuscheung wrote:pointer of WASAPI data buffer 1:
618442154544
pointer of WASAPI data buffer 2:
618442155568
pointer of app data memory:
616328200192
(I HAVE 16GB)
thx, JC.
-
- Posts: 2491
- Joined: Mon Oct 07, 2013 11:09 pm
Re: lekt player
lol... 'hacking' pointer...
what other pointers are constant? haha
constant > variable
i think if ASLR is turned off, you can reserve memory. always same address
what other pointers are constant? haha
constant > variable
i think if ASLR is turned off, you can reserve memory. always same address
- goon-heaven
- Posts: 312
- Joined: Sun Sep 15, 2013 9:38 pm
Re: lekt player
OS is server 2012 R2 Essentials.
Re: lekt player
interesting, for 4GB wasapi give good address for me, big benefit for coding (excluding reason by OS version, or system tweaks, maybe bios tweak for memory).
v2.95 256 can work if your pointer of WASAPI data buffer 1 can match. will try fix.
v2.95 256 can work if your pointer of WASAPI data buffer 1 can match. will try fix.
Re: lekt player
if i can do this...jesuscheung wrote:lol... 'hacking' pointer...
what other pointers are constant? haha
constant > variable
i think if ASLR is turned off, you can reserve memory. always same address
will learn, good idea, JC. for PC audio development need coding only with number, only small integer variables. think windows 32 bit better for it, pointer only 32 bit, faster for calculate. but after compiling, why 32bit version not clean as 64 bit, almost all others things better than 64bit, vibration much better.
-
- Posts: 2491
- Joined: Mon Oct 07, 2013 11:09 pm
Re: lekt player
yes. 2.4.3 (32bit) is not as "clean" as 2.90x (64bit). "dirty" = musical nuance?lekt wrote:if i can do this...jesuscheung wrote:lol... 'hacking' pointer...
what other pointers are constant? haha
constant > variable
i think if ASLR is turned off, you can reserve memory. always same address
will learn, good idea, JC. for PC audio development need coding only with number, only small integer variables. think windows 32 bit better for it, pointer only 32 bit, faster for calculate. but after compiling, why 32bit version not clean as 64 bit, almost all others things better than 64bit, vibration much better.
just OS is dirty -> makes musical nuance into dirty?
i like 2.4.3 a lot... less vibration. but "something" makes it great.
same as mqn2.2. not clean. but i can feel air of environment/breathing. very live+real.
new mqn has hires, but these things are missing.
xa has all these special things in vocal- only on win7 hahaha. on win8 -> musical nuance=dirty/lumpy=poor texture.
Re: lekt player
can not fix it, need matched address for this task. make new version by other method, kept code's body of v2.95 256. use render loop like as v2.4.3.lekt wrote:...v2.95 256 can work if your pointer of WASAPI data buffer 1 can match. will try fix.
uploaded:
v2.95.1 256 c1
v2.95.1 256 c2
think c1 balance better, sound like as v2.4.3. c2 more clean but lesser air
i see c1 have very good energy, but in mellow style.