| Author | Thread |
User 10.08.2007 23:58:18 | Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. I had been trying to customize buttons for Mplayer and was having trouble. Then I realized that Mplayer was using the "Default" behavior for my remotes - both the Wiimote and the Apple remote - instead of the Mplayer behavior. I am launching Mplayer from within MythFrontend. Is there a way to get it to use the "Mplayer" behavior set? |
These entries from the FAQ may be relevant to this topic: Hardware - Apple® Remote
To enable you to use all capabilities of the IR Receiver of your Mac®, Remote Buddy is using its own driver. In contrast, all other applications with integrated Apple® Remote support usually use the OS X Apple® Remote subsystem.
As long as you're running Remote Buddy, Remote Buddy and its driver are responsible for turning the received button presses into actions. As soon as you quit Remote Buddy, this task is again handled by the OS X Apple® Remote subsystem.
If other applications don't use the interface to the OS X Apple® Remote subsystem correctly, this can lead to the effect that nothing happens when you press a button on your Apple® Remote. For as long as you're running Remote Buddy, issues like this are covered by Remote Buddy and it's driver and are therefore not visible to you. However, as soon as you quit Remote Buddy, the OS X Apple® Remote subsystem is back in control and any issues caused in it by other applications become visible.
Therefore Remote Buddy is neither the cause of the issue nor is it responsible for it. Instead, the cause of the issue exists independently of Remote Buddy. It's located elsewhere and can also only be solved there.
Although our products can't cause any such issues, we're regularly contacted about such issues and asked for help. In order to make locating and fixing the cause of such issues as easy and efficient as possible, we've developed a free diagnostics tool: Remote Control Diagnostics. It can locate issues with a single click and will provide you with information about the issue as well as with instructions on how you can fix it.
Please update your copy of Remote Buddy to version 1.15 or later.
|
User 11.08.2007 17:10:02 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Hi there, is this a version of Mplayer embedded into / bundled with MythFrontend? Or a regular version? If it is a regular version, you might be using
an outdated version. From the FAQ (on a related issue): -- cut --
MPlayer OS X 2 does not appear in Remote Buddy's menu. (FAQ015E0162) You are very likely using an outdated version of MPlayer for OS X.
Older versions of MPlayer identify themselves with a different Bundle
Identifier than Remote Buddy is using to detect an MPlayer install on
your system. Please install an uptodate version of MPlayer (to be
found on the MPlayer HQ site - the version you find on the dedicated
MPlayer OS X site is outdated) in order to receive support for it
through Remote Buddy.
-- cut -- Best regards,
Felix
|
User 13.08.2007 21:42:49 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Hi Felix, Mplayer is not bundled with MythFrontend. I downloaded and installed it separately. Yes, I saw that note in the FAQ; I believe I am using a recent version as Mplayer did appear for me as an application in remote buddy's configuration once I restarted RB. That is the configuration I was attempting to change when I noticed that RB seemed to be ignoring these settings and using Default instead. Do you have the Mplayer version number that will work with remote buddy? I'm not in front of my mac right now, but will check my version when I get home- Last edited: 13.08.2007 21:46:16
|
User 14.08.2007 16:00:01 | Re: Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Thanks for the info. With "Default", do you mean the "Default Behaviour" or the "Default
mapping"? Best regards,
Felix
|
User 14.08.2007 18:57:14 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. I think this post has the most up to date version. It was mainly a update to subtittleing for "Fan Sub" viewers. Remote Buddy has worked well for me with it. http://forums.animesuki.com/showpost.php?p=1093334&postcount=426 If you read back you will see they do not recommend the "mplayerosx" it is way out of date. I use a additional pramater with it maily for my subs: -ass -embeddedfonts -fontconfig
I also use -sid 0 to default to tittles on.
All this info is just a few posts up in the thread. PS:
I have only been using this for a week or two but it's been good. I think I might have a problem with the Mac Mini but it has been working well with only one or two crashes (the mini is acting flaky form day one). Used VLC before but had subtitling problems.
|
User 15.08.2007 05:33:20 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. No, I mean the Default Behaviour, i.e. the one you get in the finder where + and - are eject, etc.
|
User 15.08.2007 14:46:01 | Re: Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Thanks for the info. Then only two remaining, possible error sources that I can think of: 1) Have you unchecked the checkbox in front of Mplayer in Preferences Behaviours by any chance? (=> an unchecked checkbox here tells Remote Buddy: do not use this Behaviour)
2) Be sure to install the Universal version of Mplayer as found on the
mplayerhq website. AFAICR the PPC-only version had a different bundle
identifier. Unofficial releases and/or the Sourceforge releases are
likely to have a different bundle identifier and thus will not be
recognized. Best regards,
Felix
|
User 17.08.2007 07:23:24 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. I've verified that the Mplayer behavior is available: when I launch Mplayer from the Finder, Remote Buddy dutifully applies the configured behavior for Mplayer. It is only when Mplayer is launched from within MythFrontend that Remote Buddy gets confused and applies the Default Behavior instead. The keyboard commands for Mplayer work the same in either case.
|
User 17.08.2007 11:59:02 | Re: Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Thanks for the info. Remote Buddy makes no difference with detecting apps - no matter how
they are started. So I guess, you have two copies of MPlayer lying
around (maybe one in a backup). When you start Mplayer through MythFrontend, right click on Mplayer's
icon in the dock, then select "Show in Finder" to see where that
application is located - whether it's the same version, a copy or
whether it's just a part of Mplayer that gets started can then be
easily determined. Best regards,
Felix
|
User 26.08.2007 04:45:42 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Hello Steven and Felix, I'm having *exactly* the same issue and I think it's because there is a distinction between "MPlayer" and "MPlayer OSX". The first is a command-line application. The second is a GUI app that wraps up the command line app. So when you run it from the dock you're running the GUI app, and Remote Buddy works fine. When we run it from within MythTv we're using the command line application and Remote Buddy doesn't know to do anything. I can see two ways to work around the issue: 1) We may be able to use the GUI app from the command line.
2) We may be able to configure Remote Buddy to know what to do with 'regular' MPlayer. I'll look into it a little more and keep you posted...
|
User 28.08.2007 11:16:01 | Re: Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Hello Matt, thanks for the info. I was aware that Mplayer OSX does launch a
seperate tool, but not that MythTV directly launches these playback
tools by itself. That, of course, would explain it. I've just had a look at the subapp bundles and their structure is
quite f***ed up (sorry) - especially with regards to their missing
bundle identifier. Another problem is that I have no idea on whether
these seperate tools will react to key presses at all or under which
circumstances which one is invoked (there seem to be at least 4
different versions). Best regards,
Felix
|
User 08.01.2008 16:06:35 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Hi Felix, I have the same issue as well.
It seems that when the player window it self (the one with the buttons :)) is selected the correct behavior is selected. but when the movie window is selected it goes to the default behavior (itunes in my case). Hope this helps :) Cheers,
Joris
|
User 08.01.2008 16:08:42 | Re: Mplayer: uses default behavior instead | |
This posting is older than 6 months and can contain outdated information. Hi Again, it seems that the window is called "MPlayer Window" as where the player itself is called "MPlayer OSX" This is because the video out module used. There are 3 of them;
- Quarts/Quicktime
- Core (BETA)
- MPlayer OSX The default is MPlayer OSX but this one seems to fail on leopard, so I have to use the Core plugin. If i'm not mistaking this starts a seccond, command line version, of mplayer. Obvioulsy this is not called mplayer osx but mplayer. Cheers,
Joris Last edited: 08.01.2008 16:56:02
|
