TROUBLESHOOTING: About the most common Log messages

The Activity and Logs window can be your best friend in case there are some issues during record. An article already explained what the different gauges mean, and below are the most common logs that you can see, what they mean and what you can do to fix those issues. These are grouped by type of issues.


Encoding and CPU

Encoding is too slow... duplicating 5 frames

This typically shows a CPU issue where the computer can not handle the different encodings going on. You should monitor CPU usage with the application "Activity Monitor" and see if you still have some margin (you should always have at least 10% free.



These are logs that are shown when there are issues to write to your storage.

Writing is too slow... As a result, the destination will stop.

This is shown when the hard drive we are recording to can not sustain the write speed required. Note that we have a 30 seconds buffer in our applications. In the typical and best situation, none of our buffer should be used. We should be able to write right away to the disk. But we know that some disk can be unresponsive for a while, or other network issue, and thus we have this 30 seconds buffer per source and destination.

And we also have logs that warn that this buffer is filling up:

Write buffer is filling up (10 seconds). Check the storage used.

Write buffer is filling up (20 seconds). Recording will soon stop if storage does not catch up.

When we reach the 30 seconds buffer, we stop writing to the disk, because usually there is no way we can recover form that (there is too much to write back to the disk and it may also impact other read/write operations).


Video device and input

It seems the selected format (NTSC) doesn't match the input signal (1080i 59.94)

This is logged either when you start the application or when you "enable" a source. It tells you that there is a mismatch between the signal that enters and the format selected. It is important because you may have some misbehaviours in such cases. We are working on making this more obvious, but in the meantime, please always make sure that the incoming signal is identical to the selected format.


Video card buffer full (dropped 1 frames)

When a video device receives video frames, it stores them in a buffer until the application (in this case MovieRecorder) comes and retrieves the frames from the buffer. When the application retrieves the frame it tells it to the video card. In case the application was not able to retrieve the frames quickly enough, the buffer will be full and the video device will get rid of one or more frames in the buffer.

This can happen when:

  • the computer is too slow to retrieve the frames from the video card
  • the PCI or Thunderbolt BUSes have performance issues (typically shown when trying 8 HD channels on a Thunderbolt 1 device, or if a Thunderbolt 1 device is connected to the same "chain" as the M|80).
  • there is a physical issue with the card.


Blackmagic-Design only

Video PTS Dropped 10 frame(s) - Check Reference Clock or CPU usage

This log is shown with Blackmagic-Design cards only. PTS stands for "Presentation TimeStamp", and it is an information that we use in order to ensure AV sync of the recorded files. When you see this log, it means that the PTS that we received from the card did not follow one another, so we are not sure to be able to ensure AV sync.

WARNING: If you are using a "None" or "Segmented Destination", it is recommended that you stop and restart the source after such a log is shown, or all your subsequent recordings may be out of sync.

Sometimes the log can mean either:

  • that the computer was too busy,
  • that there is an issue with the incoming video signal (it was interrupted, disconnected, etc...)
  • that there is an issue with the card or the driver which do not send us the correct value.


Display and Preview

Graphics card is too slow to deinterlace: stopping deinterlacer

This could be misleading because it can happen also if the computer is too busy, not only if the card is too slow. What we do is that we measure the time it takes for our deinterlacer to deinterlace a frame (which is done on the GPU not on the CPU). If for a given duration it goes over the real time duration, we disable the deinterlacer. This has no impact on the file recorded. Only the preview in the application will look as interlaced.

Have more questions? Submit a request


Powered by Zendesk