{"id":58,"date":"2007-01-06T05:48:38","date_gmt":"2007-01-06T03:48:38","guid":{"rendered":"http:\/\/katastrophos.net\/andre\/blog\/2007\/01\/06\/%e2%80%9cyet-another-zaurus-media-player%e2%80%9d%e2%80%a6-done-differently-phase-21-development-progress-2\/"},"modified":"2007-09-23T13:32:42","modified_gmt":"2007-09-23T11:32:42","slug":"%e2%80%9cyet-another-zaurus-media-player%e2%80%9d%e2%80%a6-done-differently-phase-21-development-progress-2","status":"publish","type":"post","link":"https:\/\/katastrophos.net\/andre\/blog\/2007\/01\/06\/%e2%80%9cyet-another-zaurus-media-player%e2%80%9d%e2%80%a6-done-differently-phase-21-development-progress-2\/","title":{"rendered":"\u00e2\u20ac\u0153Yet Another Zaurus Media Player\u00e2\u20ac\u009d\u00e2\u20ac\u00a6 done differently . (Phase 2.1: Development progress 2)"},"content":{"rendered":"

Yet another short update on the development of my still untitled<\/em> media player for the Zaurus. In the meantime it’s called YAZMP.<\/p>\n

Again, I’ve been working on improving performance – this time on the performance when loading playlists.
\nBefore I continue, let me give a brief overview of the structure:<\/p>\n

Library<\/strike> -> Playlists < -> Media Cache<\/strong><\/p>\n

YAZMP doesn’t manage a library similar to i*Tunes. Instead it solely relies on playlists. Metadata (title, artist, album, etc.) is kept in the database and will be associated to once the playlist is loaded. The reason for this is pretty simple: Scanning audio files (and media files in general) each and every time a playlist is loaded will definitely take a lot of time. So, for every file the gathered metadata will be saved in the DB. Think of it as a cache.
\n
\nZPlayer<\/a>, which YAZMP is based on, follows a similar approach. However, in my opinion it’s ill-conceived in the current version. It keeps the media cache in memory all the time. With lots of files this can get very expensive. Also, ZPlayer isn’t very efficient at saving the media cache to disk. It does so for the whole cache, not just changed entries. Furthermore, when saving the cache on quitting, ZPlayer sometimes simply truncates the cache file and all metadata is lost. So, next time you open it, it has to scan all files again…
\nPerhaps I’m nitpicking, perhaps I’m an optimization dork, whatever it is, please forgive my harsh words for the otherwise excellent work atty and Atmark have done in ZPlayer!<\/p>\n

Technical ramblings<\/strong><\/p>\n

For YAZMP I rewrote the metadata cache management from scratch and extended it to do a lot more.
\nAs I already mentioned above, YAZMP doesn’t manage any library, it only knows about filenames in playlist files.
\nFor that to work correctly and efficient especially in combination with the media cache, there are four cases that need to be taken care of:<\/p>\n

    \n
  1. A new file has been added to the playlist which doesn’t exist in the media cache.<\/strong>
    \nThis case is very simple: The player has to scan the file no matter what.<\/li>\n
  2. A file has been physically removed and it’s metadata is still in the cache.<\/strong>
    \nIn this case the player has junk entries in its database, which need to be cleaned once in a while.<\/li>\n
  3. A file has been renamed, that is, it’s basename changed<\/strong><\/li>\n
  4. A file or a whole directory \/ sub-tree of files have moved to another location.<\/strong>
    \nIn a naive implementation both cases would trigger a lengthy rescan of the file(s) that are about to be added in the playlist, because new location can’t be associated with any data in the cache.
    \nFor YAZMP I’ll use several approaches + fallbacks to try to limit the impact. The following messy pseudo-code illustrates this:<\/p>\n
    \r\n  get attributes<\/strong> filename<\/em>, directory<\/em>  from current playlist item to be added<\/strong>\r\n  get attributes<\/strong> filesize<\/em>, lastmoddate<\/em> for file<\/strong> (directory<\/em> + filename<\/em>)\r\n\r\n  \/\/ NOTE: check via checksum \/ hash for faster lookup<\/font>\r\n  if exactly one<\/strong> entry by hash value of<\/strong> (directory<\/em> + filename<\/em>) in DB then<\/strong>\r\n    \/\/ NOTE: did the file change since the last scan?<\/font>\r\n    if<\/strong> entry.filesize not equal<\/strong> filesize<\/em> or<\/strong> entry.lastmoddate not equal<\/strong> lastmoddate<\/em> in FS then<\/strong>\r\n      rescan file<\/strong> (directory<\/em> + filename<\/em>) and update<\/strong> entry in DB<\/strong>\r\n    return<\/strong> entry\r\n  else if exactly one<\/strong> entry by tuple of<\/strong> (filename<\/em>, filesize<\/em>, lastmoddate<\/em>) in DB then<\/strong>\r\n    \/\/ Was the file moved to a new directory? (case 4)\r\n    \/\/ If so, check for other files in the old directory and change them\r\n    \/\/ to the new location...\r\n    \/\/ NOTE: this is purely predictive. It might not always yield a benefit.<\/font>\r\n    if directory by value of<\/strong> entry.location not in FS then<\/strong>\r\n      change every<\/strong> siblingentry in DB where<\/strong> siblingentry.location is<\/strong> entry.location\r\n        set<\/strong> siblingentry.location to directory<\/em>\r\n        set<\/strong> siblingentry.locationHash to hash value of<\/strong> (directory<\/em> + siblingentry.filename)\r\n      until no<\/strong> siblingentry is left<\/strong>\r\n    \/\/ NOTE: did the file change since the last scan?<\/font>\r\n    if<\/strong> entry.filesize not equal<\/strong> filesize<\/em> or<\/strong> entry.lastmoddate not equal<\/strong> lastmoddate<\/em> in FS then<\/strong>\r\n      rescan file<\/strong> (directory<\/em> + filename<\/em>) and update<\/strong> entry in DB<\/strong>\r\n    return<\/strong> entry\r\n  \/\/ NOTE: For case 3 one could check for a smaller tuple of (filesize, lastmoddate)<\/font>\r\n  \/\/ which would result in the almost the same code as above<\/font>\r\n  \/\/ The likeness of wrong results is a lot higher though.<\/font>\r\n  else<\/strong>\r\n    scan file<\/strong> (directory<\/em> + filename<\/em>) as<\/strong> newentry and add<\/strong> newentry to DB<\/strong>\r\n    return<\/strong> newentry\r\n<\/pre>\n<\/li>\n<\/ol>\n
    Conclusion<\/strong><\/p>\n
    What that means is pretty simple: You can move your media files to a different location, perhaps a SD-Card, and the player will still be able to associate the new location in the playlist file with the data it has in cache. And that means: No useless scanning of files and fast playlist load times.<\/p>\n
    Yet another feature…<\/strong><\/p>\n
    I tend to copy several albums to my Zaurus for listening on the road. So, once I’ve copied new stuff, it’s always the same mindless and inconvenient procedure in most players: Clear the playlist, add files or directories, play stuff.
    \nAnd that brings me straight to another new feature: Dynamic Playlists
    \nIn general the idea is pretty simple: Instead of just listing every file’s location in a playlist file, one may also list folders that are automatically scanned for audio or video files. Here is an example:<\/p>\n
    Music.dynplaylist<\/p>\n
    \r\n\/hdd3\/Music\/test1.mp3\r\n\/mnt\/card\/Music\/Mozart\/\r\n\/hdd3\/Music\/Beethoven\/**\r\n<\/pre>\n
    This will add a single file “test1.mp3”, all files in “\/mnt\/card\/Music\/Mozart\/” and all files in “\/hdd3\/Music\/Beethoven\/” including all files in its sub-directories.<\/p>\n
    Conclusion<\/strong><\/p>\n
    Instead of adding files, you just define what the layout of the playlist should look like and the player does the rest automatically. It can even rescan for changes. It’s all wrapped up in a nice UI.
    \nCombined with the flexibility of the metadata cache and the fact that one isn’t forced into this library thing, I think this makes for a pretty unique solution. What do you think?<\/p>\n","protected":false},"excerpt":{"rendered":"
    Yet another short update on the development of my still untitled media player for the Zaurus. In the meantime it’s called YAZMP. Again, I’ve been working on improving performance – this time on the performance when loading playlists. Before I continue, let me give a brief overview of the structure: Library -> Playlists < -> […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[20,4,11,24,15,6],"class_list":["post-58","post","type-post","status-publish","format-standard","hentry","tag-development","tag-gadgets","tag-linux","tag-quasar","tag-random","tag-zaurus"],"_links":{"self":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts\/58"}],"collection":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/comments?post=58"}],"version-history":[{"count":0,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/posts\/58\/revisions"}],"wp:attachment":[{"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/media?parent=58"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/categories?post=58"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/katastrophos.net\/andre\/blog\/wp-json\/wp\/v2\/tags?post=58"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}