Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/17/15 in all areas

  1. Seeing the same thing as @awakening. It appears somewhere along the way the identify a movie based on the folder name instead of the file within the folder determined the name of the movie changed. I recently had to start from scratch with Media Browser (my issue not Media Browsers), however, I had about 100 movies where the files names were Year - movie name.* but the folders were clearly identified with the movie "name (year)". This had never been an issue until I re-installed Media Browser. Personally, I've corrected the issue manually but fixing all those "Year - Movie name" files within the same folder. However, for new MB3 users this could lead to a very frustrating first experience with this awesome application.
    1 point
  2. Well, metadata that was stored in MB XML or NFO files in the same folders as the video files wouldn't be destroyed, but it's not picked up until you manually set the content type for each folder (instead of being determined by the metadata files). If "unset" would at least check for the MB XML files and decide based on the filename what the folder should be, this might not have been such a SNAFU.
    1 point
  3. The switch to "unset" caused me a whole bunch of data loss when trying the new beta. Fortunately reverting to the current stable version got back all the metadata I had to manually enter for a number of movies and anime series, but none of it is being emitted into the MB XML files. On top of that, reverting caused me to be unable to administer my MB install until I deleted the users.db file in appdata (making me have to recreate all the user accounts). Before this gets promoted up to stable, you'll want to do a lot of data loss testing scenarios, I think.
    1 point
×
×
  • Create New...