I think you're exactly right that we generally want to import based high-level types like 'video', 'audio', 'image'.
So I'll add this to the dbus API... import based on an explicit set of extensions, or based on high-level types. And then I'll update the dmedia script to talk to the dmedia session daemon over dbus.
Right now I'm focusing on getting the import process right for importing from memory cards, where it's fairly safe to assume that files will have correct canonical file extensions. Building the list of files to consider based on file extension is super fast.
Down the road we could also support more sophisticated type detection by inspecting the file contents. Help when file extensions aren't correct or are missing, but is also much slower.
Did you want to work on any of this, David? I'm adding this to the dbus API right now, but if you wanted to add the correct args/options to the dmedia script, have at it!
Hehe... I was actually just thinking about this, and am working on it in lp:~jderose/dmedia/get-on-da-bus
I think you're exactly right that we generally want to import based high-level types like 'video', 'audio', 'image'.
So I'll add this to the dbus API... import based on an explicit set of extensions, or based on high-level types. And then I'll update the dmedia script to talk to the dmedia session daemon over dbus.
Right now I'm focusing on getting the import process right for importing from memory cards, where it's fairly safe to assume that files will have correct canonical file extensions. Building the list of files to consider based on file extension is super fast.
Down the road we could also support more sophisticated type detection by inspecting the file contents. Help when file extensions aren't correct or are missing, but is also much slower.
Did you want to work on any of this, David? I'm adding this to the dbus API right now, but if you wanted to add the correct args/options to the dmedia script, have at it!