You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MoviePy while effective, sometimes it's very unpredictable and unreliable. Once it runs, next time it fails. I was just running a concat on subvideos, now the same script is failing. I don't recall changing anything. Am I doing anything wrong?!
for i in range(parts):
cl = VideoFileClip(bestFilename[i])
start = 0
end = float(length / parts)
s = cl.subclip(start, end);
sub.append(s)
cl.reader.close()
final = concatenate([sub[0], sub[1].crossfadein(.5), sub[2].crossfadein(.5), sub[3].crossfadein(.5)], padding=-1, method="compose")
final.write_videofile(output+filename+".mp4",audio=False)
self.make_frame = lambda t: self.reader.get_frame(t)
AttributeError: 'NoneType' object has no attribute 'get_frame'
The text was updated successfully, but these errors were encountered:
Whenever you are reporting bugs and crashes, you need to give the entire error traceback, not just the last 2 lines. I have very little way of knowing where in moviepy the error happened from what you've given me.
However, I think if you remove the cl.reader.close() line it will work. Look at https://github.com/Zulko/moviepy/blob/master/moviepy/video/io/VideoFileClip.py#L123 for what happens when you call close on the VideoFileClip: it sets self.reader to None, which would explain why in the error it is complaining that self.reader has NoneType (ie is set to None).
Don't worry, I thought the exact same thing when I started programming/using Github 3 years ago. However, even if it was a famous/known error we can only guess that it is the same problem that is causing it without the traceback.
MoviePy while effective, sometimes it's very unpredictable and unreliable. Once it runs, next time it fails. I was just running a concat on subvideos, now the same script is failing. I don't recall changing anything. Am I doing anything wrong?!
The text was updated successfully, but these errors were encountered: