If you ask me, the values look absolutely identical. But both nodes have different names. One node is called 'Componist', the other is 'Schrijver'. (in English you could understand these words as 'Composer' and 'Writer'). I am inclined to think that both show the values of the predefined Field 'Composer'. Can someone replicate this?
side note: I also remember that we are still missing the field 'Lyricist' as a Node. It is still not possible. I would almost think that MM developers meant to refer to that one when they added, 'Schrijver'...
[1426] A Node is double in My Tree!
Moderator: Gurus
-
- Posts: 23640
- Joined: Wed Aug 09, 2006 10:20 am
- Location: NJ, USA
- Contact:
Re: [1426] A Node is double in My Tree!
Of course, that's as intended. 'Composer' and 'Screenwriter' are handled the same way (but intended for different types of files) in the same way that 'Album' and 'Series' do.
MediaMonkey user since 2006
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Re: [1426] A Node is double in My Tree!
Timelezz, do you mean _nodes_ or _columns_ afaik, we never created a 'screenwriter' node.
We probably should, though...along with Lyricist as suggested.
These are tracked at http://www.ventismedia.com/mantis/view.php?id=6236
Thanks.
-Rusty
We probably should, though...along with Lyricist as suggested.
These are tracked at http://www.ventismedia.com/mantis/view.php?id=6236
Thanks.
-Rusty
Re: [1426] A Node is double in My Tree!
Guys, I started MM in English language. So now I can tell you it is about the Columns/Nodes called 'Composer' and 'Author'. They are really identical! 
If you 'insist' on the story that it only matters for different types of files, perhaps the dutch translation is really crappy. When I read 'schrijver' (literally means 'writer') I can not distinguish whether it is about music or movie. And whether the person wrote the lyrics, or the notes, or composed something, etc... (it is the dynamics of MM that frustrates me, isn't it?

If you 'insist' on the story that it only matters for different types of files, perhaps the dutch translation is really crappy. When I read 'schrijver' (literally means 'writer') I can not distinguish whether it is about music or movie. And whether the person wrote the lyrics, or the notes, or composed something, etc... (it is the dynamics of MM that frustrates me, isn't it?

-
- Posts: 23640
- Joined: Wed Aug 09, 2006 10:20 am
- Location: NJ, USA
- Contact:
Re: [1426] A Node is double in My Tree!
Yes, it's intentional.
http://www.ventismedia.com/mantis/view.php?id=6739
http://www.ventismedia.com/mantis/view.php?id=6739
Upon discussion, there was agreement that the following guidelines should be followed in terms of mapping fields depending on file type. There are _NO_ other fields with such mappings in MM4 other than those described below:
1. Album = Podcast = Series - i.e. these fields would share the same value internally in MM.
2. Artist (Music) = Director (Video/TV) - internally, however Director should have its own suggestions in the dropdown (i.e. don't share them with Artists in Music)
3. Lyricist (Audio) = Screenplay Author (for Video/TV) i.e. these would share the same value internally in MM, but would have their own suggestions in the dropdown. Ideally, this field would always appear on the Basic properties screen. For Video type it would replace Lyricist as used in Music.
4. Note that Artist |= Actor internally i.e. the Properties UI showing 'Artist (actor1; actor2)' should be modified to 'Actor(s)', so that it's clear that it doesn't store values in Artist field. Note that this field should support multiple values (in the same way as Artists and other multiple-value fields).
MediaMonkey user since 2006
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.