fabled / bmd-tools

Tools to connect and manage Blackmagic Design video equipment with built-in H.264 encoder
MIT License
37 stars 14 forks source link

Input mode not supported #13

Closed martialgallorini closed 9 years ago

martialgallorini commented 9 years ago

Hello,

I am using your great tool to stream video over ethernet.

This happens from time to time :

Everything is ok for 2 or 3 weeks. Then image starts to lag and finally freezes. So i stop the stream and start it over, ther bmd-tools keeps on complaining :

"[2/2 1edb:bd43]: Input Mode, 0xff (display mode 0x02) not supported" "[2/2 1edb:bd43]: Input Mode, 0xff (display mode 0x02) not supported" "[2/2 1edb:bd43]: Input Mode, 0xff (display mode 0x02) not supported" ...

From here, i stop, restart the stream, reboot once, twice, unplug the h264 Pro Recorder and repeat all this once and again.

Always the same error...

And all in a sudden, unplugging and reboot one more time and all starts to work again !

what the problem could be ?

thank you

PS : this is the command i use

sudo ./bmd-tools/bmd-streamer -S sdi -k 9000 -K 10000 -P main | avconv -i - -vcodec copy -acodec copy -f mpegts udp://239.255.1.1:1234

fabled commented 9 years ago

That generally means that the encoder has lost sync with the video source. Does it work stable with the official drivers? What OS? If Mac, are you having the official black magic drivers also running at same time?

martialgallorini commented 9 years ago

Hello,

thanks for your answer.

I can't tell with the official drivers as i don't use them. I used to use the encoder with a mac and official drivers and it was working fine.

For this configuration i am using a macmini with a headless Debian Jessie installed. I am just using it to stream a video over UDP Multicast. No offical driver is installed on this configuration.

It acts like it catches an input resolution and stays with it. If the sync is lost, it keeps on using this configuration instead of switching to the new one when sync is back again.

fabled commented 9 years ago

Sounds strange. Perhaps the the encoder needs input-source being set again. The standard drivers seem to auto-rotate between inputs, which might make the difference to detect the signal reliably.

What is the image format you have when everything is working?

martialgallorini commented 9 years ago

Yes maybe encoder needs to be "force re-init" when bmd-tools starts to make sure it overrides some cached settings.

When all is ok, bmd-tools indicates 1080p 25 which is the resolution of my SDI camera.

fabled commented 9 years ago

Has this issue occured since? You stated it happened once after 2-3 weeks of uptime. Do you have reliable (and fast) way to reproduce this?

I'm considering changing the input source selection code a bit.

Though this could be hardware issue on the Pro Recorder. I have one ATEM TV Studio unit and one of the SDI inputs mysteriously just goes black (usually after 1-2 weeks of uptime). Removing and attaching power cable fixes the issue every time.

martialgallorini commented 9 years ago

Hi,

Yes it occured once 2 weeks ago : image started to lag and some compression artefacts appeared, as if Pro Recorder was missing some intermediate images. I had to stop the stream and, as stated earlier, unplug power cable again and again just to make it work again.

Maybe a hardware problem, but unplugging it and plugging it back should solve the problem without hassle.

I remember having this "Input Mode not supported" problem when manually turning the installation off (even if there was no problem) so i think i could reproduce the problem

martialgallorini commented 9 years ago

i switched my Pro Recorder device with another on i own : same issue appeared. maybe this is not a hardware issue.