CVBS HDMI encoder for live streaming

What is a CVBS HDMI encoder for live streaming?

CVBS HDMI encoder for live streaming is a device that supports CVBS analog TV composite video input and HDMI 1080P high-definition video input; The board output is IP RJ45 and supports RTSP player and UDP player, which means it connects the board to the internet. Your video sources will become the stream and play on the internet.

FAQ

Q1: Does your CVBS HDMI encoder for live streaming support MPEG-2 TS over UDP supported?

Q2: Istället för RSTP, I need an MPEG-2 Transport stream

A2: Do you need DVB-t RF out, which supports the Transport Stream?

Q3: Nej, just CVBS input and Ethernet out, Ethernet protocol: H.264. For compression, MPEG-2 TS on UDP broadcast, I need a quote for 5 qty and a complete datasheet.

A3: Vcan1746 can output the TS stream over UDP, but the output TS stream is a non-standard Transport Stream that we have modified, which needs to be interpreted by our decoder board or player.

Q5: What should I do if I can’t ping the encoder board from my computer?

Directly connect the UART-kabel för kodningskortet till datorn, and use the serial port debugging assistant to send the ATGIP_ command. Get IP address command Operationsvideo på Youtube

1. I can get the sub-stream quickly, but the mainstream needs to get it after reboot. What should I do?

I have tested your encoder multiple times with our system. It is working fine overall.
But we have one big issue to validate its usage :
Whenever we turn on the system camera and the encoder at the same time, we cannot read the “mainstream”, we can only read the “sub-stream”.
We have to “Reboot” the encoder via the web interface to make it work: after the reboot, we can directly read the mainstream.
We tried with both VLC and Gstreamer.
What could we try to have both streams readable on startup?

iVcan reply: In the opinion of our engineers, it is either a problem with camera recognition or a problem with customer use.

I suspect that the board card did not recognize the customer’s HDMI camera.
This is easy to verify (if you cannot access the sub-stream, it will be difficult to verify).
Log in to the web server of the encoder board and you can see the camera recognition status on the video page.


The video page will only display the recognition status of one camera. If HDMI and AV cameras are connected and recognized at the same time, the video page will display the recognition status of the HDMI camera (such as 1080p60):
As long as the HDMI camera can recognize it normally, Mainstream can be accessed normally.
If the HDMI camera is not recognized normally, please check the HDMI wiring and power on the board again (note that this is a power cycle, not a software restart on the web page)

Dessutom, the board uses a random Mac address, so the Mac address will change every time we restart it.
For devices with an ARP cache (such as a PC), after restarting, it will be temporary (a few seconds) unable to access the board from the network. , We cannot access it until the arp request is re-initiated after timeout (the performance is that the coding board cannot be pinged for several seconds after restarting)
Därför, I guess another possibility is that when the customer accesses the mainstream, it cannot be accessed due to the above reasons. Then when the customer accesses sub-stream, the arp cache refreshes and the customer can access it, but the customer does not revisit the main-stream.

Whenever we turn on the system camera and the encoder at the same time, we cannot read the “Mainstream”, we can only read the “subStream”.

Judging from your description here, it seems that your camera is started after our encoding board. Please start your camera first, and then power on and start our encoding board to try it. Maybe it is not powered on at the same time. The powered-on order also matters. Till exempel, your camera startup needs 10 sekunder, but our encoder board startup needs only 5 sekunder.

Because I am not sure whether your camera is very slow to initialize after power-on.
Because our encoder board starts very quickly, it may be that the camera has not been initialized after it started our encoder board, which may lead to some unexpected problems. Detta kan också förklara varför "Vi måste "starta om" kodaren via webbgränssnittet för att få det att fungera: efter omstarten kan vi direkt läsa mainStream.", för när din webbsida startar om kodarkortet, kameran har redan initierats.

Därför, de slutliga förslagen är följande (Jag gjorde mitt bästa för att lista allt som kom att tänka på och låta dig testa dem separat);

  1. Titta på videosidan för webbservern och kontrollera om HDMI-kameran känns igen normalt (du kan skicka en skärmdump till oss). Så länge kameran känns igen normalt, Mainstream kan nås;
  2. Det rekommenderas att du pingar kodningskortet under cmd först, och gå sedan till mainStream och subStream under vlc för att undvika att felaktigt tro att Mainstream inte kan nås på grund av slumpmässiga mac-problem.
  3. Låt dig starta din kamera först (i några sekunder), slå sedan på och starta vårt kodningskort för att prova (se skälen som beskrivs ovan)
  4. Följ din ursprungliga operation med "slå på systemkameran och kodaren samtidigt". When the problem “we are unable to read the “mainStream”, vi kan bara läsa "underströmmen". återges, Starta inte om kodningskortet via webbsidan, men byt ut HDMI-kabeln mellan din kamera och kodningskortet. Jag tror att det bara är en hot-swap-operation (eftersom jag misstänker att det är ett plug-in-detekteringsproblem som gör att kameran inte ansluter till kodningskortet. Skicka HDMI-signal)

Lämna ett svar

Din e-postadress kommer inte att publiceras. behövliga fält är markerade *

Discover more from iVcan.com

Prenumerera nu för att fortsätta läsa och få tillgång till hela arkivet.

Fortsätt läsa

Behöver hjälp på WhatsApp?
Exit mobile version