Octoprint won't render timelapses

So I kept running out of space, so bought a 128gb USB drive (actually the size of the wifi adapter for the pi) and mounted it as /mnt/usbdrive, modified the fstab, and it all works nicely. Then I edited the config.yaml with the folders as so:

Code:

folder:
  timelapse: /mnt/usbdrive/timelapse
  timelapse_tmp: /mnt/usbdrive/timelapse_tmp

This all works perfectly, it stores the JPGs in timelapse_tmp and creates a mpg file in time-lapse. So I can make actually higher quality movies as the JPGs are high quality and I can download them to my mac and combine them into a quicktime movie, but the issue is the time-lapse files are all blank. Permissions isn't it (see ls -l below).

Code:

pi@bigbox:/mnt/usbdrive $ ls -l
total 100
drwx------ 2 root root 16384 Apr 11 22:57 lost+found
drwxrwxrwx 2 pi   root  4096 Apr 16 06:22 timelapse
drwxrwxrwx 2 root root 81920 Apr 16 15:31 timelapse_tmp

Any ideas for you octoprint whizzes?

 

Oh, and before anyone asks:

Code:

df .
Filesystem     1K-blocks   Used Available Use% Mounted on
/dev/sda1      119271652 828528 112361384   1% /mnt/usbdrive

Code:

df /
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root        7511124 4672116   2478372  66% /

 

Pics are perfect and sitting in the tmp directory waiting to render...

 

Weirdly this:

Code:

2016-04-15 12:49:25,635 - octoprint.timelapse - WARNING - Could not render movie, got return code 1: [mpeg2video @ 0x13cd060] MPEG1/2 does not support 15/1 fps
Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height

Code:

webcam:
  ffmpeg: /usr/bin/avconv
  ffmpegThreads: 1
  # The bitrate to use for rendering the timelapse video. This gets directly passed to ffmpeg.
  bitrate: 10000k
  snapshot: http://127.0.0.1:8080/?action=snapshot
  stream: http://bigbox.local:8080/?action=stream
  timelapse:
    fps: 15
    options: {}
    postRoll: 0
    type: zchange
  watermark: false

 

Yes, I had not checked the log, BUT WTF?: Since it is 2016!?!?!?! why are we limited by MPEG2 12 YEARS LATER?? Hell MPEG2 actually supports variable frame rates, so given that, why is 15 (a nice multiple of 30) not supported?