Related
With all the different roms and different versions I'm getting really confused and which roms can do what.
I've tried phiremod v2 and cm7 nightlies and the youtube app doesn't work at all in either. Youtube in the browser I couldn't get to work in phiremod v2. I can watch youtube if I change my user agent to desktop with cm7 nightly but it's choppy.
Can somebody enlighten me as to what I should be running if I want working and smooth flash videos?
This is not an answer to your question -
But if the widespread rumors are correct, then the B&N Stock NC will be updated to 2.2 with Flash by the end of the month, and then if you root that, you will be able to sideload Youtube App for Froyo to that. In fact, the update is supposed to include a B&N Market, and one would expect B&N to have all the Free Google Apps in their Market at startup. (But that's just speculation.)
Flash Player 10.2 working for me
I downloaded Flash Player 10.2 earlier today and it installed and works much better. I am running Phiremod 4.1. I got the APK from: freewarelovers(dot)com/android/app/adobe-flash-player
It's important to remember that Flash is an application framework that can deliver video among MANY other things. If you're looking for a FLV video player, then the performance still is not here: it requires hardware support and we don't have the drivers yet.
BUT, if you want to play games and use interactive websites written in Flash, then try out 10.2. It is WAY more functional.
Interesting. Are you saying that there are no roms with smooth playing flash video? It seems odd to me that everybody is so happy with these roms when they can't watch any flash video smoothly.
flammenwurfer said:
Can somebody enlighten me as to what I should be running if I want working and smooth flash videos?
Click to expand...
Click to collapse
To specifically answer your question, smooth video is supported in Eclair (the native Nook rooted ROM) and, I think, it plays acceptably in Froyo; although I could be mistaken.
A lot depends on the size/quality of the video; standard definition (640x480) should play acceptably well in either of those OS versions. Higher definition may stall from time to time.
Gingerbread 2.3 (CM7, etc) still does not have working drivers for the hardware assist features of the chipset, and hardware assist is essential to smooth video playback.
Here are the specs on Nook Color CPU/GPU (from Androidtablets.net):
CPU Processor: ARM Cortex A8-based Ti OMAP 3621 @ 800 MHz (same processor as Droid 2 and Droid X)
GPU Processor: PowerVR SGX530 Graphics Rendering: Open GLES1.1/2.0 Hardware Scaling: 854x480 scaled to 1024x600 Video Formats: .3GP, .MP4, .3G2 ** Video Codecs: H.263, H.264, MPEG-4, ON2 VP7 ** Image Formats: JPEG, GIF, PNG, BMP ** (same GPU as Droid 2 and Droid X)
As you can see, the GPU can support a native resolution of 854 x 480 (which is scaled in hardware to 1024 x 600); H.264/MPEG4 video (which FLV is a kind of) can be decoded in the hardware with the appropriate drivers. At present, all the players have to do this through software, which frankly is beyond the capability of the CPU at 800 MHz or even overclocked at 1.1 GHz.
We need to be patient; those hardware drivers will come.
Ok, I think I get it now.
So the stock rom is the only option at the moment for smooth youtube and flash, correct? The Froyo, Gingerbread and Honeycomb roms do not have hardware decoding support?
So why are so many people running these other roms if they are missing a major function like that? What does CM7 and the other roms do that the stock rooted rom can't? Market?
flammenwurfer said:
So the stock rom is the only option at the moment for smooth youtube and flash, correct? The Froyo, Gingerbread and Honeycomb roms do not have hardware decoding support?
Click to expand...
Click to collapse
I am not sure whether the Froyo rom can play video smoothly. It does on Droid and other phones, so I would guess those drivers have been tried out. I had Froyo on my Nook Color for a while, but frankly can't remember how the video was.
flammenwurfer said:
So why are so many people running these other roms if they are missing a major function like that? What does CM7 and the other roms do that the stock rooted rom can't? Market?
Click to expand...
Click to collapse
It depends on what you need/want. For me, the text handling of Froyo was awful. I have a HTC EVO 4G (with Sense UI on top of native Froyo). On my phone, I can type pretty effectively. The user dictionary is fast and smart and if I make a mistake, I have an arrows-equipped keyboard to move the cursor to the text I want to correct and fix it.
Froyo (Android 2.2) on both my Nook Color and my Viewsonic G-Tablet were nothing like my Evo. The keyboard often got what I typed wrong and when I tried to set a cursor to make a correction, it would end up one letter off. I tried out a bunch of keyboards - some with arrows - and had an OK Froyo-based system, but as soon as a decent Gingerbread-based ROM came along (and Phiremod's is EXCELLENT!), I went with that.
In Gingerbread, you have a much more accurate keyboard and dictionary lookup. The keyboard still doesn't have arrows, but you have a very nice cursor positioning tool, plus the ability to select a little or a lot of text and copy/paste it anywhere throughout the system.
But, as you note, certain of the multimedia features aren't there yet. Since I use my tablets more as very handy computers and less as multimedia entertainment systems, the choice was pretty straightforward for me. I can wait a few weeks for video playback.
And, frankly, the reason a lot of people get excited about roms - and having lots of different roms - is because they are fun in and of themselves. They like to tinker. And with the Nook, if you have a few bucks to buy a couple of micro SD cards, you can have two or three swap-in brains that completely transform your tablet. And take them out and still have a factory fresh Nook reader. It's really kind of awesome when you think about it.
But your mileage will certainly vary. If high definition is a deal breaker for you, you may find the Nook ultimately inadequate even when the Gingerbread drivers (and eventually Honeycomb drivers) come out. There's only so much power under this hood. A tablet based on Tegra 2 (like the Viewsonic G-Tablet or Xoom) may be more what you're looking for. With the right drivers, though, we should get perfectly acceptable 480p playback.
glg
The rom you are looking for is nookiefroyo. I have great YouTube playback in app including high quality. In browser 360p plays fine, but anything above that is choppy.
I also have tested other flash websites. CNN was perfect, as was megavideo.
I purchase my nook a few days ago and thus far nookie froyo looks to be the latest and most complete rom out. That plus the softkey theme I installed and the honeycomb keyboard makes this tablet a force to be reckoned with. I might even have to post a video soon because I'm so amazed atnhow well this thing runs.
I'm on CM7 Android 2.3.3 and am very happy. Not sure if it's the websites I've been on or what, but pretty much all non-HD flash works flawlessly for me. I've OCed my NookColor to 925mhz and have tried probably 5 or 6 different websites (including youtube and zomganime) Certain embeded flash players work better than others I"ve noticed, also, so not sure why that is, but so far I'm very happy. I even was running 3 flash videos (just to test it out) at once the other day, only one was choppy beyond watching. Oh I'd also like to note that it SEEMS to work better with Dolphin Browser, but that could again just be the website(s) I was on.
Sure not having a YouTube app kinda sucks, but the desktop website works fine.
Just a little notice, YouTube app doesn't use Flash for playback, it grabs MP4 version of a video stream, which is meant to play on mobile devices.
JLCollier2005 said:
I'm on CM7 Android 2.3.3 and am very happy. Not sure if it's the websites I've been on or what, but pretty much all non-HD flash works flawlessly for me. I've OCed my NookColor to 925mhz and have tried probably 5 or 6 different websites (including youtube and zomganime) Certain embeded flash players work better than others I"ve noticed, also, so not sure why that is, but so far I'm very happy. I even was running 3 flash videos (just to test it out) at once the other day, only one was choppy beyond watching. Oh I'd also like to note that it SEEMS to work better with Dolphin Browser, but that could again just be the website(s) I was on.
Sure not having a YouTube app kinda sucks, but the desktop website works fine.
Click to expand...
Click to collapse
As in audio and video actually work smoothly (and are in sync)? What version of CM7 are you on?
I would like to know as well.
I'm on the latest CM7 Nightly and just installed the OC kernel. Youtube videos at 360p are playing ok now, but the audio is out of sync.
I might have to give Nookie Froyo another try. Interesting that the Youtube app works so well for you. I could have sworn that I would just get an error every time I tried to play anything.
flammenwurfer said:
Ok, I think I get it now.
So the stock rom is the only option at the moment for smooth youtube and flash, correct? The Froyo, Gingerbread and Honeycomb roms do not have hardware decoding support?
So why are so many people running these other roms if they are missing a major function like that? What does CM7 and the other roms do that the stock rooted rom can't? Market?
Click to expand...
Click to collapse
Eclair does hardware video decoding but no flash. Froyo and cm7 both do flash and froyo has you tube and video harddware support. However froyo for me at least has buggy wifi and screen of death issues which made it non viable for me. Hope this helps.
From Nook Color dual boot with CM7
That does help. Thanks for the clarification.
I've heard good things about Nookie Froyoa so I will probably give that another try. I find it a little frustrating that there is not a single rom with everything working, but I know that's just the norm for hacking together roms. Oh well... Hopefully the update coming from B&N will help iron out the few issues that are left.
Honestly, most of my time will be spent reading, web browsing and playing a few games. I would just like to be able to pull up a funny video for friends every once in a while. I don't plan on watching movies or anything on it.
flammenwurfer said:
That does help. Thanks for the clarification.
I've heard good things about Nookie Froyoa so I will probably give that another try. I find it a little frustrating that there is not a single rom with everything working, but I know that's just the norm for hacking together roms. Oh well... Hopefully the update coming from B&N will help iron out the few issues that are left.
Honestly, most of my time will be spent reading, web browsing and playing a few games. I would just like to be able to pull up a funny video for friends every once in a while. I don't plan on watching movies or anything on it.
Click to expand...
Click to collapse
Agreed I had thought froyo would be best compromise as it was fast had dsp and flash working, but the sleep of death and wifi connection issues led me to rebooting the thing many times/day which was a real pain.
For now I have a dual boot setup (see thread in development forum) So that I boot into eclair or CM7. This way I do most of my activities in or other rom and reboot into the other when I need say to watch a video or use stock B&N reader.....
Another thing I haven't really thought about. How does battery life compare between the roms? I seem to remember comments here and there about CM7 roms having worse battery life than froyo or stock.
I would suggest to those trying Nookie Froyo on eMMC now to try the kernel posted in post #770 of the Dalingrin kernel thread on the development forum. For myself and several others this kernel is solid and yields no wake or wifi issues whatsoever. Until a more stable interactive govenor kernel is developed this is the one I'll stick with.
glgehman said:
And with the Nook, if you have a few bucks to buy a couple of micro SD cards, you can have two or three swap-in brains that completely transform your tablet. And take them out and still have a factory fresh Nook reader. It's really kind of awesome when you think about it.
Click to expand...
Click to collapse
Indeed. I'm a nooknoob but long time techie and am brimming with questions. Is that quote accurate -- that reverting to "factory fresh" state can be as simply as removing your SD card? (Because that's not the impression I've been getting; I thought you needed to do the 8 failed boots thing and/or reload ROMs.)
Hmm, guess not. I just noticed the thread titled "[HOW-TO] : Restore Nook Color back to stock EASILY".
I believe you can run most of the roms from the sd card without modifying the internal system. I don't know if you can do it without rooting though. You might have to root, then you an try roms on sd card. Someone else will have to confirm that or tell me I'm wrong , as I've not tried any of the sd card versions.
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 have noticed that the flash player in the GB rom from Samsung is GPU hardware accelerated. Samsung probably had some discussions with Adobe to make it happen and I am glad they did When I was on Froyo, I had trouble playing 480p, but when upgrading to GB, I can play 1080p Youtube videos pretty smooth.
One thing I did notice is that the GPU HW acceleration is partially broken when you update the flash player (from 10.1 to 10.3) in the market. 1080p becomes impossible to play, but the other resolutions still work.
Now you may be thinking "if it's not broken, don't fix it" and thats the problem. Flash 10.1 has interface issues. For example, when I try to select the resolution I want to play my Youtube videos at, the menu appears for a split-second and then disappears.
Therefore, my question is that is it possible to hack this flash player, to give it to the interface fixes of 10.3, but still have the same performance?
P.S. The GB rom I am on is Serendipity VII. The flash player that comes with this rom is 10.1.
bumpity bump bump
How are you displaying 1080p on the captivate? Its screen maxes at 4780?[EDIT-that should be 480 ...]
Sent from Planet Oa.
hal.jordan said:
How are you displaying 1080p on the captivate? Its screen maxes at 4780?
Sent from Planet Oa.
Click to expand...
Click to collapse
Next we can discuss how well it plays 4K video.
Edited, thanks for the assist Mikey.
Sent from Planet Oa.
XBMC works fine on my Nook Color, see details here: http://fineoils.blogspot.com
Has anyone got XBMC working? I installed the correct files from the link. After the initial loading screen, I just get a black screen. Using the 1/6/13 nightly. Any help would be appreciated.
emax said:
Has anyone got XBMC working? I installed the correct files from the link. After the initial loading screen, I just get a black screen. Using the 1/6/13 nightly. Any help would be appreciated.
Click to expand...
Click to collapse
Mine is 1/4/2013, but if it's not later than 1/12/2013 I think it doesn't matter. I also don't use 1100 kernel which was a reason for too much sorrow with apps, especially with 3rd party apps. For the XBMC on Android, there are some self-help forums popping up. Then, a good XBMC installation may take quite a time for online updating of video add-ons at the first start. Mine get stable after maybe 5 minutes. Every second start and launching other (new) add-on (apart from obvious 1Channel) takes more time.
Then, MX Player should be installed and tuned up first. It also should be started and exited prior to launching XBMC.
Then, tons of streams may not be there at a given time, or at all.
XBMC also works fine on my Samsung Galaxy Tab GT-P1010 (WiFi-only model) running Irish Gingerbread. No HW rendering though.
aludal said:
XBMC also works fine on my Samsung Galaxy Tab GT-P1010 (WiFi-only model) running Irish Gingerbread. No HW rendering though.
Click to expand...
Click to collapse
Has any of that been integrated into the XMBC nightly, or do your directions still apply for the latest nightlies?
I didn't use XBMC nightlies, I used xbmcandroid.com unofficial build + NEON MX Player of (I think) mid-January. They might have some better builds in their main trunks, but I don't believe these offer anything of HW rendering for TI OMAP3621 as it's above our SoC capabilities once the stream has above 480p resolution or too high bandwidth whatever hits first. Some 720p streams/static files play good enough (22...27 FPS) in SW decoding mode, but that's it, end of a story for poor Nookie.
I might be interested in XBMC-Android + BS Player combos once there will be indications that BS Player can buffer/decode better than MX Player.
TI OMAP3630 in my SGT P1010 is totally equal to Nookie in XBMC handling terms, and there's not a single line of code in GB Android for IVA2 that is replaced with something better in CM10.1 (JB) that I run now in my Nook.