1 |
On Tuesday, 29 January 2019 02:55:02 GMT Dale wrote: |
2 |
> Andrew Udvare wrote: |
3 |
> >> On 2019-01-28, at 17:54, Dale <rdalek1967@×××××.com> wrote: |
4 |
> >> |
5 |
> >> So far, I have installed Griffith and GCStar. I been googling for |
6 |
> >> others but some either are not in the tree or I already know they won't |
7 |
> >> do one thing I'd like to see. I'd also like to be able to point it to a |
8 |
> >> directory and let it build the database on its own. Adding them one at |
9 |
> >> a time manually just isn't feasible at all. |
10 |
> > |
11 |
> > Seems like you could import via command line? |
12 |
> > http://wiki.gcstar.org/en/execution |
13 |
> > |
14 |
> > You can build the database you need locally with something like exiftool |
15 |
> > or MediaInfo, or even ffmpeg https://stackoverflow.com/a/8191228/374110 . |
16 |
> > I highly doubt anyone with serious collections is building their database |
17 |
> > one item at a time.> |
18 |
> >> Does anyone know of a software package that will sort a lot of videos by |
19 |
> >> resolution as well as track other things as well? It could be that what |
20 |
> >> I'd like to have doesn't exist at all. Then again, maybe I just haven't |
21 |
> >> found it yet. ;-) |
22 |
> > |
23 |
> > The closest thing I can think of is Kodi since it's scanner will retrieve |
24 |
> > all this information and store it in a straightforward database format. |
25 |
> > You can choose SQLite or MySQL (of course MySQL is definitely the better |
26 |
> > choice for larger collections). The downside is the scanner is very slow, |
27 |
> > especially over a network (and not optimised). The only viewer for this |
28 |
> > data (at the time being) is Kodi itself. |
29 |
> Not ignoring. Just pondering this one. May take some time for me to |
30 |
> test some stuff here. ;-) |
31 |
> |
32 |
> Thanks much. |
33 |
> |
34 |
> Dale |
35 |
> |
36 |
> :-) :-) |
37 |
|
38 |
Installing and having to maintain Kodi just to manage a list of videos is |
39 |
probably inefficient - unless you have a regular use for other Kodi |
40 |
functionality. I use it mostly for audio and also the odd video. It has |
41 |
loads of useful plugins to play with. |
42 |
|
43 |
If Kodi is of no use, or you prefer a more portable stand alone CLI solution, |
44 |
you could look into some basic bash scripts. I couldn't code my way out of a |
45 |
paper bag, but here's two basic ideas to get you started. First to list all |
46 |
the videos into a csv file: |
47 |
|
48 |
find . -xtype f -iname '*.mp4' -o -iname '*.avi' -o -iname '*.mkv' > |
49 |
video_list.csv |
50 |
|
51 |
You may have to add other types of video file containers depending on your |
52 |
video collection. As a second step, in order to list all the video |
53 |
resolutions you could pass the find output to xargs: |
54 |
|
55 |
find . -xtype f -iname '*.mp4' -o -iname '*.avi' -o -iname '*.mkv' | tee |
56 |
video_list.csv | xargs -d '\n' exiftool -T -ImageSize |
57 |
|
58 |
Given my non-existent coding skills I am not sure how to append the output of |
59 |
xargs as a second column to the video_list.csv, which you could thereafter |
60 |
open with localc to do your searches, or manipulate further. Of course, |
61 |
localc is not necessary. You can always use less or grep to search the csv |
62 |
file very efficiently and also re-create it quickly when you add/delete to |
63 |
your videos. |
64 |
|
65 |
Other more knowledgeable contributors should be able to polish and complete |
66 |
the above, or indeed propose something different than bash (python?) to |
67 |
perform the same task. |
68 |
|
69 |
HTH. |
70 |
-- |
71 |
Regards, |
72 |
Mick |