Interesting. I read your other thread thanks to Google Translate.
MC does everything at the file level. It doesn't even know about Albums really. It just knows that each file can have an attribute (tag) called [Album], that more than one file can have the same value for that attribute, and if so they should be grouped in some Views. For example, the total duration of an Album displayed at the bottom of Standard View when an Album is selected is always dynamically calculated, based on what files are selected. The value isn't stored anywhere, because there is no entity called "Album" to store it against. That is why this isn't a simple question to answer.
So, I don't have a complete answer for you, but I think if you created a field for the total duration of albums that was relational, so that only one value occurs for each Album, you could enter a value for just one track in an Album, and all tracks in the Album would be assigned that value.
Beyond that, you could use the Search language Expand function (~a) in an Expression, I think, to have MC select all tracks in an Album and then calculated the total duration of the Album, and store it in the new field you have created. I'm not sure if you could do that using a Calculated field in Manage Library Fields or not though. You may need to look into using a Global Variable.
Also, this may be pretty processor intensive, so it may slow down your Views a bit. Once again, I'm not sure.
But play around with the above ideas. Maybe someone who knows a bit more and has the time will come along and give you an easy answer.
PS: The new field suggested above would work something like the standard [Total Tracks] and [Total Discs] fields. A search for discussion about them may help you find a solution.
