I just got a Redmi Note 11. When trying to play a 10bit 265 (HEVC) encoded video the playback was choppy and not smooth. MX Player claims "HW decoding is unsupported" for that format. Trying to force it through the settings did not help. Other video players such as VLC did not fare any better. I found this really strange as my old Redmi Note 4 from 2017 played these videos without a problem.
Digging into it a looked up the Snapdragon 680 that powers the device, and according to what I found the CPU has support for 10bit h265 (source: https://www.cpu-monkey.com/en/cpu-qualcomm_snapdragon_680_4g). So what is going on here? Am I doing something wrong or did Xiaomi somehow cheap out on the phone? I am really disappointed by my purchase at the moment as 10bit video is something I use a lot, so any ideas for solving this will be much appreciated.
(Note: I posted a similar question over here: https://forum.xda-developers.com/t/...hevc-discussion.2725241/page-42#post-87053885 but since I got no answer I thought I'd try to get help here, and if not at least warn people of buying the phone as the lack of support is not listed anywhere. If my double post is against the rules I apologize)
magman2 said:
I just got a Redmi Note 11. When trying to play a 10bit 265 (HEVC) encoded video the playback was choppy and not smooth. MX Player claims "HW decoding is unsupported" for that format. Trying to force it through the settings did not help. Other video players such as VLC did not fare any better. I found this really strange as my old Redmi Note 4 from 2017 played these videos without a problem.
Digging into it a looked up the Snapdragon 680 that powers the device, and according to what I found the CPU has support for 10bit h265 (source: https://www.cpu-monkey.com/en/cpu-qualcomm_snapdragon_680_4g). So what is going on here? Am I doing something wrong or did Xiaomi somehow cheap out on the phone? I am really disappointed by my purchase at the moment as 10bit video is something I use a lot, so any ideas for solving this will be much appreciated.
(Note: I posted a similar question over here: https://forum.xda-developers.com/t/...hevc-discussion.2725241/page-42#post-87053885 but since I got no answer I thought I'd try to get help here, and if not at least warn people of buying the phone as the lack of support is not listed anywhere. If my double post is against the rules I apologize)
Click to expand...
Click to collapse
Try using mpv for Android (also built for Windows & Linux) -- it also supports multiple audio and subtitle tracks:
https://apkpure.com/mpv-android/is.xyz.mpv
https://play.google.com/store/apps/details?id=is.xyz.mpv
Oifan said:
Try using mpv for Android (also built for Windows & Linux) -- it also supports multiple audio and subtitle tracks:
https://apkpure.com/mpv-android/is.xyz.mpv
https://play.google.com/store/apps/details?id=is.xyz.mpv
Click to expand...
Click to collapse
Thanks for the reply. I just tried the app you suggested, and it too won't let me set it to hardware decoding. Pressing the SW button does nothing. So it seems no app is able to use hardware acceleration on 10bit 265 videos. Whether that is due to some driver issues (?) or a physical lack of support in the CPU is still unclear.
Am I the only one with this issue?
magman2 said:
Thanks for the reply. I just tried the app you suggested, and it too won't let me set it to hardware decoding. Pressing the SW button does nothing. So it seems no app is able to use hardware acceleration on 10bit 265 videos. Whether that is due to some driver issues (?) or a physical lack of support in the CPU is still unclear.
Am I the only one with this issue?
Click to expand...
Click to collapse
I think this is a problem of your Android OS -- I have just tested the x265 – Tears Of Steel 1080P @ 400kbps sample HEVC video (top left here: https://x265.com/hevc-video-files/) in mpv player (on my Xiaomi spesn) -- and I could toggle the [HW] button without problems.
I am running Android 12L - SuperiorOS, download links here:
Redmi Note 11 Updates
#SuperiorOS #Spes #UnOfficial #SL #OSS #Spesn SuperiorOS Unofficial | Android 12L Build date: 13/6/'22 ▪️Download ▪️Support Group Changelog: •Initial build. Known Bugs: •NFC •U find a bug, u can tell me Notes: •Use Mind GApps Credits & Thanks: @dblenk9 & @jabiyeff21 for trees By...
t.me
Oifan said:
I think this is a problem of your Android OS -- I have just tested the x265 – Tears Of Steel 1080P @ 400kbps sample HEVC video (top left here: https://x265.com/hevc-video-files/) in mpv player (on my Xiaomi spesn) -- and I could toggle the [HW] button without problems.
I am running Android 12L - SuperiorOS, download links here:
Redmi Note 11 Updates
#SuperiorOS #Spes #UnOfficial #SL #OSS #Spesn SuperiorOS Unofficial | Android 12L Build date: 13/6/'22 ▪️Download ▪️Support Group Changelog: •Initial build. Known Bugs: •NFC •U find a bug, u can tell me Notes: •Use Mind GApps Credits & Thanks: @dblenk9 & @jabiyeff21 for trees By...
t.me
Click to expand...
Click to collapse
That file my phone can play as well, but that file is an 8 bit file. It's the 10 bit encodes that the phone won't play with hardware acceleration. Can you try this file and say if you have hardware acceleration? I tested this file on my old Redmi Note 4 and it played back smoothly. My new Note 11 can't handle it:
https://jell.yfish.us/media/jellyfish-10-mbps-hd-hevc-10bit.mkv
Also, for the record, I am using the stock MIUI 13.
magman2 said:
That file my phone can play as well, but that file is an 8 bit file. It's the 10 bit encodes that the phone won't play with hardware acceleration. Can you try this file and say if you have hardware acceleration? I tested this file on my old Redmi Note 4 and it played back smoothly. My new Note 11 can't handle it:
https://jell.yfish.us/media/jellyfish-10-mbps-hd-hevc-10bit.mkv
Also, for the record, I am using the stock MIUI 13.
Click to expand...
Click to collapse
You are right about the bpp -- my sample MP4 has bitdepth=8 in the header, while your sample MKV has bitdepth=10 in the header.
I have just tried your sample on my SuperiorOS (build 20220613-0631), and:
mpv starts in SW-render mode and cannot switch to HW-render mode,
X-plore will just show black screen with message: Internal codec error
I guess that means that:
either the underlying hardware does not have the required decoder,
or the driver for that hardware does not support this video format.
Oifan said:
You are right about the bpp -- my sample MP4 has bitdepth=8 in the header, while your sample MKV has bitdepth=10 in the header.
I have just tried your sample on my SuperiorOS (build 20220613-0631), and:
mpv starts in SW-render mode and cannot switch to HW-render mode,
X-plore will just show black screen with message: Internal codec error
I guess that means that:
either the underlying hardware does not have the required decoder,
or the driver for that hardware does not support this video format.
Click to expand...
Click to collapse
Thank you again for taking time to test and respond.
I find the lack of hardware support (if that is indeed the issue) to be very surprising. The 680 is a 2022 chip. not supporting a popular encoding format these days just seems so unlikely and strange. It's also not something I thought I have to check before I buy a phone, and even if i would look it up I would find that it does support it.
If it is a driver issue, than who is responsible? Qualcomm or Xiaomi? And is there any way of fixing it? (i.e. some sort of custom driver or official update)
magman2 said:
Thank you again for taking time to test and respond.
I find the lack of hardware support (if that is indeed the issue) to be very surprising. The 680 is a 2022 chip. not supporting a popular encoding format these days just seems so unlikely and strange. It's also not something I thought I have to check before I buy a phone, and even if i would look it up I would find that it does support it.
If it is a driver issue, than who is responsible? Qualcomm or Xiaomi? And is there any way of fixing it? (i.e. some sort of custom driver or official update)
Click to expand...
Click to collapse
I strongly believe it's just an issue of the Adreno 610 driver (so it will be fixed in a couple of days / weeks) -- check these 3 relevant info-pages:
https://www.gsmarena.com/xiaomi_redmi_note_11-11336.php
https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231
https://cpu-comparison.com/igpu/qualcomm-adreno-610/
Regarding who will fix it -- I believe it should be Google with the help of Xiaomi / Qualcomm.
Oifan said:
I strongly believe it's just an issue of the Adreno 610 driver (so it will be fixed in a couple of days / weeks) -- check these 3 relevant info-pages:
https://www.gsmarena.com/xiaomi_redmi_note_11-11336.php
https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231
https://cpu-comparison.com/igpu/qualcomm-adreno-610/
Regarding who will fix it -- I believe it should be Google with the help of Xiaomi / Qualcomm.
Click to expand...
Click to collapse
I really hope you are right, although I am assuming this issue was present since the phone launched and it still has not been fixed after a few months. At least I now have hope that it can be fixed.
There are other phones that equipped with Snapdragon 680 4G, I wonder if they can play HEVC 10bit videos with hardware acceleration. Hope it can be fixed too.
lovinamn said:
There are other phones that equipped with Snapdragon 680 4G, I wonder if they can play HEVC 10bit videos with hardware acceleration. Hope it can be fixed too.
Click to expand...
Click to collapse
Going by the list here: https://www.notebookcheck.net/Qualc...-Processor-Benchmarks-and-Specs.611368.0.html there seems to be several phones using that chip, and I could not find a mention of anyone with an issue online. That does not mean that there is no issue, after all I couldn't find any mention of the problem on the Redmi Note 11 until I posted it here, and that phone has been out for several months already. If, as the poster above suggested, the video decoder is part of the GPU and not the CPU, then the list of devices with an Adreno 610 is even larger (https://www.notebookcheck.net/Qualcomm-Adreno-610-GPU-Benchmarks-and-Specs.434054.0.html), and I can't find any mention of an issue with those devices either.
Basically what I am trying to say is that the problem seems to be a Note 11 problem, but for some reason nobody posted anything anywhere until now. So we need people with any of the similar devices to report if by them hardware decoding is present. Meanwhile I contacted Xiaomi and so far they told me to use a third party video player if the built in app does not play my desired format. I'll report back if/when they start being more helpful.
magman2 said:
That file my phone can play as well, but that file is an 8 bit file. It's the 10 bit encodes that the phone won't play with hardware acceleration. Can you try this file and say if you have hardware acceleration? I tested this file on my old Redmi Note 4 and it played back smoothly. My new Note 11 can't handle it:
https://jell.yfish.us/media/jellyfish-10-mbps-hd-hevc-10bit.mkv
Also, for the record, I am using the stock MIUI 13.
Click to expand...
Click to collapse
Hello. I downloaded and played the video on my Note 11 in VLC. I didn't have any problems playing it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
N0b0dyy said:
Hello. I downloaded and played the video on my Note 11 in VLC. I didn't have any problems playing it.
View attachment 5645007
Click to expand...
Click to collapse
It plays totally smoothly? By me this file stutters like crazy in VLC.
How about MX Player? Does it let you select hardware acceleration? (the HW button in thew corner)
Yes it plays totally smoothly in VLC. I have tried MX player and there it stutters sometimes. And I tried selecting HW decoding and it showed that its not supported.
I am currently not on MIUI but on a custom rom.
N0b0dyy said:
Yes it plays totally smoothly in VLC. I have tried MX player and there it stutters sometimes. And I tried selecting HW decoding and it showed that its not supported.
I am currently not on MIUI but on a custom rom.
Click to expand...
Click to collapse
Interesting. In other files I tried - all of which had a lower bitrate than the jellyfish file - VLC was able to hit mostly smooth playback, while MX Player still stuttered a bit.
So my conclusion: VLC has better software decoding than MX Player. Meanwhile, whatever rom you are using is more performant than MIUI, which allows the video players to squeeze more out of the CPU in software decoding compared to my phone which is running MIUI. Still, even by you, the underlying problem remains: hardware decoding is unavailable, which is unacceptable.
As a side note, update on my attempts to get some sort of acknowledgement from Xiaomi about the issue: I sent several emails to their support address. Somewhat surprisingly they responded to all of them, but in none of their responses did they admit there is a problem. They mostly deflected and gave me uncommitted generic answers (i.e. "try a third party video player" or "the Xiaomi devices supports MPEG4, H.264/AVC, H.263/3GP and RMVB and other video formats. With the development of technology, the usage of some uncommon video formats has declined, and most mobile phones on the market support common formats such as MP4"). I also reported the issue on the built-in feedback option. Not too hopeful about that either, but at least that one should reach an actual developer.
Anyway, if anyone has an idea of something else to try, or some sort of fix for the problem I'd be happy to hear.
magman2 said:
Interesting. In other files I tried - all of which had a lower bitrate than the jellyfish file - VLC was able to hit mostly smooth playback, while MX Player still stuttered a bit.
So my conclusion: VLC has better software decoding than MX Player. Meanwhile, whatever rom you are using is more performant than MIUI, which allows the video players to squeeze more out of the CPU in software decoding compared to my phone which is running MIUI. Still, even by you, the underlying problem remains: hardware decoding is unavailable, which is unacceptable.
As a side note, update on my attempts to get some sort of acknowledgement from Xiaomi about the issue: I sent several emails to their support address. Somewhat surprisingly they responded to all of them, but in none of their responses did they admit there is a problem. They mostly deflected and gave me uncommitted generic answers (i.e. "try a third party video player" or "the Xiaomi devices supports MPEG4, H.264/AVC, H.263/3GP and RMVB and other video formats. With the development of technology, the usage of some uncommon video formats has declined, and most mobile phones on the market support common formats such as MP4"). I also reported the issue on the built-in feedback option. Not too hopeful about that either, but at least that one should reach an actual developer.
Anyway, if anyone has an idea of something else to try, or some sort of fix for the problem I'd be happy to hear.
Click to expand...
Click to collapse
I would recommend you to try to play several 10-bit videos + several 8-bit videos in mpv player (https://apkpure.com/mpv-android/is.xyz.mpv) and make screenshots of the bottom control panel when playing them -- see my screenshots below.
Then you can explain that for the 10-bit videos it's impossible to toggle the HW/SW rendering button and claim that you believe it's because of the present Adreno 610 driver is only supporting h265/HEVC(8-bit) and not 10-bit video streams (although the GPU supports it --> https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231).
Oifan said:
I would recommend you to try to play several 10-bit videos + several 8-bit videos in mpv player (https://apkpure.com/mpv-android/is.xyz.mpv) and make screenshots of the bottom control panel when playing them -- see my screenshots below.
Then you can explain that for the 10-bit videos it's impossible to toggle the HW/SW rendering button and claim that you believe it's because of the present Adreno 610 driver is only supporting h265/HEVC(8-bit) and not 10-bit video streams (although the GPU supports it --> https://www.cpu-monkey.com/en/igpu-qualcomm_adreno_610-231).
Click to expand...
Click to collapse
Thanks for the suggestion. I actually attempted something similar. I sent them a screen recording of the issue, including the stuttering video and the error message it shows every time I try to set it to HW. Unfortunately, they refuse to acknowledge the issue at all, and keep giving me those vague answers. I also sent the video as part of my report in the feedback app, but I have no way of knowing if anyone will look at it.
Meanwhile, I decided to try a slightly different tactic. Using a new email address I sent their support an email saying I want to buy a Note 11, but I was wondering if it has hardware decoding for 10 bit hevc. Their response: "we regret to inform you that as of now we don't have any official information regarding this. Generally speaking, Redmi series phones will support common video decoding methods in the market, but lesser used decoding methods are not included for the time being." It seems they just will not commit to any answer no matter how you ask it. You'd think a company would know what their product can do.
magman2 said:
Thanks for the suggestion. I actually attempted something similar. I sent them a screen recording of the issue, including the stuttering video and the error message it shows every time I try to set it to HW. Unfortunately, they refuse to acknowledge the issue at all, and keep giving me those vague answers. I also sent the video as part of my report in the feedback app, but I have no way of knowing if anyone will look at it.
Meanwhile, I decided to try a slightly different tactic. Using a new email address I sent their support an email saying I want to buy a Note 11, but I was wondering if it has hardware decoding for 10 bit hevc. Their response: "we regret to inform you that as of now we don't have any official information regarding this. Generally speaking, Redmi series phones will support common video decoding methods in the market, but lesser used decoding methods are not included for the time being." It seems they just will not commit to any answer no matter how you ask it. You'd think a company would know what their product can do.
Click to expand...
Click to collapse
Wow, you are quite resourceful I must say -- nice move...
To me it looks like the development team (in Xiaomi / Google) is either behind schedule or can't keep up with the latest video formats -- so they are just bouncing emails like yours with a standard "not included for the time being" response.
Hopefully there will be more displeased (potential) customers complaining about this, creating sufficient pressure on these corporations so that they will be sufficiently motivated to add the missing codec support to the current graphics driver -- I guess this issue isn't only with Adreno 610, but with some other GPUs as well.
However, adding features to a graphics driver on any OS is a tricky thing -- they need to test the new driver thoroughly so that these additions won't cause any crashes... Meaning it will take some weeks or even months from the moment they decide to add this feature.
Official Firmware of RN11 had this problem for me, I installed Custom ROMS and Problem was solved for most part. Movies from PSArips run smoothly on Mi Video especially. Some 10 bit videos higher bitrate struggle sometime when trying to fast forward.
tsdq512 said:
Official Firmware of RN11 had this problem for me, I installed Custom ROMS and Problem was solved for most part. Movies from PSArips run smoothly on Mi Video especially. Some 10 bit videos higher bitrate struggle sometime when trying to fast forward.
Click to expand...
Click to collapse
That does not really sound like you solved the problem. Instead you are mostly brute forcing your way through with software decoding. Struggling when trying to fast forward is not something I find acceptable in a modern phone, especially one that has the hardware to play it properly, and in no place did the manufacturer communicate the issues on the RN11. Meaning there is no reason to assume the phone will not support it. I tested hardware decoding on the Redmi Note 4, 8, 9 and 10 and they all play it with no problem.
Related
After many messages and interaction with CoreCodec, I have given up.
Coreplayer on the Fuze, TP, Diamond, and Touch HD from all accounts absolutely sucks.
I have tried to get CoreCodec personnel to discuss when a fix is coming for newer devices. He dances around the topic like Fred Astaire. He won't admit that CorePlayer does not perform as advertised and expected for these newer MSM72## devices, yet CoreCodec is MORE THAN WILLING to take the money of people just discovering their software after purchasing their new HTC devices.
There have been forum bans, user deletes, message deletes, and more on their forums. People just want to know why they are getting hosed and when it might stop. There have even been postings from CoreCodec personnel about advances and the like for freakin Sony PlayStation 2's in response to our questions about our mobile devices.
Riiiiiiiight.........
SO- I say this:
Diamond, Raphael, and HD users BEWARE. Do Not spend your money on Coreplayer until we have proof version 2.0 works becaus as of now- Windows Media Player is kicking the crap out of CorePlayer when you encode your videos with these settings (Courtesy of Sketchy in the Diamond Forum):
Video Format: MPEG-4 AVC (saves as .mp4)
Resolution: 640x360 (still maintaining the original 16:9 AR)
Video bitrate: 1000 kbps
frame rate: 29.97 fps (progressive)
Audio format: AAC
Audio bitrate: 96 kbps, 48kHz sample rate
To prove it, I have placed this video on YouTube. Crank up the volume as the Fuze's speaker was abt 3 feet under my camcorder. You can clearly see how CorePlayer at this time is NOT worth your $$ (I should say they are stating that the new version that will fix these problems will be additional $$ if you buy their product now).
Here is the video on YouTube:
http://www.youtube.com/watch?v=1lf4xteVs8M
I should state I am NOT a new purchaser of CP. Had it since my Wizard. I am just pissed they are not addressing customer concerns nor answering questions when we ask. We just want decent playback.
If it takes a while, fine. Just be honest.
**MODS> I know sticking this probably isnt too cool, but people are getting screwed. Please consider this. Tnx.
And I've been deleted from the user base on their forums.. Heh!
k9tim said:
Video Format: MPEG-4 AVC (saves as .mp4)
Resolution: 640x360 (still maintaining the original 16:9 AR)
Video bitrate: 1000 kbps
frame rate: 29.97 fps (progressive)
Audio format: AAC
Audio bitrate: 96 kbps, 48kHz sample rate
Click to expand...
Click to collapse
Out of curiosity, what apps do you use to convert videos to that format?
Use Super!
linky: http://www.erightsoft.com/SUPER.html
Man they must have deleted a lot of stuff in their forums because the threads are all wishmaster replying to non existent posts lol. I am curious why bother with CP if WMP is doing such a good job?
BTW I remember CP being slow to get the video support on the Athena, actually it may never have fully supported the hardware on that device...
Goatmaster said:
Man they must have deleted a lot of stuff in their forums because the threads are all wishmaster replying to non existent posts lol. I am curious why bother with CP if WMP is doing such a good job?
BTW I remember CP being slow to get the video support on the Athena, actually it may never have fully supported the hardware on that device...
Click to expand...
Click to collapse
It is sad actually. There were questions posted that were very simple to answer yet CoreCodec refused to do so.
I took screenshots of several of my posts knowing that they would get deleted. I'll post them tomorrow- I'm pretty wiped out from all the holiday stuff today.
All in all, I'm blown away at how little regard they have for their customer.
They have a pretty ignorant business model. I mean seriously- they portray their mobile player as the end all in the industry, yet they dont offer a trial period (oh no! people might figure out they aren't delivering what they promise depending on device) and they arent willing to let people know when they might be competitive with current apps that are... get ready for this...
INCLUDED IN THE WINDOWS MOBILE PACKAGE!!!!!
Wow!
Bad form, CoreCodec..... Bad Form!
I dont understand this thread tbh, ive been using coreplayer very happily since i got my raphael....a WIDE variety of video formats and they all play nicely....ive gotta ask are you still running a stock os??
I've also been running coreplayer since I got my Touch Pro, and for almost all videos I've tried (mostly DivX and XviD), it has performed remarkably well - I got coreplayer because WMP can't play (to my knowledge) videos requiring codecs like XviD and DivX, and most of the videos I watch are in those formats. I also tried DivX's mobile software, and that performed really poorly.
I'm always willing to try something new, so I will try converting some videos for WMP, but as far as I can tell, CP isn't giving me much of an issue at all.
The OP's point is well-taken, especially since Coreplayer doesn't have a trial ... but a little bit of due diligence would keep most people safe. TCPMP is kinda-sorta a trial ... the issue is Coreplayer is not optimized for the Raphael graphics acceleration hardware.
I do hope they manage to do it, then I'd purchase it.
Coreplayer is only good for XviD and DivX videos. When it comes to H.264 or its variants it sucks really bad. Only capable of playing half of the frames on average ( about 50% drops more or less). This is all based on my testing so far.
I am running v1.2.5 build 4506 for arm and the only issue I have is with flac files (no surprise). Even with a 500mhz cpu my phone has moments of complete silence as it tries to unfurl 30+mb songs.
I'm also running CorePlayer just fine. No problems whatsoever, and it outperforms WMP. I haven't tried the exact settings from your first post, but the normal desktop xvids work perfectly without having to transcode to a specific format for my raphael.
Make sure Qtv is enabled in Coreplayer (menu -> tools -> preferences -> select page -> qtv display -> tytn ii driver mode).
Btw, I'm not running stock ROM anymore. Maybe that makes a difference too.
NetRipper said:
I'm also running CorePlayer just fine. No problems whatsoever, and it outperforms WMP. I haven't tried the exact settings from your first post, but the normal desktop xvids work perfectly without having to transcode to a specific format for my raphael.
Make sure Qtv is enabled in Coreplayer (menu -> tools -> preferences -> select page -> qtv display -> tytn ii driver mode).
Btw, I'm not running stock ROM anymore. Maybe that makes a difference too.
Click to expand...
Click to collapse
No, I m still running the stock rom. At some point I'm sure I'll reflash, but I sure as hell am not going to because CP isnt up to the task of playing an mp4.
If you watch that video, you will see the various settings I used in CP and the result.
Maybe it is a Fuze issue (doubt it) but most of my vids are mp4 h264 (well they are now anyway) and CP just cant handle it.
It's not just my Fuze. Touch HD users are supposedly experiencing the same issue as are some Diamond owners.
The trick is that you wont see the complaints on the CoreCodec forums because posts are being deleted and people banned for "CorePlayer bashing".
I think that video speaks for itself.
Like VaThInk said: "Coreplayer is only good for XviD and DivX videos. When it comes to H.264 or its variants it sucks really bad. Only capable of playing half of the frames on average ( about 50% drops more or less). This is all based on my testing so far. "
Thats exactly what you are seeing in the video.
Fine- but if you are going to sell a app to someone with no trial then it better deliver. When it doesn't, then don't get pissed when those people want to know when it might.
Tap dancing around release dates for upgrades and then not being up front whether the upgrade is going to do anything (AFTER YOU HAVE TO PAY FOR IT-AGAIN!) to remedy a problem is simply not cool.
dr g said:
The OP's point is well-taken, especially since Coreplayer doesn't have a trial ... but a little bit of due diligence would keep most people safe. TCPMP is kinda-sorta a trial ... the issue is Coreplayer is not optimized for the Raphael graphics acceleration hardware.
I do hope they manage to do it, then I'd purchase it.
Click to expand...
Click to collapse
And I said exactly that on their forum- if it could deliver on the formats I use with an upgrade, I would gladly purchase the upgrade.
Don't get me wrong people- I did NOT buy CP for my Fuze. Had it since my wizard but my point is they are letting people purchase it then when they find out it is truly not doing what they say it will on these newer devices they say you will be able to BUY an upgrade soon.
When? They won't say. Will it be in the 1.30 upgrade? Won't Say.
2.0? Probably but won't say for sure.
The ONLY thing they WILL say for sure is that you will have to PAY all over again- thus the title of the thread: Buyer Beware.
slight update:
http://www.fuzemobility.com/?p=961
yeah sucks that it is getting hammered by wmp but they are working on it and were the ones that gave us kaiser users the first bit of hope when it came to the vid driver issues there.
i have played files of the type you mentioned (although the only setting different is i use 1200kbps) and they run fine on my touch pro
ive used coreplayer for ages now and never use wmp, so cant comment on which is better
coreplayer has a few bugs (esp tv out) and support for graphics isnt that good (htc fault) so i cant wait for a new release with these issues fixed
I had similar issues with H.264 vodcasts and Coreplayer. I thought I would have to reencode them, or subscribe to a different feed, but I happened to select one in WMP on the Fuze, and was very surprised to see it worked there, since it would not play better than 1-3fps on Coreplayer.
I love coreplayer and have no problems whatsoever, it is way better than wmp.
If you have problems with CorePlayer try different ROM or at least different video drivers. Try to put this to \windows
Code:
http://rapidshare.com/files/168326876/d3dm_ati.rar
I am playing full DivX DVD RIPs on my Raphael (ca. 800MB per movie) and it runs flawlessly even during fast actions.
Hey folks, I'm curious- Would it be fair to say that a lot of us (myself included) originally purchased CorePlayer because of the wealth of different formats it would play?
In other words letting us use one player to play our multimedia so we didnt have to take the time to re-encode the files?
well, i bought an X1 about 3 weeks ago and it is undoubtedly the best phone i have ever owned, the only problem i am having with it is the video playback.
Since i download DIVx movies, i would like to just stick them in my X1 and watch them at full speed. I tried using core player but since it is not hardware accelerated, i could only watch the movies in medium quality which is MUCH worse than the high quality and if i set at high quality i get only 80% speed.
And i see people trying to get the best possible conversion settings in order to be able to play high quality videos on the Media Panel or on Media Player. I find this useless since it takes FOREVER to actually convert videos and since i have so many, it would be a very tedious task.
I have a possible solution for this and i have no clue how to actually do this so this is my request to the brilliant developers here,
Is there a way to actually get the divx codec somehow from the samsung omnia and port it to other devices like X1 and seveal HTCs??? I mean i think it is theoretically possible since ppl have actualy gotten the Omnia ATI drivers right???
Hope this works!!!
I guess you could just download the divx mobile player from
http://labs.divx.com/MobileCommunity
I haven't used it in x1 but I did use it in the touch pro. I did not like the speed. As it wasn't my phone, I didn't bother to do any tweaks. I think it will be fine on the x1.
maybe i can help
khalilsemaan said:
well, i bought an X1 about 3 weeks ago and it is undoubtedly the best phone i have ever owned, the only problem i am having with it is the video playback.
Since i download DIVx movies, i would like to just stick them in my X1 and watch them at full speed. I tried using core player but since it is not hardware accelerated, i could only watch the movies in medium quality which is MUCH worse than the high quality and if i set at high quality i get only 80% speed.
And i see people trying to get the best possible conversion settings in order to be able to play high quality videos on the Media Panel or on Media Player. I find this useless since it takes FOREVER to actually convert videos and since i have so many, it would be a very tedious task.
I have a possible solution for this and i have no clue how to actually do this so this is my request to the brilliant developers here,
Is there a way to actually get the divx codec somehow from the samsung omnia and port it to other devices like X1 and seveal HTCs??? I mean i think it is theoretically possible since ppl have actualy gotten the Omnia ATI drivers right???
Hope this works!!!
Click to expand...
Click to collapse
well there are a lot of factors here, and im certainly no expert, but ill give this a whirl...
i have had my xperia for just about a month now and i have been watching divx movies on my coreplayer at high video quality flawlessly. or so i thought.. I watched some pretty fast paced movies too, like the matrix... and they seemed fine to me. again i dont know if any of my suggestions will make anydifference, or even be relavent to you, but i figured i could at least try to help. I will share what i found in general with my x1 and the core player
1. the x1 is highly tweakable in so many ways. I dont know how much youve looked around at how people are speeding it up using sktools, or the now famous storage card accelerator, but these things really do help. you should try them and see if you get any improvement. here is the link to the thread where this is all going down... to make it simple.. get skt tools, optimize, and get the sd card accelerator... the rest you can mess with at your own pace, but this will give you a big start.... anyway if you havent tried this stuff.. it may help..
http://forum.xda-developers.com/showthread.php?t=459328&highlight=show
2. god knows the coreplayer has so many $*$#* options... but here is something i noticed deep in the canyons of the player after my core player was bogging down horrendously for apparently no reason.... i have a lot of files on my sd card, and when i first opened the core player... the first few times even.. it lagged so much i couldnt figure out why... then i realized it was trying to scan my sd card and it wasnt really teling me it was doing this... there is an option that comes selected as default that tells the coreplayer to scan for files for its library on startup... if you have thousands of files like i did, and you didnt realize it was trying to build a library, like i didnt, and you opend and closed it several times... ok you get the point.. once it finally built its library, i found the option to turn off the auto scan, and boom,... suddenly it was working much much faster
3. i dont know if this makes any difference whatsoever, but i have an x1i, and i bet you do too, but if you have an x1a, there may be video playback differences in these "international" and "US" models that could be a factor too.
im guessing that what you are referring to, and what i have posted may not even relate, but it never hurts to try. FYI i just benchmarked for a minute or so while watching a divx movie and it read average somewhere in the 80% range... i dont know what that means, but the movie seemed to be plaing perfectly...
div x player
just tried the divx player to see how it compared to the core player...
core player works much better.... divx player was quite choppy.
maybe im missing something.. and i probably am, but the core player seems to be playing the divx movies perfectly at high quality
well, i have tried the divx player and it is absolute crap compared to coreplayer
benchmarking at 80 percent means that u skip about 1-2 frames every second. now might sound like much but i notice it and it is very annying. yes i have tried all the things u mentioned but did not notice much change except for with the memory card booster.
also the media panel and media player are hardware accelerated which means that they make use of the onboard ati graphics chip. coreplayer is not. also imagine watching a divx movie on the media panel wouldnt that be cool?? with the great interface and the speed and smoothness of the bond trailer?? i would very much like that. hope someone can get the codec somehow!
i see
thanks for the education. i guess ignorance was bliss on my part..
i hope we do find a solution here. any idea why the downloaded divx player works so poorly? maybe its tweakable?
I guess it simply sucks. Coreplayer is best player, and unfortunately by far margin. Unfortunately because there is low chance any other player will popup soon. Sooner or later Coreplayer will find a way to follow current devices.
Btw. be sure you use Coreplayer with TytnII qTV driver (should be default settings for 1.3). You can also disable AVC filter and high quality zoom. Other then that nothing really has effect on the playback speed.
The best player.
But almost half new movies are in AC3 format.
And CorePlayer don't support AC3.
core player team claim that they will support all qtv shipset in version 2
so just have to wait a litte while
ahhhhh thanks fo the info Tywith, thats definitely something to look forward to. i mean if im not mistaken, the TytnII does not have an ati chipset built in. having support for qtv chipset dedicated to XPERIA will definitely make it run smoother
all we have to do is wait.
Look at this sticky: http://forum.xda-developers.com/showthread.php?t=467590
If you convert your movies to mp4 you can play your movies using media player with hardware acceleration. You can create a joblist to convert multiple movies when you're sleeping
If you wanna use CorePlayer with hardware acceleration, use the DirectDraw in
Settings > Video. I've tried it and it works perfectly. It really takes full advantage of the Adreno 200 GPU (ATI 3D chip) and CPU.
Hammerhead89 said:
If you wanna use CorePlayer with hardware acceleration, use the DirectDraw in
Settings > Video. I've tried it and it works perfectly. It really takes full advantage of the Adreno 200 GPU (ATI 3D chip) and CPU.
Click to expand...
Click to collapse
Maybe it takes full advantage of the Adreno 200, but Xperia X1 has Adreno 130 which is much weaker than 200
radzix27 said:
Maybe it takes full advantage of the Adreno 200, but Xperia X1 has Adreno 130 which is much weaker than 200
Click to expand...
Click to collapse
DAmn!!!! But still works nice!!
Hammerhead89 said:
DAmn!!!! But still works nice!!
Click to expand...
Click to collapse
which version of coreplayer are you using?
1.3.6 didn't have hw-acceleration for playback. sure, on a good rom and with video-files not being too demanding, playback was nice -> sw-playback. but it didn't support our hw directly. and from what i can see, 1.3.6 is the last version for winmo.
btw, funny to see they closed forums on their site. probably too many threads "when will you finally deliver what you promised?" and accuses of coreguy producing vaporware...
I've just updated my firmware with the new CM7 RC4 release and Darlinger's OC Kernel (Released 3/31). According to the release log, they should support hardward decoding.
However, when I open MP4 files with RockPlayer, it still reports that this format is not supported with the system player.
Am I doing something wrong, or it still doesn't support hardware decoding?
Do these files play on other ROMs?
So far as I know, they would play with the rooted stock ROM. I'm not sure about Froyo or Honeycomb, though.
poofyhairguy said:
Do these files play on other ROMs?
Click to expand...
Click to collapse
Do a search for "nook color handbrake preset". You'll find a thread on all about how to encode mp4 videos to work on the nook. There are some options when encoding the video that when enabled will break playback on the nook color. Mainly the video resolution.
Thanks. But I don't really think that's an encoding issue. The file played perfectly with the stock rom and system video player.
woot1524 said:
Do a search for "nook color handbrake preset". You'll find a thread on all about how to encode mp4 videos to work on the nook. There are some options when encoding the video that when enabled will break playback on the nook color. Mainly the video resolution.
Click to expand...
Click to collapse
woot1524 said:
Do a search for "nook color handbrake preset". You'll find a thread on all about how to encode mp4 videos to work on the nook. There are some options when encoding the video that when enabled will break playback on the nook color. Mainly the video resolution.
Click to expand...
Click to collapse
If Nook Color' sample video cannot play by CM7 RC4 so hardware decoding is still disabled.
Here is the sample video from official Nook Color intro I extracted from latest firmware (1.10) :
http://www.mediafire.com/file/s5ka0xkdnsf4ajo/welcome_video.mp4
If default video player cannot play so hardware decoder still not enabled for CM7 RC4 and all variants...
Managing to play the video by means of diffrent 3rd party applications ( all video player that decode software and hardware based) make no sense...
Hmm I don't know what the deal is then... HW decoding is working brilliantly for me on CM7 RC-4 with latest OC kernel. I have a couple 720p mp4 movies that I re-encoded via the handbreak preset, and they played just fine.
woot1524 said:
Hmm I don't know what the deal is then... HW decoding is working brilliantly for me on CM7 RC-4 with latest OC kernel. I have a couple 720p mp4 movies that I re-encoded via the handbreak preset, and they played just fine.
Click to expand...
Click to collapse
Stock ROM from NC can play http://www.mediafire.com/file/s5ka0xkdnsf4ajo/welcome_video.mp4 videos but CM7 RC4 still cannot plays and they claim hardware video decoder enabled!...
Offical welcome_video.mp4 is the proof of CM7 RC4 is STILL software based...
Overclocking may help only software decoding? But I want to use hardware decoder and latest version not old one used 1.1.15.2766 .. NC's offical latest video decoder is 1.1.15.3172 for our NC ( PowerVR SGX 530)
NOBODY uses latest hardware because hardware decoding is still unusable... Acceptence of this current reality and then focusing on OVERCLOCKING CPU makes no sense when you have a hardware decoder's power ...
nemir said:
Stock ROM from NC can play http://www.mediafire.com/file/s5ka0xkdnsf4ajo/welcome_video.mp4 videos but CM7 RC4 still cannot plays and they claim hardware video decoder enabled!...
Offical welcome_video.mp4 is the proof of CM7 RC4 is STILL software based...
Overclocking may help only software decoding? But I want to use hardware decoder and latest version not old one used 1.1.15.2766 .. NC's offical latest video decoder is 1.1.15.3172 for our NC ( PowerVR SGX 530)
NOBODY uses latest hardware because hardware decoding is still unusable... Acceptence of this current reality and then focusing on OVERCLOCKING CPU makes no sense when you have a hardware decoder's power ...
Click to expand...
Click to collapse
Exactly! I was trying to make sense of this mess from January in my blog fineoils.blogspot.com. With a Nookie Froyo, Nookkolor started to lose everything that was there of hardware decoding AND hardware rendering. I was laghed at by CM7 NC dev dalingrin on my suggestion that lots of HW assistance in video playback is based on SGX, especially the HW overlay. CM7 team is of opinion that mp4/H.264 decoding can be made in DSP (IVA2 in our case) audio buffers for which were that "magic video fix" at the CM7 nightly 17 level. What we have is more or less smooth YouTube 2.1.16 (less smooth than EVO's 2.0.x "HQ" YouTube for Eclair) and stuttering/losing frames Flash 10.1...10.2 ("inline YouTube), plus stuttering local file playback with more than 480p or so. I have no indication that any HW-conscious FFmpeg codecs was ever used. NEON/Stagefright framework is missing/broken for unknown reason. Only Opera Mobile is capable of using 2D hardware assisted UI scrolling/layout, any other app/Webkit/launcher/wallpaper has no idea they all can use 2D/3D hardware acceleration, as, yes, drivers are broken/falling back to SW too easily. Sure, VOME engine by VisualOn might be just promised to AOSP 2.3.3 but never made it there, however I don't understand why latest Omapzoom commits on SGX driver and a special OMAP3 Adobe Flash Plugin couldn't be used.
Sorry for the long rant, but it seems that 90 % of CM7 dev efforts are concentrated on producing an "average" ROM for 40 or so supported devices. Our Nookcolor has unexpectedly better graphics hardware than all of them -- except Droid X.
Can't you try monitoring the CPU usage on stock and cm7 (top or similar), play a video and see if the CPU is way higher on cm7? I still see stutters on cm myself, and it would be sweet to see the video tweaked. We will also have new stuff to play with soon from B&N's froyo release. I'm guessing we will have a much easier time comparing apples to apples and diagnosing these issues if stock was 2.2 . There are a ton of factors in play (no pun intended), and we can all help by testing. It seemed like the last big jump in cm was prompted by the dude that found the video worked better with his bluetooth headset. That's the kind of thing that would take one person FOREVER to find, but amongst hundreds or thousands of testers becomes apparent. Test, and post results, and try not to be too emotionally attached to the issues. If it makes sense people will notice.... problems only arise when people start guessing, ranting, etc... (xda kids stuff) The nook is awesome and is only getting better
i would disagree - this has more to do with what codecs/containers are being supported rather than hardware acceleration
nook color at 2.1 did play that video but it could not play other formats becuase it did not support the codecs
same with flash - nook color 2.1 played that mp4 file but take same mp4 file and wrap it in a flash container and it cannot play it
nemir said:
If Nook Color' sample video cannot play by CM7 RC4 so hardware decoding is still disabled.
Here is the sample video from official Nook Color intro I extracted from latest firmware (1.10) :
http://www.mediafire.com/file/s5ka0xkdnsf4ajo/welcome_video.mp4
If default video player cannot play so hardware decoder still not enabled for CM7 RC4 and all variants...
Managing to play the video by means of diffrent 3rd party applications ( all video player that decode software and hardware based) make no sense...
Click to expand...
Click to collapse
cyberslug23 said:
Can't you try monitoring the CPU usage on stock and cm7 (top or similar), play a video and see if the CPU is way higher on cm7? I still see stutters on cm myself, and it would be sweet to see the video tweaked. We will also have new stuff to play with soon from B&N's froyo release. I'm guessing we will have a much easier time comparing apples to apples and diagnosing these issues if stock was 2.2 . There are a ton of factors in play (no pun intended), and we can all help by testing. It seemed like the last big jump in cm was prompted by the dude that found the video worked better with his bluetooth headset. That's the kind of thing that would take one person FOREVER to find, but amongst hundreds or thousands of testers becomes apparent. Test, and post results, and try not to be too emotionally attached to the issues. If it makes sense people will notice.... problems only arise when people start guessing, ranting, etc... (xda kids stuff) The nook is awesome and is only getting better
Click to expand...
Click to collapse
Sure, customizations and many other improvements over "standard" CM7 ROM are welcome at any time, it's just an apparent lack of basic GPU/DSP functioning, as nemir stated, what might cause a somewhat critical attitudes. I repeat, the work of dalingrin is awesome, but there are still many questions/problems remain unresolved:
-- the "original" size of an audio "buffer" (if I get it right) was either zero, or small, or adaptive, plus small anyway. Wasn't it an indication that hardware decoding when functional didn't need any?
-- the addition of 32(?) of whatever units to that buffer brought a smoother video playback on YouTube, but can be also an indication that video playback can now easily fall back to software decoding;
-- switching the audio pipeline to push it via BT encoding might be originally either working better, or didn't need to be HW assisted at all. In any case, lipsyncing was missing, just like when the software decoding beyond bandwidth specs was involved
As for how many dudes it take to find a solution out of thousands of NC's inventive users, I'd rather try to find a real TI OMAP3/Zoom2 engineer or two who are NC owners and obviously ROFLing now seeing all these attempts at XDA Devs. In other words, they not only know the solution, it's offered in the open at their gits. It's our kernel level that cannot take it. CM7.x will be formidable when based on 2.6.36...38.
aludal said:
Exactly! I was trying to make sense of this mess from January in my blog fineoils.blogspot.com. With a Nookie Froyo, Nookkolor started to lose everything that was there of hardware decoding AND hardware rendering. I was laghed at by CM7 NC dev dalingrin on my suggestion that lots of HW assistance in video playback is based on SGX, especially the HW overlay. CM7 team is of opinion that mp4/H.264 decoding can be made in DSP (IVA2 in our case) audio buffers for which were that "magic video fix" at the CM7 nightly 17 level. What we have is more or less smooth YouTube 2.1.16 (less smooth than EVO's 2.0.x "HQ" YouTube for Eclair) and stuttering/losing frames Flash 10.1...10.2 ("inline YouTube), plus stuttering local file playback with more than 480p or so. I have no indication that any HW-conscious FFmpeg codecs was ever used. NEON/Stagefright framework is missing/broken for unknown reason. Only Opera Mobile is capable of using 2D hardware assisted UI scrolling/layout, any other app/Webkit/launcher/wallpaper has no idea they all can use 2D/3D hardware acceleration, as, yes, drivers are broken/falling back to SW too easily. Sure, VOME engine by VisualOn might be just promised to AOSP 2.3.3 but never made it there, however I don't understand why latest Omapzoom commits on SGX driver and a special OMAP3 Adobe Flash Plugin couldn't be used.
Sorry for the long rant, but it seems that 90 % of CM7 dev efforts are concentrated on producing an "average" ROM for 40 or so supported devices. Our Nookcolor has unexpectedly better graphics hardware than all of them -- except Droid X.
Click to expand...
Click to collapse
Yeah you are right...
We must accept the lack of full potential power of NC's 2D / 3D GPU for both custom ROMs (CM and other variants) and OFFICAL STOCK ROM...
I have Archos 5 Internet Tablet which has only 256 MB RAM and same CPU ( 800 Mhz ) and Archos 5 Internet Tablet can play 720p .mkv .avi .mp4 .wmv files without any problem...
Moreover, Nook Color has higher RAM and can be overclocked to 1 Ghz ...
Like Archos 101 Nook Color has same GPU ...
I would prefer 800 Mhz ( maybe 1 Ghz overclocked) normal CPU with fully usable GPU ...
Processor • ARM Cortex A8 at 1 GHz with DSP
• Graphic accelerator: 3D OpenGL ES 2.0
Video Playback1 • MPEG-42 HD (up to 720p, 30 [email protected])
• MPEG-42 ([email protected] AVI, up to DVD resolution, 30 [email protected])
• H.264 HD ([email protected] up to 720p, 30 [email protected])
• WMV9/VC1 (AP up to 720p 30 [email protected])
• M-JPEG (Motion JPEG Video) in VGA resolution
With optional plug-in (downloadable on www.archos.com):
• Cinema: MPEG-2 (up to DVD resolution MP/D1, 30 [email protected] Mbps)
With the above codecs, the device can play video files with the following extensions: AVI, MP4, MKV, MOV, WMV, MPG, PS, TS, VOB, FLV, RM, RMVB, ASF, 3GP
Audio Playback1 • MP3 CBR & VBR
• WMA, WMA-Pro 5.1
• WAV (PCM/ADPCM)
• AAC, AAC+ 5.13
• OGG Vorbis
• FLAC
Click to expand...
Click to collapse
http://www.archos.com/products/ta/archos_101it/specs.html?country=us&lang=en
Here is the table of CPU and GPU list
http://en.wikipedia.org/wiki/Texas_Instruments_OMAP
For Nook Color:
OMAP3621 800 MHz ARMv7 ARM Cortex-A8 PowerVR SGX530
Another information about NC
http://www.engadget.com/2010/10/28/nook-color-processor-revealed-arm-cortex-a8-based-ti-omap3621/
So Archos 101 (1024x600) can be ported to NC to utilise ...
CM7 is generic and does not utilise the power of NC's GPU ... CM7 is beneficial for bluetooth and latest android 2.3.3 ... But Arhos firmware has a better full utilised GPU driver...
Frankly, the lack of GPU can NOT be accepted. Focusing on "CPU overclock" does not make sense if you have potential of better GPU driver...
Cool story.
CM7 does have hardware accelerated video.
Also it is the DSP chipset which controls what formats/resolutions are acceptable, not the GPU. Ours is incapable of playing 720p video in hardware acceleration. Not to mention it's a 854x480 hardware accelerator, so 1280x720 video would be wasted anyway.
You guys are loud.
That welcome video won't play because the stock software was able to tell it to play sideways. We can't do thatyet . We CAN hardware accel videos such as this:
http://www.mediafire.com/?d42dmvva9vbigm2
You know, in 16:9 instead of 9:16?
aludal said:
Exactly! I was trying to make sense of this mess from January in my blog fineoils.blogspot.com. With a Nookie Froyo, Nookkolor started to lose everything that was there of hardware decoding AND hardware rendering. I was laghed at by CM7 NC dev dalingrin on my suggestion that lots of HW assistance in video playback is based on SGX, especially the HW overlay. CM7 team is of opinion that mp4/H.264 decoding can be made in DSP (IVA2 in our case) audio buffers for which were that "magic video fix" at the CM7 nightly 17 level. What we have is more or less smooth YouTube 2.1.16 (less smooth than EVO's 2.0.x "HQ" YouTube for Eclair) and stuttering/losing frames Flash 10.1...10.2 ("inline YouTube), plus stuttering local file playback with more than 480p or so. I have no indication that any HW-conscious FFmpeg codecs was ever used. NEON/Stagefright framework is missing/broken for unknown reason. Only Opera Mobile is capable of using 2D hardware assisted UI scrolling/layout, any other app/Webkit/launcher/wallpaper has no idea they all can use 2D/3D hardware acceleration, as, yes, drivers are broken/falling back to SW too easily. Sure, VOME engine by VisualOn might be just promised to AOSP 2.3.3 but never made it there, however I don't understand why latest Omapzoom commits on SGX driver and a special OMAP3 Adobe Flash Plugin couldn't be used.
Sorry for the long rant, but it seems that 90 % of CM7 dev efforts are concentrated on producing an "average" ROM for 40 or so supported devices. Our Nookcolor has unexpectedly better graphics hardware than all of them -- except Droid X.
Click to expand...
Click to collapse
What would it take to get a working patch to enable 2D/3D HW acc? I mean, if the folks working on CM7 won't take the approach you mention.
nemir said:
Here is the table of CPU and GPU list
http://en.wikipedia.org/wiki/Texas_Instruments_OMAP
Click to expand...
Click to collapse
That link tells you right there why we can't play 720p but the Archoses can:
OMAP3621 vs OMAP3630
They have a better DSP processor.
CM7 is generic and does not utilise the power of NC's GPU ... CM7 is beneficial for bluetooth and latest android 2.3.3 ... But Arhos firmware has a better full utilised GPU driver...
Frankly, the lack of GPU can NOT be accepted. Focusing on "CPU overclock" does not make sense if you have potential of better GPU driver...
Click to expand...
Click to collapse
The GPU and the DSP of the Nook Color work fine in CM7. We are able to play games just as well as rooted stock does, and videos I have encoded that maxed the rooted stock (as it had as high of a bit-rate as I could get without frameskipping) still play fine using Vital player on CM7.
As chisleu stated its not perfect, but its certainly working because the Nook Color's CPU can't even come close to playing my files.
Overclocking NC to 1 or 1.1 Ghz should give same performance as Archos's...
By the way, Motorola DEFY has 3610 GPU but it can plays 720p files by means of changing lib files ...
http://forum.xda-developers.com/showthread.php?t=935017
We can try this method to our NC to play 720p movies ...
As I said before latest stock NC has more recent builds in lib folder. CW RC4 uses old lib files...
Anyone can compare and see the difference between latest stock ROM and latest CW R4... CW R4 does not update latest official files from lib (its sub folders and files too)
hey nemir how bout taking us to solution space
nemir said:
Overclocking NC to 1 or 1.1 Ghz should give same performance as Archos's...
By the way, Motorola DEFY has 3610 GPU but it can plays 720p files by means of changing lib files ...
http://forum.xda-developers.com/showthread.php?t=935017
We can try this method to our NC to play 720p movies ...
As I said before latest stock NC has more recent builds in lib folder. CW RC4 uses old lib files...
Anyone can compare and see the difference between latest stock ROM and latest CW R4... CW R4 does not update latest official files from lib (its sub folders and files too)
Click to expand...
Click to collapse
nemir said:
Overclocking NC to 1 or 1.1 Ghz should give same performance as Archos's...
By the way, Motorola DEFY has 3610 GPU but it can plays 720p files by means of changing lib files ...
http://forum.xda-developers.com/showthread.php?t=935017
We can try this method to our NC to play 720p movies ...
As I said before latest stock NC has more recent builds in lib folder. CW RC4 uses old lib files...
Anyone can compare and see the difference between latest stock ROM and latest CW R4... CW R4 does not update latest official files from lib (its sub folders and files too)
Click to expand...
Click to collapse
Maybe you could try to copy over those lib files and see if it works? If it does then maybe cm7 devswill port it.
From 1.1 Nook Color with 1.1 ghz overclock
poofyhairguy said:
That link tells you right there why we can't play 720p but the Archoses can:
OMAP3621 vs OMAP3630
They have a better DSP processor.
Click to expand...
Click to collapse
That link mentions (quite vaguely) where variants of the same silicon (IVA2) are different:
Not highlighted in the list below is that each OMAP 3 SoC has an "Image, Video, Audio" (IVA2) accelerator. These units do not all have the same capabilities. Most devices support 12 megapixel camera images, though some support 5 or 3 megapixels. Some support HD imaging.
Click to expand...
Click to collapse
It is worth mentioning that encoding a (mp4) video is several times harder computational task than decoding it (as in playback). Sure I'm glad and happy for all owners of OMAP3 based smartphones with cameras which can record 720p, or 480p, or 360p or any medium to high bitrate video with their devices -- thanks to DSP HW acceleration of encoding process.
Now, (mp4) video decoding routine is much simpler process, and most important, it doesn't exactly use the same circuitry (the proof is in the possibility of live view while video is recorded on a given OMAP3-based device.) Sure, it doesn't conclusively prove anything, and TI engineers were not exactly helpful in detailing the 3621 IVA2 specs. But in my blog I was writing back in January/February on how smooth Evo's YouTube HQ could play clips searched out by "1080p" "Full HD" "IMAX" and the like keywords. Today, it struggles (loses frames), or refuses to play them.
The adequacy of hardware decoding of at least 480p/720p mp4 on NC was proven back then. Sure, that was Eclair back then, and AOSP 2.3 has NEON framework/hardware Stagefright pipeline broken/unimplemented since -- probably in expectation of Renderscript of Android 3.0 (or 2.4), I don't know
Out of my years (2004 or so) of struggle with mpeg2/mpeg4 decoding of 1080i satellite streams I was of conviction that in HD video rendering the major computational task is a scaling, deinterlacing overlay: once you don't have it in your hardware (shaders of GPU: SGX530 in our case), you have a stuttering, A/V desynced video -- or no video at all. Sure, it was outdated DirectX games back then, but anyway.
------------------
fineoils.blogspot.com
The developer of DVD Catalyst 4 is reporting a serious degradation in video playback with the 1.2 update. Anyone else experience this?
http://bookclubs.barnesandnoble.com...-2-FAIL/m-p/981754/message-uid/981754#U981754
If this is the case, and the methods discussed for blocking OTA don't work, looks like I'll be joining the legions of CM7 users. Video playback on the NC is a huge draw for me.
Unfortunately looks like I'll need a crash course. Doing some cross country traveling on May 7 and want to have a fully functional, video playback capable NC on that date.
dsf3g said:
The developer of DVD Catalyst 4 is reporting a serious degradation in video playback with the 1.2 update. Anyone else experience this?
http://bookclubs.barnesandnoble.com...-2-FAIL/m-p/981754/message-uid/981754#U981754
If this is the case, and the methods discussed for blocking OTA don't work, looks like I'll be joining the legions of CM7 users. Video playback on the NC is a huge draw for me.
Unfortunately looks like I'll need a crash course. Doing some cross country traveling on May 7 and want to have a fully functional, video playback capable NC on that date.
Click to expand...
Click to collapse
Its not really a quality issue, the smoothness of the video playback is affected.
After updating, the videos I already had on my NOOKcolor just looked like frames were being skipped or doubled. Its hard to describe, but they just look "off"
I tried a bunch of different conversion tools and a collection of different settings, and all resulted in similar playback issues, which basically points to an issue with the update rather than the conversion tool used.
I managed to play 3000Kbps h264 video on the NOOKcolor before the update, but now 800Kbps files have playback issues.
Testing youtube produces similar results. While I only played a few trailers from youtube, it appears quality is locked to 360, and even then I get audio sync issues.
I haven't tried the 1.2 update but I did integrate the hardware codecs from 1.2 into to CM7 and saw the same thing. For now I'm sticking with our existing codecs as they perform better.
dalingrin said:
I haven't tried the 1.2 update but I did integrate the hardware codecs from 1.2 into to CM7 and saw the same thing. For now I'm sticking with our existing codecs as they perform better.
Click to expand...
Click to collapse
some people reported that rebooting seem to fix this?
Canadoc said:
some people reported that rebooting seem to fix this?
Click to expand...
Click to collapse
The developer of DVD Catalyst 4 conversion software has posted sample video files that demonstrate the degraded video quality. So I don't think a simple reboot will fix things. If it were that simple, I think he'd have figured it out, since his paychek in part depends upon the Nook Color being a decent platform for watching movies.
Sorry : Wrong Thread.
Mine worked but the selection method is key
My MP4's worked flawlessly with the new update - I ripped them from my own DVD's using DVD Catalyst 4.0 and the setting for Nook Color. BUT, they didn't work using the gallery - I had to select them using the My Files folder in the library app (I have two full length videos on emmc and two on my 8 Gb SD Card (a Transcend Class 6) - either choice worked.
I was looking at the new build.prop just now, and it's specifying a heapsize of 64M.
That seems to be very high to me. If someone's got a rooted 1.2, it might be interesting to see what manipulating the heap does for video playback. I'm still holding off on updating mine.
I'm running vegan tab gingerbread edition and flash works great, can play video through browser even with the default flash app found through the market. But I was wondering if its possible to get quality over 480P?
Thanks
Flash performance
I don't know of any Android devices that can credibly play flash videos in a browser at resolutions higher than 480p; some not even that dense. This has more to do with the underlying .flv format and Adobe's code implementation of Flash than with the device. My Galaxy Tab 10.1 will just barely do 480p inside a browser window - maybe 10-15 FPS if the content has substantial movement. But it can play it's own 720p videos at full frame rate without issue.
Part of the problem is, Android is an operating system, not a platform in the way that iOS+iPad hardware is. This leaves every phone and tablet manufacturer free to choose from a variety of processor and video implementations. This is one of the things I like most about Android - choice, and freedom (as in speech). But like any freedom, this one comes at a price, and that is the need for software developers to support a wide range of hardware implementations. This is not much of a problem for Angry Birds, but it is a huge problem for Adobe because the decoding of flash video is computationally intensive.
If Flash was open source the community would solve the problem, in the same way that the Linux Kernel runs on many platforms today. But the codecs involved in Flash (VP6, Sorenson H.263, H.264) are all protected by patent, and that makes open source a non-viable solution.
Adobe has not done a great job implementing Flash video for Android, in part I think because they know the war is already lost. The number of iPads in the wild (pushing 20 million this year, I think) and Apple's refusal to run Flash means that alternate solutions like HTML5 and custom video apps (think Hulu Plus or Netflix) will be developed no matter what Adobe does. So why pour money down a black hole?
Hopefully this will get better, as I would like to be able to watch 720p video on my 720p device using Flash. But I just don't think it is going to happen.
HTC sensation and Samsung galaxy s2 working 1080p plays video youtube....
My Samsung captivate with apex 9.3 with talon kernel can play 1080p on YouTube with dolphin hd. But my g tablet can only 720 poorly. But with Mx player I can watch 720p mkv,Avi, and mp4 no problem.
Edit: With Calkulin+Clemsyn 1.5ghz Froyo Combo 1.2 version 6, I was able to watch hd reviews on gametrailers. Even non overclocked using dolphin hd and latest flash from market.