INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: BUG: cannot import m3u playlist from network locations  (Read 1436 times)

Tolga

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 438
BUG: cannot import m3u playlist from network locations
« on: May 12, 2004, 06:51:24 pm »

I have library on machine X where all paths point to a network location i.e. "\\X\...".  I export a m3u playlist. If the m3u file is on a local directory, and if I right click on the file and import, the playlist does import as expected. If I move it to a network location  "\\Y\...", I cannot import with right-click.

Let me know if you need more data on this.
Logged

molex

  • Regular Member
  • Recent member
  • *
  • Posts: 8
  • Change this by choosing profile
Re:BUG: cannot import m3u playlist from network locations
« Reply #1 on: May 12, 2004, 07:27:27 pm »

Check your playlist with notepad (right click-open with-notepad)
if the drive letter is displayed in the playlist then it won't point to the correct source
I have a H120 mp3 player and have to remove the drive letter it comes up with when I create playlist
i.e.
e:\music\artist\song.mp3
is changed to
\music\artist\song.mp3
As long as your playlist is stored in the correct location i.e. at the root level and the library are exactly the same, this should work.
Logged

Tolga

  • Regular Member
  • Galactic Citizen
  • ****
  • Posts: 438
Re:BUG: cannot import m3u playlist from network locations
« Reply #2 on: May 12, 2004, 07:44:31 pm »

the file names in the playlist are network names such as:
\\ComputerName\...

What do you mean with playlist is stored at the root level? I thought its location would not be important, but only the location of the files it refers.

Logged

molex

  • Regular Member
  • Recent member
  • *
  • Posts: 8
  • Change this by choosing profile
Re:BUG: cannot import m3u playlist from network locations
« Reply #3 on: May 12, 2004, 09:09:14 pm »

I think playlist can be either absolute (stores all the file path information) or relative(stores only how to get the file from that location)
ie
folder structure
C:/music/radiohead/the bends
you could place a playlist anywhere on the machine and it says
C:/music/radiohead/the bends/songname.mp3
or you could place the playlist in radiohead folder and it would say
trhe bends/songname.mp3
and you'd get the same result

But this is only a guess based on problems I've had with playlists. As long as I store them at the root level (ie not in any folders) and remove the drive letter I've not had problems with playlists.
Logged
Pages: [1]   Go Up