Re: NHW Project - some news
Raphael Canut <[email protected]> Tue, 24 Mar 2020 13:10:12 +0100
| Newsgroups | gmane.comp.multimedia.ogg.theora.general |
|---|---|
| Message-ID | <CAKE58qFJf9YaLHASXvexdQJ6S5p3CaJAY-o-SeCbc2FTCSZXTQ@mail.gmail.com> |
--===============0824553342378776101== Content-Type: multipart/alternative; boundary="000000000000fd978805a198a298" --000000000000fd978805a198a298 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Andrey, Thank you very much for your answer and your help! > maybe live video streaming from micro-controller based > devices could be a good application domain for your codec? Very good suggestion! as I think the NHW Project could be a good solution for this very interesting domain, because compared to MJPEG, it has a better quality/compression and it can be faster to encode/decode! The problem that will arise is that's right MJPEG is used because of its very low complexity but also because of the widespread support of JPEG like in web browsers... But I think it can be worth to approach the live video streaming micro-controller based devices ecosystem.I will search the Internet for these companies.Really if you have time, would you know a person, an authority in this area that I could contact? Many thanks again! Cheers, Raphael Le mar. 24 mars 2020 =C3=A0 11:18, Andrey Nechypurenko <[email protected]= m> a =C3=A9crit : > Hi Raphael, > > > the NHW Project is extremely fast to encode/decode, a lot faster than > > these codecs > > Just a thought - maybe live video streaming from micro-controller based > devices could be a good application domain for your codec? At the > beginning, > just sending sequence of single frames (similar to MJPEG). Typical > videocodecs are usually too calculation-intensive for micro-controllers. > Maybe you can ride this IoT hype wave ;-) > > Best regards, > Andrey. > --000000000000fd978805a198a298 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi Andrey,</div><div><br></div><div>Thank you very mu= ch for your answer and your help!</div><div><br></div><div>>=20 maybe live video streaming from micro-controller based<br> > devices could be a good application domain for your codec? <br></div><= div><br></div><div>Very good suggestion! as I think the NHW Project could b= e a good solution for this very interesting domain, because compared to MJP= EG, it has a better quality/compression and it can be faster to encode/deco= de! The problem that will arise is that's right MJPEG is used because o= f its very low complexity but also because of the widespread support of JPE= G like in web browsers...</div><div><br></div><div>But I think it can be wo= rth to approach the live video streaming micro-controller based devices eco= system.I will search the Internet for these companies.Really if you have ti= me, would you know a person, an authority in this area that I could contact= ?</div><div><br></div><div>Many thanks again!</div><div>Cheers,</div><div>R= aphael<br></div><div><br></div><div><br></div></div><br><div class=3D"gmail= _quote"><div dir=3D"ltr" class=3D"gmail_attr">Le=C2=A0mar. 24 mars 2020 =C3= =A0=C2=A011:18, Andrey Nechypurenko <<a href=3D"mailto:andreynech@gmail.= com">[email protected]</a>> a =C3=A9crit=C2=A0:<br></div><blockquote = class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol= id rgb(204,204,204);padding-left:1ex">Hi Raphael,<br> <br> > the NHW Project is extremely fast to encode/decode, a lot faster than<= br> > these codecs<br> <br> Just a thought - maybe live video streaming from micro-controller based<br> devices could be a good application domain for your codec? At the beginning= ,<br> just sending sequence of single frames (similar to MJPEG). Typical<br> videocodecs are usually too calculation-intensive for micro-controllers.<br= > Maybe you can ride this IoT hype wave ;-)<br> <br> Best regards,<br> Andrey.<br> </blockquote></div> --000000000000fd978805a198a298-- --===============0824553342378776101== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KdGhlb3JhIG1h aWxpbmcgbGlzdAp0aGVvcmFAeGlwaC5vcmcKaHR0cDovL2xpc3RzLnhpcGgub3JnL21haWxtYW4v bGlzdGluZm8vdGhlb3JhCg== --===============0824553342378776101==--