Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

I'm not aware of any changes in 3.4.2 that would have caused what you describe.

Hi John,

Have you tried it? Before I could simply pass a directory name to Audacious and it would automatically cue the music recursively in the folders below the one passed, regardless of the depth. Now if I pass just a folder name nothing happens. I have tried a few permutations:

Command                   Result

audacious %folder/*       Cues everything in the folder, including pictures.
audacious %folder/*.mp3   Cues only Mp3 files in the folder.

Both commands only work in the folder passed...it doesn't cue files recursively.

With the previous version of audacious all I needed to do was "audacious %folder" and it would recursively cue only music files from that folder, all the way down. Make sense?

Unless there is a compelling reason to upgrade I think I'll roll back to the previous version of Audacious.

Thanks,

Jim.

Try installing the MP3 plugin. It might help.

Hi John,

I've already installed the MP3 plugin...without it I wouldn't be able to play MP3's. ;-)

Update: I tried downloading the latest source from this website and compiled it without error. Audacious does the same thing when cuing up directories.

Are you running Audacious on Linux? Can you try passing a folder to your installation of Audacious to see if it cues up the songs in it?

I will try downloading the previous version and confirm the behaviour.

Thanks,

Jim.

Update: I downloaded 3.2.4 from the Audacious website, compiled and installed it successfully. The old 3.2.4 version cues up files the way I'm used to. This function in 3.4.2 appears to be broken/different.

Is there anything you'd like me to check/do on my side?

Another Update: I tried downloading 3.4.2 from the Audacious site, compiled and installed it successfully. Now the folder cue function is behaving properly. Must have been one of the missing dependencies I had to resolve in order to properly compile the 3.2.4 plugins. Not sure what the dependency was (there were several I was missing). Do you have a list somewhere of all the package/library dependencies?

The following is the list of packages I installed to resolve the missing dependencies for the plugins:

libmpg123-devel      1.16.0-1.1
alsa-devel           1.0.27.2-161.1
fluidsynth-devel     1.1.6-37.1
libcdio++0           0.90-49.1
libogg-devel         1.3.0-29.1
libsamplerate-devel  0.1.8-36.1
libudf0              0.90-49.1
wavpack-devel        4.60.99-36.1
libdbus-c++-1-0      0.9.0-17.1
libdbus-c++-glib-1-0 0.9.0-17.1
flac-devel           1.3.0-204.1
libcdio-devel        0.90-49.1
libdbus-c++-devel    0.9.0-17.1
libusb-1_0-devel     1.0.9-5.1.1
libusb-compat-devel  0.1.4-23.1.1
libmtp-devel         1.1.5-3.4.1

Would any of these cause the folder cue issue? If you can pin-point the package, that would certainly help anyone else in the future having the same problem.

Cheers,

Jim.

You can play MP3s with the FFmpeg plugin, but it doesn't "officially" support them so they won't be added if you just add a directory. That's why I asked you to check if the MP3 plugin was installed (which I'm guessing you didn't actually check?)

The MP3 plugin depends on libmpg123; that's why your compiled version didn't work at first.

Jim Gravelle wrote:

Do you have a list somewhere of all the package/library dependencies?

There is a list for Ubuntu here; OpenSUSE may have different package names:
http://redmine.audacious-media-player.org/boards/1/topics/788

Hi John,

I guess I didn't understand what you meant by "is the MP3 plugin installed?". I thought you meant does it show-up in the Audacious / Preferences / Plugins / Input tab...which it did. Originally I installed Audacious and the plugins from the Pacman repo...and I didn't have any dependency issues reported. After all, the previous version (3.2.4) when installed from Pacman worked just fine.

Also, when you said in a previous post "try installing the Mp3 plugin"...I checked for the libmpg123 package to see if it was installed (found reference to it in another forum post)...the package was already installed.

In the package list I provided above; other then a couple CD access and dbus libraries, the rest are devel packages...which I thought were only relevant for compiling source. Or am I wrong on that one?

Thanks,

Jim.

Well, Jim, I guess my theory was wrong ... got a different one? :)

Happy New Year, guys!

Since I cannot reproduce the issue with 3.4.2 and Fedora 20 (and also with konqueror it works for me), I'd like to see more trouble-shooting from the reporter, such as the full output of

  ls -R directoryname
  audacious -V directoryname

and what happens if you drag'n'drop a folder onto the Audacious playlist? (e.g. from konqueror or nautilus)

Hi Michael,

I did some more investigation by uninstalling the version I downloaded from the Audacious website and reinstalling the Pacman version...turns out the biggest difference is in the Input plugins. I think it goes back to what John said a couple of days ago: "You can play MP3s with the FFmpeg plugin, but it doesn't "officially" support them so they won't be added if you just add a directory." The Pacman build installs the FFmpeg and not the "madplug.so" MPG123 Plugin that I get from the version I download here.

This can be confirmed by the output of audacious -V directoryname from Pacman:

probe.c:164 [file_find_decoder]: Probing file:///home/JimG/Work/Music/1993%20Black%20Tie%20White%20Noise%20%2814%20tracks%29%20%40320/10.Looking%20For%20Lester.mp3.
probe.c:120 [probe_by_scheme]: Probing by scheme.
probe.c:134 [probe_by_extension]: Probing by extension.
probe.c:194 [file_find_decoder]: Probe failed.

And the output of audacious -V directoryname from here:

probe.c:164 [file_find_decoder]: Probing file:///home/JimG/Work/Music/1993%20Black%20Tie%20White%20Noise%20%2814%20tracks%29%20%40320/01.The%20Wedding.mp3.
probe.c:120 [probe_by_scheme]: Probing by scheme.
probe.c:134 [probe_by_extension]: Probing by extension.
probe.c:108 [probe_func_fast]: Guessing MPG123 Plugin.
probe.c:192 [file_find_decoder]: Probe succeeded: MPG123 Plugin

So I'm confident in concluding the Pacman build of Audacious is at fault...it should have the libmpg123 support compiled in it.

Thanks for your help.

Jim.