Page 146 of 299
Re: lekt player
Posted: Fri Jul 04, 2014 4:05 pm
by goon-heaven
Have 8Gb RAM
Re: lekt player
Posted: Fri Jul 04, 2014 4:09 pm
by jesuscheung
pointer of WASAPI data buffer 1:
618442154544
pointer of WASAPI data buffer 2:
618442155568
pointer of app data memory:
616328200192
(I HAVE 16GB)
Re: lekt player
Posted: Fri Jul 04, 2014 4:16 pm
by lekt
goon-heaven wrote:pointer of wasapi data buffer 1:
24279408512
pointer of wasapi data buffer 2:
24279409536
pointer of app data memory:
24303697920
thx, goon-heaven.
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
Posted: Fri Jul 04, 2014 4:23 pm
by lekt
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)
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.
thx, JC.
Re: lekt player
Posted: Fri Jul 04, 2014 4:26 pm
by jesuscheung
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
Re: lekt player
Posted: Fri Jul 04, 2014 4:27 pm
by goon-heaven
OS is server 2012 R2 Essentials.
Re: lekt player
Posted: Fri Jul 04, 2014 4:45 pm
by lekt
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.
Re: lekt player
Posted: Fri Jul 04, 2014 4:54 pm
by lekt
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
if i can do this...
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.
Re: lekt player
Posted: Sat Jul 05, 2014 7:14 am
by jesuscheung
lekt wrote: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
if i can do this...
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.
yes. 2.4.3 (32bit) is not as "clean" as 2.90x (64bit). "dirty" = musical nuance?
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
Posted: Sat Jul 05, 2014 2:00 pm
by lekt
lekt wrote:...v2.95 256 can work if your pointer of WASAPI data buffer 1 can match. will try fix.
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.
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.