+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: XBMC General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: iOS support (/forumdisplay.php?fid=137)
+---- Thread: [old] Unofficial semi-nightly build FAQ/info/issues (here for archival purposes) (/showthread.php?tid=97246)
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104
- keith - 2011-05-08 20:01
Mr Zippy Wrote:Platform: ATV2
iOS version: 4.3
Apple TV version: 4.2.1
XBMC Build: 2 May
I am also seeing choppy playback with MKV (720p / h264), was fine with 17 April build.
pastebin a log with debugging enabled, also try the newer build.
- keith - 2011-05-08 20:07
fattoony Wrote:I am experiencing a problem with playback of .mp4 files. Very choppy, fps down to 10-12
Not sure if mp4 files are hardware accelerated so maybe its due to that, but hears the report…
XBMC log: http://pastebin.com/7NYicd3r
Media Info: http://pastie.org/pastes/1876223
Cranial is right, but that mediainfo does look AVC so unsure why it failed.
You can use:
http://www.xs4all.nl/~loekjehe/Split&Concat/
for a 'gui' to split, but the lazy way I usually do it is:
split -b 100m (filename)
and then use another terminal window to verify its onto the 2nd file and just ctrl-c it, and then test the first 100mb file. If the problem is there, I send that.
You could also do 50mb if it happens immediately.
If you could install the new build and test that first that'd be great too!
- fattoony - 2011-05-08 22:37
Hi Keith,
Tested on May 7th (Git:20110507-4b18017) same problem as before.
Included some new logs and a 50MB sample.
Should also point out that the mp4’s that I am having trouble with are downloaded from bbc-iplayer via “get iplayer automator”.
Don’t have any other .mp4 from a different source to test. But I’m pretty sure that they played ok before I started running the nightly.
Platform: ATV2
iOS version: 4.1.1
XBMC Build: May 7 (Git:20110507-4b18017)
Installed with dpkg -i latest_atv2.deb
XBMC log: http://pastebin.com/sBhK97DF
Media Info: http://pastie.org/pastes/1878906
Media sample: http://dl.dropbox.com/u/3955256/Doctor%20Who.s06e03.3.%20The%20Curse%20of%20the%20Black%20Spot.nfo.mp4
Playback fine on Platform: Mac OS X (10.7.0 i386). Built on Apr 18 2011 (Git:20110418-6281a05)
Kind regards,
FT
Un un unofficial builds.... - Cranial - 2011-05-08 23:55
Keith,
Your last build, how do I figure out the last commit included in that build?
I'm running Git:20110508-1d0c2f3 and there appears to be a bug where LCD Video Calibration is not being saved.
I think it might be related to this commit: [osx] Workaround to fix fullscreen switching in multi monitor setup. but I can't be sure.
*Edit* Just reverted to your May 07 build Keith and I can confirm this bug was introduced since then.
- davilla - 2011-05-09 05:47
Cranial Wrote:Keith,
Your last build, how do I figure out the last commit included in that build?
I'm running Git:20110508-1d0c2f3 and there appears to be a bug where LCD Video Calibration is not being saved.
I think it might be related to this commit: [osx] Workaround to fix fullscreen switching in multi monitor setup. but I can't be sure.
*Edit* Just reverted to your May 07 build Keith and I can confirm this bug was introduced since then.
if you change
#if defined __APPLE__
to
#if defined(__APPLE__) && !defined(__arm__)
in xbmc/guilib/GraphicContext.cpp ( line 310 ) does that fix the issue ?
- popcornmix - 2011-05-09 12:42
davilla Wrote:if you change
#if defined __APPLE__
to
#if defined(__APPLE__) && !defined(__arm__)
in xbmc/guilib/GraphicContext.cpp ( line 310 ) does that fix the issue ?
I tried that change, and my overscan calibration was still ignored. (Or had been reset to default on a previous run without this change).
I then set it up again, and it seeemed to work, and was still working after a restart.
However I didn't try setting calibration again before making this change, so I don't know if that could have worked anyway.
Perhaps Cranial can confirm that setting new overscan calibration does not get saved with top of tree.
- Cranial - 2011-05-09 14:10
popcornmix Wrote:I tried that change, and my overscan calibration was still ignored. (Or had been reset to default on a previous run without this change).
I then set it up again, and it seeemed to work, and was still working after a restart.
However I didn't try setting calibration again before making this change, so I don't know if that could have worked anyway.
Perhaps Cranial can confirm that setting new overscan calibration does not get saved with top of tree.
Won't get a chance to try it until tomorrow, but I'll let you know as soon as I can.
If you can set overscan and it stays set after leaving the calibration screen, then I'd say this fixed it. I couldn't get overscan calibration to stick with current build.
- Mr Zippy - 2011-05-09 14:22
keith Wrote:pastebin a log with debugging enabled, also try the newer build.
When I posted I thought I was running the latest build (7 May) but realised I was running 2 May, so I edited the post accordingly - probably should have deleted instead.
I have updated to 7 May build now.
Will test again later and post a log if applicable.
Thanks
[update]
Tested the MKV in question on my iMac core 2 duo and it's choppy in VLC too, so it must be a bad encode.
- popcornmix - 2011-05-09 15:32
Cranial Wrote:Won't get a chance to try it until tomorrow, but I'll let you know as soon as I can.
If you can set overscan and it stays set after leaving the calibration screen, then I'd say this fixed it. I couldn't get overscan calibration to stick with current build.
Okay, I believe it is fixed. With the #if changed, I could leave the calibration screen with the new settings in force, and they continue to work after a quit and restart.
It appears if you launch with current (non-modified) top of tree, you lose your current calibration settings.
- davilla - 2011-05-09 16:16
so with the change to the #ifdef: yes, no or maybe ?