<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>
<br> <BR><div>> > Aren't the playlists saved to the database? It would seem that when <br>> > you save a playlist (either new or to existing), it should be written <br>> > to the database and that should be the end of it, regardless of how <br>> > you exit the frontend, no?<br>> ><br>> You would think. On this, I have noticed (in 0.24 anyway, have not <br>> tested in 0.25). If you create a playlist via Mythweb (my preferred <br>> option for creating, editing playlists), you have to exit the restart <br>> mythfrontend before MythMusic will see a new playlist, or see the <br>> changes made to an existing playlist. It would seem it loads the <br>> Playlists when you first start the frontend, which seems a dumb way to <br>> do it (in my opinion anyway).<br>> <br>> Michael<br></div><div>I'd say it would *appear* to be worse than simply only loading playlists when you first start the frontend. It would *appear* (I can only go by what I am seeing) that MythMusic is essentially caching *everything* you do in a frontend session and then only actually committing it when you exit the frontend "properly" (which it's beyond me how Exit -> Yes, Exit and Reboot from within Myth itself isn't a "proper" exit). If this wasn't true, then why are changes that should have been committed at the time they were done lost unless you exit the frontend "properly"? If true, I'd also say seems a dumb way to do it IMO.</div> </div></body>
</html>