So, after a day with my AKU3.3 equipped 8525, Platform Builder, IDA Pro and HexCmp, I believe I've finally gotten to the bottom of the ATI ImageON acceleration bug. This is the bug that causes the screen to "tear" during accelerated video playback using CorePlayer, TCPMP or other players that take advantage of the ImageON hardware acceleration. Once this bug is occuring, the entire screen is unreadable until you somehow exit from the video player.
Note that even after this patch is applied there will still remain some "pixelation" artifacts. However, there's a great thread on CoreCodec.com that can be found here. The thread explains how to resolve most of these. Consider that thread "extra credit" though since all in all, this patch alone resolved about 90% of the ATI issues with my AKU2.3 test device (running the South African 1.35 TyTN ROM).
It was a buffer problem you see....
I've attached a cab which modifies the ATI DDI setup file to the AKU3.3 parameters. I've experienced great results with CorePlayer when using this on an AKU2.3 hermes. I only had to check all the boxes in CorePlayer's ATI IMAGEON setup page. By Default, 2 aren't checked:
"Green Tint" bug compensation
Keep ATI driver active (just test)
I believe it is the second parameter that corrects an out of memory crash when a clip is played in full screen mode the second time.
The above settings are workarounds however since the full benefits of this fix will only be available if the setup file is used in conjunction with the latest versions of the ATI drivers. Unfortunately, these drivers must be "baked" into a ROM. Do not try to install these drivers! You will brick your device if you do and a hard reset will be necessary to fix. Install the attached cab file instead and wait for the chefs here to build the new drivers into their next ROM release.
ROM Chefs: you can find the files that make up the release here
Delete the old versions and bake all three files in the zip into the /windows directory.
Now to the Technical.
ATI released 3 files as part of their DDI update: ace_ddi.dll, ahioem.dll and a hidden little configuration file named atihwtbl0.txt. It's this little text file that contains the magic since ace_ddi.dll uses it to configure several settings at startup. I haven't fully analyzed the changes yet and am in the process of doing this now but at first glance they appear to either move or increase the size of several video buffers in memory. It almost looks like there was an overlap issue with audio buffers
Anyway, enjoy this little patch!
As always, while I'm pretty sure that this patch will rock your ATI world, I take no responsibility for any "undocumented features" that may crop up. I've only done minimal testing on the TyTN 1.35 ROM so far. It must be right though... there weren't any syntax errors.
Installation instructions:
Download the attached CAB file
tap to install (it will ask to reset your device)
note: you must install this to your device. The patch won't work if you install it to a storage card.
If you experience side effects, removal is simple. From Settings->System->Remove Programs just remove "Sleuth's ATIFix". Be sure to reset your device after the uninstall finishes.
edit:
It's important to read the TyTN thread located on the CoreCodec forum. Here is the link to that thread. There's a lot of good information concerning the scope of this patch (which takes the form of AKU3.3 experiences) and what still remains to be done. In this thread, schriss does a good job benchmarking the ATI playback and also has some good suggestions, some of which I'm hoping will be implemented in future versions of CorePlayer (such as allowing a YV12 option for the ATI decoder). Also, as the thread points out, DivX decoding using the ImageON remains a challenge (like I said, my patch alone solves about 90% of the issues). Hopefully more will now be able to focus on this once the Hermes DDI setting modifications encompassed by my patch become ubiquitous.
i see you been busy to! thanks man.
Thanks Sleuth,
WMXL v0.30 will incorporate this fix.
Just tried, works perfectly! thanks!
(installed on WMXL.1)
Nice to hear Your post reminds me of something else:
Those of you running WMXL .2 already have the driver portion of the fix baked in. Installing this patch will give you full functionality.
Sleuth255 said:
Those of you running WMXL .2 already have the driver portion of the fix baked in. Installing this patch will give you full functionality.
Click to expand...
Click to collapse
since this patch also appears to be working with the older set of ATI DLL's, what's the "full functionality" what you're talking about? what functions are missing now? I didn't really see any differences playing with TCPMP with AKU3.3 and now with this patch on WM6.......
I experienced intermittent crashes on AKU2.3 when running full screen video if the driver wasn't set to remain active. This problem didn't crop up in my WM6 build that had the new drivers.
The problem appeared to be completely resolved in TCPMP/CorePlayer by simply checking all the boxes in the ATI IMAGEON setup screen however.
However, being a purist, I like to see the config file along with its matching driver running.
Lovely Jubbly! and Sleuth, thank you for all your time and hard work with this
Mike
WMXL extras updated sir. Bloody brilliant work!!
Heimiko said:
since this patch also appears to be working with the older set of ATI DLL's, what's the "full functionality" what you're talking about? what functions are missing now? I didn't really see any differences playing with TCPMP with AKU3.3 and now with this patch on WM6.......
Click to expand...
Click to collapse
Same here but as Sleuth said it was more for fixing crashes in a sense, my cingular device running a wm5 rom without the new drivers now don't crash when using this patch, though ofcourse I still get garbled boxes when playing divx files when I enable acceleration, while x.264 plays perfect when set up right with or without acceleration enabled.
My softbank tytn running xdalive .20 runs good as well as before my device froze at times when using ati video with and without acceleration enabled playing fullscreen. I get a good 20% increase now being able to use it compared to DirectDraw. Thanks for the fix
thanks man...
we were all waiting for this to come
I installed the .cab to the device and checked the two default unchecked boxes on the ATI page in TCPMP.
I opened a divx file and the audio and video were off. I performed a soft reset and everything is now perfect. This is a great find.
Advanced encoders: check out the link to corecodec on post 1. There's a lot there regarding how to optimize encoding for the accelerator (plus a few odd quirks too).
Thanks man. I will test ASAP (now my TyTN is in the hands of my wife that is playing "Ladybugs" game. Nobody in the world is dare enought to even think in ask her for a five minutes check)
Admins do you think this is worthy of a sticky?? Im still trying to root around in the coreplayer forums to find a recommended bitrate/codec etc... to encode our vids into.
I just went through the coreplayer thread again. Perhaps you might want to pm schriss for his opinion on the corecodec forum. At any rate, it looks like DivX is still a problem for the ImageON so I would avoid encoding with codec that fttb . I don't know if its Coreplayer or Hardware though (suspect the former however).
I try to install that CAB on my DOPOD U1000, after reset never can boot up again need to hard reset the device, someone can help to fix this problem?
Thanks!
That's an HTC Athena simdao! This patch is Hermes specific. As you have determined, "Undefined results" can occur if you install this patch on a different device.
Slightly OT here, but does your Athena suffer from ATI based DivX rendering issues? What other ATI ImageON issues do you have with it?
Sleuth255 said:
I just went through the coreplayer thread again. Perhaps you might want to pm schriss for his opinion on the corecodec forum. At any rate, it looks like DivX is still a problem for the ImageON so I would avoid encoding with codec that fttb . I don't know if its Coreplayer or Hardware though (suspect the former however).
Click to expand...
Click to collapse
The videos i have encoded using AutoGK, its good because i can just queu up the videos to encode and leave it running. Depending on the program i am encoding i set the filesize accordingly:
60mb for a cartoony show (family guy, futurama, simpsons etc...) approximatly 25 mins (so 2.4mb per min?)
120mb for a filmed program (friends, mythbusters etc...) again approximatly 25 mins (so 4.8mb per min?)
128kbps VBR MP3 for audio (fine for all movies)
fixed width of 320 (the program adjusts for the aspec ratio of the source)
XVid Mpeg4 (2 pass)
I used this encoding method since having success with TCPMP on one of the early iMate roms, since the South Africa HTC rom arrived all the roms since have played back on TCPMP/Coreplayer no problem with the rawframebuffer setting. Since the AKU3.3 test rom i have been using ATi Imageon setting instead and get MINIMAL artifacts onscreen with my files.
Worth a go???
Following mrvanx advice on this and another thread...
I used AutoGK and set parameters as follows:
fixed width 320
Predefined filesize 400mb
128VBR mp3
XviD Mpeg4 (2pass)
This was done on a DVD quality divx file, and produced a 400mb file which played back near flawlessly on the hermes, minimal artifacting, and much better quality than even my ipod! Great stuff
Thanks,
J
Related
Can someone please explain the easiest way to get VGA resolution on my XDA Exec? Am I right in assuming that although the screen has a 640x480 resolution, they use pixel doubling to negate it and it actually runs at the same resolution as my Dell Axim X5 (320x240)?
Is there a simple registry hack that disables this, or do I have to botch around installing a hack and then trying to botch all my apps to run in the new resoluition? Does anyone know if TomTom5 works in VGA mode?
I'm sure this has been covered already, but some of the topics are 13+ pages and date back quite a bit, and the site is a tad slow to trawl through lots of postings and searching for VGA brings up hundreds of topics.
Thanks in advance for your helps folks.
This is the best thread - there is a ZIP file on page one that I dobwloaded and it contains all the instructions to get things working
http://forum.xda-developers.com/viewtopic.php?t=32217
this is the post I didn't particularly want to have to trawl through, as it's 13 pages long and really slow to switch pages.
TheFair - as noted above, there is a zip containing instructions. You don't have to read all 13 pages, although it's useful background reading - we didn't write all 13 pages just for fun .
I had to do VGA again yesterday, for the first time in a long time, and it's very simple. Basically:
Unzip, copy files to windows, click ozvga, reset.
V
OK, thanks Vijay. Will I need to install your Bigphone application and replace other system apps once done? Also, any idea if TTN5 works in VGA mode? As my XDA is used primarily as a SatNav, I'll stick with QXGA if it's not going to work properly.
Thanks
thefair1973: VJBigPhone can be used to make the phone app usable again, (I don't use my Uni as a phone, so I don't use it ) Replacing system apps etc is optional, but obviously helpful if you use the apps effected.
No idea about TTN5, but it's basically one click to revert to QVGA, so I'd do a backup and just give it a go if I were you!
V
great, thanks very much for your help Vijay.
I use TTN5 and VGA. TTN appears to drive the screen directly, so you don't get any extra resolution, but it works fine
I use TTN5 and VGA. TTN appears to drive the screen directly, so you don't get any extra resolution, but it works fine
Is VGA in Universal already perfected? Which applications are still not showing right upon application of this hack?
Just finished reading the VGA thread. I have a headache now. One important question though, I am using the latest JASJAR ROM, would OZVGA work on this new ROM?
Yes, I did it yesterday with no probs.
V
vijay555 said:
Yes, I did it yesterday with no probs.
V
Click to expand...
Click to collapse
Thanks Vijay! I just performed a hard reset, so I am ready to try something new. I downloaded the file compliled by Khashim I believe, I'll check if I got his name right. Which one did you use? Is it the file from Carnivor or Khashim? (Yes it is Khashim.)
I think originally I used Carnivor's, but frankly, I had an old set of files that had been sitting on my SD card for some time (I've posted the zip in that thread as well, towards the end).
However, I don't think there's a big difference. Use the one that sounds positive. It's easy to copy over new files if required. But you should only need to fiddle with it if you see problems in some of your apps. I don't use many apps, but I don't see any problems.
V
I tried. It does look wonderful for browsing using PIE. But I do agree that the font are too small. I also tried VJBigPhone and it did made the buttons larger, but the bottom part has a different color. Did I miss something about the skin?
Comm Manager has the same problem about the skin on the bottom part.
I love how ozVGA changes PIE, but weighing the benefits on other applications I use, I decided it is not for me at the moment. I hope someday someone can implement an application to run a specific application on VGA mode selectively and not implement it on the whole device. Thanks for the responses.
cktlcmd said:
I love how ozVGA changes PIE, but weighing the benefits on other applications I use, I decided it is not for me at the moment. I hope someday someone can implement an application to run a specific application on VGA mode selectively and not implement it on the whole device. Thanks for the responses.
Click to expand...
Click to collapse
try tweaks 2k2 vga brute force
cktlcmd: there is a background fix for the phone on my webpage and in the VJBigPhone thread. I haven't looked at the comm manager fix yet.
Waiting for a more selective pixel doubling patch may take a while or be futile. I think it's possible but I've not had time to implement my own hack yet.
V
I've done the VGA hack & overall its a major improvement.
The size of toolbars & the fact that some fonts are too small is a nause, same as the programs that don't display properly. But its SOOO good to see so much text on the screen.
To be honest, if it doesn't really run at 640x480, is it not a case of false advertisment? Just a thought.
xyon: it is running at VGA (640x480), but just making everything sharper and emulating 320x240. I asked an Orange spokesman once and he said they were going for "quality over quantity". I suspect they just didn't know how bloody persistent haxxors could be
I prefer 640x480, but it does make day to day usage inconvenient. Perhaps all apps will eventually have native 640x480 support. But given how many years it took to go back to square screen support, I'm not very hopeful!
V
Hello,
I'm new with HTC devices, now I have a Trinity with Rom 1.15.405.
My old device was an Eten M600. Well, even if the Cpu is the same, I feel a bad performance on all gui operations, such as menu opening, tapping reactions, keyboard response...
Is this normal? Any hope it can be fixed in next roms?
Possible fix
I too have a Trinity for some weeks now and I understand what your saying this is possibly todo with the ROM on the device i.e it's still needs fine tuning and performance should improve with each subsequent ROM update - I hope!
Try using a registry hack to improve performance... just a suggestion but try using the following file - definately helped with mine.
This doesn't seen to help..
Another idea for you
I too am always on a mission to improve performance even if it isnt broken I try and fix it if you catch my drift, and have soft and hard reset my device over 200 times in the three weeks that I had it. So I have almost everything to improve performance generally. I found that installing the first file in the first post helped, try installing the attached file it contains alot of registry tweaks that I have played with and these have also helped further I would say it has improved general performance by around 20% and have made my Trinity a pleasure to use.
Turn on the following after you have installed it (you will need .Net Compact Framework installed as well to run this software):
0. Speed up the Display (this really works well)
1. Optimum Cache Size for WM5 (this really works well)
2. Increase the transfer rate in SD/MMC cards (this really works well)
3. Max TCP windows size
The rest are more general tweaks but add to the flavour...
4. Optimized cache option for Terminal Service Client
5. Smooth scrolling in Pocket Internet Explorer
6. Allows users to synchronize the device clock with NIST Internet Time Service (ITS).
7. Enable ClearType in Landscape
8. Wake Up PPC in full Power Mode (not sure about this one but won't hurt)
9. Disable Bitmap caching (not sure about this one but won't hurt)
10. Move PIE temp files to any of your storage cards
11. Animated Windows (this makes the GUI feel faster as you get some action)
NB. The trial Version will run 3 times enough to do your fixes but then you will need to buy it to further modify or revert to original settings.
Let me now what you think.
More tweaks not just for GUI but good performance
More general tweaks...
Make A2DP output stereo (joint stereo by default - why I wonder? well heaven knows) and change sound quality to excellent, these tweaks made a bloody big difference to listening to music via BT Headphones.
You can also unlock and mount the Extended ROM
Download and install the following (Hermes Registry Tweaker) - http://www.theunwired.net/?itemid=3311
I'm more and more disappointed by Trinity. Installation of Compact NET Runtime gives "out of memory", even if it seems to install anyway. I have 33 MB Storage and 17 MB Ram free memory after reboot (soft reset), no apps are running.
I tried a wmv video encoded with Pocket DVD on both Trinity and M600. Well, on the M600 it is much much smoother... My sister's K-Jam (Wizard) plays same video better than Trinity, even if it has only a 200 MHz cpu.
Hmmm curious
I have had most devices from HTC - and to be honest trinity has impressed me greatly, especially after all the tweaks.
My Trinity plays video encoded for 640x480 (vga screens with no issues it cuts straight through it) including Divx, Avi, Xvid, WMV using CorePlayer, I am suprised that you are having this problem.
Why don't you do a hard reset then install all your apps onto storage except for .NET CF. Then do all the tweaks I suggested I am hoping you then end up with one of the best windows Mobile 5 Devices out there with 3G.
Don't give up it wll be worth it - especially when they enable GPS as well.
I'm not alone:
http://www.corecodec.com/index.php?option=com_smf&Itemid=29&expv=0&topic=3688.msg21932
Curious
I think I will run some benchmarks! Results posted very soon.
It has a desturbing sound on the higher tones and the bas is muffled. I tried the fit4 program and changed to the best quality, it sounded a little bit better but it was hard to hear, beacuse now the music skips even more thnat earlier. You know you ger music for a while, it cuts of for a second and then comes back. Now it does this every 5 seconds.
Very sad
Guys am I using the same device??? I don't have any of these problems apart from the occasional skip if I am surfing the NET!
ROM HTC__001 1.15.405.5
Trin100
I am baffled.
I'm attaching Spb Benchmark tests, go here to visualize them:
http://www.spbsoftwarehouse.com/products/benchmark/handleresult.php?en
CutePinkSox said:
Guys am I using the same device??? I don't have any of these problems apart from the occasional skip if I am surfing the NET!
ROM HTC__001 1.15.405.5
Trin100
I am baffled.
Click to expand...
Click to collapse
Same rom...
Strange... my trinity works perfect. Its fast and reliabel. What today Plug-ins do you use. On all my pocket pc I noticed that most of performance issues were caused by today plug ins. Remember: They are always running in background...
CutePinkSox said:
More general tweaks...
Make A2DP output stereo (joint stereo by default - why I wonder? well heaven knows) and change sound quality to excellent, these tweaks made a bloody big difference to listening to music via BT Headphones.
You can also unlock and mount the Extended ROM
Download and install the following (Hermes Registry Tweaker) - http://www.theunwired.net/?itemid=3311
Click to expand...
Click to collapse
Will the fit4cat tweak enable a2dp stereo as well as improve the a2dp soundquality, or do I need another tweak for enabling the stereo?
Thanks!
Use this to enable True stereo!
woodsman said:
Will the fit4cat tweak enable a2dp stereo as well as improve the a2dp soundquality, or do I need another tweak for enabling the stereo?
Thanks!
Click to expand...
Click to collapse
Hi, here u go, use the attached file to enable TRUE stereo. Sounds much better. The fit4cat tweak just improves performance.
Thanks a lot, my friend! Much apprechiated.
see this spb benchmark result
i got this device yesterday.
what a performance
Try disabling the custom phone skin and use the standard OS skin. You'll lose caller prediction, but on the Universal (already a fast phone) it made a big difference.
V
vijay555 said:
Try disabling the custom phone skin and use the standard OS skin. You'll lose caller prediction, but on the Universal (already a fast phone) it made a big difference.
V
Click to expand...
Click to collapse
How can I do this?
hello all
kinoma Play looks really impressive in this video. http://www.wmexperts.com/next-release-kinoma-play-features-its-own-home-screens
are there any toshiba tg01 rom dumps floating around?
i hope people here are interested in porting this thing to our ''htc devices
This is just the next update ok Kinoma Play, which can be dowloaded on ur HTC.
Just wait few weeks for the update.
It's a good soft indeed.
wow this is very good!
the thing feels like its running on a 3GHZ machine with a geforce 8800
too damn impressive on the tg01
As this software comes bundle with TG01, Toshiba might shared the API for hardware acceleration to Kinoma Team. Remember this is a entire new processor platform (named Snapdragon). This software would never perform like this in ours old MSX7200 processors.
truly impressive
twice as smooth as the iphone with 2.5x the number of pixels so that makes it 5x as immpressive
its hard to tell where the constant 60FPS is comming from. is it from the cool coding tricks or from the CPU specs of the TG01. looks like both
I just love the Toshiba TG01
And Kinoma doesn't seem to be so bad either
Sascha
greatttttttt
I've tried this program, but there are a few hangups that really keep me from using it.
The first one is that it will only "intelligently" scan your device and storage card. There is no option to setup what folders to scan or leave out of a scan. They're only response as a "fix" to this is to put any directory you don't want scanned in the Program Files folder on your device/card. This means I have to redo my entire storage structure to work around their smart scan.
Also, they don't support .avi video files. They say "It's not used for legitimate content distribution" and that "it was always a poorly-defined format with many undocumented mutations that make it a mess to implement and support".
Well, one can argue the legitimacy of certain files, but that's not up to the video player to decide IMO. I have purchased several legitimate programs that convert my DVDs into avi files for mobile playback.
And as far as a mess to implement and support, hell, my very first Casio Cassiopeia supported avi playback with TCPMP. So that's just a cop out as far as I'm concerned.
Yes, the program looks great and has many awesome features, but it just falls short in trying to think too much for me. If I wanted to be a "dumb" user and have a "smart" media player, I'd buy an iPhone.
the new version was just released maybe these issues were sorted out. how about you upgrade and let us know
zarxic said:
The first one is that it will only "intelligently" scan your device and storage card. There is no option to setup what folders to scan or leave out of a scan. They're only response as a "fix" to this is to put any directory you don't want scanned in the Program Files folder on your device/card. This means I have to redo my entire storage structure to work around their smart scan.
Click to expand...
Click to collapse
New version has an advanced option add on that allows you select folders to be scanned. I haven't messed with it as my battery is dead but it sounds like it would help you.
how do i activate the free version of kinoma im getting invalid email man.. how do i do this guys?
Found this in another thread.
fesar said:
Hi,
Please find the link. I have uploaded the DUMP here. Please tell me how to proceed further and changing this DUMP from French to English.
http://rapidshare.com/files/253526287/Utils.rar
Regards,
Francis.
Click to expand...
Click to collapse
hey guys was just wondering what is the latest version of Kinoma Play thats out right now?
Hi everyone,
I have a small technical problem to solve and hopefully someone knows an answer for it. Someone gave me a HTC Diamond 2 (very nice toy I think). I don’t know which hardware is exactly inside the phone but I assume it’s an ATI ImageOn 2300 which fully supports OpenGL ES 1.0 + Extension Pack (that’s what GL_EXTENSION is saying). And all of these extensions are doing fine. As everyone knows HTC is not providing a D3D driver for their phones and all other drivers I have seen are just a wrapper around OpenGL ES. So using D3D is currently not an option.
I have to write an application which requires some render-to-texture functionality in realtime and here my problems are starting to grow.
[1] glCopyTexImage2D:
I recognized that glCopyTexImage2D() is very slow. My framerate is dropping dramatically from >100 frames down to ~20 frames. Somehow this is done in software by the driver and not hardware- accelerated. glCopyTexSubImage2D() is even more slow (down to ~10 frames per second), but both functions are working. I tried to move it into a different thread, but the driver is not supporting shared contexts. Also it’s not supporting two bound contexts at the same time with two different windows and threads. So this can’t be improved or I’m doing something wrong.
[2]PBuffers:
PBuffer are working fine. But PBuffers which can be bound to a texture are not supported by OpenGL ES 1.0. And that’s what happens also on this ATI card.
[3]GL_OES_framebuffer_object:
This was my preferred choice. But framebuffers are not officially supported by the installed OpenGL driver. But the libgles_cm.dll on the HTC is exporting these functions so I tried them and recognized that they are not working correctly. Somehow the vertex pipeline is allowing only triangles in the center of the viewport. All others will be discarded. When I turn it off it renders correct. Using glDrawTexiOES() will be ignored while using framebuffers. I assume that either the current implementation of the framebuffers is just waste of some development guys or the functionality is locked in some way.
[4]D3D:
Normally D3DM is supporting to switch between different rendertargets. But we are all know the D3D problem. I tested some other D3D drivers but they are not usable. Also I can’t imagine how render-to-texture will be implemented in these drivers while it’s not working in OpenGL.
I’m wondering what TouchFlow3D is using internally, whether they are using render-to-texture or not. The only thing I know is that they are using OpenGL ES and some extensions. But Manila.exe is querying the functions of libgles_cm.dll during runtime. So I have to write a few proxy dlls first and need to hook into the system to track what they are doing. And I don’t want to spend time on this.
Does someone knows an alternative to do some render-to-texture on the ATI or knows some secrets of the libgles_cm.dll which I don’t know? There are a lot of private functions inside but can’t find some documentation about it. Also ATI and Qualcomm are not very helpful to me.
Thanks.
Maybe, glReadPixels and then glTexSubImage2D (what probably glCopyTexImage2D is doing)?
(I know that this goes two times over the graphics bus, but you never know...)
What kind of scene (number of triangles, lights, textures) are you rendering with > 100fps?
glReadPixels() + glTexImage2D() is even more slow than glCopyTexImage2D...
Also this can't be parallized. I thought using AHI2DATI.dll instead to do the same thing, but I don't know how to get a surface handle from a OpenGL texture id.
>>>What kind of scene?
A very simple scene yet. Only a few depth sorted + material sorted objects (via VBO) with some textures (backed lighting) on it. Textures are compressed. Currently no lighting, no skinning or other things. While the render thread is waiting for glFinish() to return, a second thread prepares the next frame. Also the rendering thread is not redrawing the entire viewport each time.
The OpenGL texture id is the handle. There's nothing more you can do with it. PBuffers or framebuffer objects are the only way I know for doing performant render to texture in OpenGL.
No...I mean the surface handle of the AHI2DATI library. Here you have access to the raw data of the surface. Somehow the libgles_cm.dll uses these surfaces for it own buffers and/or textures or not?!
But this is not really useful unless someone tells us whats going on inside libgles_cm.dll.
See:http://greengalaxy.wordpress.com/2009/04/18/ati-direct-access-to-hardware/
Hi jeansmsixer, I don't think there is no efficient way to do it. Have you tried eglCopyBuffers?
Aren't all textures stored in system memory? - they surely have to be because the device reports no available video mem.
Even if you get a pointer to the color buffer, it's impossible to wrap the memory in a HBITMAP to select onto a HDC and use GDI fonts for instance. (which is what I need to do).
If you do write the proxy dll like you were suggesting, can you please let me know what TF3D does for fonts? Are they textures or have they somehow mixed 3D with GDI?
Hi jeansmsixer, something else you could try is what is described here:
http://brewforums.qualcomm.com/showthread.php?t=10668
Looking on glbenchmark.com it looks like HTC devices support the extension. You should be able to get a pointer directly to the color buffer (which I presume is in normal system memory) so you could copy off pixels fairly efficiently with your own memcpy(). However, you will need to eglWaitGL() etc to ensure 3d stuff is complete before attempting to access it.
I love the irony of the only helpful information for WM opengl being found on a brew site for symbian. If WM7 is as terrible as the current mess, then I'm moving to iPhone.
I am using custom rom 6.5.5 and core player is missing, I tried the new version but it still don`t support hardware acceleration, can any one kind enough to extract it from the Toshiba rom and make it in a cab? Thank you
elder T said:
I am using custom rom 6.5.5 and core player is missing, I tried the new version but it still don`t support hardware acceleration, can any one kind enough to extract it from the Toshiba rom and make it in a cab? Thank you.
Click to expand...
Click to collapse
@elder T.... can you clarify what hardware acceleration you are looking for ? I have used both versions and can't immediately see any different settings between them; I am aware however that there were a number of bug fixes, etc. in the later (paid) version.
The Toshiba Core Player has a feature that uses the SnapDragon`s hardware to do some job like what DXVA does in Microsoft Windows. Its alot smoother when rendering high bit rates encoded videos.
elder T said:
The Toshiba Core Player has a feature that uses the SnapDragon`s hardware to do some job like what DXVA does in Microsoft Windows. Its alot smoother when rendering high bit rates encoded videos.
Click to expand...
Click to collapse
Where does this show up in the menus please ? I hadn't spotted any non-standard items anywhere, but may just be being a bit dim
http://boardreader.com/thread/TG01_version_of_CorePlayer_anyone_tried_a6svXd59n.html
More discussion about It.
elder T said:
http://boardreader.com/thread/TG01_version_of_CorePlayer_anyone_tried_a6svXd59n.html
.
Click to expand...
Click to collapse
Many thanks - have just had a quick browse, but don't see a definitive clarification - mostly seems to be supposition; there is however one comment by BetaBoy (Core Player developer) which states "On speed differences.... There may be some speed improvements as the TG01 version of CorePlayer has some of our v2.0 improvements." I understood that some of this had also been incorporated into v1.3.6 (which superseeded 1.1.3) also - but in any event, seems to be very dependent on the video format/codec/size concerned.
Erm... I tested it with a `H.264 Video` `AAC Audio` MP4 file, CPU setting is at low and it drop less frames than any other version of coreplayer I used so far.
"It's presumably able to make use of the Snapdragon GPU in the same sort of way as WMP and HTCAlbum can. The normal version runs only on the CPU. I guess it may not be the GPU it's using, but in some way it is specifically tuned to the Snapdragon chipset and able to use parts of it for processing which are not accessible unless you license the ability to use them from Qualcomm."
Shasarak's comment might be true.
I got the Toshiba version now and very happy.
if your desperate for the .cab, re flash the original orange version and the coreplayer.cab is sitting in the windows directory, along with the other ones like maps etc