Odd actor submission situation -- need guidance from staff

  • 2
  • Problem
  • Updated 10 months ago
  • Solved
I've run into an interesting conundrum on the submission of a new title.  It's a documentary which features three identified actors.  There is dialog in the film, but it is all dubbed.  What's weird is that Character 1 is played onscreen by Actor 1, but voiced by Actor 2.  But Character 2 is played onscreen by Actor 2, but is voiced by Actor 3.  And the film's narrator is also voiced by Actor 3.  I'm not sure how to submit for this, since Actor 2 plays one character visually but voices a different character, one who is played visually by a different actor.  Thus, Actor 2 plays two different characters (one voice only), and Actor 1 plays one of those same characters (but doesn't voice any of them!).  Listing Actor 2 as playing Character 1/Character 2 leaves the (voice) addition sort of inaccurate, since he only voices one of the characters.  And, of course, there's the problem of two actors playing the same character "simultaneously."  For purposes of my submission, I simply listed the actors by the characters they played onscreen and described the weird voice arrangement in a Trivia item.  But I'm wondering if there isn't a means of submission that will convey this information properly in the Cast section, without one having to come across the trivia note in order to understand how this played out.
Photo of Jim Beaver

Jim Beaver

  • 5 Posts
  • 3 Reply Likes

Posted 10 months ago

  • 2
Photo of Steve Crook

Steve Crook, Champion

  • 1357 Posts
  • 1710 Reply Likes
Hello Jim Beaver,
That is a problem. You can't attach an attribute to just one role for one actor. But you can only have one record for each performer. You really want to record it as something like: 
Character 1 ... Actor 1 
Character 1 ... Actor 2 (voice) 
Character 2 ... Actor 2 
... 
But the entry for Actor 2 can only have one (voice) attribute for the entire entry for this title. You won't be able to tell if it's as Character 1 or Character 2 that they're doing the voice for. 
 
    Steve
Photo of Jeorj Euler

Jeorj Euler

  • 6572 Posts
  • 8123 Reply Likes
The hypothetical IMDb cast list would go like so...
  • Actor 1 | Character 1
  • Actor 2 | Voice of Character 1 / Character 2
  • Actor 3 | Character 2 / Narrator | (voice)
Photo of Steve Crook

Steve Crook, Champion

  • 1357 Posts
  • 1710 Reply Likes
Thanks Jeorj, 
But saying "Voice of Character 1 / Character 2" could be read as meaning that they are the voice of Character 1 & the voice of Character 2. 
Might it be better to put the voice credit last saying more like: 
Character 2 / Voice of Character 1 
 
    Steve
Photo of Jeorj Euler

Jeorj Euler

  • 6572 Posts
  • 8123 Reply Likes
The slash take precedence over all other delimiters, especially spaces.
Photo of Steve Crook

Steve Crook, Champion

  • 1357 Posts
  • 1710 Reply Likes
But would regular users be aware of that? They tend to take things literally. 
 
    Steve
Photo of Jeorj Euler

Jeorj Euler

  • 6572 Posts
  • 8123 Reply Likes
Regular users would be aware if the outward display was programmed to convert all slashes to carriage return line feed codes, but then some confusion would perhaps be created in the submission interface.
Photo of Jeorj Euler

Jeorj Euler

  • 6572 Posts
  • 8123 Reply Likes
The subdivisions of the the character field are meant to be ordered in a very particular way, that of the source credits. However, it probably wouldn't hurt if voice credits are given secondary recognition.
(Edited)
Photo of Jeorj Euler

Jeorj Euler

  • 6572 Posts
  • 8123 Reply Likes
This whole matter is largely a technical problem. We don't have the adequate tools to sort out some of the issues that may arise. Basically the role field is intended formatted in a manner consistent with something like the following tree of EBNF expressions:
role description set = role description, { space, slash, space, role_description }

role description = specific role, [ space, left parenthesis, segment indicator, right parenthesis ]

segment indicator = "segment", space, double quote, segment title, double quote

specific role = phrase, [ space, hyphen, space, phrase ]

segment title = phrase

phrase = word set, { end delimiter, space, word set }

end delimiter = dot | comma

word set = word, { space, word }

word = [ single quote ], [ start delimiter ], word part, { single quote, word part }, [ single quote ]

start delimiter = pound sign | at sign

word part = word atom, { inter delimiter, word atom }

inter delimiter = ampersand | hyphen

word atom = letter | numeral, { letter | numeral }
You could potentially have a cast+role breakdown like the following:
  • Actor 1 | Alice (segment "Alice") / Betty (segment "Bob") / Claire (segment "Charlie")
  • Actor 2 | Ben (segment "Alice") / Bob (segment "Bob") / Dave (segment "Charlie")
  • Actor 3 | Colin (segment "Alice") / Donny (segment "Bob") / Charlie (segment "Charlie")
The EBNF expressions could be reconstructed into a really lengthy Regular Expression which I won't bother to state, long because of how overly rigid the aforementioned expression tree is.
Photo of Jim Beaver

Jim Beaver

  • 5 Posts
  • 3 Reply Likes
I'm afraid this explanation is beyond my ability to assimilate.  :-)
Photo of Jeorj Euler

Jeorj Euler

  • 6572 Posts
  • 8123 Reply Likes
Hi, Jim Beaver. Don't worry about it for now.