+- 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! - rpoenaru - 2013-04-26
This is the message generated when I have to forcefully quit Vi Media Manager
Code:
Pageins: 1 pages
Pageouts: 0 pages
Process: ViMediaManager [7390]
Path: /Applications/ViMediaManager.app/Contents/MacOS/ViMediaManager
Architecture: i386
Parent: launchd [180]
UID: 501
Task size: 19719 pages
CPU Time: 0.065s
Thread 0x17cb5a priority 46 cpu time 0.065s
18 start + 43 (ViMediaManager) [0xe4d50e]
18 _start + 116 (ViMediaManager) [0xe4d5b8]
18 % main + 36 (ViMediaManager) [0x25b8]
18 _Main + 245 (ViMediaManager) [0x75c8]
18 REALbasic._RuntimeRun + 34 (ViMediaManager) [0x22d614]
18 RuntimeRun + 50 (rbframework.dylib) [0x10add02]
18 ??? (rbframework.dylib + 555088) [0x10e2850]
18 ??? (rbframework.dylib + 554148) [0x10e24a4]
18 Application._CallFunctionWithExceptionHandling%%o<Application>p + 248 (ViMediaManager) [0xe20f5]
18 Delegate.Invoke%% + 34 (ViMediaManager) [0x486b8]
18 ??? (rbframework.dylib + 554629) [0x10e2685]
18 ??? (rbframework.dylib + 544683) [0x10dffab]
18 ??? (rbframework.dylib + 545409) [0x10e0281]
18 ??? (rbframework.dylib + 546749) [0x10e07bd]
18 ??? (rbframework.dylib + 861551) [0x112d56f]
18 ??? (rbframework.dylib + 1175336) [0x1179f28]
18 ??? (rbframework.dylib + 450840) [0x10c9118]
18 ??? (rbframework.dylib + 1221794) [0x11854a2]
18 ??? (rbframework.dylib + 1221885) [0x11854fd]
18 ??? (rbframework.dylib + 1222391) [0x11856f7]
18 TrackControl + 100 (HIToolbox) [0x92ca129d]
18 HIView::ClickInternal(CGPoint const&, unsigned long, void (*)(OpaqueControlRef*, short), OpaqueEventRef*, bool) + 259 (HIToolbox) [0x92ca1223]
18 HIView::NotifyControlHit(OpaqueEventRef*, short, unsigned long) + 123 (HIToolbox) [0x92ca1063]
18 SendControlCommand(HIView*, unsigned long, unsigned long) + 64 (HIToolbox) [0x92cac4a4]
18 SendHICommandToTarget + 72 (HIToolbox) [0x92bf562d]
18 SendHICommandEvent(unsigned long, HICommand const*, unsigned long, unsigned long, unsigned char, void const*, OpaqueEventTargetRef*, OpaqueEventTargetRef*, OpaqueEventRef**) + 498 (HIToolbox) [0x92d8186a]
18 SendEventToEventTarget + 88 (HIToolbox) [0x92c1c655]
18 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 430 (HIToolbox) [0x92c08780]
18 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1343 (HIToolbox) [0x92c09394]
18 _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36 (HIToolbox) [0x92d819bb]
18 ??? (rbframework.dylib + 444314) [0x10c779a]
18 ??? (rbframework.dylib + 1219727) [0x1184c8f]
18 ??? (rbframework.dylib + 1197220) [0x117f4a4]
18 ??? (rbframework.dylib + 1036450) [0x11580a2]
18 AddHandler.Stub.15%% + 54 (ViMediaManager) [0x371992]
18 Delegate.IM_Invoke%%o<PushbuttonPro> + 110 (ViMediaManager) [0x3ab3b9]
18 wndMovieMetadata.wndMovieMetadata.btnNext_Action%%o<wndMovieMetadata.wndMovieMetadata>o<PushbuttonPro> + 1861 (ViMediaManager) [0x875138]
18 wndMovieMetadata.wndMovieMetadata.GetNFO%%o<wndMovieMetadata.wndMovieMetadata> + 28035 (ViMediaManager) [0x87d607]
18 Globals.$Reload%%o<Canvas>b + 97 (ViMediaManager) [0xab4ce9]
18 RectControl.Refresh%%o<RectControl>b + 59 (ViMediaManager) [0xf62be]
18 RuntimeControlRefresh + 76 (rbframework.dylib) [0x10f54dc]
18 ??? (rbframework.dylib + 451906) [0x10c9542]
18 ??? (rbframework.dylib + 1173572) [0x1179844]
18 ??? (rbframework.dylib + 1173063) [0x1179647]
18 EraseRect + 49 (QD) [0x94ec02d2]
18 CallRect + 48 (QD) [0x94ec0259]
18 StdRectWithPort + 239 (QD) [0x94eb5369]
18 DevRect + 327 (QD) [0x94eb5911]
18 SetupOtherDrawVars + 133 (QD) [0x94ebec66]
18 LockPortBits + 115 (QD) [0x94ea0f30]
18 QDPlatformLockPortBits + 161 (QD) [0x94ea0940]
18 CGSLockWindowBits + 60 (CoreGraphics) [0x99819eda]
18 CGSLockWindowRectBits + 358 (CoreGraphics) [0x99819d47]
18 _CGSLockWindow + 3142 (CoreGraphics) [0x9977e569]
18 _CGSSynchronizeWindowBackingStore + 131 (CoreGraphics) [0x997d1f98]
18 mach_msg_trap + 10 (libsystem_kernel.dylib) [0x963a37d2]
*15 ipc_mqueue_receive_continue + 0 (mach_kernel) [0xffffff8000213030]
*3 hndl_mach_scall + 222 (mach_kernel) [0xffffff80002cdaee]
*3 ??? (mach_kernel + 679038) [0xffffff80002a5c7e]
*3 mach_msg_overwrite_trap + 427 (mach_kernel) [0xffffff800021970b]
*3 ipc_mqueue_receive + 59 (mach_kernel) [0xffffff800021310b]
*3 thread_block_reason + 275 (mach_kernel) [0xffffff800022d9f3]
*3 ??? (mach_kernel + 187521) [0xffffff800022dc81]
*3 processor_idle + 227 (mach_kernel) [0xffffff800022f1c3]
*3 machine_idle + 282 (mach_kernel) [0xffffff80002b901a]
Thread 0x17cb6f DispatchQueue 1701273966 priority 48
18 _dispatch_mgr_thread + 53 (libdispatch.dylib) [0x90a387a9]
18 kevent + 10 (libsystem_kernel.dylib) [0x963a69ae]
*18 ??? (mach_kernel + 3467664) [0xffffff800054e990]
Thread 0x17cb8c priority 53
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 6251948) [0x98ff25ac]
18 TSWaitOnSemaphoreRelative + 24 (CarbonCore) [0x9857c40d]
18 TSWaitOnSemaphoreCommon + 272 (CarbonCore) [0x9857c184]
18 TSWaitOnConditionTimedRelative + 177 (CarbonCore) [0x9857c6ad]
18 pthread_cond_timedwait_relative_np + 47 (libsystem_c.dylib) [0x939a0572]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb98 priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb99 priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb9a priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb9b priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb9c priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb9d priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cb9e priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 ??? (QuickTimeComponents + 7394646) [0x99109556]
18 pthread_cond_wait + 48 (libsystem_c.dylib) [0x93a2daf0]
18 __psynch_cvwait + 10 (libsystem_kernel.dylib) [0x963a58e2]
*18 psynch_cvcontinue + 0 (mach_kernel) [0xffffff80005b4b40]
Thread 0x17cc00 priority 62
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 __NSThread__main__ + 1396 (Foundation) [0x9295474b]
18 -[NSThread main] + 45 (Foundation) [0x929547c8]
18 +[NSURLConnection(Loader) _resourceLoadLoop:] + 395 (Foundation) [0x928f063a]
18 CFRunLoopRunInMode + 123 (CoreFoundation) [0x936abe9b]
18 CFRunLoopRunSpecific + 378 (CoreFoundation) [0x936ac02a]
18 __CFRunLoopRun + 1247 (CoreFoundation) [0x936ac96f]
18 __CFRunLoopServiceMachPort + 185 (CoreFoundation) [0x936a6f89]
18 mach_msg_trap + 10 (libsystem_kernel.dylib) [0x963a37d2]
*18 ipc_mqueue_receive_continue + 0 (mach_kernel) [0xffffff8000213030]
Thread 0x17cc0a priority 46
18 thread_start + 34 (libsystem_c.dylib) [0x93985d4e]
18 _pthread_start + 344 (libsystem_c.dylib) [0x9399b5b7]
18 __select + 10 (libsystem_kernel.dylib) [0x963a5be6]
*18 ??? (mach_kernel + 3576624) [0xffffff8000569330]
Binary Images:
0x1000 - 0xed685c com.vidalvanbergen.vimediamanager-alpha v0.7α7 (0.7.0.1.7) <21EFD05A-0FB2-356A-9814-79D8BCCFF531> /Applications/ViMediaManager.app/Contents/MacOS/ViMediaManager
0x105b000 - 0x11bbff6 rbframework.dylib <9E9655DF-38F6-3372-A26E-1329EDD16AAF> /Applications/ViMediaManager.app/Contents/Frameworks/rbframework.dylib
0x90a34000 - 0x90a46ff7 libdispatch.dylib <86EF7D45-2D97-3465-A449-95038AE5DABA> /usr/lib/system/libdispatch.dylib
0x928b6000 - 0x92bd4ff3 com.apple.Foundation 6.8 (945.16) <C4D95341-B4FF-30AC-815A-A23C019C57A3> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92bd5000 - 0x92fb8fff com.apple.HIToolbox 2.0 <ECC3F04F-C4B7-35BF-B10E-183B749DAB92> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox
0x93675000 - 0x9385dffb com.apple.CoreFoundation 6.8 (744.18) <68AFEE40-0078-347E-9DEE-32CFE0062A10> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x93985000 - 0x93a42feb libsystem_c.dylib <6E35A83F-1A5B-3AF9-8C6D-D7B57B25FB63> /usr/lib/system/libsystem_c.dylib
0x94e6f000 - 0x94f0fff7 com.apple.QD 3.42 <1B8307C6-AFA8-312E-BA5B-679070EF2CA1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD
0x96391000 - 0x963abffc libsystem_kernel.dylib <70C520E8-0394-3DFB-823B-FE8C251C169A> /usr/lib/system/libsystem_kernel.dylib
0x984b9000 - 0x987beff7 com.apple.CoreServices.CarbonCore 1037.5 (1037.5) <356AE2DF-ABB0-319C-8B5B-2F33D693889F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore
0x989fc000 - 0x99734fff com.apple.QuickTimeComponents.component 7.7.1 (2599.24) <51BE2DF8-7B3B-36F5-8860-50071A8702E4> /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTimeComponents
0x99735000 - 0x99b77ff3 com.apple.CoreGraphics 1.600.0 <BC041647-FB5A-3D07-A253-F3D34E25BF6C> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics
*0xffffff8000200000 - 0xffffff8000734d7c mach_kernel <3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6> /mach_kernelRE: [MAC] ViMediaManager - Media Manager for Mac OS X! - rpoenaru - 2013-04-26
Rebooting the NAS and the desktop did not help. Trying to create a new library either. And it only happens with movies
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - jacox - 2013-04-26
There are no error messages. Just crashes out. I'll try and get a log.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - SevenNine - 2013-04-26
(2013-04-14, 05:48)SevenNine Wrote:(2013-04-14, 04:52)ammace Wrote: I've just realized, in XBMC, none of the clearart or logo images that ViMM has downloaded are showing up.
All of them are downloaded and in the folder, but unless I refresh the tv show from the internet within XBMC (which defeats the entire purpose) they won't show up in any OSD with any theme.
Do you know any way to fix this?
Pretty sure same issue here.
Did we ever find a fix for this? None of my clearart or logo are appearing in xbmc that ViMM downloaded?
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - SevenNine - 2013-04-26
(2013-04-26, 06:32)SevenNine Wrote:(2013-04-14, 05:48)SevenNine Wrote:(2013-04-14, 04:52)ammace Wrote: I've just realized, in XBMC, none of the clearart or logo images that ViMM has downloaded are showing up.
All of them are downloaded and in the folder, but unless I refresh the tv show from the internet within XBMC (which defeats the entire purpose) they won't show up in any OSD with any theme.
Do you know any way to fix this?
Pretty sure same issue here.
Did we ever find a fix for this? None of my clearart or logo are appearing in xbmc that ViMM downloaded?
Looks like this may have something to do with it: http://forum.xbmc.org/showthread.php?tid=154680
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-04-26
@rpoenaru: From what I understand in the crash log, these where your last actions:
You opened up the metadata editor, no crash yet.
Then you pressed the 'next' button in the metadata editor, and BOOM, crash!
something along those lines?
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - rpoenaru - 2013-04-26
Hi @MariusTh86
That is correct. I can open the metadata editor, but then whatever action I choose it becomes unresponsive and I need to force quit out of it.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - Glorious1 - 2013-04-26
(2013-04-26, 06:53)SevenNine Wrote:(2013-04-26, 06:32)SevenNine Wrote:(2013-04-14, 05:48)SevenNine Wrote: Pretty sure same issue here.
Did we ever find a fix for this? None of my clearart or logo are appearing in xbmc that ViMM downloaded?
Looks like this may have something to do with it: http://forum.xbmc.org/showthread.php?tid=154680
Yeah, this is not a ViMM issue. It has to do with the complex and kooky way that XBMC handles artwork. Why you need an "Artwork Downloader" to recognize and use art that is already sitting there in the folder is beyond me. XBMC will recognize fanart and poster without any incantations or helper programs, but things like disc art and logo don't work that way.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - SevenNine - 2013-04-26
(2013-04-26, 14:09)Glorious1 Wrote:(2013-04-26, 06:53)SevenNine Wrote:(2013-04-26, 06:32)SevenNine Wrote: Did we ever find a fix for this? None of my clearart or logo are appearing in xbmc that ViMM downloaded?
Looks like this may have something to do with it: http://forum.xbmc.org/showthread.php?tid=154680
Yeah, this is not a ViMM issue. It has to do with the complex and kooky way that XBMC handles artwork. Why you need an "Artwork Downloader" to recognize and use art that is already sitting there in the folder is beyond me. XBMC will recognize fanart and poster without any incantations or helper programs, but things like disc art and logo don't work that way.
I tend to agree. This was definitely it. Seem to be some varying degrees of opinion in posts about this.
Regardless, I've setup a script to update artwork nightly now.. using curl and json.. for others that may need it:
curl --user USER
ASS --include --header 'content-type: application/json;' --request POST --data '{"jsonrpc": "2.0", "method": "Addons.ExecuteAddon", "params": { "wait": true, "addonid": "script.artwork.downloader", "params": [ ] } } ' http://HOSTNAME:8080/jsonrpcObviously, replace USER, PASS, and HOSTNAME with appropriate for the config. This updates all artwork configured in the add-on settings (blank params).
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-04-26
(2013-04-26, 13:58)rpoenaru Wrote: Hi @MariusTh86
That is correct. I can open the metadata editor, but then whatever action I choose it becomes unresponsive and I need to force quit out of it.
Even if press the 'Cancel' button?
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - Glorious1 - 2013-04-27
(2013-04-26, 21:17)SevenNine Wrote: Regardless, I've setup a script to update artwork nightly now.. using curl and json.. for others that may need it:
curl --user USER
Obviously, replace USER, PASS, and HOSTNAME with appropriate for the config. This updates all artwork configured in the add-on settings (blank params).
Wow, that's pretty technical! Does the file need anything else in it besides that curl statement? Just for the meatheads among us, how do you get it to run nightly? Would that process wake the computer up? Or if it's not awake would it just do it the next time it wakes up? Does XBMC have to be running for it to work?
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - SevenNine - 2013-04-27
(2013-04-27, 00:54)Glorious1 Wrote:(2013-04-26, 21:17)SevenNine Wrote: Regardless, I've setup a script to update artwork nightly now.. using curl and json.. for others that may need it:
curl --user USER
Obviously, replace USER, PASS, and HOSTNAME with appropriate for the config. This updates all artwork configured in the add-on settings (blank params).
Wow, that's pretty technical! Does the file need anything else in it besides that curl statement? Just for the meatheads among us, how do you get it to run nightly? Would that process wake the computer up? Or if it's not awake would it just do it the next time it wakes up? Does XBMC have to be running for it to work?
My primary is on an Ubuntu Linux box.. so I just set this up with cron. That's all the curl statement needs to be. You'd probably want / need a central backend system running XBMC to manage the library; and then you could schedule this to run. Otherwise, maybe on startup?
You'll need xbmc webserver turned on for this, also. And, yes, XBMC needs to be running with the webserver enabled.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - rpoenaru - 2013-04-27
Yes,
I can't use any button. Only "Force Quit" works.
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - MariusTh86 - 2013-04-28
Just opening up the metadata editor doesn't get it stuck, but any action after opening it up does? how about 'tab' switching on the top?
RE: [MAC] ViMediaManager - Media Manager for Mac OS X! - Glorious1 - 2013-04-28
I'm having trouble downloading any trailers, after choosing one and pressing the Download button. On AOL or Yahoo trailers, the Download button stays with it's pressed appearance and eventually the spinning beach ball appears and I have to force quit. For Apple trailers, it starts downloading slowly, but after only about 3% is downloaded it stops and says download is completed.
Is anyone else getting this, or just me? Next step will be deleting prefs etc.