|
Batch Metadata Tools This forums is for discussing the user-created Batch Metadata Tools for SageTV. |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
BMT 4.1/4.2 bugs?
I've noticed a few problems since upgrading to the newer BMT versions. I'm not sure if any or all of the problems existed prior to v4.1, but with v4.1/4.2 I'm using different settings and now I'm starting to see some bad things happen. Some background info (much of my setup is in my Signature at the bottom of the post)...running Window Home Server w/PP3, all current updates, Java 6 update 20, SageTV for WHS v7.0.11 (runs as a service), SageTV7.xml v7.0.11.0, and no obvious duplicate .jar files in the JARs directory.
I'll start off with the easy one Some of the fanart downloads aren't being saved with a file extension and therefore aren't being seen by SageTV. What I'm seeing is the jpg extension is being appended to the file name without the period instead of as an extension. So I get this: Fanart-5386025623459790795jpg instead of this: Fanart-5386025623459790795.jpg Previously I was using the BMT automatic metadata/fanart lookup to do just my import directories. The upgrade defaulted the automatic lookup to ANY_VIDEO and it is causing problems with fanart of recordings. It looks like the fanart for one recording is getting crosslinked with each successive recording. When I enable automatic lookup with ANY_VIDEO, the first movie records and gets its FanArt Title property set with the name of the movie...so far, so good. Every movie or TV show to record after that then gets its FanArt Title and Metadata ID set to the same values as the movie that recorded right after enabling the automatic lookup. With v4.1 installed Friday evening, on Saturday morning I noticed this fanart problem happened overnight and I was able to eventually straighten out the fanart of several recordings with the BMT web UI. I disabled the automatic lookup Saturday morning when I noticed the problem and enabled it again after upgrading to v4.2. With v4.2 installed Sunday evening, the same problem happened overnight where the first recording was fine and successive recordings had the same fanart as the first. However, today I wasn't able to get the fanart for the Sunday night/Monday morning recordings straightened out. Everytime I changed one of the crosslinked recordings, it changed all of the other crosslinked recordings too. I'll attach the phoenix.log to this post (let me know if you want the SageTV debug log, I'll have to split it in 3 parts to get the zips small enough to attach to the post)...you'll see I enabled the automatic lookup at timestamp 2010-06-27 20:33:38,263 in the phoenix.log, then a liveTV lookup happened for Seinfeld, then the movie The Rocker recorded and was correctly set with fanart, but Black Sheep and some recordings of I Survived and It's Me or the Dog were incorrectly showing The Rocker fanart in the SageTV recordings list and none of the recordings after The Rocker show up in the phoenix.log. When I woke up and checked the fanart this morning and noticed the same problem, I disabled the automatic lookup again...the disabling shows up in the phoenix.log at about 5:45am Monday morning, and my attempts to straighten out the fanart start at approximately 3pm. Saturday morning, when trying to fix metadata and fanart in the web UI, when I changed the FanArt Title field and clicked Save, it also saved the previously defined incorrect fanart from the previously configured FanArt Title name to the newly defined fanart directory based on the newly configured FanArt Title property. Another problem in the web UI, I believe is related to the fanart problem above, possibly when the FanArt Title is defined and is then cleared, and then clicking Save. The previously defined posters and backgrounds are saved as mentioned above, but since the FanArt Title is blank, it doesn't save them to a movie or TV show directory. Instead, the Backgrounds and Posters folders are being created in the Phoenix/FanArt/Movies and Phoenix/FanArt/TV root folders and not within a movie or TV show directory. So I ended up with Phoenix/FanArt/Movies/Backgrounds and Phoenix/FanArt/Movies/Posters (same deal with the TV folder). I know it's been mentioned before about the views in the web UI looking all messed up. I'll attach a screenshot of what I'm seeing that may be the same issue others have mentioned. It looks like thumbnails/poster art are being scaled vertically to 120 pixles, but aren't always being scaled horizontally or are being scaled incorrectly. I hope all of that makes sense
__________________
--Jason Server Hardware: GIGABYTE GA-EP45-UD3R, Intel Q9550 CPU 2.83GHz, 11GB RAM, 1xHDHR, 1xHVR1600, 1xHVR2250 29TB Server Storage: 1TB SSD (OS), 1TB (data), 2x6TB+2x10TB (22TB FlexRaid storage pool), 2x2TB (recordings), 1x750GB (VMs). Server Software: Win10 Pro x64 OS, SageTV 64bit v9.2.0.441, Java 1.8 u241, PlayOn, Comskip (Donator) v0.82.003, WampServer v2.5. Clients: 3xHD300s, 2xHD100, 2xPlaceshifters |
#2
|
|||||
|
|||||
Quote:
Quote:
I'm not 100% sure, but I have feeling the crosslinking is comming from the properties files. Quote:
Quote:
Quote:
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#3
|
||||
|
||||
Another potential bug. I've turned off sending system messages on failed metadata searches, but when I search through the web ui for a folder I get a ton of system messages (they're legitimate failures, but I thought I shouldn't get them).
I'm also still having the problem of not getting any metadata for shows during 2-3 hours in the evening every day. |
#4
|
|||
|
|||
Quote:
Fanart-1131882411931827300jpg Fanart-3643542565329594814jpg Fanart-5507706165156623642jpg invictus-original.jpg MV5BMjAyMzExMDM1N15BMl5BanBnXkFtZTcw...512_SY512_.jpg And the contents of the "images" file in that directory are: # Ignoring these image files http://hwcdn.themoviedb.org/posters/...s-original.jpg http://hwcdn.themoviedb.org/posters/...s-original.jpg http://hwcdn.themoviedb.org/posters/...s-original.jpg http://hwcdn.themoviedb.org/posters/...s-original.jpg http://ia.media-imdb.com/images/M/MV...512_SY512_.jpg
__________________
Server: Sage 7.1.9 beta; Dell Inspiron 530; Windows 7 Ultimate 32-bit (UAC turned off); 2TB Internal SATA (TV Recordings) Storage: Synology DiskStation DS411+, RAID 5, 5x 2TB SATA for (DVDs/Music/Other Videos) Tuners: Ceton InfiniTV w/ Verizon FIOS cablecard (using babgvant's SageDCT plugin) Clients: 1x STP-HD300; 1x Acer Aspire Revo 3610 (Atom/Ion) w/ SageTV client (Win 7, EVR, FSE on) Last edited by LehighBri; 06-28-2010 at 07:15 PM. |
#5
|
||||
|
||||
Quote:
Quote:
Quote:
That's for all the feedback.
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#6
|
|||
|
|||
Quote:
Going into SageTV, in All Recordings and Recording Detail screens, The Rocker still shows the proper metadata for The Rocker and Black Sheep shows the proper metadata for Black Sheep, even though the web UI shows both movies with Black Sheep metadata. So it appears somehow BMT is populating the first recording correctly and failing on successive recordings and is incorrectly applying the non-failed recording FanArt Title and Metadata ID to these successive recordings instead of fully processing them. It must be failing somewhere on successive recordings since only the first one showed up in my phoenix.log and none of the successive recordings showed up. Is there any additional logging I can enable or more verbose logging I can set to possibly catch that failure? I'm not sure what to think about the discrepancy between the metadata that displays in SageTV and what displays in the BMT web UI. Is it possible that instead of .properties file linking, could it be the metadata that is stored in the recording files themselves that is somehow causing the linking? Is there any way I can compare what metadata is stored in the recording file to the metadata that is in the wiz.bin? Quote:
Quote:
__________________
--Jason Server Hardware: GIGABYTE GA-EP45-UD3R, Intel Q9550 CPU 2.83GHz, 11GB RAM, 1xHDHR, 1xHVR1600, 1xHVR2250 29TB Server Storage: 1TB SSD (OS), 1TB (data), 2x6TB+2x10TB (22TB FlexRaid storage pool), 2x2TB (recordings), 1x750GB (VMs). Server Software: Win10 Pro x64 OS, SageTV 64bit v9.2.0.441, Java 1.8 u241, PlayOn, Comskip (Donator) v0.82.003, WampServer v2.5. Clients: 3xHD300s, 2xHD100, 2xPlaceshifters |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
BMT: Read this if you don't see any BMT topics | Opus4 | SageTV Customizations | 0 | 04-25-2010 09:17 PM |
decoder bugs | broderp | SageTV Software | 7 | 08-09-2006 09:05 PM |
Two bugs in 3.0.13 | neilbradley | SageTV Beta Test Software | 4 | 10-20-2005 01:10 PM |
bugs... | Kanati | SageTV Beta Test Software | 3 | 07-26-2005 03:26 PM |