Support > Remote Buddy Forum > Can Behaviours (e.g. System volume slider) trigger Applescripts? // IOSPIRIT [EN]

Support

All support resources for our products. Here you can find answers to frequently asked questions, discuss with other users, recover a lost license code or file a support request.

Forum closed

This forum was closed and turned into an archive effective April 21, 2018. It is no longer possible to create new topics or reply to existing topics.

Thanks everyone for all the great questions and contributions over the years.

Please use the Contact form to get in touch.

Remote Buddy Forum

Overview

Author

Thread

User

17.12.2007 17:27:31

Can Behaviours (e.g. System volume slider) trigger Applescripts?

View

This posting is older than 6 months and can contain outdated information.

The reason I ask this is because I have IRTrans+iRed setup. First I created some IR actions in iRed for my receiver. Second I created the needed actions in RB. For the implementation I used applescripts. An example: tell application "iRed" to send ir Code "Volume Up" of RC "Pioneer"
I bundled the actions into an behaviour and added it to the RB menu. No real problem so far. But I would like the custom "Volume Up" and "Volume Down" actions to be displayed like the "System volume slider". Note that since I use digital audio out that slider has no effect.

Any thoughts? or solution(s)?

These entries from the FAQ may be relevant to this topic:

Behaviours

How can I create my own Behaviours? (FAQ015E0240)
You can create your own Behaviours with the Behaviour Construction Kit. A video on the Remote Buddy website provides you with an overview and step by step instructions.

You can also find step by step instructions in the Remote Buddy Help under "How Tos". You can access the Help via Remote Buddy's icon in the menu bar and via the support area of this website.
The installed application XY, for which a behaviour exists, does not turn up in Remote Buddy's menu. What should I do? (FAQ015E0160)
There are several possible error sources:
- The application has been installed after Remote Buddy has already been launched
  For efficiency reasons, Remote Buddy only searches for supported applications when its started. If you have installed an application after launching Remote Buddy, please quit Remote Buddy and launch it anew.
- Oudated program versions
  The installed version of the program in question could be outdated and identify itself with a different Bundle Identifier than the version supported by Remote Buddy. This problem often occurs with Mplayer OS X. The most recent version of that application is not to be found on Sourceforge but on directly on the pages of Mplayer HQ.
- Custom menus
  If you use a custom menu in Remote Buddy and you don't make use of Remote Buddy's smart folders, the menu structure is static. You have to manually add the behaviour into a place of your choice in the menu.
- The behaviour is deactivated.
  Make sure, the checkbox in front of the Behaviour's name in the Mappings pane of the preferences is active.
- The Launch Services database is outdated.
  Remote Buddy uses Launch Services to check for the availability of an application on your Mac. If the Launch Services database of OS X is incomplete or outdated, so is Remote Buddy's dynamically created menu. The solution, though is easy. Download LSRefresh, launch it, select the application(s) that don't turn up in Remote Buddy's menu, wait until the update is finished and then restart Remote Buddy.

Configuration

How do I add a new action to a Behaviour - f.ex. an emulated key press or AppleScript? (FAQ015E0153)
1) Open the Remote Buddy Preferences via the pulldown-menu and choose "Mapping".
2) Choose the mapping you want to modify.
3) Select "Custom actions" for the button you want to map to an action of your own.
4) Create the action you need using the appearing editor.

Hardware - Apple® Remote

After uninstalling/quitting Remote Buddy, my Mac® no longer reacts to the Apple® Remote. (FAQ015E0241)
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.

User

18.12.2007 23:18:01

Re: Can Behaviours (e.g. System volume slider) trigger Applescripts?

View

This posting is older than 6 months and can contain outdated information.

Thanks for asking.

While Behaviours can run AppleScripts very well (and the system volume
+/- actually does exactly this), you can't override parts of existing
actions with your own code. So while you can create and map your own
system volume up/down action anywhere you want, you currently can't
display a volume slider / bar for it.

Given your description that would also be quite hard as the volume
level at application start would be unknown and thus a volume bar
wouldn't appear to be accurate or useful.

Best regards,
Felix

User

19.12.2007 00:37:09

Re: Can Behaviours (e.g. System volume slider) trigger Applescripts?

View

This posting is older than 6 months and can contain outdated information.

Felix,

Well to be able to have control over the volume slider / bar would be a step in the right direction for me.

And yes I know the volume bar would not be very accurate. My theory is to calibrate it once and a while (start both the slider and the receiver volume at zero). So I have to disagree with it not being useful, but I agree it won't be very accurate.

Maybe an idea would be to provide a sort of slider widget with decrease value and increase value actions.

User

07.01.2008 18:05:01

Re: Re: Can Behaviours (e.g. System volume slider) trigger Applescripts?

View

This posting is older than 6 months and can contain outdated information.

What you could do AppleScript-wise is this:

- use the osdmessage command to display the volume level in numbers at
a big font size

- use the storage command(s) to store and retrieve the volume level
either dynamically or permanently

Best regards,
Felix

Am 19.12.2007 um 00:37 schrieb Daniel Knippers:

Felix,

Well to be able to have control over the volume slider / bar would
be a step in the right direction for me.

And yes I know the volume bar would not be very accurate. My theory
is to calibrate it once and a while (start both the slider and the
receiver volume at zero). So I have to disagree with it not being
useful, but I agree it won't be very accurate.

Maybe an idea would be to provide a sort of slider widget with
decrease value and increase value actions.

[standard mail footer removed]

Remote Buddy
Support
1. Overview
2. Manuals
3. FAQs
4. Forums
1. Lost license code
2. Support inquiry
IOSPIRIT
1. About us
2. Blog
3. Labs
4. Developers
1. Contact
2. Press releases
3. Imprint
4. Jobs