IR Blaster plug in config problem

[netchord]

So, I want to setup the IR Blaster plugin so I can control volume (and perhaps power) via the squeezepad and ipeng apps.

Here's my Setup:
LMS Version: 7.7.1 - r33735
Mac Mini, OS 10.7.2
Logitech Transporter
Meridian G61 controller

The G61 has an IR input jack on the back, and I'd like to connect an IR blaster cable from the TP to the G61. I've installed the IRBlaster plugin, and downloaded the Meridian conf file. Here's where my problem begins:

the instructions say to place the conf file in the following directory:

/Users/netchord/Library/Caches/Squeezebox/InstalledPlugins/Plugins/IRBlaster

however, said directory does not exist on my system. in fact, there is no "Library" folder in the "netchord" directory under Users. I have tried to create one, but receive an error message that the name is already in use! there is a Library/Cache folder path at the root of the hard drive, and also in System/Library/Cache. Neither path has a Squeezebox folder. nor is there one in ApplicationSupport under either path.

if i follow /Library/PreferencePanes/Squeezebox.prefPane/(show)Contents/server/slim/Plugins i find all the other plugins that are directly installed by LMS, but no folder labled IRBlaster.

so...how do i stall the Meridian conf file, or, since Meridian uses standard RC5 controls, and i only care about volume (and maybe power) perhaps i don't need to, and can use the default settings?

[epoch1970]

Been a long time since I've used SBS/LMS on Mac OS, however I suppose it is still true that, according to your choice to run the server only when some user is logged-in vs. at machine start, the whole Squeezebox file hierarchy will move either under /Users/xxx/Library (user) or under /Library (system)
This may explain discrepancies between what you see and read.

There is also a difference in folder location, according to the plugin installation mode. Manual installs should go to (something like) .../squeezeboxserver/Plugins/ and automatic installs go to .../squeezeboxserver/cache/InstalledPlugins/Plugins
I'd recommend using automatic install. Then you need to copy your files to the right location.
To locate the "IRBlaster" directory perhaps you could look for a file named "slim.conf" (it contains the IR codes of the slim remote.) Or to this string
"<module>Plugins::IRBlaster::Plugin</module>" (from IRBlaster's install.xml file).

[netchord]

Been a long time since I've used SBS/LMS on Mac OS, however I suppose it is still true that, according to your choice to run the server only when some user is logged-in vs. at machine start, the whole Squeezebox file hierarchy will move either under /Users/xxx/Library (user) or under /Library (system)
This may explain discrepancies between what you see and read.

There is also a difference in folder location, according to the plugin installation mode. Manual installs should go to (something like) .../squeezeboxserver/Plugins/ and automatic installs go to .../squeezeboxserver/cache/InstalledPlugins/Plugins
I'd recommend using automatic install. Then you need to copy your files to the right location.
To locate the "IRBlaster" directory perhaps you could look for a file named "slim.conf" (it contains the IR codes of the slim remote.) Or to this string
"<module>Plugins::IRBlaster::Plugin</module>" (from IRBlaster's install.xml file).

thanks, yes, i did automatic install, and the plugin shows up in the player menu, ready to be configured. what i can't find is the directory to drop the .conf file into.

[epoch1970]

In the server web interface, in the "Settings" window, look for the "Information" tab. At the bottom of the page you'll see the directories used for plugins.
There must be an IRBlaster folder in there.

(BTW if you're using the latest-and-greatest OS X Lion, the Library directory in users home is now hidden in the Finder. You can have the Library dir show permanently as before, with this command in Terminal: "chflags nohidden ~/Library". The whole story in this CNET blog page)

[netchord]

In the server web interface, in the "Settings" window, look for the "Information" tab. At the bottom of the page you'll see the directories used for plugins.
There must be an IRBlaster folder in there.

(BTW if you're using the latest-and-greatest OS X Lion, the Library directory in users home is now hidden in the Finder. You can have the Library dir show permanently as before, with this command in Terminal: "chflags nohidden ~/Library". The whole story in this CNET blog page)

thanks, that worked for finding the IRBlaster folder (which oddly didn't come up in a search.) i dropped the meridian.conf file in that directory, restarted the server, reloaded the directory in the IRBlaster configuration tab of the LMS web interface, and....Meridian is not listed as an option. "slim" is still there, but no merdian option. do i need to delete the slim conf file?

[epoch1970]

I think I have noticed sometimes IRBlaster likes to have a refresh when the config files have been changed. In the preferences for a player, in the IR-Blaster page, you should see a field named "Configfile Path:" along with a "reload" button.
Make sure the path is indeed the right one and hit reload. Then see if you get a "Device" named "meridian" to play with.

It could also be a matter of unix rights on the file. I've had IRBlaster disregard my files until the rights were ok.
If you "get info" (cmd-I) on slim.conf and on your file, and compare the Sharing and Permissions settings at the bottom of each window, are they any different ?

Don't remove slim.conf. Try to make meridian.conf belong to the same owner, with same rights, as slim.conf.

[netchord]

I think I have noticed sometimes IRBlaster likes to have a refresh when the config files have been changed. In the preferences for a player, in the IR-Blaster page, you should see a field named "Configfile Path:" along with a "reload" button.
Make sure the path is indeed the right one and hit reload. Then see if you get a "Device" named "meridian" to play with.

It could also be a matter of unix rights on the file. I've had IRBlaster disregard my files until the rights were ok.
If you "get info" (cmd-I) on slim.conf and on your file, and compare the Sharing and Permissions settings at the bottom of each window, are they any different ?

Don't remove slim.conf. Try to make meridian.conf belong to the same owner, with same rights, as slim.conf.

thanks- checked permissions, hit reload, etc, but still no option other than "slim" is present. uninstalled, reinstalled, re-added the meridian conf file- still nothing.

[epoch1970]

thanks- checked permissions, hit reload, etc, but still no option other than "slim" is present. uninstalled, reinstalled, re-added the meridian conf file- still nothing.

Maybe the file itself has a problem. Can you post it ? I'll see if it loads on my SBS 7.6.2/linux.

[netchord]

Maybe the file itself has a problem. Can you post it ? I'll see if it loads on my SBS 7.6.2/linux.

sure, thanks for taking a look- see attached. on install, i changed the ext to .conf

[epoch1970]

And it worked. I copied the file across to the server, moved it to my IRBlaster dir, changed as root and relocated to that directory, fixed ownership on the file to look the same as the others (in my case, squeezeboxserver;nogroup). Then I went to a player prefs>IR-Blaster, hit Reload and there was the MSR device in full glory.

I believe there are 2 possibilities at this point: either you're not adding to the right directory, or the file is not readable (owner/rights issue) by the server.

Do you savvy the Terminal app on the Mac ? This is what I'd do:
1. Go the the dir: "cd /full-path-to-IRBlaster-dir<return>"
(don't type the quotes. Hit return after each commands below to launch execution)
2. Have a look at the damage: "ls -la"
(a list of files in the dir, owner, rights… is displayed)
3. Change what's needed.
3.1 Ownership: "sudo chown newowner:group-of-newowner MSR.conf"
(sudo asks for your mac login password first. Then when you're authenticated the command is executed with elevated privileges. The idea here is to assign ownership of the file to the user:group that owns the standard slim.conf file.
Once executed, do another "ls -la" and the landscape should look different)
3.2 Relax access rights: "sudo chmod a+rwx MSR.conf"
(makes the file readable, writable and executable for anybody. Not secure but practical.
Once executed, do another "ls -la" and landscape should look different)
4. You're done, time to quit: "exit"
(and you can close the window and quit Terminal.app. Keeping the window open won't harm and allows to look at the trace. You can use copy-paste if you want to post what you see.)

With a reload on the server, a restart if reload fails, you should see the MSR device. If not, I guess this is not the right directory.