Logitech 1080p Pro Stream
Miriam
So i had a read up online and found some posts stating the main differences between the Pro and the Stream Edition were the packaging is different (i can live with that), the Stream Edition included a 12 months licence premium XSplit licence (bonus) but they run different firmware although its believed the hardware is the same (Sound ok). So perhaps a bit of marketing consumer vs business.
The Stream seems to be more for the gamers and streamers. I also checked the Teams Certified device page and it lists the Brio 4K Webcam as certified and not specifically calling out the Pro or Stream so believe the Stream should be a certified device.
I then started searching for Windows Hello not working on Brio Stream and started finding more and more posts and then i remembered the comment on Amazon about different firmware between the Pro and the Stream! nooo! why didnt i listen and i was warned! So there must be different firmware out there somewhere.
I searched Logi site and just couldnt find the Stream device on their webcams just the Pro! again! I download a firmware update tool from the Pro page but it said device not found ? arghhh confirms different firmware story. Again!
Thank you for this article. You saved me a lot of time. It ranked #1 in Google and pretty much instantly found the fix, unlike you and many others, that had to waste so much time. Just wanted to let you know that I appreciate you, whoever wrote this post.
I want to reproduce what was done with a Beaglebone, but using a Raspberry Pi: send a H264 stream to the network. The Raspberry Pi is then only here to packetize the stream in RTP, the video compression is done by the webcam itself. The H264 mode is enforced using video4linux.
However, if I use the raspberry Pi to send the video stream, the result is quite poor. Lots of garbage in the image as soon as something moves. Image keys are well received every 10 seconds, but in the meanwhile, it is not good enough as compared with the stream from a common computer.
It is not a network problem: I did some network checks with Wireshark and the statistics of VLC, I have no packet loss. I tried with Raspbian, and Arch Linux for Raspi (gstreamer 0.10 in raspbian, gstreamer 1.0 in Arch Linux).
I do not know if it is relevant or not, but I also tested with the soft float support version of Raspbian. An update must be done first to use a 3.2 kernel ; but same problem, the video has some garbage.
You can then pipe the data from the V4L driver to FFMPEG with these settings. Where the -i "fifo" should just be -i to caputre the piped stream and the -f you will need to double check how to output it H264. the FLV repackages it into FLV that can be played with HTML players.
the -f denotes the format to output in. It does not mean it will transcode it like H264 to FLV just gets wrapped in the FLV format. then change the address to your clients VLC player. for example -f mpegts udp:192.168.1.19:1234
You may also look at install nginx with rtmp module that works a treat. Look at this guide but you will need to tweak the settings a bit. You then connect your VLC player to the nginx-rtmp stream and it will work like a charm.
If I understood your situation well, you want Raspberry to transcode video to H264? I think that is why you get bad performance, because VLC is using software encoding and Raspberryis not powerful for that task.
At this point, FFMpeg will begin capturing video from your camera. It'll do the transcoding to the proper format locally and send that off to your server.Leave it to encode for about half a minute and then hit your server's stream URL using a Pideo Player, in this URL: YOUR_IP_ADDRESS/cam1.asf The player will buffer for a bit and your video will start playing.
During printing (not typically while not printing) the screen will be okay and streaming then suddenly
it freezes. Usually see a white stripe on the bottom of the screen or the entire screen is white.
I seem to have resolved it. I changed the stream aspect ratio from 4:3 to 16:9. This removed the black bars at top and bottom. I also moved the usb cable from USB 3 port to USB 2 port on the pi. Not sure which made the difference but I don't see the freezing anymore.
Last week I finally purchased a webcam for online meetings, something I had been holding off on for quite some time. I was using a 12" MacBook for these up until now, but I wanted to get a webcam for my main computer as I sometimes need to look over or go through a project while in a meeting, and that's easier to do on my main macine. For a quick family call this certainly makes it easier, too.
Since webcams are not necessarily cheap, I had a hard time convincing myself to get it. This is actually the primary reason it took me so long to purchase one in the first place. But, I have to find a solution for this sooner or later, so let's just get it over with now, I thought.
The Logitech StreamCam is, as the name implies, targeted somewhat more towards the YouTube and Twitch gamers. For what reason I am not entirely sure, as it does not necessarily seem like a great choice for that market. It actually looks like a better all-round choice, or perhaps just for anyone who prefers to have a slightly sharper and higher framerate capture (bandwidth permiting, of course) and spends some time in front of a webcam throughout the year, whatever their purpose may be.
And so, I chose to get the Logitech StreamCam. Not because I'm planning on doing any streaming, but simply because it offers a sharper looking image in most lighting conditions, and supports 1080p at 60 frames per second, if so desired. Perhaps this is overkill now, but as I am not someone who enjoys upgrading hardware often, I like to think that this camera is future proof.
There are two colors available: white and "graphite," the latter of which is basically the black-equivalent version. Included with the StreamCam are two mounts; one is your typical camera mount designed to be placed on top of your LCD display, and the other has a standard tripod screw mount, which is super handy and the one I ended up using alongside an off-brand GoPro bar mount, attached to my monitor arm.
The camera is hard-wired with an 1.5 meter long USB-C 3.1 cable, which depending on your setup might be a bit short. Fortunately it seems to work fine with a 1 meter USB-C extension cable I purchased separately. No USB-C to USB-A adapter is included in the box by default, although this is something the store I purchased it from did include.
Fortunately Logitech webcam support is pretty good under Linux, with video4linux (or v4l2) providing support. What follows is a quick step-by-step guide on how to get the StreamCam to work at full 1080p, 60fps quality, although you can use this same guide for other Logitech cameras too, as the steps should be identical.
To see if your computer recognizes the webcam you can use the v4l2-ctl tool, which is provided by the v4l-utils package. It is not necessary to install this package, you only need it if you want to use some of the helper tools it provides.
When you first launch guvcview you should be greeted with your camera's view, it's working! However, things probably don't look quite right. You'll probably get an abysmal framerate, too. Let's fix that. Whenever you make a change, you should immediately see the difference in the camera view. The window title of the camera view will tell you what the current framerate is, so keep an eye on that too.
Sometimes the camera seems to need a nudge in the right direction, and this might help it. After this your framerate should jump up to whatever option you chose, and you should be able to change Exposure, Auto back to Aperture Priority Mode. Alternatively you can leave it at whatever specific setting you want, of course.
These are just the default settings needed to get the StreamCam to show up at its full resolution and framerate. From here you can tweak its white balance, exposure, etc. if you like, although I must admit I have done none of those things. I did use the mirror filter to match what I see on-camera with what I expect to see, which is a bit more convenient for me.
Take a look at all the available settings and see what you like. Fortunately Guvcview supports saving and loading of profiles, so once you have made your basic configuration, simply use the Save profile option under Settings, and store this somewhere convenient. That way you can always go back to your defaults, or even switch between different settings depending on specific situations, for example.
Guvcview allows you to snap a photo and record a video directly, too, which can be handy in certain situations. What you may find though is that by default as soon as you hit Cap. Video, the framerate tanks.
This seems to be a limitation with this application, but a solution I found was to change the Video codec from the Video menu to MJPG - compressed. Raw camera input works fine, too. This seems to avoid the issue, although the resulting video file will become quite large, quite fast, so keep that in mind. If you're planning on recording videos more frequently, it would probably make sense to use something like OBS instead, just make sure you check the aperture-related settings if your framerate seems low.
Most settings you specify in Guvcview should be preserved by other applications that use the camera, unless they apply their own settings or defaults. So once you have configured things the way you like in Guvcview, your next Zoom/Skype/Google Hangouts call should look quite alright.
I skipped over the audio settings, mostly because this webcam's audio quality is nothing to write home about. It'll be fine for a quick meeting, I'm sure, but you'll pretty much sound like you're on the other end of a landline. If you plan on recording videos or just want to have better audio because you care about that sort of thing, I recommend using a stand-alone microphone. I have a Zoom H1n, which can also be used as a USB microphone, so that's what I've been using, but basically any recommended USB microphone will do a better job than a webcam might.
c80f0f1006