+- 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
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-02-24
@yannickrose: Added to the list of supported media types.
@gizmotoy:
If you have 'Growl' installed, it should post messages as notifications rather then process stopping dialogs, depending on the messages you're getting, it's better if people know something went wrong during the process rather than remaining ignorant of possible missing parts.
Since it crashes during the writing of metadata, I think it has something to do with the process I use to get mediafile information through 'mediainfo', looking at the filesize of your movie, I guess it's somekind of bluray rip? Maybe you could show me the folder structure?
@villieb:
Are there any messages that show up about the crash? or is it just the spinning beach ball?
If the movie is actually on a network drive, it might be because 'deleting' a movie actually moves it to the trash, and for some reason it'll try to move the movie over the network to your local trash file, which would take some waiting time causing the spinning ball.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - gizmotoy - 2013-02-25
(2013-02-24, 22:54)MariusTh86 Wrote: @gizmotoy:
If you have 'Growl' installed, it should post messages as notifications rather then process stopping dialogs, depending on the messages you're getting, it's better if people know something went wrong during the process rather than remaining ignorant of possible missing parts.
Since it crashes during the writing of metadata, I think it has something to do with the process I use to get mediafile information through 'mediainfo', looking at the filesize of your movie, I guess it's somekind of bluray rip? Maybe you could show me the folder structure?
Fair enough. In my case, subjectively it appears that it happens most often when trying to get recomendations, but it's hard to say for sure. (Edit: Growl for $4 is kind of crazy given it just replicates a feature in 10.8, but it works perfectly, thanks!).
From the above, it seems like you're using this library to pull the media information, is that right? The executable budled in your application contents seems to suggest so (also FYI, there's a newer version available). http://mediainfo.sourceforge.net/en/Download/Mac_OS
If so, I have some information regarding the audio codec stuff. I looked at several of my movies for the 'mediainfo' output, and I think I see where the problem resides, and was hoping you could take a look. According to their forums, Mediainfo's author says you need to use the Format field in tandem with the Profile field in order to get accurate codec output.
Movie #1, Track #1: "Format: TrueHD" = Correctly ecognized as "TrueHD" by VMM
Movie #2, Track #1: "Format: TrueHD / AC-3" = Recognized as "AC-3" by VMM, should preferably be "TrueHD"
Movie #3, Track #1: "Format: DTS" "Profile: MA / Core" = Recognized as "DTS" by VMM, should preferably be "DTS-HD MA" or "DTS MA"
Movie #4, Track #1: "Format: DTS", No Profile field = Correctly recognized as "DTS" by VMM
Movie #5, Track #1: "Format: AC-3" = Correctly recognized as "AC-3" by VMM
For the crashing item, I did rip it from a Blu Ray. However, I rip to .mkvs, so there's essentially just the one file in the folder if all the metadata is deleted. I tried deleting everything again, renamed the file to a simple unrelated word, and then attempted the Manual Search again. This time it completed. It happened again on another movie, and completed fine once I deleted the .nfo. It seems like it must be encountering something in the .nfo file that causes it to crash. The next time it happens I'll save the .nfo file.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-02-25
I still need to get around to putting in OS X 10.8 notification support.
Since the last post, i've updated mediainfo, thanks for notifying me, and yup, that's the one I use. ^^
Could you see what the '<codec>' tag says on those files? if that one's more correct, i might switch to that.
I'll be pretty interested in that .nfo file.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - yannickrose - 2013-02-25
Thank's Vidal !
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - gizmotoy - 2013-02-26
(2013-02-25, 11:13)MariusTh86 Wrote: I still need to get around to putting in OS X 10.8 notification support.
Since the last post, i've updated mediainfo, thanks for notifying me, and yup, that's the one I use. ^^
Could you see what the '<codec>' tag says on those files? if that one's more correct, i might switch to that.
I'll be pretty interested in that .nfo file.
I tried a couple of the files, sometimes the codec field is semi-relevant (DTS and DTS-HD both return a codec of "A_DTS"), other times it is useless (TrueHD has simple "131" in the codec field). It looks like the only way that's completely useful is a combination of format and profile. I think it'd be straightforward to handle, though. If result of the format field contains TrueHD, output TrueHD. If the format is DTS, additionally check the profile field for "MA". A little annoying, but not too bad.
I had another one of the crashes, and saved off the .nfo file. Again, deleting the .nfo file and rerunning the update resolved the issue. This one is somewhat vexing, though, as I had previously run the update on this movie several times in the past day. Since the update always processes movies in title order, I've been through #s and A-C four or five times. Possible theory: my movies are on a huge external array. If the drive the movie is on is asleep, there's a good 3-4 second delay while the drive spins up and starts passing the file over the network. Maybe something is timing out? Here's the .nfo just in case:
http://pastebin.com/mAB4wjL2
One other note: If I mark any movie as watched using Command-T, if I update that movie or change any of its extras, the movie loses its watched status. So every time I try to Update->All I have to manually go movie by movie and mark everything as watched again
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - giwwi - 2013-02-26
Hello everyone!
I am trying to add my folder with movies located in time capsule and receives error: Out of bounds error: 0 stack. I can access Time Capsule in Finder via smb and afp. Can you help me?
http://pastebin.com/3HLEXYze
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-02-26
@Gizmotoy: Actually, placing "DTS MA" in the .nfo '<codec>' field makes XBMC not recognise it. (In Metropolis & default Confluence skin, the 'dts' tag disappears, and nothing is placed instead)
So as an XBMC user, i'd rather use 'DTS' and have the tag show up then using 'DTS MA' or 'DTS-HD MA' which doesn't seem to show up at all.
It seems I was using the <Commercial_name> tag for audio codecs, but I made an exception for 'TrueHD / AC-3' to be recognised as 'TrueHD'.
I've uploaded a nightly build that should hopefully mitigate the crashing when trying to write the .nfo file text to disk, let me know how it works out.
Oops, forgot to re-add watched status when updating movies, should also be fixed in the next nightly:
http://www.mediafire.com/vimediamanager
@giwwi: The error seems to occur when right-clicking (or ctrl+clicking) a movie or empty list, correct? I think I fixed it in the latest nightly build:
http://www.mediafire.com/vimediamanager
Let me know if it still happens.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - gizmotoy - 2013-02-26
(2013-02-26, 14:02)MariusTh86 Wrote: @Gizmotoy: Actually, placing "DTS MA" in the .nfo '<codec>' field makes XBMC not recognise it. (In Metropolis & default Confluence skin, the 'dts' tag disappears, and nothing is placed instead)
So as an XBMC user, i'd rather use 'DTS' and have the tag show up then using 'DTS MA' or 'DTS-HD MA' which doesn't seem to show up at all.
It seems I was using the <Commercial_name> tag for audio codecs, but I made an exception for 'TrueHD / AC-3' to be recognised as 'TrueHD'.
I've uploaded a nightly build that should hopefully mitigate the crashing when trying to write the .nfo file text to disk, let me know how it works out.
Oops, forgot to re-add watched status when updating movies, should also be fixed in the next nightly:
http://www.mediafire.com/vimediamanager
Hmm. I didn't even realize codec information went into the .nfo file. I think my old .nfo files from Ember has been tricking me into thinking that this was fine in VMM. I'll check it tonight. In reality, I had mainly been referring to what I'd like to see go in the $A file renaming pattern.
That said, if you'd like to make the <codec> tag work properly, it has to be formatted per the XBMC specs, which are here:
http://wiki.xbmc.org/index.php?title=InfoLabels (Check out ListItem.AudioCodec)
DTS HD MA = "dtshd_ma"
TrueHD = "truehd"
Those would be fine as the $A return for file naming in my opinion, as well.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - giwwi - 2013-02-26
(2013-02-26, 14:02)MariusTh86 Wrote: @giwwi: The error seems to occur when right-clicking (or ctrl+clicking) a movie or empty list, correct? I think I fixed it in the latest nightly build:
http://www.mediafire.com/vimediamanager
Let me know if it still happens.
Thanks for support. The error is solved in nightly build, but I still can't access to Time Capsule folders. I can see and choose all of them from browse window, but after that nothing happened. The list of films/tvshows is empty(
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-02-26
you might have to press the 'refresh list' button in the toolbar
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - giwwi - 2013-02-26
(2013-02-26, 20:47)MariusTh86 Wrote: you might have to press the 'refresh list' button in the toolbarI tried, but without result.
My actual path to the folder is afp://Capsule/Home/Movies (or smb://...). When I add it to MediaManager it changes to /Volume/Home/Movies. If I close preferences and enter it again I observe the new location: /home/Movies. I tried to add location manually, but without any result also.
Maybe the problem is that the access to Time Capsule secured by password (I didn't find any solution to get guest access to it) and MediaManager can't recognize it. But on the other way I can choose all folders in browse window(
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-02-26
Hmm, I believed ViMM to work with any mounted volume, though that it changes /volume/home to just /home is very odd.
I'll make some changes to the way paths are stored, maybe it'll help.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - giwwi - 2013-02-26
I tried to change path manually to /Volume/Home/Movies, but after updating the list I receive:
/Users/alekseyvoloschuk/Downloads/:Volume:Home:Movies
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-02-27
Alright, I hope I got all the path setters & getters, let me know if this build works better:
http://www.mediafire.com/?tafv3tcwf3xjnuu
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - gizmotoy - 2013-02-27
(2013-02-26, 14:02)MariusTh86 Wrote: @Gizmotoy:
I've uploaded a nightly build that should hopefully mitigate the crashing when trying to write the .nfo file text to disk, let me know how it works out.
Definite improvement. In unattended operation, it got further than it ever has before. I made it into the 'H's before it crashed. It produced the following. I tried clicking continue, but the process locked up and I had to force quit. If there's anything I can do to help debug, let me know.
http://imgur.com/ZV8Kn0C
Code:
Nil object exception ERROR: 0
Stack:
RaiseExceptionClass
RaiseNilObjectException
ViMMCore.FindTrailerItem%o<FolderItem>%o<FolderItem>
MovieSckt.GetMovieNFO%%o<MovieSckt>sb
MovieCore.MovieByID%%sb
MovieCore.MovieUpdateAll
dlgProgress.dlgProgress.thrProgress_Run%%o<dlgProgress.dlgProgress>o<Thread>
Delegate.IM_Invoke%%o<Thread>
AddHandler.Stub.0%%
threadRun
CooperativeThread