Recently, i bought the Raspberry Pi Camera Board v1.3 and hooked it up to my Raspberry Pi, because i wanted to make a livestreaming (web) camera.
Many tutorials are advising me to use ''Motion'', but this simply DOESN'T work, and i'll tell you what:
I installed everything following every single detail on installing Motion for the Raspberry Pi and it's costum camera, but when i go to my Raspberry Pi's IP address and add :8081 or :8080 my browser simply does NOT find the page ''this page does not exist'', but just going to :80 works fine, and i can ping, SSH, and FTP it normally.
After reflashing my SD-card and installing Raspbian like a hundred times it only worked ONCE, but for just 3 seconds! after that it failed again.
So because Motion is a piece of crap i tried other livestreaming stuff like MJPEG and MJPG, but it's storing like 10 pictures every second on my SD-card, if i would continue using that software my SD-card would die/wear-out within a few weeks, so that's not going to be it too.
I also tried using a simple command line together with VLC so i can watch it from there, but the problem is that you cannot set the FPS any lower than 24, i need to do that because streaming 1080p 24 FPS via a raspberry outside your local IP causes it to lag (because the RPI cannot handle the bandwith?) and setting the camera to anything lower than 24 FPS causes huge lag too (looks like the camera doesn't support it?).
So what now? how can i make a simple HD with 2-5 FPS livestream via web with a Raspberry Pi? should i buy a simple USB Logitech webcam? what other software can i use?
Related
Hi,
I want to install XBMC on my Raspberry Pi B model. I have done that sometime in the past, but at that time XBMC was very unstable and it was crashing a lot. So, has anyone recently installed XBMC? If so, does it have any stability issues? Is it running smoothly (performance-wise)?
If you faced anything strange please let me know...
Do some research on Raspbmc, xbian and openelec. I run Openelec hard wired to a NAS without any issues. From rrading the foruns most issues come about because of special requirements and customisations (where the user lacks the skills/knowledge) run stock and its a pretty sweet media centre for the price tag.
Raspbmc
I've used Raspbmc with great success. It's optimised for running xbmc on the Pi and I've found it fast considering the hardware it's running on.
It's very easy to set up and playback is very smooth over wired ethernet.
A couple of my non-techie mates use it daily without problem.
I can't comment on other solutions as I've not tried them.
I'm in a similar boat - about to set up a new B+ for both my kids to use in their education and also as a "secondary" (although I can see it being the default day to day) configuration as a media player for my dumb TV.
From the research I've done so far, currently (overclocked) OpenElec seems to be slightly recommended against XBian, with RaspBMC a bit behind that. But all the reviews and websites seem to indicate that all three will do the job fine, with the recommendations being from ease of set-up and how "cutting edge" they are in terms of maintenance and improvement. And also that each tend to get boosted at their updates so the lead changes quite regularly.
In my case I think I'm going to set up one SD card for the kids with Raspian and stuff like Scratch and maybe Python etc, with a second card dedicated to media use and swap them out when the usage changes over. That way I can nuke from orbit and play around on the media side without affecting their set-ups at all.
One of the better comparisons sites I saw was the links below (and the pages linked from them):
http://www.htpcbeginner.com/overclocked-openelec-vs-xbian-raspberry-pi/
http://www.htpcbeginner.com/raspbmc-vs-openelec-comparison-2014/
http://www.htpcbeginner.com/raspbmc-vs-openelec-comparison-2014/
I prefer openELEC. I set it up so that the USB drive was the root device so I had more storage and so I can safely overclock without corrupting my SD card
Hello!
I was wondering about the feasibility of having an HD capture setup using Raspberry Pi. Is there any boards that we can host on Raspberry Pi 3 which can capture clear HDMI signals?
Basically I am looking at a cheaper solution to capture multiple HDMI sources (1080p or 4k) using individual Raspberry Pi modules per each (or 2) signals. By this, my aim is to avoid using expensive multi-input cpature cards and a PC to capture.
Any inputs highly appreciated
Thanks!
HUBPiWi
Hi
What about HUBPiWi with three USB and a wifi which can be used with Raspberry Pi0 or 1.3. Have anybody used it or bought it please let me know
Most HDMI capture adapters require USB 3.0, which none of the released Pi's have. Even if this was feasible, once you start adding up the cost of the Pi's and USB capture cards, you quickly start to approach the cost of lower-end professional units/a dedicated PC.
If you're using this to do production work, I'd recommend looking into a dedicated solution like a Tricaster Mini or a Blackmagic ATEM Production Studio 4k. I'm not sure if it'll record multiple streams simultaneously, as it's more for live productions. I used to have the 1080p version of the ATEM. You could only record the output channel via USB, but it worked good as a production-level switcher.
Trust me...I've went down this same route in an effort to save on equipment for doing production-quality podcasts. In the end, I wound up going with multiple 1080p webcams w/ multiple USB PCIe cards (so I could do 2 cameras per bus), XSplit Producer and only use HDMI capture when absolutely necessary.
I've been enjoying my Raspbery PI 2 for the past 18 months.. today i wanted to watch a movie on it and i got an unpleasant present..
There was no sign of life on the TV, first i tought for the worst, but than i managed to "trigger" a noise from the speakers that i have on the PI, i was scrolling trough the menu of OpenELEC and the sound was there!
I started to troubleshoot, SSHed onto the PI.. tvservice recognized the TV, even the right resolution.. Than the google research started. After a couple of hours browsing the web, trying several options (various combinations in the config.txt) i decided to re-install a fresh version of OpenELEC, everything went smooth, now i can access it over http + SSH, but there is still no image on the TV(no signal).
I tested the PI on another 2 TVs + 2 HDMI cables, didnt have the chance to get my hands on a S-video cable yet.
I sure hope someone could give me a hint or two what could be wrong.. or else i'll have to buy a new Raspbery PI 3
Thanks for everything in advance
It probably the HDMI connector on the raspberry board. It can easily replace with some soldening skill.
Try to install Windows 10 on it which, I think is the most stable os for your Raspberry. I had the same display problem and it was solved magically when installing Windows 10.
If this does not apply, then think about of getting that Rapsberry pi 3
Sent from my MLS IQ1855 using XDA Labs
2022 WORKAROUND TO PARSEC ON TABLETS
This guide is intended for anyone who is trying to get Parsec running on an Android or even Apple tablets. It would also apply to anyone really wanting to play ANY PC game on ANY tablet.
Disclaimer:
This IS a workaround and NOT a way to FIX the issues with Parsec Android.
If you are interested in how my Parsec Android testing went, and if your really want to give it a try see Parsec below for my suggestions.
Otherwise if you just want to skip to the good stuff head down to WORKAROUND
PARSEC ANDROID
Parsec Android is in the EXPERIMENTAL phase, and even after testing on multiple versions and variations of devices I could not get the decoding to work. Regardless of H.264 vs H.265, Frame Rate, Resolution, Overlay, or any other setting for that matter. I have seen that some capable people are playing around with settings in the actual configuration file, and I am sure SOME people have gotten it to work but I don’t not see it as a viable option as this point in time. More development is needed, and I am a WARP supporter of Parsec myself.
If you DO want to give it a try, I have personally found that the Android APK version V3.150.046.00 seemed to be the closest to working for me across all versions. (You can find it online from APK resources) Coincidentally I noticed that this version of the APK has a lot of options that FUTURE versions remove. Not sure why they decided to remove thinks like the H.265 vs H.264, probably because compatibility wise it was better to just force H.264 and remove the option. Not sure just guessing. I did not have a lot of luck with the current V3.150.078.00 version. Which was a little disappointing but hopefully they are working on it. Even the App resolution is worse, the login screen from .046.00 version looked amazing, now its looks very pixelated like they dropped the main menu resolution.
WORKAROUND
What you need:
A windows based Parsec Host Machine
A windows based Parsec Client Machine
An Android tablet within the last decade, or an Apple Ipad of any generation
A Bluetooth controller of some sort
Bluetooth Headset of some sort
A Bluetooth 5.0 receiver (Sorry Bluetooth 5.0 is leaps and bounds better, get a 5.0 dongle)
Basic Theory:
Parsec Windows works better than any version of Parsec, so we need to ensure that both the HOST and client machines are Windows based. Preferable Windows 10 as this is what used. The client machine does not have to be very powerful, a cheap laptop is a good option, the reason is we are going to be setting this to the resolution of our tablet. Which is most cases is relative low.
After you have your client and hosts setup the next step is the workaround part. As we have said Parsec android is still far from a stable version, so we need to find a way to work around it for now while still using the Parsec software.
Now you have two options here. I would suggest you use both option depending on the game you are playing. Regardless install the following programs to your CLIENT MACHINE as well as your TABLET/IPAD.
Software to Install;
Spacedesk (www.spacedesk.net)
Splashtop Wired XDisplay (https://www.splashtop.com/en-ca/wiredxdisplay)
Once both of those are installed on your CLIENT PC and your TABLET/IPAD. Do the following;
For Splashtop Wired XDisplay you need to turn on USB debugging mode. Google this for your specific device, very easy to do.
For Spacedesk you need to open the application on your CLIENT and read the IP address of this machine (It will be listed on the main page), then on your tablet enter this IP address in the APP to create the wireless connection between your tablet and your Client PC.
Now that both of these tools are configured here is the fun part;
Using Splashtop Wired XDisplay (Wired, HIGHEST RESOLUTION, ZERO LAG)
If you are playing games where FPS and LAG are very important, IE when I play warzone for example. Use Splashtop Wired XDisplay from your client machine to the tablet.
This will basically let you use the tablet as the PRIMARY MONITOR (Make sure to set this in windows display “Only on display 2”) for your client windows machine.
I realize that you could just use the laptop as a the client and not need the tablet, but personally speaking Id rather have a laptop under my couch and just connect a cable with the tablet on my lap then use the laptop itself. In my case my client is a very small M73 Tiny so it basically gives me a display that is just as compact.
…Not the point as we are about to get to the wireless part that you all really care about.
Using Spacedesk (Wireless, Decent resolution, Minor LAG)
I have used spacedesk to play games like CSgo and Warzone but there is a bit of lag, I would say its playable in my opinion as the lag isn’t brutally bad or anything. For basically NON-FPS games I have no issue with the amount of lag here, I play a lot of RPG games in this mode and have no issues.
Start the Spacedesk Host program on your Client PC.
Open the Android APP and connect to the Client PC that we setup earlier when we put in its IP address.
You should now see your full desktop of your client PC, and be able to click Parsec and load into your HOST PC as normal. Except you now have the video feed directly to the tablet by Spacedesk.
Caviate:
To get this to work well you NEED a Bluetooth 5.0 received on the Client PC. I have a 5.0 bluetooth dongle I got off Amazon in my M73T. You setup your controller AND your audio through the client PC directly to your Bluetooth device. So you do not have any addition input lag then you work using parsec on the client pc directly, same with audio.
This means that the only thing the Spacedesk app is taking care of the is the video signal to the device, all the input and audio is direct from the client PC instead of through the tablet.
It just means you need to have the client PC you use (Just buy a cheap laptop and keep it closed at all times, basically using it as a server for Parsec) Both of these tools can be initiated from power on so you don’t actually need any screen. Like in my case I have the M73T Tiny that I can carry around as it is the size of a book, full 64bit windows 10 capable. I just power it on wherever I want to play and walk away from it, the tablet automatically grabs the video feed and gives me the login screen.
I recognize this is not an idea solution, as the ideal solution would be a stable Parsec Android app, but who knows when that will be. So for the time being THIS does work for playing Games Wirelessly as long as you have a spare laptop, or willing to invest very little money.
My M73T Tiny was $80, and it came with a 1TB drive. So basically free lol. They are everywhere, highly recommended as a client machine. Even on my full size 55” TV I stream 1440P through parsec and its flawless.
Example of me running warzone wirelessly.
https://drive.google.com/file/d/1238JsH1vzgoMqtKXJzllPjKgCEqHy5DB/view?usp=sharing
with a wired Splashtop connection the quality is unreal. Try it.
Cheers,
Sniper Fox 22
Forgot to mention. Set your Parsec HOST resolution to that of your tablet. Set your client pc resolution to that of your tablet (most times this happens automatically when you connect to the apps on tablet) it helps that a tablets resolution is lower than most pcs as parsec will run smoother at lower resolutions. At this low a resolution switch from low latency to best quality on your HOST computer as well.
Hi All,
I'm not overly experienced with my pi but looking for some support and hopefully will get better with more use.
I have a Raspberry Pi 3 with Raspberry Pi OS (64 bit), freshly flashed a couple weeks ago. It is running headless, with a wired ethernet connection.
I have installed Portainer and Docker with three different containers. (qBittorrent, Gluten, Zwave2mqtt)
There is a an Aeotec Zwave USB stick installed.
The pi becomes unresponsive every day or every other day. No ability to SSH in.
Historically, the pi worked fine with a similar (though not exact) setup, including the USB stick. This was with the 32bit version of the OS, not using portainer and only the Zwave2mqtt as a docker image.
Would be glad to get log files, but I haven't been able to figure out which log files I need to pull to help diagnose this problem. Where do I start with this kind of troubleshooting?
Thanks!