Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[peterdrowan]

MC doesn't seem to bring the field - release date - from Itunes. As podcasts don't usually have a track number type field without that field you can't sort them in episode order.  Is there a way to map that field to one of the MC Data fields. Description is also ignored too.   To be honest without those fields the utility is enormously reduced.

Peter Rowan

[Arindelle]

this should help you http://wiki.jriver.com/index.php/File_Properties_(tags)

do a tagdump on your file and then you can play around with the remapping  (http://yabb.jriver.com/interact/index.php?topic=52473.msg358677#msg358677)

or post the dump here and I'll take a look at it if you want

[peterdrowan]

MP3tag shows the tag is called releasetime and is formatted like this
2012-06-11T00:00:00Z.  How would I map that to a mediacentre field. The description is a field called SUBTITLE. They are ID3v2.2 tags

Peter Rowan

[MrC]

You can create a new use field with exactly the same name as the tag in the file.  Use the tag dump to see the name.  This method will ensure you have the tag in MC always.  The "mapping" can be achieved using auto-import rules.

Assuming it is RELEASETIME, you could then convert it to an MC internal date format with:

   ConvertDate([RELEASETIME])

and assign it to a field, such as Date, by setting the Date tag with:

  =ConvertDate([RELEASETIME])

If you don't want to create a custom field, and only want to populate some date field periodically, you can use Tag() to grab the physical tag for the occasional assignment:

  =ConvertDate(Tag(RELEASETIME))

Don't use the leading = in an auto-import rule (it is only for setting the value of a tag in the UI).

The same concept applies with SUBTITLE.  Just set an auto-import rule to set Description with the value of SUBTITLE.

[peterdrowan]

I have created a field RELEASETIME  (manage library fields) Using the calculation you suggest but it is not populated.  Do I have to reimport the data to make it populate.  In the calculated data field I have put ConvertDate([RELEASETIME]). Are auto import rules different to manage library?

I have now found auto import rules (under configure auto import, edit, add custom rule) and added a custom rule RELEASETIME:ConvertDate([RELEASETIME]) but it doesn't populate and MP3Tags tells me the tags are inconsistent.
I have now solved the problem of sorting by creating an expression field that process the episode name in tha name field and gives me  the episode number e.g Episode 234 gives 234 though I can't get Iff to work prorperly as there is more than one format.

Peter Rowan

[peterdrowan]

I have created a field RELEASETIME  (manage library fields) Using the calculation you suggest but it is not populated.  Do I have to reimport the data to make it populate.  In the calculated data field I have put ConvertDate([RELEASETIME]). Are auto import rules different to manage library?

I have now found auto import rules (under configure auto import, edit, add custom rule) and added a custom rule RELEASETIME:ConvertDate([RELEASETIME]) but it doesn't populate and MP3Tags tells me the tags are inconsistent.
I have now solved the problem of sorting by creating an expression field that process the episode name in the name field and gives me the episode number e.g Episode 234 gives 234 though I can't get Iff to work prorperly as there is more than one format.

Peter Rowan

[MrC]

I think you've misunderstood.

The field RELEASETIME you created must not be a calculated value, but a standard string field so that MC can have a location to read and store the value.  Once you have this field, *then* you can use it in other calculated fields or expressions.

Take small steps.  First create the field, and see if you're getting it filled.  Use Update library (from tags) on a selection of files to see if your field populates.