http://redmine.audacious-media-player.org/http://redmine.audacious-media-player.org/welcome/favicon.ico?15159353402016-04-28T14:45:25ZRedmineAudacious - Feature #638: Bypass crossfade settings when playing a file.http://redmine.audacious-media-player.org/issues/638?journal_id=23822016-04-28T14:45:25ZJohn Lindgrenjohn@jlindgren.net
<ul></ul><p>Perhaps multiple instances (with separate settings) would be helpful.</p> Audacious - Feature #638: Bypass crossfade settings when playing a file.http://redmine.audacious-media-player.org/issues/638?journal_id=23832016-04-28T15:20:54ZChris Lauriechris-audacious@acron.biz
<ul></ul><p>I'm not sure how the multiple instances would work. If it can remember the settings on a per instance then maybe. How would command line scripts and audtool calls know which instance to use as target for the api request?</p>
<p>An api to enable/disable a plug-in at runtime seems a simpler solution.</p> Audacious - Feature #638: Bypass crossfade settings when playing a file.http://redmine.audacious-media-player.org/issues/638?journal_id=23842016-04-28T20:35:19ZJohn Lindgrenjohn@jlindgren.net
<ul></ul><p>Something like <code>audacious -2</code> would start a second instance (which would store its own settings in, say, <code>~/.config/audacious-2</code>), and <code>audtool -2 <command></code> would control it remotely. It would actually be fairly simple to implement.</p>
<p>This approach might not have any advantage for your particular needs, but I think it's more generic and could be useful in other scenarios as well. For example, some time ago we had another user, also running sound for a theater, who wanted to run a playlist of background music in one instance, while at the same time playing individual sound effects from a playlist in another instance (using the "No Playlist Advance" setting).</p> Audacious - Feature #638: Bypass crossfade settings when playing a file.http://redmine.audacious-media-player.org/issues/638?journal_id=23852016-04-28T20:54:01ZChris Lauriechris-audacious@acron.biz
<ul></ul><p>I can totally see the value of this, If the 2 instances are feeding separate sound outputs. In my case the sound is output on the same device. So the only one should play at a time.</p>
<p>I suggest being able to enable a plug-in through the command line is a very useful functionality anyway, for many other uses, not only my own.</p>
<p>My solution for the playlist no advance described above is to have the lighting software (QLC+) call audacious from the command line to play a track, so it creates a single entry in the now playing playlist. That way I do not have to actually administer the Audacious instance manually, it all happens via the command line. In fact I could run it headless, but I don't because in live theatre it is good to have some insurance.</p>
<p>Being able to control more parameters from the command line also allows me to create and thoroughly test the control scripts and then it becomes easier to give the full production to a less experienced and knowledgeable operator.</p> Audacious - Feature #638: Bypass crossfade settings when playing a file.http://redmine.audacious-media-player.org/issues/638?journal_id=23862016-04-29T01:22:20ZJohn Lindgrenjohn@jlindgren.net
<ul></ul><p>Chris Laurie wrote:</p>
<blockquote>
<p>I suggest being able to enable a plug-in through the command line is a very useful functionality anyway, for many other uses, not only my own.</p>
</blockquote>
<p>Yes, I agree, provided it worked for all plugins, not just crossfade.</p> Audacious - Feature #638: Bypass crossfade settings when playing a file.http://redmine.audacious-media-player.org/issues/638?journal_id=23872016-04-29T02:52:20ZJohn Lindgrenjohn@jlindgren.net
<ul><li><strong>Category</strong> set to <i>audtool</i></li><li><strong>Status</strong> changed from <i>New</i> to <i>Closed</i></li><li><strong>Target version</strong> set to <i>3.8</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li><li><strong>Affects version</strong> <i>3.7.2</i> added</li></ul>