![]() |
|
Batch Metadata Tools This forums is for discussing the user-created Batch Metadata Tools for SageTV. |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
||||
|
||||
EPGID...
I am curious, are you making up/overwriting the regular EPGID with something like: EPmt75760S05E18 (instead of EP757600518) or is it SageTV 7.0 (or the guide data provider) doing it? The lower cap "mt" is kinda pointing to BMT, but...
![]()
__________________
SageTCPServer (2.3.5): Open source TCP interface to the SageTV API MLSageTV (3.1.8)/Sage Media Server (1.13): SageTV plugin for MainLobby/CQC TaSageTV (2.58)/TaSTVRemote (1.14): Monitor/control SageTV with an Android device TbSageTV (1.02)/STVRemote (1.11): Monitor/control SageTV with a PlayBook 2 TiSageTV (1.64)/TiSTVRemote (1.09): Monitor/control SageTV with an iPhone/iPod/iPad |
#2
|
||||
|
||||
Yes, that is done by BMT. It is how BMT moves imported tv shows to the recordings.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
#3
|
||||
|
||||
OK, thanks. So I guess I have to go put a work around in my MainLobby, CQC and Android applications that got broken by that non standard modification...
![]() EDIT: Probably a good idea to double check with someone from Sage that it won't break anything in SageTV itself, having those non conform EPGID... For example when grouping by series or something...
__________________
SageTCPServer (2.3.5): Open source TCP interface to the SageTV API MLSageTV (3.1.8)/Sage Media Server (1.13): SageTV plugin for MainLobby/CQC TaSageTV (2.58)/TaSTVRemote (1.14): Monitor/control SageTV with an Android device TbSageTV (1.02)/STVRemote (1.11): Monitor/control SageTV with a PlayBook 2 TiSageTV (1.64)/TiSTVRemote (1.09): Monitor/control SageTV with an iPhone/iPod/iPad Last edited by Fonceur; 09-03-2010 at 09:53 AM. |
#4
|
||||
|
||||
Quote:
More recently, I've had discussions about sage using other prefixes to identify imported media, and as of 7.0.16, sage now support IM and IE which represent, "Imported Movie" and "Imported Episode" respectively. So in future releases of BMT, i'll probably not use the EPmt and MVmt and use IEmt and IMmt instead. The reason that I wasted a new prefix is so that I can easily identify an imported recording vs a real recording. fyi, bmt uses 2 formats for epgid, EPmtTVDBIDS##E00, and MVmt########, and soon (IEmt and IMmt), but the one thing that is for certain, is the characters 3 and 4 will be 'mt'. EDIT: As Fuzzy noted as well, bmt only ever modifies the EPGID if a user requests to import an existing file in as a Sage Recording. EDIT2: I am curious how this epgid modification created a bug in your apps?
__________________
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 Last edited by stuckless; 09-03-2010 at 10:10 AM. |
#5
|
||||
|
||||
There are some more prefixes, like SP for sporting events. And the length of the series id is not a constant, about 3 years ago they had to add a digit or 2, to prevent running out of them... I've been extracting the episode production numbers since 2004 in BTV...
![]() What broke is that I was taking the Integer value of the last 4 digits. While 1E01 could be wrongfully extracted as 10, the value 5E18 just doesn't fit in an Integer... ![]() ![]()
__________________
SageTCPServer (2.3.5): Open source TCP interface to the SageTV API MLSageTV (3.1.8)/Sage Media Server (1.13): SageTV plugin for MainLobby/CQC TaSageTV (2.58)/TaSTVRemote (1.14): Monitor/control SageTV with an Android device TbSageTV (1.02)/STVRemote (1.11): Monitor/control SageTV with a PlayBook 2 TiSageTV (1.64)/TiSTVRemote (1.09): Monitor/control SageTV with an iPhone/iPod/iPad |
#6
|
||||
|
||||
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 |
#7
|
||||
|
||||
OK, all good, I can work with that.
The only possible issue that I'm seeing with that scheme, instead of the usual production number, is for a daily shows with more than 99 episodes a year (i.e. Virginie in Quebec), but I guess there might not be a lot of those... ![]()
__________________
SageTCPServer (2.3.5): Open source TCP interface to the SageTV API MLSageTV (3.1.8)/Sage Media Server (1.13): SageTV plugin for MainLobby/CQC TaSageTV (2.58)/TaSTVRemote (1.14): Monitor/control SageTV with an Android device TbSageTV (1.02)/STVRemote (1.11): Monitor/control SageTV with a PlayBook 2 TiSageTV (1.64)/TiSTVRemote (1.09): Monitor/control SageTV with an iPhone/iPod/iPad |
#8
|
||||
|
||||
Quote:
__________________
Buy Fuzzy a beer! (Fuzzy likes beer) unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers. Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA. Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S Other Clients: Mi Box in Master Bedroom, HD-200 in kids room |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|