[FFmpeg-devel] [PATCH] make fast option with h264 actually do something:
http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/2008-February/thread.html#42162

I think the reason why someone would be willing to use skiploopfilter and sacrifice picture quality is if they got say an older Mac mini connected to a 720p display but they download native 1080p videos that they like to play on that setup. The older Mac mini will not be able to playback that perfectly smooth without some serious compromise like the skiploopfilter.

Yes but by all means, please make it have an optional setting in the GUI.

Please don’t sacrifice picture quality to get better framerates in OSXBMC.

For those that have a very fast Mac, we just want the best picture quality no matter what

Of course there should a way for slower machines (Mac Mini’s ie.) to play HD content, but please consider making it an option/setting that can be turned on/off.

Thanks
/Martin

http://pastie.caboo.se/156513

Use this to look for the process number
$ ps axuw | grep XBMC

Attach to process (substitute the process number for xxxx, of course)
$ gdb /Applications/XBMC.app/Contents/MacOS/XBMC xxxx

Get a list of threads
(gdb) info threads

For each thread:
(gdb) thread x
(gdb) where

Send to Pastie and post a link. Thanks!

I’m having the same ‘force quit’ problem running on a MBP CoreDuo.

Don’t know my way around console or logs very well but point me in the right direction and I’ll post some for you if you’d like.

@elan

Very nice work. When the new MBP is purchased, this one will definitely be replaced by a Mini. Cheers.

By the way, how does XBMC handle downmixing to analog on the Xbox?

Sure it might be fun to test it, but now you have been warned

Uhh… this is odd enough. If I run XBMC from the command line as you suggest, it shuts down just fine. But if I run it by double-clicking the icon in Finder, the shutdown doesn’t complete.

The last two lines, when I run from the command-line, are:

CRITSEC[0x970c64]: Trying to enter destroyed section.
CritSect[0x970c64]: Some other thread trying to leave our critical section.

These never appear in the case of a GUI shutdown (I’m monitoring the messages in Console).

The first three lines appear in both cases:

WARNING: The XBMC_HOME environment variable is not set.
++ WARN: could not retrieve file info for `image.nrg’: No such file or directory
++ WARN: can’t open nrg image file image.nrg for reading

Browsing the Console logs further, these two messages concerning XBMC appeared at some point, too:

CPSGetCurrentProcess(): This call is deprecated and should not be called anymore.
CPSSetForegroundOperationState(): This call is deprecated and should not be called anymore.

Deprecation isn’t fatal, but I thought I should report them anyway.

I really don’t know what could be causing this. I erased the XBMC app support files before upgrading, so this can’t be due to some inter-version cruft, at least.

If you think this issue is worth investigating (or even possible to investigate, given its strange nature), just tell me and I’ll file a bug in Trac.