Hey Pogo.. thanks for the reply...

Assuming you're referring to the alert image generated by Blue Iris and not the camera, there are a couple places to adjust for size and quality. Under the Trigger tab in the 'When Triggered' options -> 'Immediate Actions' there's a selection for 'Hi-Res JPEG files' that may be inadvertently causing problems in the unlikely event that's where you set up your email alerts instead of from the actual 'Alerts' section. The latter would generally use an image based on the options in the Record settings which provides for quality and sizing adjustments that would normally apply to images used for an alert..., more or less.

here are 3 pics of what I'm talking about.. , Goal is to try to get Amcrest_IP8 pic to look like the one for the C520WS.

What specific method is being used to send the emails?

And do you have the sub-stream enabled for the Amcrest?

Thanks for helping me troubleshoot..
No, I do not have sub stream configured.. I will attach a few more pics of the Amcrest config.. Using Make: Generic/ONVIF, Model: *RTSP H.264/H.265/MJPEG/MPEG4 on Media/video/RTSP port 554, Discovery/ONVIF port 80 with Stream profiles of Main: (default) / and Sub: (none)


Not sure what you were referring to regarding 'specific method is being used to send the emails?'
here are a 3 pics of the Amcrest config being used.. maybe they will shed some light on your questions about 'specific methods'

I'd be happy to share any additional information you may need.. and if using Amcrest for Make & Model makes a difference, I'm willing to try it..
Thanks again for your help

'Spcific method' was referring to what actual platform/method was being used; the Tapo/Amcrest vendor-based method for each camera, or Blue Iris..., and whether the Action set was from the Trigger or Alert tab with any associated options from either. I now see how you have it set up for the most part, at least for the Amcrest.

What I would suggest is enabling JPEGs 'When Triggered' in the Record tab to generate your image and play around with the quality and size for an acceptable result. (Seeing the action configuration would possibly be helpful to assist a bit more there also.) I'm also curious about any difference between the Tapo and Amcrest Alert setups.

So for the Amcrest camera Blue Iris config, I would urge use of the substream for a few reasons, not the least of which is CPU resource management. It's a little more to manage and get a handle on since it is the trigger source when active, but sub streams (especially when there are lots of cameras) can cumulatively save a ton of CPU headroom by it only needing to process much less demanding streams for most of the relevant BI functions. The lower display resolutions are hardly noticable when viewing multiple cameras on the desktop simply due to the reduced size of the images. The main stream is activated when a camera is clicked for full screen viewing and/or other types of functionality in a fairly automatic and seamless fashion when all is set up correctly..., which is generally the default settings in most cases.

And to see what may make Blue Iris the happiest with the Amcrest, do a fresh 'Find Inspect' with just the IP address and user/pass and see what it spits out. You should get the make and model of the camera in the resulting readout with Amcrest as Make and and *ProHD/IP.....Main Stream RTSP (or similar) as Model in the Make/Model boxes of the BI configuration. The main profile should be populated with the stream address while the sub stream profile may show 'none'. Clicking the drop down arrow in the box should show the sub stream address selection for adding to the configuration. Going this route may or may not make much difference over the generic ONVIF approach in the bigger picture with the possible exception of the audio format. Then again, it may avoid peculiarities and performance issues that won't occur until certain combinations of mismatched stuff occurs or piles up. Blue Iris is very unforgiving when it gets annoyed or has its feelings hurt. What it WILL do is activate the sub stream for the reasons already mentioned.

Anyway, give the above a test drive around the block and see how it goes. Others may have additional suggestions or clarification as well.

You seem to have a pretty good handle already. The learning curve should continue to be a fairly gentle one if you take it a step at a time.

An update.. followed suggestion regarding the Amcrest. I deleted the camera and start over from the beginning.. Plugged in IP addy with user/psw and used the Find/Inspect function. Make: Amcrest, Model: *ProHD/IP.....Main Stream RTSP. Media/video/RTSP port: 554, Discovery/ONVIF' port:80. Under Video tab, Image format- Size: 960x 480, Max rate: 15 fps, Anamorphic is checked.

Stream profile: Main stream was selected. Sub identified 2 MediaProfiles of substreams1 and substream2 were identified. When using either sub-stream, the camera windows became fuzzier and lower res. Also noticed that video stream in the camera windows were choppy. After much trail & error, for Sub stream, I used the MediaProfile:Main stream.. image became sharp and motion was no longer choppy. Topping it all off, the Gmail notification, image was no longer 'overblown'.

I have been using the import/export function quite a bit.. to 'save' my configs as I went along.. so I can restore to a config that I had previously use..
Still a bunch of tinkering / massaging to fine tune trigger/record/alert (trigger>Motion Sensor>Config Object Detection, Use Zones + Hotspots) to avoid missing alerts or false alarms.

Attempted to use the AI function with no success.. BI hangs or becomes sluggish.. unusable!. When the spirit moves me, I'll give it another try..
First things first.. let see if BI in its current configuration is stable, capturing, and displaying all the 'necessary' stuff.. then I'll embellish with the bells & whistles..

apple2k wrote: ↑Tue Jun 11, 2024 3:48 am An update.. followed suggestion regarding the Amcrest. I deleted the camera and start over from the beginning.. Plugged in IP addy with user/psw and used the Find/Inspect function. Make: Amcrest, Model: *ProHD/IP.....Main Stream RTSP. Media/video/RTSP port: 554, Discovery/ONVIF' port:80. Under Video tab, Image format- Size: 960x 480, Max rate: 15 fps, Anamorphic is checked.

Stream profile: Main stream was selected. Sub identified 2 MediaProfiles of substreams1 and substream2 were identified. When using either sub-stream, the camera windows became fuzzier and lower res. Also noticed that video stream in the camera windows were choppy. After much trail & error, for Sub stream, I used the MediaProfile:Main stream.. image became sharp and motion was no longer choppy. Topping it all off, the Gmail notification, image was no longer 'overblown'.

I have been using the import/export function quite a bit.. to 'save' my configs as I went along.. so I can restore to a config that I had previously use..
Still a bunch of tinkering / massaging to fine tune trigger/record/alert (trigger>Motion Sensor>Config Object Detection, Use Zones + Hotspots) to avoid missing alerts or false alarms.

Attempted to use the AI function with no success.. BI hangs or becomes sluggish.. unusable!. When the spirit moves me, I'll give it another try..
First things first.. let see if BI in its current configuration is stable, capturing, and displaying all the 'necessary' stuff.. then I'll embellish with the bells & whistles..

Cool beans. Mission accomplished..., for the most part.

On the sub streams: They are lower resolution and will look like crap compared to 4K unless being viewed in a small display situation such as in BI desktop console view among a bunch of other cameras also at their sub stream resolutions..., or remotely via a phone app on a 2 1/2 x 5 display over a low bandwidth connection or even on a laptop or computer that lacks the horespower to process 4K, (let alone H.265 4K.) That's generally their function from the 'viewability' aspect.

On the other hand, sub streams perform very useful utility roles in the background of most any video camera surveillance system, not the least of which is diminishing the role of the CPU in processing massive amounts of hi resolution video data unnecessarily when it is neither being viewed or processed/encoded for recording and storage..., among other things such as triggers and alerts, etc.

Think of sub streams as the worker bees of the system doing the heavy lifting to keep the queen happy until it's time for her to emerge in all her glorious Super UHD 4K wonder...., which generally occurs automatically by simply double clicking something or reviewing stored files, etc. The 4K stuff is still there, but only when called upon to be viewable or processed further than its stored state -- if the system and camera configuration are set up to work accordingly.

That gets us to the camera(s). A common issue that causes performance problems when just getting acquainted with Blue Iris is going by what the vendor provides as the optimal settings for their devices. They may be appropriate for their particular (proprietary) ecosystem or version of a standard (ONVIF) or interpretation/implementation of a protocol (RTSP) or video codec (e.g. MPEG/H.264/H.265), but may not play nice with how Blue Iris wants to process things on its own terms -- which are generally very accommodating, but with a few notable exceptions especially relating to decoding and especially with higher resolution cameras at higher frame and bit rates.

Stutter and jerky streams/recordings are usually the result of mismatches between the camera encoding and what Blue Iris is capable of decoding effectively. The most common mismatch is caused by 'Smart Codec', H.264/5 'High', '+', 'Super', or whatever 'extra' designation is applied the their particular version of H.264 or H.265 encoding.
Don't use these settings. Only use H.264 or H.265 alone.

Another issue with Blue Iris is what some consider just poor H.265 processing in general. Some will obviously debate this. Others have yet to find H.265 ready for prime time even though every vendor out there would have you believe otherwise. When having weird stuttering or tearing or artifact filled streams, check the codec in the camera's webUI configuration. If it's not set to straight up H.264, change it. Reboot things and your problems will likely disappear.

Anamorphic is usully only active if a non-standard image size exists for the sub-stream. The third sub-stream is rarely used.

AI is a whole other bag o' snakes. My advice there is to learn the basics of BI's motion and object detection features before jumping head first into CPAI and all the issues that come with it -- and they are numerous on every level no matter what anyone would like to have you believe otherwise. Also bear in mind that sub streams are used for motion and object detection triggering when active. This also alleviates additional strain on processing resources.

The more experienced you become with how BI can directly process triggers from an AI camera itself via ONVIF, the less time you'll waste and less headaches you'll have..., at least initially.

Good luck and have fun with it!