Dear visitor, welcome to KDE-Forum.org.
If this is your first visit here, please read the Help. It explains in detail how this page works.
To use all features of this page, you should consider registering.
Please use the registration form, to register here or read more information about the registration process.
If you are already registered, please login here.
amarok engine setting
Is there a way to prevent amarok from switching output engines if the hardware for the one it's set to use isn't available?
since the upgrade to amarok 1.4, this seems to happen automatically during startup if it can't find the hardware associated with the one it's currently looking for. Of course if the hardware isn't there the engine won't work so in a way it makes sense. Only, it ends up being a pain because if xine is configured to use my USB speakers but the speakers aren't actually plugged in, it defautls to the 'void engine'. this means that I have to reset the engine once I get the speakers plugged in. It didn't do this in the past.
And amaork often loads at startup if it was open when I shutdown, even if I'm not planning to use it (and so don't have the speakers plugged in).
Thanks
The poopsmith's job is obvious.
RE: amarok engine setting
You could write a script which starts amaroK like this:
|
Source code
|
1
2
3
4
|
#!/bin/bash
kwriteconfig --file amarokrc --group Playback --key "Sound System" xine-engine
amarok
|
Replace it by the amaroK link in your K Menu for example, or whatever you use to start amaroK.
Bram Schoenmakers
KDE Netherlands (www.kde.nl)
Thanks for the idea. This solves the problem of the xine engine not being set when it starts up.
There's no way to disable the feature that changes engines automatically though? In the previous version this didn't seem to be an issue.
The poopsmith's job is obvious.
No, I'm not aware of such option (else I didn't make up a work around
)
Bram Schoenmakers
KDE Netherlands (www.kde.nl)
Friday, November 8th 2024, 3:49pm
Go to the top of the page
