•   
  • 1
  • 122
  • 123
  • 124(current)
  • 125
  • 126
  • 174
  •   
OpenELEC Testbuilds for RaspberryPi
Hi there rbej. Thanks for your contribution to the community. I just have a couple of questions before I try out your build


On this part of the instruction (bolded part)
(2013-02-27, 09:01)rbej Wrote: For Rpi 512Mb set gpu_mem=256 and change GUI to 1080p.

Do you mean that I should do this
(2013-02-27, 09:01)rbej Wrote: Add to advencedsettings <guires>XXXX</guires>

XXXX = GUI resolution. 480p,720p,900p,1080p. <guires>720</guires>, <guires>1080</guires> etc...

Or is it a different setting on config.txt?

And my seconds question is, is there a preparation I could make so I could roll back my OpenElec in case something goes horrible wrong.

Thanks a lot in advance
1) Nothing to do with config.txt, it's a setting in advancedsettings.xml which is a file you need to create in /storage/.xbmc/userdata.

2) Do you mean keeping all of your data too (metadata, thumbnails etc.), or just the system files? If the latter, then just backup (zip) the contents of your SD card FAT partition (it's 8 or 9 files, about 100MB total uncompressed). For the former, you'll need to take a complete image of the SD card, use Win32DiskImager to read the entire SD card and create a backup image.
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.
You can also use the openelec plugin to backup and restore.
 
  • Intel NUC Kit DN2820FYKH ~ Crucial DDR3L SO-DIMM 4GB ~ SanDisk ReadyCache 32GB SSD ~ Microsoft MCE model 1039 RC6 remote
(2013-04-09, 22:06)MilhouseVH Wrote: 1) Nothing to do with config.txt, it's a setting in advancedsettings.xml which is a file you need to create in /storage/.xbmc/userdata.

Thanks for the clarification. I was just a little confused because the instructions said "change to 1080p" twice and I thought I need to change it both in advancedsettings AND in config.txt (because the gpu_mem is there too)

Thanks again
Hi there everyone.

So, I updated my OpenElec with rbej's custom build. I followed the instructions EXCEPT for this part
(2013-02-27, 09:01)rbej Wrote: Before update please remove smb://openelec/userdata/addon_data/skin.confluence folder

Because this folder didn't exist in mine for some reason.

Anyway, my screen looked like this after the update

Image

Which is pretty hilarious actually.

I assume this would have something to do with the <guires> instruction.

Anyways, sorry I'm not so experienced here so please tell me what to do next

Thanks.



P.S. In addition, for this part

(2013-02-27, 09:01)rbej Wrote: For Rpi 512Mb set gpu_mem=256 and change GUI to 1080p.

I'm confused on what values should I change

This

gpu_mem=x

Or This

gpu_mem_256=128
(2013-04-10, 00:50)Squall13 Wrote:
(2013-04-09, 22:06)MilhouseVH Wrote: 1) Nothing to do with config.txt, it's a setting in advancedsettings.xml which is a file you need to create in /storage/.xbmc/userdata.

Thanks for the clarification. I was just a little confused because the instructions said "change to 1080p" twice and I thought I need to change it both in advancedsettings AND in config.txt (because the gpu_mem is there too)

Thanks again

Ah, well, it's also true you'll need to edit config.txt to set gpu_mem=256, but I thought you were referring to the <guires> setting and this is made in advancedsettings.xml. So really you need to edit both files... Smile

(2013-04-10, 04:38)Squall13 Wrote: P.S. In addition, for this part

(2013-02-27, 09:01)rbej Wrote: For Rpi 512Mb set gpu_mem=256 and change GUI to 1080p.

I'm confused on what values should I change

This

gpu_mem=x

Or This

gpu_mem_256=128


There are two ways of setting gpu_mem - a way that works the same on all Pis, eg. gpu_mem=128, and then gpu_mem_xxx where xxx represents the amount of onboard memory, so gpu_mem_256=128 would set the GPU memory on a 256MB Pi to 128MB, and gpu_mem_512=160 would set the GPU memory on a 512MB Pi to 160MB. In your case you can just set gpu_mem=256 - this would be the same as setting gpu_mem_512=256, and any gpu_mem_256 setting will be ignored on your device (assuming your device is a 512MB model).
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.
Hi Everybody.

I came to this thread while searching about RaspberryPi, XBMC/OpenElec and the PVR support.

I saw that some people had somewhat success while watching FullHD streams from their local tv broadcasters with rbej's builds.

I'm currently using a 512 MB RaspberryPi with the following lines in advancedsettings.xml:

<advancedsettings>
<alwaysforcebuffer>true</alwaysforcebuffer>
<freememorycachepercent>5</freememorycachepercent>
<guires>1080</guires>
</advancedsettings>

As the PVR server I'm using TvHeadend version 3.5.80~g7588429 on my server (an Atom Netbook), running Arch Linux. And the TV streams are encoded with H.264 and AAC audio (I live at Brazil).

The problem I'm having is that some high def channels start ok right after bootup, but if I stop the transmission in XMBC and try to watch the same channel again or some other HD channel, all I get is a black screen.

This happens as well as to other high def channels, not a specific one. SD channels seem to be ok, only with some audio sync problems. But tend to give a black screen after watching the first FullHD channel.

For the people that successfully managed to get their Raspberry's to work with XBMC and PVR, what is the setup being used? Is there any additional configuration I'm missing here?

Any help would much appreciated! Thanks in advance

PS: Also, as a minor problem, does any one know how to output XBMC's UI sounds through HDMI in Raspberry? Sometimes I tend to click the same button several time. thinking that I did't, at the first time.
(2013-04-10, 04:38)Squall13 Wrote: Anyway, my screen looked like this after the update

Image

Which is pretty hilarious actually.

I assume this would have something to do with the <guires> instruction.

Anyways, sorry I'm not so experienced here so please tell me what to do next

Delete file guisettings.xml (or at least all the whole resolutions section inside, if you don't want to lose most of your XBMC settings). After this, just reboot and enjoy your gorgeous 1080p XBMC.
*Damn, too slow Tongue*
Thanks pplucky. I'll try that when I get home.

Last question. On this part:

(2013-02-27, 09:01)rbej Wrote: For Rpi 512Mb set gpu_mem=256 and change GUI to 1080p.

For Rpi 256Mb set gpu_mem=100 and change GUI to 900p.

Why do I have to change the resolution depending on the memory? Does this mean that 256 RPis can't handle 1080?
(2013-04-10, 15:53)Squall13 Wrote: Why do I have to change the resolution depending on the memory? Does this mean that 256 RPis can't handle 1080?
If you don't do it, Rpi will run out of memory and crash/restart by itself (randomly, when the memory runs out).

XBMC GUI for Rpi was designed to be 720p for a reason.
(2013-04-10, 15:55)pplucky Wrote:
(2013-04-10, 15:53)Squall13 Wrote: Why do I have to change the resolution depending on the memory? Does this mean that 256 RPis can't handle 1080?
If you don't do it, Rpi will run out of memory and crash/restart by itself (randomly, when the memory runs out).

XBMC GUI for Rpi was designed to be 720p for a reason.

Aww that sucks. I didn't know that I had a 256 Pi just now. I thought all B models have 512mb. I guess I won't be able to enjoy 1080p right now Sad

Anyways, with your previous reply on deleting the guisettings.xml. If I just want to delete resolution parts, ill just remove everything with <resolution> on it right? I really don't want to redo all my settings lol

Thanks
(2013-04-10, 17:13)Squall13 Wrote: Aww that sucks. I didn't know that I had a 256 Pi just now. I thought all B models have 512mb. I guess I won't be able to enjoy 1080p right now Sad

Anyways, with your previous reply on deleting the guisettings.xml. If I just want to delete resolution parts, ill just remove everything with <resolution> on it right? I really don't want to redo all my settings lol

Remember the video with be true 1080p on a 256M board. Just not the GUI.
(2013-04-10, 17:13)Squall13 Wrote: Aww that sucks. I didn't know that I had a 256 Pi just now. I thought all B models have 512mb. I guess I won't be able to enjoy 1080p right now Sad

If you purchased your Pi after November 2012 there's every chance it's a 512MB model, unless you bought it from RS of course then who knows...

The easiest way to tell (without looking at the hardware*) is to run "cat /proc/cpuinfo | grep Revision" - if the last two digits are greater than 04 then you've got a 512MB model (eg. 0f is greater than 04).

Originally you could also tell by looking at the memory chip in the middle of the board - if its got K4P2G324 its a 256MB Pi, if its got K4P4G324 its a 512MB Pi, though not sure if this remains true (different memory suppliers etc.)
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.
(2013-04-10, 17:13)Squall13 Wrote: Anyways, with your previous reply on deleting the guisettings.xml. If I just want to delete resolution parts, ill just remove everything with <resolution> on it right? I really don't want to redo all my settings lol

You should find something like:
<resolutions>
<resolution>
...
</resolution>
<resolution>
...
</resolution>
....
</resolutions>

You should delete the whole block, save and reboot right after. Still then, I would go the way of deleting guisettings.xml (it is more straightforward, although you'll actually may have to redo some settings).

(2013-04-10, 17:35)popcornmix Wrote:
(2013-04-10, 17:13)Squall13 Wrote: Aww that sucks. I didn't know that I had a 256 Pi just now. I thought all B models have 512mb. I guess I won't be able to enjoy 1080p right now Sad

Anyways, with your previous reply on deleting the guisettings.xml. If I just want to delete resolution parts, ill just remove everything with <resolution> on it right? I really don't want to redo all my settings lol

Remember the video with be true 1080p on a 256M board. Just not the GUI.
Yeah, exactly. Forgot to mention that.
  •   
  • 1
  • 122
  • 123
  • 124(current)
  • 125
  • 126
  • 174
  •   



Logout Mark Read Team Forum Stats Members Help
OpenELEC Testbuilds for RaspberryPi12
This forum uses Lukasz Tkacz MyBB addons.