+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: Supplementary Tools for Kodi (https://forum.kodi.tv/forumdisplay.php?fid=116)
+--- Thread: OS X ViMediaManager - Media Manager for Mac OS X! (/showthread.php?tid=109976)
Pages:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
- MariusTh86 - 2011-09-22
The preferences would be in HDD/users/yourname/library/preferences.
Maybe you can try reconnecting the disk before restarting ViMM, and make sure it's accessible from the finder, and possibly re-add it.
- smilenkovski - 2011-09-22
Nice update. Thanks.
- morikaweb - 2011-09-23
I'm eager to give this a go. Just want to know though, is it stable enough to use on a live library? Or would you suggest I just play with a temp libary for now?
- demosthien - 2011-09-23
morikaweb Wrote:I'm eager to give this a go. Just want to know though, is it stable enough to use on a live library? Or would you suggest I just play with a temp libary for now?
I've been using it on my live library & the only adverse effect I've had is an occasional "Search All *.jpg, *.nfo etc" action so I can delete the images and nfo files and start over again. Or an occasional incorrect identification which can be fixed with a manual search.
ViMM hasn't had any bad effects on my files and I don't think it actually does anything to your videos (aside from scan them) anyway.
- demosthien - 2011-09-23
@marius
I have just been playing with images and found that after ViMM had downloaded a series of images if I went into XBMC and used the "TV Logo Script" in the context menu there were multiples of certain images in some folders. In each case there was a capitalisation difference. eg: Poster.jpg & poster.jpg sat happily together in the same folder and were different pictures.
It's late here so I haven't yet followed this further to see if it caused any conflict/issues in XBMC. Maybe someone else could test it out further?
- demosthien - 2011-09-23
demosthien Wrote:@marius
I have just been playing with images and found that after ViMM had downloaded a series of images if I went into XBMC and used the "TV Logo Script" in the context menu there were multiples of certain images in some folders. In each case there was a capitalisation difference. eg: Poster.jpg & poster.jpg sat happily together in the same folder and were different pictures.
It's late here so I haven't yet followed this further to see if it caused any conflict/issues in XBMC. Maybe someone else could test it out further?
Quick follow up... XBMC displays the files with lower case letters in preference to the files with a first capital letter. I think ViMM names files with the first letter as a capital so they're not being seen after that script gets run.
- antah - 2011-09-23
MariusTh86 Wrote:The preferences would be in HDD/users/yourname/library/preferences.
Found, no problems. Thanks. In lion this folder is hidden, that's why.
MariusTh86 Wrote:Maybe you can try reconnecting the disk before restarting ViMM, and make sure it's accessible from the finder, and possibly re-add it.
Strange, but this doesn't help. Even rebooting, then connecting the disk (i even tried to play movie from finder first) and then starting ViMM - doesn't work at all. When I started ViMM first time - there were no problems at all. And.. even when I deleted this com. file and started all over again - nothing happened. Any ideas? Thanks!
- MariusTh86 - 2011-09-23
demosthien Wrote:@marius
I have just been playing with images and found that after ViMM had downloaded a series of images if I went into XBMC and used the "TV Logo Script" in the context menu there were multiples of certain images in some folders. In each case there was a capitalisation difference. eg: Poster.jpg & poster.jpg sat happily together in the same folder and were different pictures.
It's late here so I haven't yet followed this further to see if it caused any conflict/issues in XBMC. Maybe someone else could test it out further?
If the only difference is capitalization, you might have your hard drive formatted in a case-sensitive format which allows both to coexist together, otherwise it should have registered as the same file.
To fit it, maybe I should go around and change all the image names to lower characters?
- pecinko - 2011-09-23
MariusTh86 Wrote:To fit it, maybe I should go around and change all the image names to lower characters?
Maybe you should consider it as Linux is case sensitive. (You can manage library on MAC, but you can have linux based HTPC).
- MariusTh86 - 2011-09-23
antah Wrote:Strange, but this doesn't help. Even rebooting, then connecting the disk (i even tried to play movie from finder first) and then starting ViMM - doesn't work at all. When I started ViMM first time - there were no problems at all. And.. even when I deleted this com. file and started all over again - nothing happened. Any ideas? Thanks!
Very strange indeed... are you using the latest beta 13?
You can download it from here if you're not: https://github.com/vidalvanbergen/ViMediaManager/downloads
- Tiny Clanger - 2011-09-23
MariusTh86 Wrote:If the only difference is capitalization, you might have your hard drive formatted in a case-sensitive format which allows both to coexist together, otherwise it should have registered as the same file.
To fit it, maybe I should go around and change all the image names to lower characters?
Please do - those of us who are running XBMC on Linux only have case-sensitive filesystems, even if most Macs are formatted case-insensitive.
Thanks
Edit: doh, pecinko already said this. Sorry for the waste of space!
- MariusTh86 - 2011-09-23
Tiny Clanger Wrote:Please do - those of us who are running XBMC on Linux only have case-sensitive filesystems, even if most Macs are formatted case-insensitive.
Thanks
Edit: doh, pecinko already said this. Sorry for the waste of space!
No worries, and the next release should use all lowercase filenames. ^^
- antah - 2011-09-23
MariusTh86 Wrote:Very strange indeed... are you using the latest beta 13?
You can download it from here if you're not: https://github.com/vidalvanbergen/ViMediaManager/downloads
of course I do. Today will try to reboot everything and try fresh install. Will revert! have a nice weekend!
- MariusTh86 - 2011-09-23
antah Wrote:of course I do. Today will try to reboot everything and try fresh install. Will revert! have a nice weekend!
Then maybe the last time it worked was in an older beta? though I don't remember changing anything to the way it read paths in between betas...
Anyway, keep me posted! and nice weekend to you too!
- DrPepper - 2011-09-23
ok
looks like i found another bug.
i have plenty of NFS error messages , so i dug deeper into it
21:54:05 T:140695395800832 ERROR: NFS: Failed to stat(export/2tb/Series/Dark Matters Twisted but True/poster.jpg) stat call failed with "NFS: Lookup of //2tb failed with NFS3ERR_NOENT(-2)"
21:54:05 T:140695040939776 ERROR: NFS: Failed to stat(export/2tb/Series/Oz/poster.jpg) stat call failed with "NFS: Lookup of //2tb failed with NFS3ERR_NOENT(-2)"
21:54:05 T:140695395800832 ERROR: NFS: Failed to stat(export/2tb/Series/Person of Interest/poster.jpg) stat call failed with "NFS: Lookup of //2tb failed with NFS3ERR_NOENT(-2)"
21:54:05 T:140695058765568 ERROR: NFS: Failed to stat(export/2tb/Series/Ringer/poster.jpg) stat call failed with "NFS: Lookup of //2tb failed with NFS3ERR_NOENT(-2)"
21:54:05 T:140695040939776 ERROR: NFS: Failed to stat(export/2tb/Series/The Secret Circle/poster.jpg) stat call failed with "NFS: Lookup of //2tb failed with NFS3ERR_NOENT(-2)"
21:54:07 T:140695387408128 ERROR: NFS: Failed to stat(export/2tb/Series/The Closer//landscape.jpg) stat call failed with "NFS: Lookup of //2tb failed with NFS3ERR_NOENT(-2)"
This is causing the error. once i scrape with ViMedia, it gives me this error , with Ember it doesn't.
Hope it helps
Cheers
DrP