[AppleTV] Launcher 3.0 Testing (ATV)

[MaestroDD]

Launcher moves to a new major version (3.0 aka Unified Launcher), but needs some testing.

What's new?
- no more Multifinder/pure-Launcher differences
new Launcher handles both MultiFinder and the pure approach. MultiFinder can be enabled/disabled directly in Launcher if XBMCExpertMode is activated (defaults write com.teamxbmc.xbmclauncher XBMCExpertMode 1)

-default is the version without MultiFinder (MultiFinder gets disabled on update)

-fixed universal-mode (thread (http://xbmc.org/forum/showthread.php?t=39209) with infos about that)
-MultiFinder.app is removed from /Applications and instead started from Launcher's bundle

Known issues?
Differences (http://code.google.com/p/atv-xbmc-launcher/issues/detail?id=19) of the 2 ways to launch are still the same.

Howto test?
you need to modify the url of the repository Launcher gets its updates from. It's stored in
/System/Library/CoreServices/Finder.app/Contents/PlugIns/XBMCLauncher.frappliance/Contents/Info.plist
as:
<string>http://atv-xbmc-launcher.googlecode.com/svn/tags/mf-info/update_urls.plist</string>
or
<string>http://atv-xbmc-launcher.googlecode.com/svn/tags/xbmc-info/update_urls.plist</string>
depending on the Launcher version you're running and needs to be modified to:
<string>http://atv-xbmc-launcher.googlecode.com/svn/tags/ul-info/update_urls.plist</string>

ofc manual installation is possible, just grab the urls from the new update_urls.plist.

Please post bugs here or to the issues list on googlecode (http://code.google.com/p/atv-xbmc-launcher/issues/)

Thanks,
MDD

[Livin]

The title is confusing since there are other plug-ins call "Launcher" You might want to append "Apple" to the name to reduce confusion.

[davilla]

The title is confusing since there are other plug-ins call "Launcher" You might want to append "Apple" to the name to reduce confusion.

Name them please so we can evaluate your request.

Since Launcher has nothing to do with launching Apple items, appending "Apple" to the name seems like it would be even more confusing.

[Livin]

Does your launcher work with an OS other than Apple?

here's the Launcher that started a long time ago (even before this the linked started) for XBOX, WIN, Linux...

http://xbmc.org/forum/showthread.php?t=35739

[davilla]

Does your launcher work with an OS other than Apple?

here's the Launcher that started a long time ago (even before this the linked started) for XBOX, WIN, Linux...

http://xbmc.org/forum/showthread.php?t=35739

Launcher is an AppleTV frontrow plugin. It's used to "launch" xbmc or boxee apps for running them under the AppleTV. It's name only appears in the AppleTV frontrow menu listing. It only runs under the AppleTV frontrow interface and has nothing to do with any other OS besides the AppleTV.

[Livin]

Since your's is specific to ATV, I'd put on ATV on the front... up to you. The only reason I bring it up is I did a search for the other Launcher and found yours thinking it was the same.

[davilla]

Since your's is specific to ATV, I'd put on ATV on the front... up to you. The only reason I bring it up is I did a search for the other Launcher and found yours thinking it was the same.

I think we will pass, "ATV Launcher" in the frontrow menu is confusing. We are not launching ATV and since this is only the AppleTV, ATV is redundant.

This is nothing new, Launcher has been around for over six months. It was previously named XBMCLauncher and showed XBMC/Boxee in the right side frontrow menu. This also was confusing to xbmc/boxee users. So we just call it Launcher now.

Yes, searches via the forums can be confusing at times :) I tend to focus the searching to a specific forum less I get info that only applies to the other platforms.

[gilbreen]

I have updated one of our AppleTV units to Launcher 3.0 and so far no issues have resulted. I had been using Launcher 0.9 previously. I am using it in the default mode.

ATV OS 2.3.1
XBMC Current release (bf1)

Thanks for the update!

[MaestroDD]

I have updated one of our AppleTV units to Launcher 3.0 and so far no issues have resulted. I had been using Launcher 0.9 previously. I am using it in the default mode.

ATV OS 2.3.1
XBMC Current release (bf1)

Thanks for the update!

Thanks for the report!

[osxrulz]

I'll give it a go this weekend.

[gilbreen]

I have installed it on a second ATV and continue to use it without any issues. Also using it in default mode.

Launcher 3 Beta 3
ATV OS 2.3.1
XBMC Current release (bf1)

Thanks!

[bu1ak3]

Everything looks good so far. I will set my ATV to boot XBMC by default and see how that works out.

Launcher 3 Beta 3
ATV OS 2.3.1
XBMC Current release (bf1)

[GrimSage]

How do you get ATV to boot straight into XBMC?

[S80_UK]

How do you get ATV to boot straight into XBMC?
Simple - use the search facility or read through the recent posts... and find this...
http://xbmc.org/forum/showpost.php?p=271761&postcount=1
(hijacking threads such as this helps no-one).

Back on topic...

Have just installed Launcher 3 Beta 3

ATV OS 2.3
XBMC 8.10 (bf1)

No issues so far. (and using HDMI - will check beta 4 and report back)

[MaestroDD]

Launcher was updated to beta4. You should see in in Launcher->Downloads.
Changes:
-few ui fixes
-possibility to have more than one update source (will ease use of xbmc svn revisions)
-Updated boxee's Downloads entry

We're still not sure if we fixed the HDMI disconnect issues, so if someone with HDMI is using it, it would be great to hear reports about that / see logs when it failed. Problem is that e.g. after switching to a different source on your AV-Receiver and later back to XBMC on the ATV, the display is blank.

cheers,
MDD

[KeRbDoG]

ATV OS 2.3
XBMC 8.10 (bf1)
Using HDMI

Working fine

[brentonmac]

ATV OS 2.3
XBMC SVN rev18298

Using HDMI - doesn't work for me :(

I switched back to the ATV I saw XBMC then it scrambled and went black. Do I just switch on debug mode to get logging for this?

Log file can be found here - http://pastebin.com/m66a66feb

[MaestroDD]

ATV OS 2.3
XBMC SVN rev18298

Using HDMI - doesn't work for me :(

I switched back to the ATV I saw XBMC then it scrambled and went black. Do I just switch on debug mode to get logging for this?

Log file can be found here - http://pastebin.com/m66a66feb

Console.log would be interesting, too.
I wasn't yet able reproduce it. I tried disconnecting the HDMI, switching source on projector :/
Will try again later...

[bu1ak3]

Everything looks good so far. I will set my ATV to boot XBMC by default and see how that works out.

Launcher 3 Beta 3
ATV OS 2.3.1
XBMC Current release (bf1)

Still looking good for me. Now running:

Launcher 3 Beta 4
ATV OS 2.3.1
XBMC Current release (bf1)
HDMI

Great job!

[MaestroDD]

ATV OS 2.3
XBMC SVN rev18298

Using HDMI - doesn't work for me :(

I switched back to the ATV I saw XBMC then it scrambled and went black. Do I just switch on debug mode to get logging for this?

Log file can be found here - http://pastebin.com/m66a66feb

We got a few steps further.
We missed to update a script that installs XBMC on the ATV. There should be a file advancedsettings.xml in ~/Library/Application\ Support/XBMC/userdata, that (now) gets created on update/install of XBMC through Launcher. It should look like this (+any additional stuff from yourself):

<advancedsettings>
<skiploopfilter>48</skiploopfilter>
<osx_gl_fullscreen>true</osx_gl_fullscreen>
</advancedsettings>

Not setting osx_gl_fullscreen to true creates the problems with HDMI.

This can be fixed by (re)downloading xbmc-atlantis-bf1 from Launcher->Downloads again, or by manually editing it.

HTH,
stephan

[S80_UK]

Updated Launcher 3.0 beta 3 to beta 4, no problems.
XBMC 8.10 (bf1) on ATV 2.3 with HDMI to Panasonic TH37PX60 working fine.

[FreddieD]

I have no idea if this is a bug, or something with no intention of being featured in Launcher 3.0. In my quest to have both the regular and playback buttons working on my universal remote, it was revealed (http://xbmc.org/forum/showpost.php?p=301694&postcount=74) that the Launcher 3.0 beta is capable of relaying learned remote signals (the new feature in Apple TV v2.3) for XBMC. Because the learned remote signals also record the playback buttons (play, stop, pause, etc) it was my hope that those signals would also be relayed to XBMC. I had it working with Launcher 2.3 using Universal Mode (http://code.google.com/p/atv-xbmc-launcher/wiki/UniversalMode), but was working towards something that didn't require the menu_hold workaround.

When testing this (I had AppleTV learn an old Philips DVD remote), I found that the normal Apple remote buttons (direction arrows, select, menu) worked flawlessly, but playback buttons such as play, pause, stop, and rewind did not. One thing I did find, however, was that the fast forward button caused the video to skip ahead 10 minutes.

There was no output at all from console.log, and while there was xbmc.log output (http://pastebin.com/m54e6d825), there appeared to be nothing that would indicate that XBMC had any idea that these playback buttons were being pressed. While I didn't find any log files under /Users/frontrow/Library/Logs or /Library/Logs/Console, is there somewhere that I can find log output specifically for Launcher (perhaps in the portion that relays button presses over to XBMC)?

Of course, if there is no intention of supporting the playback buttons through AppleTV's learned remote feature then the above is mostly moot, and my next question would be is this something that is on the potential roadmap for a future release? Thanks and keep up the great work! My environment specs are below:

AppleTV v2.3.1
Launcher v3.0b4
XBMC Atlantis bf1

[MaestroDD]

I have no idea if this is a bug, or something with no intention of being featured in Launcher 3.0. In my quest to have both the regular and playback buttons working on my universal remote, it was revealed (http://xbmc.org/forum/showpost.php?p=301694&postcount=74) that the Launcher 3.0 beta is capable of relaying learned remote signals (the new feature in Apple TV v2.3) for XBMC. Because the learned remote signals also record the playback buttons (play, stop, pause, etc) it was my hope that those signals would also be relayed to XBMC. I had it working with Launcher 2.3 using Universal Mode (http://code.google.com/p/atv-xbmc-launcher/wiki/UniversalMode), but was working towards something that didn't require the menu_hold workaround.

Must admit I wasn't aware of that. Thanks for pointing it out!


When testing this (I had AppleTV learn an old Philips DVD remote), I found that the normal Apple remote buttons (direction arrows, select, menu) worked flawlessly, but playback buttons such as play, pause, stop, and rewind did not. One thing I did find, however, was that the fast forward button caused the video to skip ahead 10 minutes.


hehe, Apple reused old keycodes present on ATV <= 2.1 (right and left hold). That's why some buttons were working. The new ones are not recognized by Launcher 3beta4...


There was no output at all from console.log, and while there was xbmc.log output (http://pastebin.com/m54e6d825), there appeared to be nothing that would indicate that XBMC had any idea that these playback buttons were being pressed. While I didn't find any log files under /Users/frontrow/Library/Logs or /Library/Logs/Console, is there somewhere that I can find log output specifically for Launcher (perhaps in the portion that relays button presses over to XBMC)?

This
tail -F /Library/Logs/Console/501/console.log
should do it. If log doesn't refresh, just restart Finder and it should work again.


Of course, if there is no intention of supporting the playback buttons through AppleTV's learned remote feature then the above is mostly moot, and my next question would be is this something that is on the potential roadmap for a future release?


Beta5 is uploaded with the fix. Thanks for the excellent report!

To use the learned buttons, you'll need to modify Keymap.xml. This is what I came up with:

<keymap>
<global>
<joystick name="AppleRemote">
<!-- plus --> <button id="1">Up</button>
<!-- minus --> <button id="2">Down</button>
<!-- left --> <button id="3">Left</button>
<!-- right --> <button id="4">Right</button>
<!-- play/pause --> <button id="5">Select</button>
<!-- menu --> <button id="6">PreviousMenu</button>

<!-- hold play --> <button id="7">Fullscreen</button>
<!-- hold menu --> <button id="8">ContextMenu</button>

<!-- old buttons (ATV <2.2) -->
<!-- hold left --> <button id="9">BigStepBack</button>
<!-- hold right --> <button id="10">BigStepForward</button>

<!-- Learned remote buttons (ATV >2.3) -->
<!-- Play --> <button id="70">Play</button>
<!-- Pause --> <button id="71">Pause</button>
<!-- Stop --> <button id="72">Stop</button>
<!-- Previous --> <button id="73">SkipPrevious</button>
<!-- Next --> <button id="74">SkipNext</button>
<!-- Rewind --> <button id="75">StepBack</button>
<!-- Forward --> <button id="76">StepForward</button>
<!-- Return --> <button id="77">ParentDir</button>
<!-- Enter --> <button id="78"></button>
</joystick>
</global>
</keymap>

We'll update Keymap.xml for the next release. Suggestions?

cheers,
dd

[sircube]

Just waited for this info! :grin::grin::grin::grin::grin::grin::
Will give it a go in the evening.

[brentonmac]

We got a few steps further.
We missed to update a script that installs XBMC on the ATV. There should be a file advancedsettings.xml in ~/Library/Application\ Support/XBMC/userdata, that (now) gets created on update/install of XBMC through Launcher. It should look like this (+any additional stuff from yourself):

<advancedsettings>
<skiploopfilter>48</skiploopfilter>
<osx_gl_fullscreen>true</osx_gl_fullscreen>
</advancedsettings>

Not setting osx_gl_fullscreen to true creates the problems with HDMI.

This can be fixed by (re)downloading xbmc-atlantis-bf1 from Launcher->Downloads again, or by manually editing it.

HTH,
stephan

Thanks this worked great!

[gilbreen]

Any chance that the Download section for Launcher Beta 5 will list the newest Boxee beta (9.10.5534)?

[MaestroDD]

Any chance that the Download section for Launcher Beta 5 will list the newest Boxee beta (9.10.5534)?

ouch, forum must be laggy. It's there since 16 hours, updated with beta5:
http://code.google.com/p/atv-xbmc-launcher/source/detail?r=617

[gilbreen]

ouch, forum must be laggy. It's there since 16 hours, updated with beta5:
http://code.google.com/p/atv-xbmc-launcher/source/detail?r=617

Excellent - I did update to Beta 5 but the old Boxee entry was still there. Does one have to (or rather should one) reboot the ATV after updating the Launcher?

Thanks again.

[gilbreen]

Hmm - I am stumped. I have rebooted the ATV and re-installed Beta 5 but it still shows the 9.9 version of Boxee in the Downloads section.

Any other suggestions to try or are others seeing something different?

[MaestroDD]

Hmm - I am stumped. I have rebooted the ATV and re-installed Beta 5 but it still shows the 9.9 version of Boxee in the Downloads section.


indeed. damn copy'n'paste :)
It was the new version, but displayed name was old. Should be fixed.
Thanks!

[MaestroDD]

Does one have to (or rather should one) reboot the ATV after updating the Launcher?


no, update restarts Finder.
Downloads get only updated when entering the menu. To have those updated, just go to a different submenu and then back.

[gilbreen]

indeed. damn copy'n'paste :)
It was the new version, but displayed name was old. Should be fixed.
Thanks!

Thanks again for the quick response. Working as advertised and have now updated to the new Boxee (v. 9.10)

[sircube]

Beta5 is uploaded with the fix. Thanks for the excellent report!

To use the learned buttons, you'll need to modify Keymap.xml. This is what I came up with:

<keymap>
<global>
<joystick name="AppleRemote">
<!-- plus --> <button id="1">Up</button>
<!-- minus --> <button id="2">Down</button>
<!-- left --> <button id="3">Left</button>
<!-- right --> <button id="4">Right</button>
<!-- play/pause --> <button id="5">Select</button>
<!-- menu --> <button id="6">PreviousMenu</button>

<!-- hold play --> <button id="7">Fullscreen</button>
<!-- hold menu --> <button id="8">ContextMenu</button>

<!-- old buttons (ATV <2.2) -->
<!-- hold left --> <button id="9">BigStepBack</button>
<!-- hold right --> <button id="10">BigStepForward</button>

<!-- Learned remote buttons (ATV >2.3) -->
<!-- Play --> <button id="70">Play</button>
<!-- Pause --> <button id="71">Pause</button>
<!-- Stop --> <button id="72">Stop</button>
<!-- Previous --> <button id="73">SkipPrevious</button>
<!-- Next --> <button id="74">SkipNext</button>
<!-- Rewind --> <button id="75">StepBack</button>
<!-- Forward --> <button id="76">StepForward</button>
<!-- Return --> <button id="77">ParentDir</button>
<!-- Enter --> <button id="78"></button>
</joystick>
</global>
</keymap>

We'll update Keymap.xml for the next release. Suggestions?
[/QUOTE]

OSX Version 10.4
Platform AppleTV v2.3
Launcher version of AppleTV.: 3 Beta5
Install Method: Launcher, thne downloaded custom Launcher (Beta5)
SVN Revision (bf1)
Other: Custom Keymap.xml from above.

Detailed Instructions to Reproduce the Problem:

Initial State: APPLE TV is switched off. Frontrow appears. In Launcher menu: Universal Mode ON, AutoUpdate OFF. Multifinder OFF (No change in problem result whether Multifinder is used or not.)

Goal: control XBMC with custom remote using leared IR codes from Frontrow. (I guess this is possible now)???

Steps:
1. Power up AppleTV.
2. Learn keys for arrows and play buttons. Works fine in Frontrow menus
3. Launch XBMC from frontrow using custom remote.
4. Front LED in ATV does not flash upon button press
5. No movement on the menu sreen of XBMC
6. launching film from VIDEOS (original remote), no effect of PLAY/STOP when using custom remote.

Any idea?
Is something I miss completely here ?? If not, which log do you need for tracing?

br,
Sircube

[MaestroDD]

Multifinder OFF (No change in problem result whether Multifinder is used or not.)

learned remotes won't work with MultiFinder.


4. Front LED in ATV does not flash upon button press

hm, I'm not sure about that. Will try later...

Any idea?
Is something I miss completely here ?? If not, which log do you need for tracing?


xbmc.log: Probably your modified Keymap.xml doesn't get picked up, xbmc.log reveals that
console.log: maybe buttons are not recognized, console.log reveals that.

[davilla]

Front LED in ATV does not flash upon button press

Pairing maybe. The LED flash (white or amber) is at the internal IR controller level. If that does not flash (white or amber), the atv does not recognize the IR remote and is ignoring it.

[sircube]

steps continued from reported state:

X+1 ... I switched the ATV OFF/ON. At this stage Launcher was configured to Multiboot into XBMC.
+2 Exited XBMC
+3 Switched Multiboot off. Launched XBMC again.
+4 SUCCESS!!! Custom remote controls XBMC. LED flashes.

Bit strange. Might be that others will not have the struggle. Or it might be that I've switched on Multiboot to ON before first test. I remembered not.. but this can be the only logical reason although....

Now will play with the keymap.xml a bit.

All-in-all I can confirm that all keypress events go through and understood by XBMC.--- Awesome work! Thanks for the feature! :grin:

[sircube]

OSX Version 10.4
Platform AppleTV v2.3
Launcher version of AppleTV.: 3 Beta5
Install Method: Launcher, thne downloaded custom Launcher (Beta5)
SVN Revision (bf1)
Other: Custom Keymap.xml from above.
Multifinder switched off

Problem: watching video from smb share. Pause presssed. After 4-5 min... XBMC exited and APPLE TV completely rebooted and entered Frontrow. (last video from log). XBMC was not in debug log mode. But what I've captured is here. http://pastebin.com/m10b5df29
Any guesses?

Have not experienced it with Launcher 0.9 but did with Launcher 2.3.
Strange ...my console log (/mnt/Scratch/Library/Logs/Console/501/console.log) has no entry from today.

I will try to reproduce it with debug. I'm only posting to let you you and maybe others have also similar results.

Also---: watching movie from sbm share. XBMC exits to it's main menu suddenly. Around 10-15 minutes of the movie. HAppened already twice since I have Launcher 3.0. And it happened with 2.3 as well. That was the reason for moving me back to Launcher 0.9 a month ago.

[Tsf42m]

Hopefully I will have some time tonight to play with Lancher 3b5
I have released a few SVN builds and would like to get things setup to work with the new multi source feature. Would you mind giving me the quick and dirty setup for getting this tested.

Thanks a lot for all your work

[MaestroDD]

Hi Tsf42m,

Hopefully I will have some time tonight to play with Lancher 3b5
I have released a few SVN builds and would like to get things setup to work with the new multi source feature. Would you mind giving me the quick and dirty setup for getting this tested.

Thanks a lot for all your work

Yeah, I pm'ed you about that last week.
Just updated Launcher's wiki http://code.google.com/p/atv-xbmc-launcher/wiki/XBMCUpdater to include info about it.
Best is probably to go through one or two of the update scripts (http://code.google.com/p/atv-xbmc-launcher/source/browse/#svn/tags/xbmc-info/scripts) to see how they do it (e.g. xbmc-8.10.bf1_update.sh).
Feel free to ask about details I forgot to mention, best in a new thread.

cheers,
stephan

[criti]

is 3.0 going to fix the HDMI black screen issue? I'm still having the problem with it on the beta and don't see it as an issue on the project page.

[aedile]

Latest Beta is giving me no problems. If anything, XBMC seems to be perfoming a bit more snappily than before. Also love the new remote functionality. I just did a little HOWTO on it. Perhaps we'll get a few more willing beta testers once they realize that it has increased remote functionality (that does seem to be the number one complaint about ATV). In the keymap.xml file listed above, you are using button names that seem different from what the ATV calls them. You might want to consider changing them to exactly what ATV does. Also, do you have access to all of the universal remote buttons, or does up, down, etc on the universal remote correspond to up, down, etc on the apple remote? Hate to be greedy, but I want all the functionality I can get.

Great job guys, keep up the good work!

-aedile-

[davilla]

is 3.0 going to fix the HDMI black screen issue? I'm still having the problem with it on the beta and don't see it as an issue on the project page.

which version of the beta ?

[criti]

which version of the beta ?

AppleTV: 2.3.1
XBMC: rev19065
Launcher 3.0b5

i'm guessing you guys know more about it, but its weird for me. i've seen a few different things after i switch back and only see black. sometimes after just letting it sit for 10 min, i go back and its back to front row and sometimes i can do the remote shortcut to unpair and pair the remote and it actually shows up on the black screen.

every time i've seen, when i switch the input back to the appletv it switches to 1080i first no matter what resolution the previous input was on, gives up and goes back to 720p, and stays there and remains black. not sure if thats a symptom or just something with my tv.

[MaestroDD]

Hi Criti,

AppleTV: 2.3.1
XBMC: rev19065
Launcher 3.0b5

i'm guessing you guys know more about it, but its weird for me. i've seen a few different things after i switch back and only see black. sometimes after just letting it sit for 10 min, i go back and its back to front row and sometimes i can do the remote shortcut to unpair and pair the remote and it actually shows up on the black screen.

every time i've seen, when i switch the input back to the appletv it switches to 1080i first no matter what resolution the previous input was on, gives up and goes back to 720p, and stays there and remains black. not sure if thats a symptom or just something with my tv.

Do you have advancedsettings.xml in ~/Library/Application\ Support/XBMC/userdata/advancedsettings.xml?
Needs to look like this (+ any additional stuff you put there):
<advancedsettings>
<skiploopfilter>8</skiploopfilter>
<osx_gl_fullscreen>true</osx_gl_fullscreen>
</advancedsettings>

If it's not there, please try it with that file. Otherwise, please post console.log.
cheers,
MDD

[criti]

maestro you are a god. works perfect. i tried just <fullscreen> in there and it didn't help, but didn't know about the osx_gl one. yay! no more appletv reboots.

[MaestroDD]

maestro you are a god.

probably.... _NOT_ ;)

works perfect. i tried just <fullscreen> in there and it didn't help, but didn't know about the osx_gl one. yay! no more appletv reboots.

glad it works. advancedsettings.xml should be created/updated after download/install of XBMC from Launcher. Did you remove it, installed manually,...? There was a bug with this a week ago, thought we fixed it...

[criti]

pretty sure it was there but didn't have the fullscreen option. i installed the latest xbmc through Tsf42m's atvhelper though not through Launcher.

[fullquiver8]

Sorry Newbie Question
I have accessed to .plist file but am not able to modify it because I "don't have sufficient access privileges" I tried changing them to 755 but still not able to edit this file. Would love to try the new launcher

[davilla]

Sorry Newbie Question
I have accessed to .plist file but am not able to modify it because I "don't have sufficient access privileges" I tried changing them to 755 but still not able to edit this file. Would love to try the new launcher

http://xbmc.org/forum/showthread.php?t=45493

[fullquiver8]

Thanks for the quick reply
I guess I am not sure how to navigate to the info.plist and change permissions. I have accessed this file using forklift and used a plist editor to update the file but cannot save it because of permissions. I read your tutorial but am still having trouble (or just a little slow :) Can you give me a little more detail?
Thanks

[davilla]

Thanks for the quick reply
I guess I am not sure how to navigate to the info.plist and change permissions. I have accessed this file using forklift and used a plist editor to update the file but cannot save it because of permissions. I read your tutorial but am still having trouble (or just a little slow :) Can you give me a little more detail?
Thanks

you can't save it because the user "frontrow" does not own the file in question. save it where you do have permission then ssh in and move it into place with the help of the "sudo" command.

[fullquiver8]

I have saved it where I have permissions now can you please explain how to move it into place with the sudo command.
Thanks

[fullquiver8]

I have saved it where I have permissions now can you please explain how to move it into place with the sudo command.
Thanks

[MaestroDD]

fullquiver8,

I have saved it where I have permissions now can you please explain how to move it into place with the sudo command.
Thanks

please show a bit of cooperation and don't let youself spoonfeed. Yes, many of us know how this works, and it would not be much trouble to just simply say "do that, then that, ...", but the howto is written as it is for a reason. E.g. a simple google search for "move file sudo (http://www.google.com/search?hl=en&q=move+file+sudo&btnG=Google-Suche&meta=&aq=f&oq=)" turns up a page in ubuntu forum (http://ubuntuforums.org/showthread.php?t=1068) where exactly the stuff is explained what you're searching for.
Different thing is, I'm not really sure if it helps if you get the beta running. What do you want to if it breaks? And it probably will, it's beta for a reason. It's not like google's "betas" which were probably tested by hundreds of engineers before they even get public :)

Anyways, don't get me wrong. We really appreciate that you want to help testing, but you will need to get stuff yourself into this (not by just typing commands someone posts here), otherwise it's probably better to just wait for a release. But hey, I think Launcher looks good so far, and it will hopefully get to you this weekend with a simple click to "Downloads->Launcher 3.0" ;)

cheers,
stephan

[fullquiver8]

Thanks for the reply. I have been doing a lot of searching but your right I am kind of looking to be spoonfed a bit :) The main reason I want to try the new Launcher is for the ability to use my universal remote which at the moment does not work. Anyways thanks for the comments, I will wait for the release.
Thanks
Kevin

[shadwarr]

All working great here:

AppleTV 2.3.1
Launcher 3.0beta5
XBMC 8.10 bf1:ATLANTIS (Compiled : Dec 18 2008)
HDMI

I've used the new remote functionality and Keymap.xml to get my Logitech Harmony 880 working awesomely. I've been in and out of XBMC and playing a ton of media this afternoon without any problems, lockups etc.

One question I did have to complete my setup: Is the AutoBoot into XBMC not working anymore. I tried defaults write com.teamxbmc.xbmclauncher XBMCExpertMode 1 and then in and out of XBMC but I don't see that new option in the Settings for the default boot app.

[MaestroDD]

All working great here:

AppleTV 2.3.1
Launcher 3.0beta5
XBMC 8.10 bf1:ATLANTIS (Compiled : Dec 18 2008)
HDMI

I've used the new remote functionality and Keymap.xml to get my Logitech Harmony 880 working awesomely. I've been in and out of XBMC and playing a ton of media this afternoon without any problems, lockups etc.

Great, thanks for the feedback!


One question I did have to complete my setup: Is the AutoBoot into XBMC not working anymore. I tried defaults write com.teamxbmc.xbmclauncher XBMCExpertMode 1 and then in and out of XBMC but I don't see that new option in the Settings for the default boot app.

Autoboot should still work, but you'll loose the "Learned Remote" feature. Autoboot switches between XBMC and Frontrow, while in the default mode XBMC runs ontop of Frontrow (where we e.g. get the new multimedia buttons from).
Enabling it should still work the way you described above. There'll be a new setting called MultiFinder. Enabling that adds the default-boot-toggle. You can check if the plist is properly modified with
defaults read com.teamxbmc.xbmclauncher
which should give
{XBMCExpertMode = 1; }

cheers,
MDD

[shadwarr]

Autoboot should still work, but you'll loose the "Learned Remote" feature. Autoboot switches between XBMC and Frontrow, while in the default mode XBMC runs ontop of Frontrow (where we e.g. get the new multimedia buttons from).
Enabling it should still work the way you described above. There'll be a new setting called MultiFinder. Enabling that adds the default-boot-toggle. You can check if the plist is properly modified with


Aha - MultiFinder was disabled. When I re-enabled the functionality worked exactly as you described. Ill leave this off to keep the remote working fine - but at least I was able to test it was working as expected.

Top job - thanks for your help and great product!. Ill report if there are any probs with the beta.