Persistent errors: Windows error (123) and max() arg is empty sequence about videogrep

[d8sconz]

Further:

The problem seems to be that the try block fails and falls through to the except block. It fails within create_supercut() at the point that moviepy is called:

videofileclips = dict([(f, VideoFileClip(f)) for f in all_filenames])

The call to VideoFileClip() is also what throws the Windows(123) error, so my suspicion now falls on moviepy.

[Zulko]

Can you paste the whole error that occurs when you remove the try block ?

[d8sconz]

Hi Zulko, Here is the error message I get when I perform a search that returns fewer than the max clips threshold. This just means that I bypass the create_supercut_in_batches() function and it's try/except block.

  File "videogrep.py", line 261, in <module>
    videogrep(args.inputfile, args.outputfile, args.search, args.searchtype, arg
s.maxclips, args.padding, args.test, args.randomize, args.sync)
  File "videogrep.py", line 241, in videogrep
    create_supercut(composition, outputfile, padding
  File "videogrep.py", line 86, in create_supercut
    videofileclips = dict([(f, VideoFileClip(f)) for f in all_filenames])
  File "D:\Python27\lib\site-packages\moviepy\video\io\VideoFileClip.py", line 5
5, in **init**
    self.reader = FFMPEG_VideoReader(filename, pix_fmt=pix_fmt
  File "D:\Python27\lib\site-packages\moviepy\video\io\ffmpeg_reader.py", line 1
  7, in **init**
    infos = ffmpeg_parse_infos(filename, print_infos)
  File "D:\Python27\lib\site-packages\moviepy\video\io\ffmpeg_reader.py", line 2
  07, in ffmpeg_parse_infos
    stderr=sp.PIPE)
  File "D:\Python27\lib\subprocess.py", line 710, in **init**
    errread, errwrite)
  File "D:\Python27\lib\subprocess.py", line 958, in _execute_child
    startupinfo)
WindowsError: [Error 123] The filename, directory name, or volume label syntax i
s incorrect     

I have to call it quits for tonight. Tomorrow I want to follow the process through ffmpeg where I'm beginning to think the problem lies..

Thanks for your interest.

[d8sconz]

Hi Zulko, Here is the error message I get when I perform a search that returns fewer than the max clips threshold. This just means that I bypass the create_supercut_in_batches() function and it's try/except block.

Traceback (most recent call last):
  File "videogrep.py", line 261, in <module>
    videogrep(args.inputfile, args.outputfile, args.search, args.searchtype, arg
s.maxclips, args.padding, args.test, args.randomize, args.sync)
  File "videogrep.py", line 241, in videogrep
    create_supercut(composition, outputfile, padding
  File "videogrep.py", line 86, in create_supercut
    videofileclips = dict([(f, VideoFileClip(f)) for f in all_filenames])
  File "D:\Python27\lib\site-packages\moviepy\video\io\VideoFileClip.py", line 5
5, in __init__
    self.reader = FFMPEG_VideoReader(filename, pix_fmt=pix_fmt
  File "D:\Python27\lib\site-packages\moviepy\video\io\ffmpeg_reader.py", line 1
  7, in __init__
    infos = ffmpeg_parse_infos(filename, print_infos)
  File "D:\Python27\lib\site-packages\moviepy\video\io\ffmpeg_reader.py", line 2
  07, in ffmpeg_parse_infos
    stderr=sp.PIPE)
  File "D:\Python27\lib\subprocess.py", line 710, in __init__
    errread, errwrite)
  File "D:\Python27\lib\subprocess.py", line 958, in _execute_child
    startupinfo)
WindowsError: [Error 123] The filename, directory name, or volume label syntax i
s incorrect     

Thanks for your interest.

[Zulko]

It seems like a file name issue... strange.

[d8sconz]

Man, that was a mission! I've finally cracked it (chest puffed, superior expression...)

at the beginning of videogrep.py, and the appropriate place in conf.py (for moviepy), where you indicate your path to ffmpeg and IMAGEMAGICK_BINARY, place an 'r' immediately before the opening quote. For example, on my (Windows) machine, in conf.py:

FFMPEG_BINARY = r'D:\ffmpeg\bin\ffmpeg'
IMAGEMAGICK_BINARY = r'D:\ImageMagick\convert'

...and in videogrep.py

FFMPEG_BINARY = r'D:\ffmpeg\bin\ffmpeg'

(note the leading r)

This inputs a raw string and stops python from shagging around with double backslashes etc (I think). Maybe the instructions can be amended?

[Zulko]

Yes they will be ! Thanks a bunch !