Redmine: Issueshttp://redmine.audacious-media-player.org/http://redmine.audacious-media-player.org/welcome/favicon.ico?15159353402023-04-11T20:35:32ZRedmine
Redmine Audacious - Bug #1209 (New): Dual play icons in default Audacious Winamp skinhttp://redmine.audacious-media-player.org/issues/12092023-04-11T20:35:32ZManuel Grießmayr
<p>I've a 4K screen and the play icons looks like in attached image. The workaround is easy by simply modifying the source image.</p> Audacious - Bug #1199 (New): Inaccurate seeking in WebM (and Ogg Opus) audio fileshttp://redmine.audacious-media-player.org/issues/11992022-11-04T03:40:29ZNyan Pasu
<p>In WebM audio files downloaded through yt-dlp (Opus) or encoded myself (Opus and Vorbis), Audacious's seeking is extremely imprecise. In some cases, I click on different timestamps in the seek bar, seconds apart in a given file, yet playback jumps to the same point.</p>
<p>In testing:</p>
<ul>
<li>.flac and Ogg Vorbis seeking are always accurate to sub-second precision.</li>
<li>With WebM (Opus/Vorbis) files, clicking ahead of the current play point can jump up to ~5 seconds ahead (to the next "start point" of some sort) which is quite awful. Clicking back into an already-played and decoded section of a file which has played continuously from the file's beginning is accurate. Clicking forward or back from a forward click is inaccurate, and usually jumps to the same "start point".</li>
<li>With Ogg Opus files, seeking jumps up to 1-2 seconds <strong>behind</strong> the click point. Seeking into already-decoded audio is <strong>not</strong> more accurate than seeking ahead (unlike WebM). This is mostly less bad than WebM, but still inaccurate.</li>
</ul>
<p>The worst part to me is that Audacious's play time viewer and seek bar act as though you've seeked to the exact time in the song, yet the actually playing audio can be multiple seconds off the point you clicked. So effectively the program is lying to you, and with many songs I thought I was just really bad at seeking to the right spot, not realizing Audacious was at fault.</p>
<p>I've attached a set of test audio files containing identical pitched sweeps (aside from lossy compression), designed so you can easily hear the exact point in time you seeked to (even if Audacious's play time viewer is inaccurate).</p> Audacious - Feature #1119 (New): ADD ability to silence internet radio timeout Error dialog popup http://redmine.audacious-media-player.org/issues/11192021-07-31T18:36:18ZAllan Laalallan.laal@gmail.com
<p>please add an option to hide these errors:</p>
<p>!!</p>
<p>normally this happens when my connection breaks for a bit and its pretty evident an error happened, since there is no music :)</p> Audacious - Bug #1106 (New): Could not communicate with last.fm: Error in the HTTP2 framing layer.http://redmine.audacious-media-player.org/issues/11062021-06-07T20:51:17ZNelson Suniaga
<p>Today I downloaded and recompiled the last Audacious master release from GitHub, and I wanted to check the last tracks submitted to Last.fm to find out Audacious Scrobbler Plugin 2.0 hasn't been communicating with Last.fm in the last few months (the last scrobble was on April 5th), it says</p>
<pre>
You need to allow Audacious to scrobble tracks to your Last.fm account
</pre>
<p>but in my Last.fm account Audacious has permission (along with Qmmp and Last.fm Desktop Scrobbler for Windows) or might say "HAD" because I disconnected it just to try it once again, which I couldn't.</p>
<p>In the plugin settings I clicked on "Check Permission", and it answered:</p>
<pre>
There was a problem contacting Last.fm. Your scrobbles are being saved on your computer temporarily. They will be submitted as soon as Audacious is allowed access.
</pre>
<p>And in the console Audacious wrote:</p>
<pre>
ERROR scrobbler_communication.cc:124 [send_message_to_lastfm]: Could not communicate with last.fm: Error in the HTTP2 framing layer.
</pre>
<p>That make me think Last.fm API has changed and is not my mistake. I forgot which config file I put my Last.fm credentials, so I'm unable to test it again (but I haven't change it so far).</p> Audacious - Bug #1105 (New): LADSPA host setting menu does not show up with Qt interfacehttp://redmine.audacious-media-player.org/issues/11052021-06-01T12:26:07Zchris denice
<p>With Qt interface:</p>
<p>Go to Settings -> Plug-ins -> Effects -> LADSPA Host.</p>
<p>Now click on the "gear", a blank window appear with only one button "Close". This renders All LADSPA plug-ins unusable as they cannot be selected, neither adjusted.</p>
<p>Everything works fine with the GTK Legacy interface!</p> Audacious - Feature #1046 (New): Add all id3v2 frames in the settings of Playlist available columnshttp://redmine.audacious-media-player.org/issues/10462020-12-28T18:26:15ZNelson Suniaga
<p>The GTK interface allows to add and remove columns from the Playlist, but those columns are just ten out of the many id3v2 frames existent. For most cases, those ten columns available are enough, but now I want to sort tracks chronologically from "Best of..." / "Greatest Hits" / "Anthology" albums by using the "Original Date" column.</p>
<p>In the current state, the only option is to put the "original year track" on the "Comment" frame, which is not an option cause sometimes that frame holds relevant information about the track.</p>
<p>A question pops up to my mind: Why just ten columns are available in the Playlist, out of all id3v2 frames?</p> Audacious - Bug #1014 (New): Some .VGM/.VGZ files fail to playhttp://redmine.audacious-media-player.org/issues/10142020-08-05T22:32:04ZBail Shamber
<p>"DOOM vgm" and "skyroads vgm" files (can be obtained from the first google search result) fail to play on audacious using the "Game Console Music Decoder" plugin, while they do play in deadbeef and foobar2000.<br />Some other vgm files play fine such as road rash for the sega genesis "road rash vgm" first google result.<br />I'm using the flatpak version, btw.</p> Audacious - Feature #998 (New): aacgain in aac / r128 in opushttp://redmine.audacious-media-player.org/issues/9982020-06-17T00:12:59ZMauricio Salinas
<p>Hi,</p>
<p>ReplayGain in .aac files tagged (using aacgain v. 1.9) seems to not being recognized.</p>
<p>It happens as well in files with R128_TRACK_GAIN tag (using opus-tools 0.1.10 and r128gain v1.0.1) in .opus files.</p>
<p>I'm not sure if these two requests should be together: sorry if they shouldn't.</p>
<p>Thanks! Loving the player since years ago!</p> Audacious - Bug #993 (New): Lyrics for streamed content are written to cache but not read.http://redmine.audacious-media-player.org/issues/9932020-06-07T13:10:51ZRóbert Čerňanskýopenhs@tightmail.com
<p>While playing a track from (HTTPS) stream the lyricwiki plugin correctly fetches lyrics and writes them to local cache (~/.config/audacious/lyrics/...). If however the same remote track is played again the lyrics are not read back from the cache (they are read from the web again). For local files it works as expected (lyrics are written to and read from the cache).</p>
<p>From the issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: lyricwiki - Please add support for local .lrc lyric files (patch included) (Closed)" href="http://redmine.audacious-media-player.org/issues/906">#906</a> it seems that it is a feature. To me it seems as rather odd requirement. Why write but not read? I am not sure what was the motivation for it. Behaviour I would expect is one of the following:</p>
<pre><code>1. lyrics from streamed content are not cached at all (not written, not read)<br /> 2. lyrics from streamed content are both written and read back to/from the cache<br /> 3. lyrics from streamed content are only read from cache but not written to</code></pre>
<p>Option 2 is preferred.</p>
<p>Reason for option 3 could be not to pollute the cache when listening to an internet radio (not sure if this is a real use case though; a few radio streams I have checked did not provide track names and did not cache any lyrics).</p> Audacious - Bug #975 (New): Segfault/leak on exit with streamtuner enabledhttp://redmine.audacious-media-player.org/issues/9752020-04-22T06:40:51ZJim Turnerturnerjw784@yahoo.com
<p>Fresh install of 4/21 GIT (to test proposed patch), ran (control run) pristine b4 making any changes several times, often getting a segfault OR a "string leak" when exiting with radio stream from StreamTuner.iheart playing (and the streamtuner plugin window active and embedded in the main window). Otherwise seem to work as expected. Then applied patch (for unrelated issue), tested, same results. Saved core each time and ran gdb. I've since cleared playlist, re-added a StreamTuner.iheart station (don't remember what the one that failed was). Anyway, got the same backtrace from the cores I looked at (see attached). I'm running Qt, version 5.71, system is 32-bit Linux (uname -a: Linux integra 4.20.12-antix.1-486-smp #1 SMP Mon Feb 25 10:34:04 EET 2019 i686 GNU/Linux)</p>
<ul>
<li>I can't seem to reproduce IF I close the StreamTuner plugin and restart, but if I re-enable the StreamTuner plugion, I CAN easily reproduce repeatedly (alternating between either the "string leak" or the "segfault"). Both are included in the attachment.</li>
</ul>
<p>Normal way to reproduce (StreamTuner loaded): start Audacious from command line, no args, either start playing something or not, and just quickly exit.</p>
<p>Cheers,</p>
<p>Jim</p> Audacious - Bug #973 (New): "snd_pcm_recover failed" alsa error and "String leaked" warningshttp://redmine.audacious-media-player.org/issues/9732020-04-21T17:56:37ZIgor Kushnir
<p>Steps to reproduce:<br />1. Enable Song Change Audacious plugin and set its <em>Command to run at the end of the playlist</em> to:<br /><pre><code class="ruby syntaxhl"><span class="CodeRay">bash -c <span class="string"><span class="delimiter">"</span><span class="content">sleep 0.1 && audacious -p -E '/usr/share/sounds/alsa/Front_Center.wav'</span><span class="delimiter">"</span></span>
</span></code></pre></p>
<p>2. Set Audio Output plugin to <em>ALSA Output</em>.<br />3. Disable all Repeat and Shuffle options in Audacious to let the configured Song Change command run.<br />4. Quit Audacious and run it from terminal like this:<br /><pre><code class="ruby syntaxhl"><span class="CodeRay">audacious -p <span class="string"><span class="delimiter">'</span><span class="content">/usr/share/sounds/alsa/Front_Center.wav</span><span class="delimiter">'</span></span>
</span></code></pre></p>
<p>5. Let Audacious play this short file repeatedly for several minutes. You may want to mute Audacious in <em>pavucontrol</em>.<br />6. If no errors appear in Audacious output after 10 minutes, try a different sleep interval. I get more than one error per minute with the interval 0.1. But I also get at least one error in less than 10 minutes with intervals 0.01, 0.05, 0.2 and 0.5.<br />7. Quit Audacious and examine its output. Possible result:<br /><pre><code class="ruby syntaxhl"><span class="CodeRay"><span class="error">$</span> audacious -p <span class="string"><span class="delimiter">'</span><span class="content">/usr/share/sounds/alsa/Front_Center.wav</span><span class="delimiter">'</span></span>
<span class="constant">ERROR</span> alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
ERROR alsa.cc:<span class="integer">253</span> [get_delay_locked]: snd_pcm_recover <span class="key">failed</span>: <span class="constant">Input</span>/output error.
WARNING strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: sounds - alsa - <span class="constant">Front_Center</span>
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: <span class="key">file</span>:<span class="regexp"><span class="delimiter">/</span><span class="delimiter">/</span></span>/usr/share/sounds/alsa/<span class="constant">Front_Center</span>.wav
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: <span class="constant">Microsoft</span> <span class="constant">WAV</span> (signed <span class="integer">16</span> bit)
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: wav
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: <span class="constant">Mono</span>, <span class="integer">48</span> kHz
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: <span class="regexp"><span class="delimiter">/</span><span class="content">usr</span><span class="delimiter">/</span><span class="modifier">s</span></span>hare/sounds/alsa
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: sounds
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: alsa
<span class="constant">WARNING</span> strpool.cc:<span class="integer">181</span> [operator()]: <span class="constant">String</span> <span class="key">leaked</span>: <span class="constant">Front_Center</span>
<span class="constant">WARNING</span> runtime.cc:<span class="integer">364</span> [aud_leak_check]: <span class="constant">Bytes</span> allocated at <span class="key">exit</span>: <span class="integer">160</span>
</span></code></pre></p>
<p>8. Expected result: empty output.<br />9. Note that the <em>String leaked</em> warnings don't appear every time. Perhaps once in three such tests on average.<br />10. In case you don't have an audio file at the specified path, I'm attaching mine to this bug report. The path to the file shouldn't matter. The bug is not limited to this particular file, but it allows to reproduce the issue with minimum effort due to its short duration.<br />11. I have reproduced this bug with <em>audacious</em> and <em>audacious-plugins</em> built from current git master: <a class="external" href="https://github.com/audacious-media-player/audacious/commit/ffd9ac46a43f3fb0e02d06adf382291f82037a16">https://github.com/audacious-media-player/audacious/commit/ffd9ac46a43f3fb0e02d06adf382291f82037a16</a> ; <a class="external" href="https://github.com/audacious-media-player/audacious-plugins/commit/89b6ab575ec823b67655bea2fbd2dc7429465377">https://github.com/audacious-media-player/audacious-plugins/commit/89b6ab575ec823b67655bea2fbd2dc7429465377</a> (built both in Debug and Release modes)</p> Audacious - Bug #859 (New): .wsz skins cannot be used on Windowshttp://redmine.audacious-media-player.org/issues/8592019-01-10T05:13:52ZJohn Lindgrenjohn@jlindgren.net
<p>The current scheme uses the external "unzip" program which generally isn't present on Windows.</p>
<p>We could ship an "unzip.exe" along with the Windows build, but it would be better if we could read the .wsz/.zip files directly through the VFS layer, without running an external .exe and creating temporary files on the C: drive.</p> Audacious - Bug #784 (New): Audio jumps at the start of some tracks when playing CUE+TTA fileshttp://redmine.audacious-media-player.org/issues/7842018-03-31T20:54:31ZNet Helin
<p>Steps to reproduce:</p>
<p>1. Download and play the example file with the attached cue sheet:</p>
<p><a class="external" href="https://0x0.st/sMTG.tta">https://0x0.st/sMTG.tta</a> (rename to "Fantasia of the Shades, by the Shades, for the Shades.tta")</p>
<p>2. Play the 4th track (you can seek to a few seconds before the end) and play it to the end.</p>
<p>3. When the 5th track starts the audio jumps - a small fragment of the track is played twice.</p>
<p>Happens with Audacious 3.9 and libcue 2.2.0 on Manjaro Linux. Also happens with other files.</p> Audacious - Bug #585 (New): "Remove Unavailable Files" temporarily freezes UIhttp://redmine.audacious-media-player.org/issues/5852015-11-09T15:04:52ZVitalii Cherniakvitaliic@ukr.net
<p>Steps to reproduce:<br />1) Prepare playlist with more than 20000 songs.<br />2) Select Playlist -> Remove Unavailable Files</p>
<p>Actual result:<br />Audacious UI freezes. If there were song play it will stop playing after song end.</p>
<p>Expected result:<br />Audacious UI have no freezes. Next song in the list start to play after played one ends. The best will be to add some progress on "Remove Unavailable Files" operation.</p>
<p>Additional notes:<br />My music collection (>20k songs) is sshfs folder.</p> Audacious - Bug #196 (New): Wrong channel map when doing surround playbackhttp://redmine.audacious-media-player.org/issues/1962012-10-12T03:10:33ZAdriano Mouraadriano.lols@gmail.com
<p>Seems that Audacious pulseaudio output plugin has never set an appropriate channel map. This little patch will use pa_channel_map_init_auto and assume WAVEEX style channel mapping. Audacious can now properly output any 5.1 file I trow at it.</p>
<p>Before:</p>
<pre><code>sample spec: float32le 6ch 88200Hz<br /> channel map: front-left,front-left-of-center,front-center,front-right,front-right-of-center,rear-center<br /> resample method: copy<br /> module: 6<br /> client: 20094 &lt;Audacious&gt;</code></pre>
<p>Now:</p>
<pre><code>sample spec: float32le 6ch 88200Hz<br /> channel map: front-left,front-right,front-center,lfe,side-left,side-right<br /> Surround 5.1<br /> resample method: copy<br /> module: 6<br /> client: 20114 &lt;Audacious&gt;</code></pre>
<p>For correct 4.0/6.1/7.1 surround mappings you will need some pulseaudio patches, but I'm still working on this. WAVEEX seems to be wrongly implemented in pulseaudio right now.</p>