ESP32-P4 is now ESP32-P4X starting at revision 3.x

Just saw this and people may be aware but didn't see any information about this. Starting at revision 3.x it's now the P4X. While lower revisions only ran at 360Mhz it seems like the main issue was h264 hardware acceleration never really worked. All current P4 (revision 1.x) boards, the hardware h264 encoder ONLY accepts O_UYY_E_VYY pixel format input, and basically no cameras output to that. This makes using the hardware h264 encoder pointless because you have to use slow SW to convert the format.

That and some power fixes, runs at 400Mhz among other things (see links below for all changes). Non issue except using the CSI output which is probably why, to my understanding, the CSI interface didn't work in ESPHome granted the P4 is still very beta/alpha. Espressif replaced all their current development boards with the P4X version but I had bought some waveshare POE P4 boards that I was planning to use as dedicated camera's but that's obviously not happeninf.now. I read you could get maybe 14fps at 720p using mpeg software conversation but can't confirm that.

Espressif says it's a revision change but that usually doesn't come with a name change. Just thought I would let anyone know so they don't buy one for camera use because it won't work as advertised. Still works great as tablet devices like the M5Stack M5Tab outside camera functionality. Considering that this was announced when S31 boards started shipping I would imagine this is a non issue for the S31. Just an FYI. Revision 1.3 chips are EOL now and no more will be made.

All changes:

I use a waveshare dev board with a ov5647 camera and can get 27fps @ 1080p if i increase the buffers to 3 or above. Normally i get 15fps with 2 buffers.

Hmm,... Well I stand corrected. I was basing that on this post were the poster did post to GitHub pointing out the issue but I'm also not a dev so I was taking his word for it. The P4X also come with a suite of image processing algorithms so that.made me think it was a legit issue. I doubt the entire 360Mhz vs 400Mhz matters in 99% of use cases. There were some power issues, either that or poor engineering by M5Stack on the M5Tab as it has an odd warning on their detailed description page.

Regardless, do you mind posting your yaml if it's working in ESPHome? If it's working via some other method I understand but if you can still add it via RTSP or IP in HA a GitHub link would be appreciated I have that same camera and was struggling to get it to work and kind of gave up after reading that post. Thanks for the correction and feedback!

From the link above:

the hardware h264 encoder ONLY accepts O_UYY_E_VYY pixel format input, and basically no cameras output to that. This makes the using the hardware h264 encoder pointless because you have to use slow SW to convert the format. Here is the code where it's gated:

https://github.com/espressif/esp-h264 -component/blob/master/esp_h264 /interface/include/esp_h264_types.h#L252

There are way more differences than I thought on rev > 3, faster processor (400mhz vs 360), a suite of image processing algorithms, faster sd card support. Here is a list of all the changes (there are a lot).
https://documentation.espressif.com/esp32-p4-chip-revision-v3.x_user_guide_en.pdf