Ok, I've been wrong: Actually saving playlists works for me: Just the save-playlist-dialog sucks: It has the "Cancel" button on the right side and the "Create" button on the left side - so I clicked "Cancel" all the time.
Perhaps we are lucky and you made the same error ;). Please post console output (if any) otherwise.
I can't open the save playlist dialog. The console output say:
Traceback (most recent call last):
File "/usr/share/apps/pyjama/modules/clWindow.py", line 977, in
on_bSave_clicked
self.main.playlists.cb_save_playlist(None)
File "/usr/share/apps/pyjama/extended_modules/clPlaylists.py", line
234, in cb_save_playlist
dialog = clPlaylistDialog.SaveDialog(self)
File "/usr/share/apps/pyjama/extended_modules/clPlaylistDialog.py",
line 288, in __init__
if len(playlists)>0:
UnboundLocalError: local variable 'playlists' referenced before assignment
Thanks,
Pedro
Daniel Nögel escribió:
> Ok, I've been wrong: Actually saving playlists works for me: Just the
> save-playlist-dialog sucks: It has the "Cancel" button on the right side
> and the "Create" button on the left side - so I clicked "Cancel" all the
> time.
>
> Perhaps we are lucky and you made the same error ;). Please post console
> output (if any) otherwise.
>
> Sincerely,
>
> Daniel
>
Hi,
I also had this issue with the release version 0.3.0.1 but on branch rev. 265 it works well for me, I can save and load playlists.
>Just the save-playlist-dialog sucks
Yep, I don't know where they are saved and you can't change the folder.
sincerely,
mesrumma
When clicking on "save playlist" a window will pop up asking you for a name. After entering that and pressing "ok", pyjama will save the playlist in its database. So "saving playlist" just saves it for pyjama.
What you want to do is to *export* a playlist. This function is available in the menu "Playlists->Export Playlist". There is even a "Save to..." dialog, so you can in fact change the folder.
Short answer: Saving=Just for use in pyjama // Exporting=Making the playlist available as an m3u-file.
Hi Peloteos,
thanks for reporting this issue; its the same here in the current development version - so I'll have a look at it.
You'll be notified when this bug has been fixed.
Sincerely,
Daniel