Tarik

In avf mode, the jit.record object doesn't accept many frames in rapid succession. After about 4 frames triggered by an uzi, it posts the message 'writer input not ready for media data'. In quicktime mode all's fine.

to reproduce, please paste this bit & click button.

anybody got easy workarounds apart from working with delays and such?

jit-record-writer-input-not-ready-for-media-data-bug

this is not so much a bug, as it is a limitation of the AVF engine. lots of things like this, that used to work with quicktime, don't work with avf due to the asynchronous nature of so much of the library.

i've registered a feature request to output a notification from jit.record when it's ready to accept media data, which could be used to trigger the next frame.

in the meantime, some sort of delay is your only option. i did it like this (adjust the delay time for your setup and processing needs):

this is not so much a bug, as it is a limitation of the AVF engine. lots of things like this, that used to work with quicktime, don't work with avf due to the asynchronous nature of so much of the library. 

in the meantime, some sort of delay is your only option. i did it like this (adjust the delay time for your setup and processing needs):


Yes, that feature would be really handy. Until then, the delay method will do.

One thing I've noticed is that the choice of codec has some influence over the occurrence of this 'writer input not ready for media data' error. If I use h264, the Max console rains full of errors. If I use prores4444 I only have a very occasional 'writer input not ready for media data', and they do not occur at all with prores422 on my MBP running 10.10.3. Which is a perfect codec for the experimental nonsense I output from jitter.

fyi I get the same error under avf when trying to export movs from jit.matrixset

I still encounter this problem with jit.record & jit.matrixset on OSX nowadays.

Using jit.vcr instead of jit.record solved the problem for me (using OSX 10.13.6 & Max 7.3.5).

I still encounter this problem with jit.record & jit.matrixset on OSX nowadays.
Using jit.vcr instead of jit.record solved the problem for me (using OSX 10.13.6 & Max 7.3.5).

for exporting from jit.matrixset, try switching the video engine preference to viddll

jit.record: writer input not ready for media data (bug?)