|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Import recording .properties file
Is there a way to import saved .properties files to correct bad metadata in recordings? My server now periodically gets confused about a batch of recordings - often 10-40 at a pop every 2-3 weeks, changing a show that was recorded in 2011 or 2014 (that seems to be the current binge it's on) to something that will be recorded in the future, and has a different title, description, etc.
To assist myself in recovering the metadata I used BMT to create .properties files for everything & stashed those in a zip file for later use. While I can manually enter the data from the .properties file in a variety of ways to correct the record, is there a way to just tell BMT or Sage (I use the older Sage Web server to do most of it) to import the data from the .properties file for the affected recording? I use the file name to identify the recording and locate the .properties file that I would like to import, but have found no way to automagically import the .properties file and save myself some manual data entry. Note that although I understand that in theory, metadata are saved in the original recordings, it has been my long-term practice to convert (using Sage's tools) recordings into smaller-sized formats, since I have multiple terabytes on hand. So far as I know, there's no way to preserve that data inside the file - and if it was preserved, it's not obvious how to recover it - especially without risking the metadata in all of the other files. I'm working through the current batch of 14 or so (though I haven't checked for a spate of "no data" files which often seem to accompany each spate of wrong-data files, so there may be a bunch of those to handle too), but it would be great to have something less time-consuming to use for the next round that will inevitably occur. Interestingly, I had this problem a lot before updating from Sage 6 to Sage 9, and though my problems were over, but they resurfaced this past June.
__________________
Server: Windows 8.1 4gb RAM; 4TB SATA + others. Homebrew quad core AMD. Inputs: Haup. 980, 850 & 950Q on ATSC; Haup 1600 on ATSC & Comcast 2 DTAs with USBUIRT for NTSC. Haup 1800 on ATSC. HDHR Dual (ATSC). Sage 9.22 64 bit. |
#2
|
|||
|
|||
I think all you need to do, is change the time stamp on the .property file. This SHOULD force SageTV to read the file and overwrite the data in it's database.
__________________
Server #1= AMD A10-5800, 8G RAM, F2A85-M PRO, 12TB, HDHomerun Prime, HDHR, Colossus (Playback - HD-200) Server #2= AMD X2 3800+, 2G RAM, M2NPV-VM, 2TB, 3x HDHR OTA (Playback - HD-200) |
#3
|
|||
|
|||
I keep the .properties files zipped offline. I can extract the relevant ones & put them in the locations they came from (i.e. where the recordings are, which could be in one of a few locations.) I actually used BMT to create properties files for everything a week or so ago, then moved those files offline. By changing the date, do you mean I should give them today's date, or at least a date later than their original creation date? Do I need to do anything in particular to make Sage read these files?
__________________
Server: Windows 8.1 4gb RAM; 4TB SATA + others. Homebrew quad core AMD. Inputs: Haup. 980, 850 & 950Q on ATSC; Haup 1600 on ATSC & Comcast 2 DTAs with USBUIRT for NTSC. Haup 1800 on ATSC. HDHR Dual (ATSC). Sage 9.22 64 bit. |
#4
|
||||
|
||||
Quote:
John |
#5
|
|||
|
|||
Quote:
edit: Oh - you mean the stamp on the video file, not the .properties file. I should have read more carefully. So I just changed the "modified" date on both the video & the .properties file to the current date & time (or do I need to change the "created by" also? Any idea of how long I should give it to sort itself out, or anything I can do to nudge it?
__________________
Server: Windows 8.1 4gb RAM; 4TB SATA + others. Homebrew quad core AMD. Inputs: Haup. 980, 850 & 950Q on ATSC; Haup 1600 on ATSC & Comcast 2 DTAs with USBUIRT for NTSC. Haup 1800 on ATSC. HDHR Dual (ATSC). Sage 9.22 64 bit. Last edited by VCRUser; 09-29-2022 at 12:15 AM. |
#6
|
||||
|
||||
From the Home screen. Setup -> Scan Imported Media
|
#7
|
|||
|
|||
This worked on a file that was counted as imported media, but not on two I tested that are counted as recordings. It's recordings, not imported videos (so far at least) that periodically get their metadata messed up.
For each test, I copied over the .properties file from its zip archive to the folder where the associated media file is stored, made a test-addition to the show's description in the .properties file, so I could determine if anything changed, changed the timestamp (created & modified dates) on both the .properties and media file to the current date/time, and scanned imported media. The change was visible in the description of the imported video, but not in the two recordings. It makes sense that scan imported media would do nothing for recordings, so, is there a way to force recordings to update their properties from the .properties file? As I was running these tests, a whole new crop of messed-up metadata recordings appeared, so it would be great if there were a way to make this process work for them.
__________________
Server: Windows 8.1 4gb RAM; 4TB SATA + others. Homebrew quad core AMD. Inputs: Haup. 980, 850 & 950Q on ATSC; Haup 1600 on ATSC & Comcast 2 DTAs with USBUIRT for NTSC. Haup 1800 on ATSC. HDHR Dual (ATSC). Sage 9.22 64 bit. Last edited by VCRUser; 09-29-2022 at 03:28 AM. |
#8
|
||||
|
||||
In BMT, there is a check box about preserving original metadata, maybe that needs to be unchecked for the recordings.
__________________
"Unencumbered by the thought process" The only constant in the Universe is change. |
#9
|
|||
|
|||
That didn't help, and now for some reason, when I add files to import directories, they're treated as recordings, not imports. I had tried that setting briefly, but it didn't help with this situation, so I reset it. But the reset hasn't taken, and now, while copying my problem files to a new location and giving them the current timestamp (both the media file & the .properties file), then rescanning gets them correct metadata, even though I also copy the .properties file to the original folder and re-time those as well, the original one, which is in the folder I want it to be in, still has the wrong metadata attached. I could delete the original, but then I'd build up files in the "fix" folder, which isn't where I want them. Or I could go back to fixing each original by hand, but would rather not. And, I'd like to be able to have imported videos treated as imported videos when I tell Sage to treat them that way. I can't figure out why I can't get that setting to go back to its default.
__________________
Server: Windows 8.1 4gb RAM; 4TB SATA + others. Homebrew quad core AMD. Inputs: Haup. 980, 850 & 950Q on ATSC; Haup 1600 on ATSC & Comcast 2 DTAs with USBUIRT for NTSC. Haup 1800 on ATSC. HDHR Dual (ATSC). Sage 9.22 64 bit. |
Tags |
bmt, metadata, properties |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
properties file for each show recording? | ThePaladinTech | SageTV v7 Customizations | 5 | 02-19-2017 02:24 PM |
Properties file done away with? | RBraverman | SageTV Software | 3 | 01-29-2017 11:54 AM |
Properties file | heffneil | SageTV Software | 9 | 02-15-2012 08:07 PM |
Changing properties of existing widgets using import file | Morgan111 | SageTV Studio | 2 | 10-18-2006 05:36 PM |
Properties file | RRR | SageTV Software | 10 | 08-24-2004 10:37 AM |