Bugzilla – Bug 190
Unable to play MP3 files with CUE files present using UNC musicfolder path
Last modified: 2008-09-15 14:37:04 UTC
I'm unable to play MP3 files with CUE files when the musicfolder is set to an UNC path (\\[server]\[share]) It works when using local drive letters (C:\, D:\ ...) I get two identical files in the server window when browsing any MP3 file with a matching CUE file. Example: In music folder: MP3 file #1 with CUE file MP3 file #1 with CUE file MP3 file #2 without CUE file MP3 file #3 with CUE file MP3 file #3 with CUE file MP3 file #4 without CUE file In PlayList view (when selecting play from 'Browse Music Folder' on any directory containing one MP3 file and one matching CUE file: Track 1 from MP3 file #1 with CUE file Track 2 from MP3 file #1 with CUE file Track 3 from MP3 file #1 with CUE file Track 4 from MP3 file #1 with CUE file MP3 file #1 with CUE file <--- Only this one will play (SliMP3 automatically jumps to this song) The MP3 file is played as one continous file. The tracks that are seperated by the CUE file will not play. I need this to work because I have the SliMP3 server running as an service on a server (Windows Server 2003) connecting to another computer (Windows XP) to read the MP3 files. I'm using version 5.1 (have also tried the beta 5.1.1 Firmware 2.2 (SliMP3)
can you attach one of the cue files in question?
Created attachment 10 [details] Cue file Note that when I set the music folder to a local drive there is no problem with the CUE file. The MP3 file is located in the same directory. When playing in winamp it works like it should (with mp3cue installed).
Fixed in the latest nightly build. Please try it and comment if it's not working for you.
Yes it works now, I can play the files with CUE files present. Great work :-) But I still get 2 files in the "browse music folder view". One for the CUE file, and one fro the actual MP3 file. It's annoying to have both of them visible. When a CUE file is present, the MP3 file shouldnt be displayed as a seperate file.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.