Hangs on render because of malformed progress message

Running the following command:

`-r 30 -f image2 -s 1080x1080 -start_number 0 -i element-%01d.jpeg -c:v libx264 -crf 18 -pix_fmt yuv420p out.mp4`

the following message gets passed to `parseMessage` in the source:

```
"frame I:1 Avg QP:16.16 size: 29141frame P:3 Avg QP:18.38 size: 9961frame B:6 Avg QP:20.72 size: 5600consecutive B-frames: 20.0% 0.0% 0.0% 80.0%mb I I16..4: 10.3% 71.9% 17.8%mb P I16..4: 5.3% 14.6% 1.4% P16..4: 22.9% 11.0% 3.9% 0.0% 0.0% skip:40.9%mb B I16..4: 0.7% 3.1% 0.0% B16..8: 46.3% 7.8% 0.7% direct: 1.4% skip:39.8% L0:56.8% L1:40.6% BI: 2.6%8x8 transform intra:71.8% inter:86.6%coded y,uvDC,uvAC intra: 13.2% 2.9% 2.0% inter: 6.2% 1.7% 1.4%i16 v,h,dc,p: 40% 51% 9% 0%i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 40% 6% 51% 1% 1% 1% 1% 0% 1%i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 61% 7% 21% 2% 3% 2% 2% 1% 1%i8c dc,h,v,p: 97% 1% 2% 0%Weighted P-Frames: Y:0.0% UV:0.0%ref P L0: 77.7% 1.7% 16.5% 4.1%ref B L0: 81.9% 14.9% 3.2%ref B L1: 93.8% 6.2%kb/s:2223.05FFMPEG_END"
```

Then, in parseProgress, an error happens because `message.split('time=')[1].split(' ')[0]` throws an error because `time=` is not in the string.