Project

General

Profile

Actions

Feature #454

closed

Need to support auto-detect of new video databases

Added by Hammel over 6 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Urgent
Assignee:
Category:
Database
Start date:
29 Jun 2015
Due date:
% Done:

100%

Estimated time:
Severity:
03 - Medium

Description

VideoFE doesn't support handling of hot-plugged USB sticks. To support these I need to have a thread that continues scanning and updates the local db. This includes plugging in a new stick and removing an existing one. It probably makes sense for the thread to use a double-buffered db: create one and then quickly (via mutex lock) replace the current one.

Actions #1

Updated by Hammel over 6 years ago

  • Subject changed from Need to support auto-detect of new libraries to Need to support auto-detect of new video databases
Actions #2

Updated by Hammel over 5 years ago

Actually what I need is to use inotify to watch for directory changes. This is much more efficient than the scanning I'm currently doing. I just need a thread to handle the inotify events.

Actions #3

Updated by Hammel about 5 years ago

  • Target version changed from 0.11.0 to 0.12.0
Actions #4

Updated by Hammel almost 3 years ago

  • Target version changed from 0.12.0 to 1.1.0 - Upgrades
Actions #5

Updated by Hammel over 1 year ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 70

This is close to done. I've got the inotify stuff working. The problem now is how I update the poster. That gets updated when the liststore is changed. However, if the liststore is cleared then the poster remains. Also, the poster doesn't get cleared if we switch from movies to TV or back.

I have code now that does do this but it's crashing because of some memory leak. Fix that and I can call this done.

Actions #6

Updated by Hammel over 1 year ago

  • Status changed from In Progress to Closed
  • % Done changed from 70 to 100

Done. Buffer overrun in reading config file was causing crashes. Poster update is now fixed. Dynamic updates are NOT done but if a db disappears and user tries to use a removed entry the app switches to the other db, which will be updated at that point.

Tested, committed and pushed.

Closing issue.

Actions

Also available in: Atom PDF