Related
What on earth is going on? I know where talking about 2 different Moblie operating Systems and devices, but he performance difference explains alot in terms of why the TyTN/Hermes....is underperforming in the Video department, especially with TCPMP.
If this is the case with Video, which can easily be measured for performance, how much more are these Hermes devices lacking in other departments.
Apparently the developers of TCPMP at corecodec are aware of this problem, but it seems to be more related to the Hermes itself.
Below are a few screenshots of 2 different Pocket PCs using the same Samsung 400 Mhz CPU but with completely different results.
Also, I would not necessariliy pay the figures too much mind if the Video performance was at least as good as on the Vario I or the HTC Prophet, but it is not IMHO.
Tell me what you guys think. Maybe I've got it all wrong.
I did have it at all wrong. please read up about the ATI thingy in other post.
I'm dissapointed with the speed too. I'm wondering if it's got anything to do with the 32-bit bus used?
bydandie said:
I'm dissapointed with the speed too. I'm wondering if it's got anything to do with the 32-bit bus used?
Click to expand...
Click to collapse
Hi bydandie.
You may have a point, but then I'm not having any other speed issues. What were the bus speeds on the Universal and Wizard? Do you know? Also;
Samsung (R)2442A [Hermes]
Samsung S3C2440 [HP iPAQ rx3715]
Both run @ 400Mhz
but as we can they don't appear to be identical processors. I'll google around for some info as I'm no expert, but it may still be ROM specific.
What Hermes variant have you got again? and what ROM version?
I was hoping the upgraded 200 extra mhz over the Vario, would be good, apprently it doesn't sound like the video playback is that much better. What is the video playback like ?
This is down to the Hermes not being able to utilise the ATI acceleration technology (can't remember the actual name) properly.
If you try playing a video in TCPMP with the acceleration on, on the Hermes, you will find that the screen shutters like mad!
So you can only use raw video mode for now, which is pretty slow. (But plenty quick enough for 320x240 videos, i.e. most "pocket pr0n")
mackaby007 said:
bydandie said:
I'm dissapointed with the speed too. I'm wondering if it's got anything to do with the 32-bit bus used?
Click to expand...
Click to collapse
Hi bydandie.
You may have a point, but then I'm not having any other speed issues. What were the bus speeds on the Universal and Wizard? Do you know? Also;
Samsung (R)2442A [Hermes]
Samsung S3C2440 [HP iPAQ rx3715]
Both run @ 400Mhz
but as we can they don't appear to be identical processors. I'll google around for some info as I'm no expert, but it may still be ROM specific.
What Hermes variant have you got again? and what ROM version?
Click to expand...
Click to collapse
The Wizard was 16-bit. I'm using the v1605 but with the HTC ROM.
mackaby007 said:
Hi bydandie.
You may have a point, but then I'm not having any other speed issues. What were the bus speeds on the Universal and Wizard? Do you know? Also;
Samsung (R)2442A [Hermes]
Samsung S3C2440 [HP iPAQ rx3715]
Both run @ 400Mhz
but as we can they don't appear to be identical processors. I'll google around for some info as I'm no expert, but it may still be ROM specific.
What Hermes variant have you got again? and what ROM version?
Click to expand...
Click to collapse
Both run at the same CPU speed, but have very different operating systems. According to the screen shot in the first post, the rx3700 tested is running pocket pc 4.21 (2003 second edition IIRC), whereas the Hermes is running Windows Mobile 5. I would guess the rx3700 doesn't have the slowdown related to persistant storage (for example), using some form of flash for memory is going to be slower than RAM.
I have a Eten M600 on WM5 and the samsung 400 proc. the TyTN use also the 400 proc.
When i compare them both on speed then my Eten is much faster in every way. much more responsive. opening and rendering screens.
Altough i prefer my TyTN over the M600, the build-hardware and sound is much better.
I guess it must be the ROM that isn't perfect yet ( and it isn't perfect yet for sure).
I have a Eten M600 on WM5 and the samsung 400 proc. the TyTN use also the 400 proc.
When i compare them both on speed then my Eten is much faster in every way. much more responsive. opening and rendering screens.
Altough i prefer my TyTN over the M600, the build-hardware and sound is much better.
I guess it must be the ROM that isn't perfect yet ( and it isn't perfect yet for sure).
ROM or CPU lacking?
luminus said:
I have a Eten M600 on WM5 and the samsung 400 proc. the TyTN use also the 400 proc.
When i compare them both on speed then my Eten is much faster in every way. much more responsive. opening and rendering screens.
Altough i prefer my TyTN over the M600, the build-hardware and sound is much better.
I guess it must be the ROM that isn't perfect yet ( and it isn't perfect yet for sure).
Click to expand...
Click to collapse
Thanks for your input guys. Luminus your point sounds like there may be hope for us all yet, but having said that, bydandie has switched to the TyTN ROM and I have moved to the I-mate ROM and admittedly we have both both probably experienced some improvements over the ROMs our devices shipped with but the Video playback issue remains, albeit slightly improved too (therefore indicative of being software related).
I spent several hours reading up on the SC32442A Samsung processor and I have to admit, whilst not having enough knowledge to fully understand all the technicalities, it seems that the CPU in the Hermes is one serious 'dude' which is not being used to its Full potential. Apparently its just as quick as a Xscale 520MHz CPU!
I can believe it due to the responsiveness of my device in general (with I-mate ROM), but its just not evident in the Videoplayback department.
I've also tried many differently encoded movie clips like its native MP4 and Divx etc but only negligable differences. I now believe, as posted by bydandie (I think), that its due to the ATI acceleration chip/software not doing what it is supposed and that maybe HTC should look into this as the different ROMs don't seem to make any worthwhile difference in this particular department.
For anyone who's reading this for the first time let me clarify that playback speed is acceptable to watch any well encoded movie (320x240 @ up to 768 kbps) but pausing, forwarding etc then resuming playback is where the problems occurr (for me anyhow). Benchmarking shows that the Wizard (overclocked @240MHz) easily outperforms the Hermes, but not in everything else. Though admittedly I also find the overclocked HTC Prophet @240MHz more responsive all round! Again this seems to indicate that acceleration support is missing across the border.
For the record: I no longer believe TCPMP is in any way at fault. It performs outstandingly on every other device I have ever installed it on, including Samsungs i300 which also had a 400MHz CPU and benchmarked the same videos at well over 300% compared to 120% - 180% were getting on the Hermes!
I give up for now, the problem is way beyond me but hopefully not far off from being found.
Samsung CPU
I'd be interested where you read about this CPU.
It's based on ARMv4 dating back to 2002 and as such is functionally very poor in comparison to the ARMv5 Xscale platforms. This is why it won't allow the current versions of iPlay to operate. It's also unlikely to have the xscale power and performance scaling capabilities as it pre-dated Xscale.
In practise the only thing that has affected me is iplay.
I have just upgraded my 2750 to WM5.
Contrary to what I was told when I purchased the upgrade (many months ago) it is much much faster than the tytn in every respect. It also seems more stable.
For day to day work though - I don't use the TyTN for video - ipod and Archos cover that for me - I find performance very adequate though.
Paul.
Re: Samsung CPU
pgamble said:
I'd be interested where you read about this CPU.
It's based on ARMv4 dating back to 2002 and as such is functionally very poor in comparison to the ARMv5 Xscale platforms. This is why it won't allow the current versions of iPlay to operate. It's also unlikely to have the xscale power and performance scaling capabilities as it pre-dated Xscale.
In practise the only thing that has affected me is iplay.
I have just upgraded my 2750 to WM5.
Contrary to what I was told when I purchased the upgrade (many months ago) it is much much faster than the tytn in every respect. It also seems more stable.
For day to day work though - I don't use the TyTN for video - ipod and Archos cover that for me - I find performance very adequate though.
Paul.
Click to expand...
Click to collapse
Hi again pgamble. I remember you answered an earlier post of mine regarding the CPU. It seems you understand more on these CPUs than I do.
I've provided the linl below to where I read all about the 2442 CPUs (they seem to have variants of it). Hope you understand it better than me. Please let us know what you make of it. Bydandie mentioned that the Hermes uses a 32bit Bus as opposed to the 16 bit Bus used on the first Vario. Do you know if this would negatively or positively affect the speed of data? I would have thought positive, but then I don't fully understand all the technical jargon in the provided link which will probably explain how the technology is utilised.
I hope it doesn't have to share too much of the available data bus/ bandwidth (whatever it is), thus bottlenecking the CPU. I still think at this time its related to the acceleration technology of the ATI Imageon.
http://www.samsung.com/products/sem...ationProcessor/ARM9Series/SC32442/SC32442.htm
http://forum.xda-developers.com/viewtopic.php?t=61370 :wink:
Hermes is a mini-powerhouse!!
Sorry I should have elaborated in that last post which directs you to more accurate information since I started this thread. The Hermes is in fact a mini-powerhouse and even beats the Universal for playback performance under the right conditions.
It's great that the Hermes is powerfull and beats the Universal under the "right conditions"!
But under the "right conditions" DOS beats Windows, it's just a matter on how you compare... :wink:
However, TCPMP still doesn't work as it should on the Hermes. *Standing by for new ROM*
Moskus said:
It's great that the Hermes is powerfull and beats the Universal under the "right conditions"!
But under the "right conditions" DOS beats Windows, it's just a matter on how you compare... :wink:
However, TCPMP still doesn't work as it should on the Hermes. *Standing by for new ROM*
Click to expand...
Click to collapse
The ROM ive settled on (imate) will play back no problems with rawframebuffer set for the video output. Admittedly id prefer to use the ATI acceleration but this temporary measure is still ok for me. Sound playback has improved as it does not stutter to a halt after a pause or skip. (for the record im using a 2pass Xvid encoded avi file with 128kbps MP3 audio) this is evident in both the imate and dopod roms......but not the updated HTC rom.
ATI & The Core Player v1.0
I agree with you both (last 2 posts), but from further investigations, it seems that the problem is not related to the ROM either but onlt to the ATI decoder. I've e-mailed ATI in the hope that they can enlighten or help us all. :lol: Fat chance of that I know, but in the ATI Hanheld Interface, there is a version number v2.30.......maybe that can somehow be updated directly if ATI will offer some support or through a ROM update (though it does seem like firmware) .
Anyway all said and done I'm going to keep looking until I find a way to get that bloody decoder to work permanently as it seriously improves all video formats by at least 100% in benchmarking, which means no dropped frames for High Quality encoded files.
Alternatively keep an eye out for the new TCPMP player (The Core Player v1.0) which will hopefully address all these issues within the coming weeks/months. :wink:
Yer i can imagine a ROM update may include an ATI-written updater within it which will sort out the problems. It DOES sound like something that can be fixed though so hopefully soon we will all have it working correctly. :lol:
So, AKU3.3 ROM did fix the problem with ATI, where you had screen going crazy, but there are decoding artefacts which I belive are down to TCPMP/Coreplayer to fix.
schriss said:
So, AKU3.3 ROM did fix the problem with ATI, where you had screen going crazy, but there are decoding artefacts which I belive are down to TCPMP/Coreplayer to fix.
Click to expand...
Click to collapse
Yer, if you look on the coreplayer forum there is a recommended encoding rate etc... but ive still watched videos no problem even using a different encoding rate.
Hey there,
Was doing alot of research online about the graphic chipset from ATI on Athena but not even ATi has any infomation on their Webby.
Anyone know the specs of this w2284 chipset? Would really like to have more information on the chipset.....
Cheers
i agree with you, i tried to find info on the chipset to but i couldn't so i was like fu*k it and bought it anyways
Interesting thing, I was looking for Intel® PXA270 and found out all things are over to Marvell. Pretty confusing but ATI is just part of that chip, not a special chip
I saw some posts at the Coreplayer (comercial version of TCPMP) forum that ATI has refused to make the specs of that chip available to the Coreplayer developers, effectively crippling the chip for being used my alternative media players.
that very intersting, will i think we all need to find a player that ati likes
ATI W2284 not only for processing video and graphics, but also for handling the camera. Particularly, calculating autofocus algorithms and settings of automatic white balance are done with the help of this graphic subsystem
hmm... i think tt is known.... But if i m not wrong my old blueangel also uses ATI chipset...
problem is like example nVidia's Goforce 5500 is known to have a clock speed of 150 to 200 mhz....
how much is ATI's W2284??? Secondly does it have hardware encoding N decoding of H.264 videos??
Blah blah blah... Lots of qns left unanswered.
Anyone knows??
Cheers....
bLiTz^ said:
hmm... i think tt is known.... But if i m not wrong my old blueangel also uses ATI chipset...
problem is like example nVidia's Goforce 5500 is known to have a clock speed of 150 to 200 mhz....
how much is ATI's W2284??? Secondly does it have hardware encoding N decoding of H.264 videos??
Blah blah blah... Lots of qns left unanswered.
Anyone knows??
Cheers....
Click to expand...
Click to collapse
Read here:
http://ati.amd.com/products/handheld/imageonfaq.html
http://ati.amd.com/products/imageon2282/index.html
and here:
http://ati.amd.com/products/handheld/products.html
Not very definitive I know, but never really found much else about them since last year and I believe ATI is remaining tight lipped for a reason...also not releasing info to Corecodec so they can support the chipset properly.
Notice also in the 3rd link, 2282 is listed,......but where is the mention of 2284?
I give up with ATI/AMD/Imageon....Imagine if we could get the best out of it via hardware decoding...how sweet that would be.
Just have to settle for using the Imageon driver for now, as it still yields visually better results thatn Rawframe buffer mode or direct draw and outperforms both in benchmarks fo speed.
Sorry can't help any more than that. Good luck on finding anything else useful.
no probs mackaby007......
Hmm i wonder...... mayb W2284 is actually a Modified Imageon W2282...
W2282 supports 3MP Cam.....
bLiTz^ said:
no probs mackaby007......
Hmm i wonder...... mayb W2284 is actually a Modified Imageon W2282...
W2282 supports 3MP Cam.....
Click to expand...
Click to collapse
That's what I thought too.
Ive noticed a real delay between image and sound when playing some games.
Games in question are FIFA 2002 from EA Sports and also Smart Tennis from SIMBSOFT.
Did anybody noticed something similar??
Any news? I'm waiting for optimized Ati W2284 driver for HTC Athena... May be it will be supported in CorePlayer...
Any news? I'm waiting for optimized Ati W2284 driver for HTC Athena... May be it will be supported in CorePlayer...
up )
bLiTz^ said:
Hey there,
Was doing alot of research online about the graphic chipset from ATI on Athena but not even ATi has any infomation on their Webby.
Anyone know the specs of this w2284 chipset? Would really like to have more information on the chipset.....
Cheers
Click to expand...
Click to collapse
Hey, thinks for your work.I'm sorry I don't konw how to help you.But i think it maybe like qualcomm 7200's graphics chip.because the first ppc phone base on qualcomm 7200 is kaiser/TyTN II has the same problem as our 7500 at first.but someone solved it by modfy the 7201a driver for diamond for it.and the 7200 is the first product after ati sold the handheld products to qualcomm.so i think they maybe a little like.
i'm sorry for my poor english!
I was surfing around wmpoweruser.com and saw this article: http://wmpoweruser.com/?p=2252. It says that Pharos will release this PDA in the Q1 of 2009 and it will rival the HTC Touch HD.
In fact, the specs of the phone are very similar to the HD, but what calls my attention is one really interesting fact: the Pharos phone uses the very same processor as the Touch HD (Qualcomm MSM 7201A 528MHz).
I would like to ask the experts: if the Pharos payed for the video drivers to use hardware acceleration, will it be easy or, at least, possible to import them to Touch HD and we´ll finally have decent video playback?
Thanks!
I think if the drivers for WM existed we would have them by now. I think the GPU is broken and simply doesnt work properly in the Qualcomm CPU or Qualcomm themselves cant get it to work properly, thats why there is only partial support for all its functions.
HTC Touch HD/Diamond/Touch Pro all three of them have video drivers but they are used only with inbuilt players(WMP and video player in gallery). What we need now is to Coreplayer use those DS filters or gain access straight to QTv 'chip' and they said that they finally came to terms with qualcomm about it and now they can start working on it. So one of the upcoming updates(which one I don't know) should finally end this problem but I don't know when it will come.
Here you have link to the topic regarding QTv situation.
The simple test is whether ANY devices on any platform that use the CPU have decent video performance. If not then its clearly a problem with the CPU itself, rather than just the phone manufacturers being cheap.
Qualcomm has other, cheaper CPUs that are just as fast in general terms, but without the GPU, so why fit a CPU with a GPU if your not going to use it?
Sure the HTC Album App can play some files with acceleration, but that is not offering full QTv support and is not providing us with everything the GPU is capable of in theory.
In my view the GPU is broken (or qualcomms implementation is) and therefore writing drivers to fully utilise it is very difficult, which is why there are no fully featured drivers.
Acceleration clearly works - you can play 800*480 high bitrate files in h264 via wmp, but they're a slideshow through other players.
Yes, but its only partial, its not accelerating everything it should. I still say such drivers do not exist, even at qualcomm. Their recent request for windows mobile driver specialists and developers speaks volumes.
It wouldn't be the first time a technology company has launched a broken product on the unsuspecting world, or talked up a product when it really isnt capable of what they claim.
Back to this Traveler 137, it does have impressive specs, looks, gps, and best of all 3G for us T-Mobile USA users! It just won some innovation awards at CES: http://www.pcworld.com/article/1563...ne_offers_navigation_no_network_required.html
I still think that the drivers are here but I think that winmo itself can be blamed for the situation too(using drivers by the system). WinMo should be rewritten for the multimedia so it would bring some universal standards for all video solutions that SoC has to offer. Something like openCL but for mobiles.
The fact that they are looking for programmers and enginners is a good thing and it means that they want to improve the way their products handle wm but it doesn't mean that they don't have people now.
Until somebody gives me concrete proof that the drivers arent there I won't change my opinion. And please don't start talking about GPU problem(which problem I think lies in faulty use or implementation of drivers and that HTC can be blamed cause they take full responsibility of how they configure the device and not SoC maker). I'm only talking here about video acceleration.
Its just that ive seen the same thing happen before, and its usually graphics drivers or memory controllers that suffer. Almost every graphical device we have has some element of broken hardware in it that requires a work around. It may not be the GPU itself, but the interconnect to the CPU, or the way the CPU and GPU interact is just not optimal. Either way something is not right as it is right now.
I very much doubt that there is a driver sitting on a PC in Qualcomm labs that will fix all the issues. I dont believe that no one has been bothered to buy it or that Qualcomm has priced it so high that it wont be used, that makes no sense at all.
HTC are not responsible for the poor driver performance, in fact they have clearly done their own work to work around the issue. What they are responsible for is using the chipset in the first place.
Im waiting to see exactly what Coreplayer ends up like after their improved QTv suport is out. Im willing to bet that it wont make a great deal of difference to anything but H.264 that is already accelerated by the HD native player, but not by Coreplayer currently.
rovex, you might have a point here btw...
I know that the Touch HD runs H264's inloop deblocker in hardware for example. Switching it on or off has no effect on CPU. For pure software decoders it has about 15-25% effect.
Since you can't really apply that specific acceleration to other types of video, it will be interesting to see what other media will be sped up by implementing QTV.
http://developer.sonyericsson.com/s...ws/newsfeb09/p_xperia_sdk_opengles_update.jsp
The SDK v1.0.5 release adds Xperia Panels with OpenGL ES support, allowing developers to incorporate a broad set of redering, texture mapping, special effects and other powerful visualization functions and provides a graphics pipeline that allows free access to graphics hardware acceleration on the Xperia X1 phone through the Xperia Panels interface.
Click to expand...
Click to collapse
So can everybody now finally admit/accept that the drivers are already included in the HTC HD/Diamond/Pro/eXperia etc...
The only problem is that no software so far has ever been coded to work with the MSM7XXX on WinMo (besides TouchFlo 3D and SPB Mobile Shell 3). Every past stuff has been compiled to run on ARMv4/v5 CPUs (MSM7XXX is a v6) and SGX/PowerVR 3D HW (intel2700G)...
Now it's time for HTC to release the SDK they "promised" a lil while ago during the Diamond launch.
yes it was posted earlier..
there's a gl demo inside..
anyone want to play?
it's a real pity that Visual studio is so expensive, would be good to see if it's possible to compile the libgles files.
MAK11 said:
http://developer.sonyericsson.com/s...ws/newsfeb09/p_xperia_sdk_opengles_update.jsp
So can everybody now finally admit/accept that the drivers are already included in the HTC HD/Diamond/Pro/eXperia etc...
The only problem is that no software so far has ever been coded to work with the MSM7XXX on WinMo (besides TouchFlo 3D and SPB Mobile Shell 3). Every past stuff has been compiled to run on ARMv4/v5 CPUs (MSM7XXX is a v6) and SGX/PowerVR 3D HW (intel2700G)...
Now it's time for HTC to release the SDK they "promised" a lil while ago during the Diamond launch.
Click to expand...
Click to collapse
Huh, sounds you mix stuff up. Graphics acceleration has nothing to do with the processor and its instruction set. The Qualcomm chip is a chipset, which includes, among much other stuff, an ARM CPU but also a graphics chip (an ATI Imageon i think). The graphics hardware could already be accessed by some 3D games - just have a look here in the forum, it's nothing new. The panel SDK now only allows to use 3D acceleration also for the panels, even though I think you could have achieved this before already by acessing the graphics lib directly. So I'd say it's just more convenient for the programmer now and officially supported.
Does any one know if EVO is capable of hardware based 2D/3D acceleration out of the box, or is it similar to the rest of HTC/Qualcomm devices without proper drivers?
Thanks.
Mike