•   
  • 1
  • 2
  • 3(current)
  • 4
  • 5
  • 12
  •   
Video of latest xbmc code on Raspberry Pi
#31
(2013-09-29, 14:24)MilhouseVH Wrote:
(2013-09-29, 14:15)evangelion Wrote: Will this build be available to install for us regular punters who don't have a clue about newclock3, makepkg options, forking/cloning repositorys etc? Smile

You can find it here. If you're already using OpenELEC, use a tool like 7zip (on Windows) to extract the four files from the target folder, copy them into your Update folder on the Pi and reboot to automatically update to this new *test* version.

Thanks! Spent too much time watching the Video and totally missed the linky Blush

Perfect timing as it happens, just doing a re-install following that exact procedure, I'll remove the Update folder current contents and use the linked one's instead,

Cheers!
Reply
#32
popcornmix, very nice and thank you for work on rpi!

I've got a similar install as you on a usb stick, it is certainly faster than the sdcard. I have to admit that yours seems a bit faster. Any chance you could post your config.txt and advancedsettings for us? Thanks.
Reply
#33
(2013-09-29, 19:20)Bonzi Wrote: popcornmix, very nice and thank you for work on rpi!

I've got a similar install as you on a usb stick, it is certainly faster than the sdcard. I have to admit that yours seems a bit faster. Any chance you could post your config.txt and advancedsettings for us? Thanks.

Sure:
http://pastebin.com/hjZ9Erw2
http://pastebin.com/LgDNDVF4
Reply
#34
Another useful trick is to run Milhouse's texture cache maintenance utility from time to time:
http://forum.xbmc.org/showthread.php?tid=158373

The first time an image is displayed, it gets reencoded (using imageres/fanartres sizes) and stored in a local cache.
This is obviously slower than just having to decode it. Eventally all your images end up in the cache, but rather than waiting for maximum speed, you can force it.
Run:
Code:
./texturecache.py c movies
./texturecache.py c tvshows
After that, viewing new unseen images will be quicker.
Reply
#35
What is your Temperature?
Reply
#36
(2013-09-29, 19:38)Koloss Wrote: What is your Temperature?
56C at moment, but it's not doing much.
Reply
#37
(2013-09-29, 19:29)popcornmix Wrote:
(2013-09-29, 19:20)Bonzi Wrote: popcornmix, very nice and thank you for work on rpi!

I've got a similar install as you on a usb stick, it is certainly faster than the sdcard. I have to admit that yours seems a bit faster. Any chance you could post your config.txt and advancedsettings for us? Thanks.

Sure:
http://pastebin.com/hjZ9Erw2
http://pastebin.com/LgDNDVF4

Ty, a few of your tweaks seemed to speed it up a tad bit more. Previously I had disabled the backgrounds since several months ago the Pi was too slow for this. Now it seems ok.
Reply
#38
(2013-09-29, 13:13)popcornmix Wrote: newclock3 is rebased off a newer point in Gotham. You either need to update xbmc in OpenELEC (with makepkg) to the same point,
or (what I did) rebase newclock3 onto a branch created from 7f45288, and then create the patches form there.

I've got it building now with mkpkg_xbmc-gotham, and also mkpkg_bcm2835-driver - many thanks.

(2013-09-29, 19:37)popcornmix Wrote: After that, viewing new unseen images will be quicker.

Now that the GUI can be run more easily at 1080p I'm just wondering if it's a good idea to re-cache fanart which has been converted from 1920x1080 to 1280x720 as a result of <fanartres>720</fanartres> in advancedsettings.xml.

Setting <fanartres> to 1080 should result in more-or-less original resolution fanart, shouldn't it? (It actually results in 1920x1088 artwork, is that slightly unusual height anything to worry about?)

Selectively re-caching ONLY fanart should be easy enough, using the following calls to texturecache.py:
Code:
./texturecache.py '@cache.ignore.types=+^(?!.*-fanart\.jpg$)' C movies
./texturecache.py '@cache.ignore.types=+^(?!.*[/\\]fanart\.jpg$)' C tvshows

This will cause the re-caching option to ignore everything but *-fanart.jpg (movies) and <tvshow folder>/fanart.jpg (tv shows). Modify as appropriate if using different naming conventions.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#39
Impressive.

Also like the skin, can you tell me which skin this is?
Reply
#40
(2013-09-29, 21:05)schumi2004 Wrote: Also like the skin, can you tell me which skin this is?

Amber.
Reply
#41
@popcornmix

I noticed you have readbufferfactor set to 10.0. Im also assuming that you do a nfs mount for your media and if so what is your rsize and wsize set at? Is there any reason to alter rsize and wsize with the newly added readbufferfactor? Im currently on a wired network so im not concerned with dropping packets so would larger packets mean increased performance? I personally noticed an increase in network performance switching to udp from tcp. Which would you suggest?

Teh
Reply
#42
Great achievement popcornmix.

Did you added a heatsink on top of the ram before overclocking.
Reply
#43
This makes me wish my RPi wasn't actively engaged in other duties. I might buy another just to play with.

Shit I might buy half a dozen as I have a lot of projects in my little old brain...
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#44
My Pi hangs after some time, with this overclocking 1000, 500, 500, 6!
force_turbo=1
Reply
#45
(2013-09-30, 10:49)Koloss Wrote: My Pi hangs after some time, with this overclocking 1000, 500, 500, 6!
force_turbo=1

Every single RPi has different overclocking limits. I own 3 and they're all different.

I own one that can go up to 1000/500/500/6 without problems. Another one won't go above 1000/333/500/2. You should try incrementing values step by step instead of jumping to 1Ghz immediately.

Also, using an USB stick for Storage helps a lot. Lock the SD card and you're good to go.
Reply
  •   
  • 1
  • 2
  • 3(current)
  • 4
  • 5
  • 12
  •   



Logout Mark Read Team Forum Stats Members Help
Video of latest xbmc code on Raspberry Pi6
This forum uses Lukasz Tkacz MyBB addons.