http://redmine.audacious-media-player.org/http://redmine.audacious-media-player.org/welcome/favicon.ico?15159353402019-02-24T13:41:21ZRedmineAudacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32232019-02-24T13:41:21ZJohn Lindgrenjohn@jlindgren.net
<ul><li><strong>Category</strong> set to <i>plugins/m3u</i></li><li><strong>Subject</strong> changed from <i>m3u file: metadata is ignored, short links do not work</i> to <i>Extended M3U support</i></li><li><strong>Tracker</strong> changed from <i>Bug</i> to <i>Feature</i></li></ul><p>That's the "Extended M3U" format, we don't support that currently.</p>
<p>And your short links point to HTML pages, how exactly did you expect Audacious to "play" those?</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32252019-02-24T13:43:07ZRaitaro Hikami
<ul></ul><p>Ok so what kind of format does audacious support exactly? Should I copy the ones found in .config/audacious/playlists?</p>
<p>Again, `vlc <a class="external" href="https://youtu.be/HQeIivIacJc">https://youtu.be/HQeIivIacJc</a>` works :)</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32292019-02-24T13:50:01ZRaitaro Hikami
<ul></ul><p>Getting the full link from that I get this loooooong thingy here. But whatever, this is to be used for streaming some stuff. The issue is this links is very long and takes a while to be generated vs the nice and quick js option :(</p>
<pre>
▶ youtube-dl -g https://youtu.be/HQeIivIacJc
https://r1---sn-pouxga5o-vu2l.googlevideo.com/videoplayback?signature=58109388B28D71A5815495CB4827A2D73CAA7F56.82E7968B3696D80553E47011C32B8E3C63987695&fvip=3&ratebypass=yes&requiressl=yes&sparams=dur%2Cei%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cexpire&itag=22&ei=V6ByXNWkA9fk7gOn_6_4BQ&key=yt6&id=o-AAwXENMdGgnmEGU_QIkXjRdcuhutGvT1ZLgqYbppgiBJ&lmt=1550360255567520&mn=sn-pouxga5o-vu2l%2Csn-c0q7lnsl&c=WEB&ipbits=0&mm=31%2C29&txp=5532432&initcwndbps=186250&pl=24&mime=video%2Fmp4&mt=1551015881&ip=94.176.148.35&ms=au%2Crdu&expire=1551037623&mv=m&dur=585.026&source=youtube
</pre>
<p>Would be cool to pipe btw... `youtube-dl -g <a class="external" href="https://youtu.be/HQeIivIacJc">https://youtu.be/HQeIivIacJc</a> | audacious --qt`</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32332019-02-25T18:16:27ZRaitaro Hikami
<ul></ul><p>🤞😤</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32372019-03-07T03:54:30ZJim Turnerturnerjw784@yahoo.com
<ul><li><strong>File</strong> <a href="/attachments/777/m3u.diff">m3u.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/777/m3u.diff">m3u.diff</a> added</li></ul><p>Supporting extended m3u playlists does not appear to be difficult. Here's a patch to m3u.cc to do just that that seems to work for me. It also adds a checkbox to the plugin's [settings] labeled "Save in Extended M3U format" []. It will load either normal or extended playlists regardless.</p>
<p>Regards,</p>
<p>Jim</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32392019-03-12T15:19:49ZRaitaro Hikami
<ul></ul><p>Jim Turner wrote:</p>
<blockquote>
<p>Supporting extended m3u playlists does not appear to be difficult. Here's a patch to m3u.cc to do just that that seems to work for me. It also adds a checkbox to the plugin's [settings] labeled "Save in Extended M3U format" []. It will load either normal or extended playlists regardless.</p>
<p>Regards,</p>
<p>Jim</p>
</blockquote>
<p>So... I assume I will have to apply the diff in this: <a class="external" href="https://github.com/audacious-media-player/audacious-plugins/blob/master/src/m3u/m3u.cc">https://github.com/audacious-media-player/audacious-plugins/blob/master/src/m3u/m3u.cc</a><br />Then I need to configure and make install the repo itself, right?</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32402019-03-12T16:35:26ZRaitaro Hikami
<ul></ul><p>To be fair I tried.</p>
<p>To build audacious I did:<br /><pre>
TPUT=/bin/true ./configure --prefix=/usr --enable-qt --disable-gtk &&\
make
sudo make install
</pre></p>
<p>For plugins:<br /><pre>
TPUT=/bin/true ./configure --prefix=/usr --disable-wavpack --with-ffmpeg=none --enable-qt --disable-gtk &&\
make
sudo make install
</pre></p>
<p>And I just get<br /><pre>
ERROR plugin-init.cc:147 [start_required]: No output plugin found.
(Did you forget to install audacious-plugins?)
</pre></p>
<p>Not sure why so I simply `sudo make uninstall` and reinstalled audacious normally and not it works. (-H works btw)</p>
<p>Ah well, will be waiting for the support to trickle down in my ppa ¯\_(ツ)_/¯</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32442019-03-13T16:18:35ZJohn Lindgrenjohn@jlindgren.net
<ul></ul><p>Jim Turner wrote:</p>
<blockquote>
<p>Supporting extended m3u playlists does not appear to be difficult.</p>
</blockquote>
<p>The problem is that refreshing the playlist will throw away the info from the extended M3U. We need a way (for example, a flag in the Tuple class) to mark info that came from a playlist (cuesheet or extended M3U) rather than from the audio file itself.</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32552019-03-18T04:01:36ZJim Turnerturnerjw784@yahoo.com
<ul><li><strong>File</strong> <a href="/attachments/787/playlist-data.cc.diff">playlist-data.cc.diff</a> <a class="icon-only icon-download" title="Download" href="/attachments/download/787/playlist-data.cc.diff">playlist-data.cc.diff</a> added</li></ul><p>@John: That's what the playlist-data.cc part of my Bug#878 patch addresses. BTW, I've replaced the scanner.* parts of that patch with your fix for that issue and it seems to work fine now, thanks! I'm including an update to the playlist-data.cc patch here that incorporates that change, see attached.</p>
<p>@Raitaro: Sry you're having trouble building Audacious, but I actually was addressing that patch toward the developers. Here's how I build Audacious:</p>
<p>1) Make sure you have all the "dev" vsns of the required libs: <br />sudo apt-get install git automake build-essential libasound2-dev \<br />libavformat-dev libbinio-dev libbs2b-dev libcddb2-dev libcdio-cdda-dev \<br />libcue-dev libcurl4-gnutls-dev libdbus-glib-1-dev libfaad-dev libflac-dev \<br />libfluidsynth-dev libgl1-mesa-dev libgtk2.0-dev libguess-dev \<br />libjack-jackd2-dev liblircclient-dev libmms-dev libmodplug-dev libmp3lame-dev \<br />libmpg123-dev libneon27-gnutls-dev libnotify-dev libpulse-dev \<br />libsamplerate0-dev libsdl2-dev libsidplayfp-dev libsndfile1-dev libsoxr-dev \<br />libvorbis-dev libwavpack-dev libxml2-dev libsndio-dev libswscale-dev libdvdread-dev libdvdnav-dev</p>
<p>2: UNINSTALL all your existing Audacious packages from your distro (it shouldn't delete your /home/you/.config/audacious files - Tar 'em up to be SURE)!</p>
<p>3):<br />mkdir audacious; git clone git://github.com/audacious-media-player/audacious.git audacious</p>
<p>mkdir audacious-plugins; git clone git://github.com/audacious-media-player/audacious-plugins.git audacious-plugins</p>
<p>5):<br />cd audacious<br />./autogen.sh<br />./configure --prefix=/usr/local [--enable-qt]<br />make -j2<br />sudo make install<br />cd ../audacious-plugins<br />./autogen.sh<br />./configure --prefix=/usr/local<br />make -j2<br />make install<br />cd ..<br />/usr/local/bin/audacious</p>
<p>Good luck!</p>
<p>Jim</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=32562019-03-20T19:11:05ZRaitaro Hikami
<ul></ul><p>@Jim<br />Thank you for the build script. What I did to get the devs was compiling, see what I was missing, and compiling again, which I don't think I did well.</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=43592022-07-17T17:34:40ZJohn Lindgrenjohn@jlindgren.net
<ul></ul><p>Just linking back to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add HLS support (Closed)" href="http://redmine.audacious-media-player.org/issues/1173">#1173</a> where there was some additional discussion. The issue of how to distinguish different sources of Tuple data (e.g. ID3 tag, extended M3U, or cuesheet) remains.</p>
<p>My suggestion would be to add some additional Tuple fields (Tuple::ExtTitle, Tuple::ExtArtist, etc.) which would hold the info from the extended M3U. Then e.g. Tuple::get_str(Tuple::Title) would also optionally look up Tuple::ExtTitle, similar to the existing FallbackTitle logic.</p>
<p>I think there's an opportunity for some nice cleanups here. We could, for example, make use of the new "Ext" fields for cuesheet support, and get rid of the whole CueCache workaround.</p> Audacious - Feature #875: Extended M3U supporthttp://redmine.audacious-media-player.org/issues/875?journal_id=43612022-07-18T00:31:54ZJim Turnerturnerjw784@yahoo.com
<ul></ul><p>John, something else I noticed in additional testing with the official Audacious playlist format (.audpl) is that the same metadata refresh issue you mentioned happens there as it does with my ext-m3u patch (m3u.cc), so I'm assuming that it's working as designed for playlists (cue-sheets work completely differently and don't suffer this issue). Therefore, I doubt the need for the extra tuple fields (assuming that ext-m3u metadata should work same as other "playlist" plugins) - or are you wanting it to work more like cuesheets?</p>
<p>I see what you're saying a/b blanking a field, as I ran into this awhile back while working on something unrelated in song-info updating and discovered that blanking simply left it unchanged ant that I had to enter a space in order to make it "blank", but didn't think anything amiss at the time, but now I realize that the correct behaviour is to reset it to it's "default", in the case of Title, back to the entry's file-name. Not sure off top of my head how to fix that in the patch or if it would need fixing somewhere else though.</p>