Video Design to an ethernet 10/100
Video Design to an ethernet 10/100
(OP)
I am looking to have a video chip (MT9V032) to a coldfire processor (66mhz) which is connected to a 10/100 Ethernet port. I am trying to develop a system to display this image onto a web page. It needs to be at least 60 frames per second. I have little familiarity with video and am worried that the 100 Mbit/s limitation would impact the upload speed to the computer screen.





RE: Video Design to an ethernet 10/100
TTFN
FAQ731-376: Eng-Tips.com Forum Policies
RE: Video Design to an ethernet 10/100
RE: Video Design to an ethernet 10/100
John D
RE: Video Design to an ethernet 10/100
TTFN
FAQ731-376: Eng-Tips.com Forum Policies
RE: Video Design to an ethernet 10/100
If you have to ask about it, hardware is your only choice as software is going to be way out of your league. Have you thought about how you intend to wrap the video? You can't just send raw data to a webpage an expect video to pop out... you need something like a Quicktime wrapper, or an MPEG decoder. Since you're not capable of writing the software portion of it, the choice of wrapper will dictate the type of hardware compression you use.
Dan - Owner

http://www.Hi-TecDesigns.com
RE: Video Design to an ethernet 10/100
But that leads to the questions. Does your system start with a camera? If not, then why are you creating video and sending it? Why not just send the data? If there is a camera (real video), then why not skip the processor and just encode the video? Are you overlaying text onto video? If so, the more modern approach is to insert metadata into the stream. Then the overlay text can be selectively displayed by software at the far end.
Depending on exactly what you're doing, there may be much simpler approaches. Apologies in advance if I've misunderstood.
H.264 gives very good picture quality (for NTSC video) at 2 Mbps. It even looks good on a laptop screen (blown up 4:1 by pixels). We don't see any compression artifacts, except (obviously) when the signal drops out.
RE: Video Design to an ethernet 10/100
I am mostly a hardware guy but I do have the IP/stack already written by a third party. The web page hardware interface already works and the video design and web software engineering is new to me(computer end not firmware).
Is the wrapping done in the firmware or in the PC?
The Ethernet port ideally can handle 12.5 MBytes an sec. I am using other features so I need a little room for other features (although not much). The chip I am looking at has 360,960 pixels.
I need a steady image because I am trying to remotely pilot through the internet. The size and the resolution I am still trying to understand. I think I need a tutorial on video design. I believe 60 frames per sec is needed. How to get from 360,960 pixels to frames I don't know.
RE: Video Design to an ethernet 10/100
Dan - Owner

http://www.Hi-TecDesigns.com
RE: Video Design to an ethernet 10/100
Reading between the lines, are you conceptualizing "inserting" the video "into" the webpage at the ROV / server end? As you may already know, the video is normally streamed separately, and the webpage just contains an HTML chunk to make that happen. By way of clarification, the webpage is normally TCP, while the video stream might be better transported as UDP. Apologies in advance if that's already clear to you.
If so, then you're back to simply trying to encode and stream the video. The processor at the ROV end shouldn't get involved in processing the real-time video bits. But absolutely might be involved in multiplexing and transporting the packets (probably enough to keep it busy).
RE: Video Design to an ethernet 10/100
non color
360,960 x 1 = 360,960 bits per sec
360,960 per 60 frames = 21,657,600 bits a sec
color 3x 21,657,600
64,972,800 bits per sec
which trans late too 8 Mbytes and 2.7 Mbytes per sec.
How much I loss if I use UPD verses IP.
RE: Video Design to an ethernet 10/100
http://www.skullbox.net/tcpudp.php
For your own point-to-point wired LAN, data loss even with UDP/IP should be essentially zero.
The assured delivery "advantage" of TCP/IP only helps if you buffer data to span the gaps while it tries again. Buffers are latency. Latency bad. Variable latency is even worse.
RE: Video Design to an ethernet 10/100
RBG is 3 times that.
TTFN
FAQ731-376: Eng-Tips.com Forum Policies
RE: Video Design to an ethernet 10/100
For a 720x480, 30 fps in full colour, they will compress down to 6 Mbps.
Benta.
RE: Video Design to an ethernet 10/100
If this is a one-off project or a prototype, then it might be a good first step to use an Ethernet security camera for the initial integration. Insert an Ethernet switch or router into the LAN, plug in the Ethernet camera, and start playing. POE would simplify the wiring. This would get the concept up and running in an easy afternoon, and probably save time and money in the long run.
RE: Video Design to an ethernet 10/100
Dan - Owner

http://www.Hi-TecDesigns.com
RE: Video Design to an ethernet 10/100
RE: Video Design to an ethernet 10/100
New questions
How does this compression affect the 173 Mbps?
Why are DSP's so expensive and is there a cheaper solution?
Is there a dedicated chip that can do this?
RE: Video Design to an ethernet 10/100
TTFN
FAQ731-376: Eng-Tips.com Forum Policies
RE: Video Design to an ethernet 10/100
RE: Video Design to an ethernet 10/100
TTFN
FAQ731-376: Eng-Tips.com Forum Policies
RE: Video Design to an ethernet 10/100
RE: Video Design to an ethernet 10/100
http://www.mobilygen.com/default.asp?contentID=20
I'm sure there are many similar ICs.
I'm not too sure about "60 fps", unless you mean interlaced fields (vice frames). North American video is 30 frames per second (or 29.97).
When discussing video encoding, it's best to refer to the video encoding standards, such as H.264 (not "MPEG-4").
RE: Video Design to an ethernet 10/100
Dan - Owner

http://www.Hi-TecDesigns.com
RE: Video Design to an ethernet 10/100