[fritsch]

Nice - thx for reporting back.

[Slurp]

Is the AE_SINK=ALSA a env var, because using export AE_SINK=ALSA doens't work.
Or is it possible to set it with the advancedsettings.xml ?

[un1versal]

It's

Code:

AE_SINK=ALSA xbmc

and you start xbmc from terminal with that. I imagine you can do it via xinit or similar upstart medhods or whatever.

[nickr]

It's

Code:

AE_SINK=ALSA xbmc

and you start xbmc from terminal with that. I imagine you can do it via xinit or similar upstart medhods or whatever.

So

Code:

export AE_SINK=ALSA
xbmc

should work. I think he is saying it doesn't.

[Slurp]

It's

Code:

AE_SINK=ALSA xbmc

and you start xbmc from terminal with that. I imagine you can do it via xinit or similar upstart medhods or whatever.

I know that works, but that is not possible from the launcher. And i don't want to start a terminal. And my girlfriend doesn't know how then

[nickr]

What launcher are you referring to.

[Slurp]

Ubuntu launcher.

But would be really nice to do it through the advanced settings.

And indeed the

Code:

export AE_SINK=ALSA
xbmc

way doens't work. Also not in the bash.rc or other ways to set a env var

[nickr]

Write a script to start xbmc and run that from the launcher.

[un1versal]

It's

Code:

AE_SINK=ALSA xbmc

and you start xbmc from terminal with that. I imagine you can do it via xinit or similar upstart medhods or whatever.

I know that works, but that is not possible from the launcher. And i don't want to start a terminal. And my girlfriend doesn't know how then

Yes, like nickr says, write a script and call that from launcher, the girlfriend excuse was great but that also means you cant ask us how to write a script haha

Linux lets you do anything you want so as long as you doing it in a sane manner fyi the answer is in the interwebs in case your "girlfriend" doesn't know how to google.

Edit: Also the advancedsettings is less likely since the philosophy is to not have advancedsettings at all.

[fritsch]

Let's stick to the topic. advancedsettings.xml is not possible cause it is loaded after audio engine initialization ...

Still interested why people run full blown ubuntu sessions with unity (that kills sync and swapbuffers) and pulseaudio installed and then - don't want to use it. DTS-HD passthrough at 60hz and a compositer behind is the last thing I would want ...

[Slurp]

Yes, like nickr says, write a script and call that from launcher, the girlfriend excuse was great but that also means you cant ask us how to write a script haha

Linux lets you do anything you want so as long as you doing it in a sane manner fyi the answer is in the interwebs in case your "girlfriend" doesn't know how to google.

Edit: Also the advancedsettings is less likely since the philosophy is to not have advancedsettings at all.

Did i ask for a script? I asked for a better solution. Because i find running a script not the best solution if it where possible to use the AE_SINK as a env var. Which was mentioned in the thread.
And the laucher takes exec cmd's but the EXEC = AE_SINK = ALSA xbmc breaks on the second =.
And the girlfriend just knows which icon she needs to click to start xbmc and start watching.


And the advancedsettings is just for these kind of things IMHO.

Let's stick to the topic. advancedsettings.xml is not possible cause it is loaded after audio engine initialization ...

Still interested why people run full blown ubuntu sessions with unity (that kills sync and swapbuffers) and pulseaudio installed and then - don't want to use it. DTS-HD passthrough at 60hz and a compositer behind is the last thing I would want ...

But can it be a env var? because now it doesn't work as it seems.

Sometimes you don't have much of a choice.

[RipT]

I was using a script from the launcher to get xbmc to start with alsa, but I don't anymore as the latest nightlies work fine with pulse. So it can be done. write an actual script file, such as a text file called xbmc-alsa. put this in it:

Code:

#!/bin/bash

AE_SINK=ALSA xbmc

Put it in your path and make it executable with chmod. Then just call xbmc-alsa with your launcher. Or, better yet, upgrade to the latest nightly and let it run pulse.

[nickr]

No need to get snarky.

Try this approach: /usr/bin/xbmc is a script anyway. It starts xbmc.bin which does the real work. Edit /usr/bin/xbmc how you want.

It will break next time you update xbmc from a repo as /usr/bin/xbmc will be over written.

Alternative 2, write a script named xbmcmyway (or whatever you want to call it

Code:

#!/bin/sh
AE_SINK=ALSA xbmc

Put it in /usr/local/bin and make is executable.

Copy /usr/share/applications/xbmc.desktop to /usr/share/applications/xbmcmyway.desktop

Change the line Exec=xbmc to Exec=xbmcmyway

Now click on that to make xbmc go. Even edit the icon to distinguish it from the usual xbmc icon.

I am not sure why your environment variable method isn't working, it should. How are you setting the variable?

[Slurp]

Got the second approach already working, but thanx for the help.

But the environment variable is indeed not working.

First tried export.
And also added it to my .bashrc

Tested it with :

Code:

set | grep AE
AE_SINK=ALSA

So it seems that it is set but doesn't get picked up.

[nickr]

You have to be sure it is set in the right environment.

For example if I open an x-terminal and type

Code:

export MYVAR=test
echo $MYVAR

I get the response

Code:

test

However if I then open another x-terminal it returns nothing, because it is not set in that new environment.

So I suspect your .bashrc is not read by whatever mechanism is starting xbmc.

Try putting it in ~/.profile, or read man bash, particularly the section titled INVOCATION.