Move a playlist file to another installation

[MickeyRat 10]

I found the .m3u file for the playlist and the directory it's in and I need to use it on another box.  The directory layout is identical on both boxes and I copied the file to the right place.  However I can't get the destination instance to see the playlist.

Any suggestions would be appreciated.

[Luke 39835]

Hi, can you show us what exactly you did?

[MickeyRat 10]

2 hours ago, Luke said:

Hi, can you show us what exactly you did?

Thanks for the reply.

Actually I was able to solve it on my own.  I just now have time to reply.  I'll try to explain what worked.

Playlists are stored in /var/lib/emby/data/userplaylists/play list name [playlist]/play list name.m3u

I tried copying (rsync -av) the play list directory from the source machine to the same location on the destination machine but, I couldn't get emby to see the playlist. That's when I started this thread. Then, of course, I thought of something else to try.

Here's what worked.

1. On the destination machine I added one song to a new play list with the name of the play list I was copying. So Emby shows a play list with one song in it.
2. Copied the play list from the source machine over the new play list on the destination machine. Emby still showed a play list with one song in it.
3. Performed a refresh metadata on the play list on the destination machine.

That did it. I'm not sure it had any effect but, I did restart the Emby server a couple times while I was doing this.

There might be an easier way to do it but, this is what worked for me.

Edited April 25 by MickeyRat

[Luke 39835]

Quote

I tried copying (rsync -av) the play list directory from the source machine to the same location on the destination machine but, I couldn't get emby to see the playlist.

This is because each playlist under userplaylists is assigned to a user internally when the playlist gets created. If you just copy a playlist file into there, the library scan will find it but you won't be able to see it due to it not being associated with a user.

Thanks for following up.