View Issue Details

IDProjectCategoryView StatusLast Update
0003102MMW v4Otherpublic2009-02-22 06:47
Reporterrusty Assigned To 
PriorityimmediateSeverityminorReproducibilityalways
Status closedResolutionfixed 
Product Version3.0 
Fixed in Version3.1 
Summary0003102: Podcasts: fields are sometimes assigned metadata that doesn't make sense
DescriptionArtist field is often given a name that doesn't make sense, based on the filename. e.g. Peter Rojas, Ryan Block - Engadget Podcast 109.mp3 -->
 Artist=Peter Rojas, Ryan Block
 Album=Peter Rojas, Ryan Block
 Title=Engadget Podcast 109

Apparently, many podcasts also use filename structures that screw up standard podcast downloaders and there's often a need to customize these fields. I would propose:
 a) changing the default behaviour so that the Album Field is filled with the Podcast Name
 b) creating a simple mask per podcast, so that users can customize how fields are populated. e.g.
    Podcast tagger: <Artist> - <Title>
    A proposal for this appears at: http://www.mediamonkey.com/forum/viewtopic.php?t=15658&highlight=podcast , but I'm hoping we can create something a lot simpler

if b) is too complicated, another option might be to allow users to populate Artist and Album fields manually in the podcast subscription dialog.
Additional InformationSee item 2 at:
http://www.mediamonkey.com/forum/viewtopic.php?p=139286#139286
TagsNo tags attached.
Fixed in build1200

Relationships

parent of 0005122 resolvedLudek Podcasts: Tags from downloaded episodes are incorrectly rewritten sometimes 

Activities

jiri

2007-06-11 22:07

administrator   ~0009321

I'd suggest the following: For each Podcast add a configuration:

[ ] Set Artist to ____________
[ ] Set Album to ____________
[ ] Set Genre to ____________

The idea is that for unchecked entries MM will try to fill the best possible values (for Artist and Album from RSS feed, for Genre set 'Podcast') and in case of checked set filled in values. Later, we could also add support for some more masks (not for this feature only, but generally in MM, so that user could set something like <NowYear>-<NowMonth>-<NowDay> either here, or e.g. in Conversion dialog.

rusty

2007-06-17 13:15

administrator   ~0009457

I would suggest a small change:

Rather than using checkboxes, why not just have the following after the 'Description:' field:

Artist: _________________
Album: _________________
Genre: _________________

And have them auto-filled based on the characteristics of one of the episodes. I realize that this means that Artist/Album/Genre couldn't vary on a per-episode basis, but does that really matter? It would make this much easier to understand.

jiri

2007-06-18 22:23

administrator   ~0009501

It probably wouldn't be any problem in case of Album or Genre, but in case of Artist I'm sure users would complain soon because there are Podcasts with Episodes published by different authors. I'm afraid that it would be very limiting then. After all, the check box isn't that much, is it?

rusty

2007-06-22 13:43

administrator   ~0009533

Ok then how about:

[ ] Artist: _____________
[ ] Album: ______________
[ ] Genre: ______________

If the checkbox isn't filled in, then the field is displayed greyed out, based on the information contained within the podcast. If the checkbox is filled in, then the user can change the field to a hardcoded value.

Note: The reason I don't like the simpler '[ ] Set Artist to ______' approach is that if a user sees that, it implies that the Artist is set to nothing unless the user enters something into the field.

Ludek

2007-06-23 14:45

developer   ~0009549

Last edited: 2007-06-24 11:29

The most common fields that are extracted as metadata from the feed for each episode are:
title, author, link, description, subtitle, summary, PubDate, URL, keywords, category and the Podcast name is common of course.

and the current assigning to the SongData structure is:
SD.song := title;
SD.Comment := summary;
SD.artist := author;
SD.album := author;
SD.Genre := 'Podcast';

therefore the 1) would make the most sense.
i.e.
a) changing the default behaviour so that the Album Field (SD.album) is filled with the Podcast Name and the Artist field could be filled with Author (as currently is) and if the Autor (accidentaly) is an empty string then it would be filled with the Podcast Name too. But mostly (99 percent) the Author field is presented.

note:
Maybe Comment field should be filled with Description instead of Summary episode's metadata.
i.e. SD.Comment := description;

Ludek

2007-06-24 20:20

developer   ~0009554

And for each Podcast configuration:

[x] Tag episodes based on data included in rss feed

rusty

2007-06-25 15:54

administrator   ~0009564

a i) I agree with the proposed approach of "changing the default behaviour so that the Album Field (SD.album) is filled with the Podcast Name and the Artist field could be filled with Author (as currently is) and if the Autor (accidentaly) is an empty string then it would be filled with the Podcast Name too."

a ii) Regarding filling the Comment field should be filled with Description (instead of episode Summary) metadata (i.e. SD.Comment := description;), how about using the same approach as above. i.e. if episode Summary exists, SD.Comment=summary, but if episode Summary doesn't exist, then SD.Comment=Description.

c) Re: "[x] Tag episodes based on data included in rss feed", is there any case for which that option is required (i.e. why would a user want no tags ? )? My feeling is that such an option isn't required.

If we decide to include such an option, it would probably be implemented as follows (because in stating 'tag podcast based on metadata' isn't accurate since it can be subdivided into 'Tag podcast based on metadata' and 'Tag podcast based on assigned values'):

. . [ ] Artist: _____________
. . [ ] Album: ______________
. . [ ] Genre: ______________

. . [ ] Do not tag Podcast

Note: As discussed previously, if the Artist/Album/Genre checkboxes aren't filled in, then the respective field is displayed with greyed out metadata.

Ludek

2007-06-26 09:59

developer   ~0009583

a) Both is fixed as you described in build 1046.

c) Re: "why would a user want no tags ?":
I thought the situation that downloaded episodes are already tagged by feed creator and the data are already presented in the file's tags (like Album Art) and there is no need to re-tag it based on feed XML metadata. So for such podcasts user would want to not re-tag it.

rusty

2007-07-15 05:10

administrator   ~0009743

Tested 1048 and issue a) is resolved correctly.

As far as issue c) goes, I see your point so how about:

Podcast URL: _______________________
[ ] Title (Album): ___________________________
[ ] Description: ____________________________
[ ] Artist: ______________________________
[ ] Genre: _______________________________

[x] Update episode tags after downloading

Ludek

2008-08-28 07:13

developer   ~0014497

There are three reasons why I would suggest to add only

[x] Update episode tags after downloading

Reasons:
1. There is not enough space on the 'Edit Subscription' dialog.
2. There is not enough possibilities how to tag episodes based on the feed data and I think we currently do this job fine (I haven't see a complaint)
3. This issue is related to what Petr has suggested:
What about to have opportunity to create a script that is launched when the download process (of an episode) has finished. In this script user can e.g. edit tags.

rusty

2008-08-28 15:23

administrator   ~0014499

OK, we can defer the ability to customize podcast tags on a per-episode basis for now... Perhaps it may never really be required...

Thus the only change at the moment will be:

[x] Overwrite existing episode tags with info from Podcast feed

---

If we decide to implement the per-episode tagging, then I would suggest that the bottom half of the Edit Subscription dialog be changed to have 2 tabs. e.g.:

|| Custom Subscription Rules || Custom Tagging Rules | |
| [x] Customize subscription rules for this podcast |
| ... |

and when the second tab is selected, something like the following could appear:

| Custom Subscription Rules || Custom Tagging Rules || |
| [x] Customize episode tags for this podcast |
| (o) Overwrite episode tags with info from Podcast feed |
| ( ) Use custom tags |
| [ ] Title (Album): __________________________ |
| [ ] Description: ____________________________ |
| [ ] Artist: ______________________________ |
| [ ] Genre: _______________________________ |

perhaps such a panel could even support masks for the feed attributes...

Ludek

2008-09-09 19:45

developer   ~0014558

Fixed in build 1186.
i.e. added the
[x] Overwrite existing episode tags with info from Podcast feed
checkbox to the 'Edit Subscription' dialog and to the Options|Podcasts

rusty

2008-12-04 21:58

administrator   ~0015390

Please change the wording to:
[x] On download, tag episodes based on data from Podcast feed

Ludek

2008-12-04 22:19

developer   ~0015391

Fixed in build 1200.

stephen_platt

2009-02-22 06:47

developer   ~0016878

verified 1224