I have just got a Kaiser/TYTNII , I have jockeys spl3.28 And duttys WM6.1 On it. Quite pleased with being able to do this first go thanks To all the info on these forums....
Question.. I need to play some videos on my phone (work Related Unfortunately) But the playback is shocking the video just freezes while the sound continues. normally the sound associted with the clip is finished before the video is a quarter way through.
Phones I have had years ago are better than this. Any way to fix this. these are just windows media files. Any adivice would be helpful.....
Kaiser/TYTNII
Duttys Toch v6.1 WWE
Radio 1.64.08.21
No offense but, you're kidding right?
Read through this site; everything is explained there:
http://www.htcclassaction.org/
The latest ROMs have some improvements in video playback. The commercial 'Coreplayer' app has some builtin support for some part of the Kaiser video playback hardware (QTv).
If you did already know this, try reconverting the vids to a lower resolution and bitrate. That will help.
The media you're trying to play, what resolution and bitrate has it got?
Good luck!
Sorry If this in the wrong place new to this forum. Resoloution Not sure in propertys it says the bit rate is 668kbps...
Don't worry, this isn't really the wrong place. But since the problem is so very well known, this question could get you some harsh remarks.
What about the resolution of the vid?
Furthermore, which WM6.1 realease from Dutty are you using?
I first had the Apr29 release before switching to the Jun07 release. I play my media using 'Coreplayer'. The Apr29 release was much smoother for playback than the latest Jun07 release. If you're using the latest release, you might have to check his thread for any updates regarding the playback performance. I still have to check it myself...
Properties of the vid does not display resolution only bit rate @ 668kbps...
And not you-tube app either, that has been spotless in performance. However other streaming sites, as well as certain "adult" app's produce a "sorry this video cannot be played".
Worked fine in eclair, not so good on FroYo...searched hi and lo, but to no avail. Just lots of other stumped folks.
Anybody????!?!
JamesAK said:
And not you-tube app either, that has been spotless in performance. However other streaming sites, as well as certain "adult" app's produce a "sorry this video cannot be played".
Worked fine in eclair, not so good on FroYo...searched hi and lo, but to no avail. Just lots of other stumped folks.
Anybody????!?!
Click to expand...
Click to collapse
Why do you want to watch porn on a 4" screen when your computer has a bigger screen?
But as for your question, all depends on the format of the video. Try a different video app as your default and see if it works. If not, I guess you'll have to go back to Eclair.
While you understand what you are saying, im looking for root causes & possible fixes, not hearsay and conjecture. I'm not the only one wondering why there is video restrictions on the froyo leak. (well besides att likes to nanny)
I don't have these restrictions you speak of. I've never had any problems with video playback of any format. And as you can see in my signature, I am running the leaked 2.2
I also have no problems with video playing, RockPlayer runs very well on the Captivate during saved file usage, damn near any format I could throw at it....Except for streaming files. (3gp). Am I missing a way to make the third party video app the "default" for all incoming media? (streaming & saved)
I don't believe there is an option for default streaming app.
Been using this last few days and overall am quite impressed. It is pretty fast, has all that froyo goodness....Flash works though video is still slow and jerky
Have following issues:
YouTube- shows but videos don't play in app
Music- my mp3 which play on autonootered 2.1 don't work.
Statusbar shows no service cell reception icon and lockscreen says no service.
Wifi not always reconnecting from sleep without manually turning off/on.
Anyone else have any of these issues? Any fixes?
What are your pleasant surprises so far?
I think you need to look here.
And here.
BigBadger said:
I think you need to look here.
And here.
Click to expand...
Click to collapse
Thanks, I guess. Red all the threads and am reporting my issues and seeing if they really unique to me as most I have mentioned are not discussed,....
mp3 the no service message on lockscreen.....
On YouTube, you may want to look at the "HQ" YouTube thread I started here and detailed a tidbit more in my blog (fineoils.blogspot.com).
Takes a careful deleting a stock youtube.apk.
If it won't work (me, I run simply Auto-Nootered and partially tweaked NC with stock A2.1, and HD YouTube is working just fine) then this is your "usability" at this stage.
You fail to mention Flash 10.1 in your list of problems with Nookie Froyo, does it mean you can watch HQ/HD Flash video already?
Don't get me wrong: the move to Froyo is a great development. But so far, it's more of a proof of a concept. For usability, it may take tons of tweaks and optimizations of Cyanogen class, plus backporting the best features and kernels of Android 2.3
aludal said:
On YouTube, you may want to look at the "HQ" YouTube thread I started here and detailed a tidbit more in my blog (fineoils.blogspot.com).
Takes a careful deleting a stock youtube.apk.
If it won't work (me, I run simply Auto-Nootered and partially tweaked NC with stock A2.1, and HD YouTube is working just fine) then this is your "usability" at this stage.
You fail to mention Flash 10.1 in your list of problems with Nookie Froyo, does it mean you can watch HQ/HD Flash video already?
Don't get me wrong: the move to Froyo is a great development. But so far, it's more of a proof of a concept. For usability, it may take tons of tweaks and optimizations of Cyanogen class, plus backporting the best features and kernels of Android 2.3
Click to expand...
Click to collapse
It is beyond proof of concept and 90% works as good or better than 2.1
Flash works. But seeing embedded flash video on some sites the video framerate is slow and jerky. Some sites play well. I suspect the 800 MHz processor and no hardware acceleration are the culprits and so OC to 950-1 ghz and hardware access might make it more useable.
So far I seem to ne the only one stating I can't get mp3 music playing so don't know if this is a known problem.
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.