The 'M' constraint seems to currently refer to size, rather than time (that is, "M (Megabyte)") .
Thanks for spotting this. I have fixed my previous answer.
Note: we can get close enough for our purposes using 182D instead of 6M...
Isn't that enough?