2013-10-01, 01:55
I re-cached (using texturecache.py) all my movie fanart (almost all of which is 1920x1080) with <fanartres> set to 1080.
With 256/256 GPU split, 1080p GUI and 32bpp textures, all the latest newclock3 patches and using next firmware (24 Sep f7cc4e449a45c6818095ce9ac87ee414290ea9a7), re-caching of the fanart went well although I did get the following:
and two fanart items failed to cache entirely - Alien and Spider-man 3.
It appears that Alien was partially cached - XBMC created a row in Textures13.db, but didn't create an image file in the Thumbnail folder. The only errors written to the log are those above.
Running "c movies", Spider-man 3 failed to re-cache with more "Bitstream corrupt" and "timeout" errors in the log.
I rebooted, and ran "c movies" once more, but still the Spider-man 3 fanart failed to cache, so maybe there is something "odd" about this JPG that causes the new decode/encode algorithm a problem? Viewing the uncached Spider-man 3 fanart item in the GUI results in the same "Bitstream corrupt" and "timeout" errors.
Removing the database row for the Alien fanart from Textures13.db allowed me to re-cache this fanart successfully, so maybe it was just a one-off issue, however Spider-man 3 is 100% repeatable. The Alien fanart does have a slightly odd resolution - 1980x1080 and it's not the highest quality - but that could be just coincidental.
I've uploaded the original fanart files to Dropbox: Alien and Spider-man 3.
The debug log when re-caching just Spider-man 3 is here (pastebin). Note that texturecache.py will try to download the artwork from XBMC three times before giving up. The logging of the "wait event timeout" message also continues for what seems like forever - I uploaded the log about 5 minutes after the last download request occurred at 00:05:03, but 15 minutes later (00:20:00) the logging of timeout events continues.
On to the decode (GUI) side of things... with the standard 5 second texture deletion timeout, I am able - with an IR remote control - to scroll rapidly through the Movies library in Fanart view (Amber skin, "Show Info" enabled) without any display related problems, although there are a *lot* of these messages in the log:
so the timeout setting could certainly do with tweaking (this is with Thumbnails mounted over NFS).
I'll rebuild with the texture deletion timeout set to 0, but I'm not expecting it to make much if any difference since I didn't see any memory related problems with it set to 5 seconds.
With 256/256 GPU split, 1080p GUI and 32bpp textures, all the latest newclock3 patches and using next firmware (24 Sep f7cc4e449a45c6818095ce9ac87ee414290ea9a7), re-caching of the fanart went well although I did get the following:
Code:
23:33:50 T:2980050000 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_ErrorStreamCorrupt, Bitstream corrupt
23:33:51 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:33:51 T:2980050000 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_ErrorStreamCorrupt, Bitstream corrupt
23:33:52 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:33:52 T:2980050000 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_ErrorStreamCorrupt, Bitstream corrupt
23:33:53 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:33:54 T:2980050000 ERROR: Previous line repeats 1 times.
23:33:54 T:2980050000 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_ErrorStreamCorrupt, Bitstream corrupt
23:33:55 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:33:56 T:2980050000 ERROR: Previous line repeats 1 times.
23:33:56 T:2980050000 ERROR: COMXCoreComponent::DecoderEventHandler OMX.broadcom.image_decode - OMX_ErrorStreamCorrupt, Bitstream corrupt
23:33:57 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:34:14 T:2779251792 ERROR: Previous line repeats 16 times.
23:34:14 T:2779251792 NOTICE: Thread JobWorker start, auto delete: true
23:34:15 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:35:12 T:2762474576 ERROR: Previous line repeats 57 times.
23:35:12 T:2762474576 NOTICE: Thread JobWorker start, auto delete: true
23:35:13 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:37:37 T:3043263296 ERROR: Previous line repeats 144 times.and two fanart items failed to cache entirely - Alien and Spider-man 3.
It appears that Alien was partially cached - XBMC created a row in Textures13.db, but didn't create an image file in the Thumbnail folder. The only errors written to the log are those above.
Running "c movies", Spider-man 3 failed to re-cache with more "Bitstream corrupt" and "timeout" errors in the log.
I rebooted, and ran "c movies" once more, but still the Spider-man 3 fanart failed to cache, so maybe there is something "odd" about this JPG that causes the new decode/encode algorithm a problem? Viewing the uncached Spider-man 3 fanart item in the GUI results in the same "Bitstream corrupt" and "timeout" errors.
Removing the database row for the Alien fanart from Textures13.db allowed me to re-cache this fanart successfully, so maybe it was just a one-off issue, however Spider-man 3 is 100% repeatable. The Alien fanart does have a slightly odd resolution - 1980x1080 and it's not the highest quality - but that could be just coincidental.
I've uploaded the original fanart files to Dropbox: Alien and Spider-man 3.
The debug log when re-caching just Spider-man 3 is here (pastebin). Note that texturecache.py will try to download the artwork from XBMC three times before giving up. The logging of the "wait event timeout" message also continues for what seems like forever - I uploaded the log about 5 minutes after the last download request occurred at 00:05:03, but 15 minutes later (00:20:00) the logging of timeout events continues.
On to the decode (GUI) side of things... with the standard 5 second texture deletion timeout, I am able - with an IR remote control - to scroll rapidly through the Movies library in Fanart view (Amber skin, "Show Info" enabled) without any display related problems, although there are a *lot* of these messages in the log:
Code:
23:39:52 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:14 T:2737308752 ERROR: Previous line repeats 21 times.
23:40:14 T:2737308752 NOTICE: Thread JobWorker start, auto delete: true
23:40:14 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:47 T:2737308752 ERROR: Previous line repeats 33 times.
23:40:47 T:2737308752 NOTICE: Thread BackgroundLoader start, auto delete: false
23:40:47 T:2728920144 NOTICE: Previous line repeats 1 times.
23:40:47 T:2728920144 NOTICE: Thread JobWorker start, auto delete: true
23:40:48 T:2812277840 NOTICE: Previous line repeats 1 times.
23:40:48 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:51 T:2868384848 ERROR: Previous line repeats 3 times.
23:40:51 T:2868384848 NOTICE: Thread JobWorker start, auto delete: true
23:40:52 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:52 T:2737308752 ERROR: COMXCoreComponent::GetInputBuffer OMX.broadcom.image_decode wait event timeout
23:40:53 T:2712142928 NOTICE: Thread JobWorker start, auto delete: true
23:40:53 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:54 T:2737308752 ERROR: COMXCoreComponent::GetInputBuffer OMX.broadcom.image_decode wait event timeout
23:40:54 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:54 T:2728920144 ERROR: COMXCoreComponent::GetInputBuffer OMX.broadcom.image_decode wait event timeout
23:40:55 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:55 T:2868384848 ERROR: COMXCoreComponent::GetInputBuffer OMX.broadcom.image_decode wait event timeout
23:40:56 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
23:40:57 T:2712142928 ERROR: COMXCoreComponent::GetInputBuffer OMX.broadcom.image_decode wait event timeout
23:40:57 T:2812277840 ERROR: COMXCoreComponent::WaitForOutputDone OMX.broadcom.image_encode wait event timeout
...so the timeout setting could certainly do with tweaking (this is with Thumbnails mounted over NFS).
I'll rebuild with the texture deletion timeout set to 0, but I'm not expecting it to make much if any difference since I didn't see any memory related problems with it set to 5 seconds.
