2011-08-20, 15:54
Konrad77 Wrote:Just forgot that I am using dirty regions in my advancedsettings.xml!
can it play 1280x720 60fps video without stuttering?.
Konrad77 Wrote:Just forgot that I am using dirty regions in my advancedsettings.xml!
iamjustme Wrote:can it play 1280x720 60fps video without stuttering?.I think XBMC switches to 24 fps while playing movies, the FPS shown in systeminfo is for the GUI.
Doraemonn Wrote:I've just noticed the buildbot has successfully compiled a new nightly dated 19th August. Anyone tried it?
http://mirrors.xbmc.org/nightlies/darwin/atv2/
ady199 Wrote:Just installed it and everything seemed to run fine until I loaded the MUZU.TV plugin. (one of my favourites ) it loads up ok and shows you a list of the music videos available, but when you select the video you want to play, its reboots the ATV2....
I know its a problem with this build as I've just gone back to the latest_atv2.deb build and the plugin works fine..............
I'm now sticking with latest_atv2.deb build...........works great for me.
keith Wrote:Don't post issues without a link to a pastebin'd debug log, otherwise it will never be marked as 'needs verifying' even.How do you tell if your post was marked as needs verifying?
pcm2a Wrote:How do you tell if your post was marked as needs verifying?
http://forum.xbmc.org/showpost.php?p=868...tcount=137
keith Wrote:Your post is great when I put together a new post with bugs you'll be on it.That will do, just let me know any other troubleshooting I can do to help provide additional information.
keith Wrote:So guys, should we have the other thread 'faq/issues/etc' be the 'bleeding list bugs' thread, or should we continue to have 2 different threads, one for 'from apt-get' and a nightly one for bug list/organization?
Maybe we should break it out, so we have a FAQ/installation/etc one thats geared for apt-get/new folks, and then a bug list one as well, that may list bugs from the repo, but also nightlies.
Kind of a 'this is FAQ on how it should work' 'now here's the bug list on broken things'.
If we do go down that route, I want to try to keep the FAQ thread specific to iOS/ATV2 just like the bug list thread.
Also should these threads be locked so we don't get troubleshooting on the threads themselves? I'm against locking threads AND continuing to post in them usually, but since the platform is fairly mature/usable now, I am not against this use of it for organizational purposes.
What does everyone else think of how we should structure it? Chuckles, Konrad77?
Recent new users, I'd love your input too on how you think this process could be improved on since you just started out.
keith Wrote:So guys, should we have the other thread 'faq/issues/etc' be the 'bleeding list bugs' thread, or should we continue to have 2 different threads, one for 'from apt-get' and a nightly one for bug list/organization?Iam new to xbmc, I think we should ask the devs instead, how do they want us to report problems. But IMO Threads are great for detect common problems and even clarify whats a user configured problem and whats a bug.
Maybe we should break it out, so we have a FAQ/installation/etc one thats geared for apt-get/new folks, and then a bug list one as well, that may list bugs from the repo, but also nightlies.
Kind of a 'this is FAQ on how it should work' 'now here's the bug list on broken things'.
If we do go down that route, I want to try to keep the FAQ thread specific to iOS/ATV2 just like the bug list thread.
Also should these threads be locked so we don't get troubleshooting on the threads themselves? I'm against locking threads AND continuing to post in them usually, but since the platform is fairly mature/usable now, I am not against this use of it for organizational purposes.
What does everyone else think of how we should structure it? Chuckles, Konrad77?
Recent new users, I'd love your input too on how you think this process could be improved on since you just started out.
Konrad77 Wrote:Iam new to xbmc, I think we should ask the devs instead, how do they want us to report problems.
Quote:09:59:59 T:140746752 WARNING: FileSmb::OpenForWrite() called with overwriting enabled! - smb://cifs:cifs@MISI%2dPC%2dx64/F/MyMedia/TvShows/Alphas/Alphas%2eS01E01%2ePilot%2e720p%2eWEB%2dDL%2eDD5%2e1%20%2eH264%2dKiNGS/Alphas%2eS01E01%2ePilot%2e720p%2eWEB%2dDL%2eDD5%2e1%20%2eH264%2dKiNGS%2een%2esrt
09:59:59 T:140746752 ERROR: FileSmb->Open: Unable to open file : 'smb://cifs:cifs@MISI%2dPC%2dx64/F/MyMedia/TvShows/Alphas/Alphas%2eS01E01%2ePilot%2e720p%2eWEB%2dDL%2eDD5%2e1%20%2eH264%2dKiNGS/Alphas%2eS01E01%2ePilot%2e720p%2eWEB%2dDL%2eDD5%2e1%20%2eH264%2dKiNGS%2een%2esrt'
unix_err:'d' error : 'Permission denied'
keith Wrote:So guys, should we have the other thread 'faq/issues/etc' be the 'bleeding list bugs' thread, or should we continue to have 2 different threads, one for 'from apt-get' and a nightly one for bug list/organization?
Maybe we should break it out, so we have a FAQ/installation/etc one thats geared for apt-get/new folks, and then a bug list one as well, that may list bugs from the repo, but also nightlies.
Kind of a 'this is FAQ on how it should work' 'now here's the bug list on broken things'.
If we do go down that route, I want to try to keep the FAQ thread specific to iOS/ATV2 just like the bug list thread.
Also should these threads be locked so we don't get troubleshooting on the threads themselves? I'm against locking threads AND continuing to post in them usually, but since the platform is fairly mature/usable now, I am not against this use of it for organizational purposes.
What does everyone else think of how we should structure it? Chuckles, Konrad77?
Recent new users, I'd love your input too on how you think this process could be improved on since you just started out.