Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Raspberry Pi 4 #1969

Closed
Chiny91 opened this issue Jun 24, 2019 · 39 comments
Closed

Raspberry Pi 4 #1969

Chiny91 opened this issue Jun 24, 2019 · 39 comments
Labels
enhancement

Comments

@Chiny91
Copy link

Chiny91 commented Jun 24, 2019

Surprising many by the look of it, the new R Pi 4 is out. Alongside the extra cpu grunt, the long-desired "full throughput gigabit ethernet" should be very helpful to motioneyeos with multiple cameras.

All in due course, in the fullness of time, naturally. My existing 2 R Pi with motioneyeos remain ultra-reliable running for months on end unattended, and a third R Pi motioneye cam with the @jasaw AI mod still beating my doorbell, and rock stable.
@wronglebowsk
Copy link

As someone new to the project I am curious to understand better what the current bottlenecks are in the existing hardware and how the new hardware could be best leveraged to make for a better system.

Is the most common use case currently multiple Pi-Zero or Pi-X(Fast Network Mode) with one master Pi encoding and saving to disk?

If the new h264 encoder on Pi 4 CPU allows for 1080p 30 FPS encoding does that mean we can have the full speed while maintaining the smart features we otherwise lose in "Fast Network Mode"?

Either way I'm very excited for the new hardware and the existing h264 Fast Network Mode in the current pre-release. Thanks for the hard work!

@jasaw
Copy link
Collaborator

jasaw commented Jun 25, 2019 •
edited
Loading

Previously, the bottleneck was on Ethernet throughput, CPU (maybe), GPU H264 encoder, memory bandwidth, USB2 port (if you store your media on external disk).
Based on the benchmarks I've seen so far, the RPi4 removes all the above bottlenecks, except for the GPU part. The GPU has been upgraded, gained HEVC hardware decoder, slight speed increase, but no huge improvement.

@MrJBSwe
Copy link

MrJBSwe commented Jun 25, 2019 •
edited
Loading

Built for the kill : NanoPi M4
https://www.friendlyarm.com/image/catalog/description/M4SSD_en_04.jpg

@ericjanvanputten
Copy link

Do I assume right I cannot take the Pi 3 image and we need to wait for the Pi 4 image? :)
Hoping this can replace 2 Pi 3's (one at 40% and the other 95% load)

@weiserhei
Copy link

Do I assume right I cannot take the Pi 3 image and we need to wait for the Pi 4 image?

I get no hdmi output on RPI4 using motioneyeos and trying to run motioneye on raspbian buster (even on PI3) also fails for me (pycurl error).

@wronglebowsk
Copy link

Do I assume right I cannot take the Pi 3 image and we need to wait for the Pi 4 image?

I get no hdmi output on RPI4 using motioneyeos and trying to run motioneye on raspbian buster (even on PI3) also fails for me (pycurl error).

The GPU in the Pi4 is completely new and different and so is the rendering engine used in Buster. It's going to take real time and work for anything that ran on prior Pi's or versions of Raspbian. It's not even working on RetroPie yet which has significantly more developer input involved. Let's just be patient and wait for them to make a pre-release build. I'm not sure where they are located geographically but they may even have a hard time getting their hands on the hardware.

@rotrials
Copy link

@Nameback check the wiki 😊

Can motionEyeOS be ported to [insert-your-board-here]?

I don't buy boards just to port motionEyeOS on them. If you really want me to try to port motionEyeOS to your favorite board, feel free to send me one and I'll do my best to make motionEyeOS run on it. Also please note that I won't return it to you, given that once motionEyeOS is available for that platform, I'll use it to test new builds.

@PieBru
Copy link

PieBru commented Jul 1, 2019

I would not hurry up to adopt the new Raspi 4.
Not all that glitters is gold, as [Andreas Spiess] pointed out in his video: https://www.youtube.com/watch?v=0diTHAmVbhc
Piero

@jasaw jasaw mentioned this issue Jul 4, 2019
Closed
@diegoweb
Copy link

diegoweb commented Jul 9, 2019

Can someone tell me if Raspberry Pi 4 would be able to handle 3 or 4 IP cameras in 1080p? I was planning to buy some Dahua Starlight cameras.

@ccrisan
Copy link
Collaborator

ccrisan commented Jul 15, 2019

The latest nightly build has rpi4 support.

@ccrisan ccrisan closed this as completed Jul 15, 2019
@tkmilbaugh
Copy link

I have tried out the latest nightly build "motioneyeos-raspberrypi4-dev20190715", and was able to boot and configure on a pi 4 with 2GB RAM. The only issue that I have found so far is that it will panic and reboot if I don't connect to a wired network. I have configured the wireless network properly, IMHO:

  • I used the same wpa_supplicant.conf file that I have used with 3 other raspberry pi models (zeroW, 3B+, 3A+)
  • I placed the wpa_supplicant.conf file on the card before booting for the first time (in that same location as the start.elf file).

@ccrisan
Copy link
Collaborator

ccrisan commented Jul 16, 2019

@tkmilbaugh thanks for the feedback. I'll try to reproduce myself these wifi problems and get back to you. Let's keep the issue open for now.

@ccrisan ccrisan reopened this Jul 16, 2019
@wronglebowsk
Copy link

wronglebowsk commented Jul 17, 2019 •
edited
Loading

My Pi 3+ died so I'm using a Pi 4 1GB model with the nightly build as my network recorder device. Using the new HEVC introduces dramatically reduced performance. It's under 1 FPS. I have it configured with 2x Network Cameras(Pi Zero W) and using H264/OMX quality and speed is solid. I wanted to adjust my GPU memory allocation since I'm using OMX but I don't see an option to. Does this still need to be implemented on the Pi 4 build?

@jasaw
Copy link
Collaborator

jasaw commented Jul 17, 2019

RPI4 does not have a hardware HEVC encoder. It only has HEVC decoder. Doing HEVC encoding in software is expected to be extremely slow.

@ciggybumly
Copy link

I have tried out the latest nightly build "motioneyeos-raspberrypi4-dev20190715", and was able to boot and configure on a pi 4 with 2GB RAM. The only issue that I have found so far is that it will panic and reboot if I don't connect to a wired network. I have configured the wireless network properly, IMHO:

I used the same wpa_supplicant.conf file that I have used with 3 other raspberry pi models (zeroW, 3B+, 3A+)
I placed the wpa_supplicant.conf file on the card before booting for the first time (in that same location as the start.elf file).

New user here. Im having the same issue. Ive taken the wpa_supplicant.conf from a fresh rasbian install and was working fine. Im getting the same failed message when trying to use the wifi, wired is fine so far. I also find, when I put the card back into windows, the wpa_supplicant.conf has disappeared.

@rusticranger
Copy link

rusticranger commented Jul 19, 2019 •
edited
Loading

I have exactly the same issue as above after following all advice - using the Pi4 with 4GB and another with 2GB - both fail on the wpa_supplicant.conf as placed in the above - and disappears when putting the card back in Windows10 - if I boot off the Rasbian disk all is good for both wireless and wired.

MotionEyeOS build "motioneyeos-raspberrypi4-dev20190715" works perfectly if on wired connection.

@ccrisan ccrisan closed this as completed Jul 26, 2019
@ccrisan
Copy link
Collaborator

ccrisan commented Jul 26, 2019

Fixed via 907cc4d.

@kay-jahnke
Copy link

Just a quick feedback: I'm using the Raspi 4 (2 GB version) with two Trust Webcams. The Rapsi is in the closed box it gets delivered with, so it goes to over 80°C and then throttles. The streams on both webcams run flawlessly though. Good work on that!

@jlr4u
Copy link

jlr4u commented Aug 4, 2019

I am trying to install motioneye on raspbian buster on a 4 gig pi-4 that boots off of a 500 gig sdd.
I was attempting to use https://github.com/ccrisan/motioneye/wiki/Install-On-Raspbian
Step 2 fails because libmariadbclient18 has been demoted so I used libmariadb3 instead.
Step 5 (sudo pip install motioneye) fails not finding /tmp/pip-install-xix646/pycurl/

Is there anything I can do to get this up and running?

@jlr4u
Copy link

jlr4u commented Aug 4, 2019

Just a quick feedback: I'm using the Raspi 4 (2 GB version) with two Trust Webcams. The Rapsi is in the closed box it gets delivered with, so it goes to over 80°C and then throttles. The streams on both webcams run flawlessly though. Good work on that!
Try this 👍 https://www.amazon.com/dp/B07V1QRXTT/ref=cm_sw_em_r_mt_dp_U_e.SrDb0YC19QX
Mine was running in the upper 70s and with this open side case and fan, It is now in upper 40s.

@FCPercival
Copy link

FCPercival commented Aug 28, 2019 •
edited
Loading

Can someone tell me if Raspberry Pi 4 would be able to handle 3 or 4 IP cameras in 1080p? I was planning to buy some Dahua Starlight cameras.

I need this answer too, but i need to install 6 cameras in 1080p.
Someone that can reply?

@h4d3z
Copy link

h4d3z commented Nov 17, 2019 •
edited
Loading

Can someone tell me if Raspberry Pi 4 would be able to handle 3 or 4 IP cameras in 1080p? I was planning to buy some Dahua Starlight cameras.

I need this answer too, but i need to install 6 cameras in 1080p.
Someone that can reply?

I also would love to know this.
Does it run alot better on the 4 ? 2 GB or 4 GB?
If it can do 4 cams on 720 it is also acceptable for me

@RafaelK34
Copy link

Hi,

I would be also very interested how the Raspberry PI 4 performs with MotionEye and 4 IP cameras.
Any feedback is really appreciated… also with other configurations.

Many thanks in advance…

@bradleyproject
Copy link

Hi,

I am trying to complete my final year project at university, which is a vehicle surveillance system. I have come across motioneyeOS and it has ticked so many boxes in terms of functionality relating to my project. However, one functionality is that it will be able to run off 4G technology, which will use my sim card to provide the portable internet connection. My question is, am i able to use 4G with motioneye or will i be limited to use a WiFi or Ethernet connection ?? If someone could please shed some light on this it would be greatly appreciated.

I have watched some tutorials on how to set up the wifi and it is done quite easily using wpa_supplicant.conf file. I wonder now is it possible for me to get an SSID for my 4G as i have set the password on the mobile hotspot already. The reason i ask is because i have already located the ip address which the 4G connection uses meaning if done i will be able to assign my cameras under this ip address. Any information shared will be awesome. Many thanks in advance guys and gals

@jasaw
Copy link
Collaborator

jasaw commented Jan 18, 2020

The easiest is to get a portable wifi access point with 4G connection. They are quite readily available. Search for Nighthawk M1 MR1100 LTE Router. I've used this particular one before, it's not bad.
All you need to do is to configure your motioneyeos device to join this wifi network.

@bradleyproject
Copy link

bradleyproject commented Jan 18, 2020 via email

@bradleyproject
Copy link

bradleyproject commented Jan 18, 2020 via email

@jlr4u
Copy link

jlr4u commented Jan 18, 2020 via email

@jasaw
Copy link
Collaborator

jasaw commented Jan 20, 2020

@bradleyproject You're right that only Wifi has SSID. 4G works very differently depending on your 4G hardware. With the nighthawk portable wifi access point, you just stick in your SIM card, configure the router via its web interface (you can configure the Wifi SSID and password at this point). Now you have a portable Wifi network with internet connection. You can configure your MotionEyeOS device to join this Wifi network by setting the SSID and password in the wpa_supplicant.conf file.

If you have Ethernet connection to your portable router, then there is no need to configure wifi on your MotionEyeOS, i.e. no need wpa_supplicant.conf file.

Whether using ready-made off-the-shelf parts meet your final year project requirements or not is another question.

@Ngiri67
Copy link

Ngiri67 commented Nov 11, 2020

Hi there. I hope someone can point me in the right direction.
So I flashed the latest motioneyeos-raspberrypi4-20200606.img.xz, connected the camera and an ethernet cable and tried to boot my Pi4 8GB. It starts to boot and then I get "This board requires new software" and it stops booting.
Any ideas?

@starbasessd
Copy link

starbasessd commented Nov 11, 2020 via email

@Ngiri67
Copy link

Ngiri67 commented Nov 11, 2020

Thank you starbasessd . I'll give it a go right now.

@roger-
Copy link

roger- commented Nov 11, 2020

You have to update the eeprom software

I have a remotely connected RPi4, does this mean updating to the latest motioneyeos could brick it until I update the firmware?

@starbasessd
Copy link

starbasessd commented Nov 11, 2020 via email

@starbasessd
Copy link

starbasessd commented Nov 11, 2020 via email

@Ngiri67
Copy link

Ngiri67 commented Nov 11, 2020

Ok, so I ran through the steps you gave. It took a long time to get all the upgraded files and "diversions" in place. Installed the latest bootloader and then tried a fresh Motioneyeos and still getting that error about the board needing new software.
Hmm, what to do?

@starbasessd
Copy link

starbasessd commented Nov 11, 2020 via email

@starbasessd
Copy link

starbasessd commented Nov 11, 2020 via email

@Ngiri67
Copy link

Ngiri67 commented Nov 11, 2020

Thank you. The eeprom was up to date and it still didn't work. Then I tried the dev version and it booted immediately.

Now to try it out.

@gitberry gitberry mentioned this issue Aug 9, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Milestone
No milestone
Development

No branches or pull requests