A

24 Messages

 • 

514 Points

Monday, January 25th, 2021 5:29 PM

Closed

Editor who didn't work on film keeps attaching himself to our film

Hi, I'm the Executive Producer of a made-for-TV film releasing next month. We were recommended to try a new editor - let's call him, "Con-artist". We gave him a chance to produce a line-cut and a scene sample. It was absolutely horrible - it was clear he had no idea how to cut the genre, or a film in general. It turns out he is just an Assistant Editor, by trade, and lacks the experience - we were conned. When he was fired, he admitted that he "should have learned how to cut one of these films" before trying to. The Con-artist then held our drives hostage to extort money from us. 

We got the drives back and moved on to an Editor that we know and like. That Editor started all over, didn't use any work of the Con-artist - how could he? It was absolutely un-usable. 

Suffice to say that there is no chance in hell that we're going to give the Con-artist credit. First and foremost - he did not contribute to the film whatsoever, in fact he only set us back in time and money, not to mention the insult of extortion. 

The problem now is that he is attaching a credit for himself to this film, without our permission. For some three days in a row, we have removed his credit, only to find that he is attaching it again. Each day we have to take it down, again. This is a huge waste of our time, this platform doesn't feel secure, and it is atrocious that he is able to continue trying to attach himself to a film that he categorically DID NOT WORK ON. 

Why doesn't IMDB block him from continuing to do this? How many Executive Producers have to write in and remove him before this becomes a permanent correction? 

Accepted Solution

Employee

 • 

578 Messages

 • 

11.2K Points

4 years ago

Hey - I can see that the editor in question is no longer credited and I have fed back to the data editors in question that he should not have been approved. Apologies for the annoyance this may have caused, but it shouldn't happen again.

24 Messages

 • 

514 Points

Thank you, Grayson! I appreciate the update, and the help.