Hi Mark, thanks for your suggestion too.
On Tue, 6 Aug 2024 at 23:34, Mark Filipak wrote:
>
> Hey Rob,
>
> On 06/08/2024 08.40, Rob Hallam wrote:
> > Hi,
> >
> > I'd like to programmatically detect the 'busiest' parts of a video- ie
> > the most visually active areas. I am leaving audio aside for
Might this be achieved simply by detecting the differences between adjacent
frames?
P
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffm
> On 7 Aug 2024, at 11:04, Phil Rhodes via ffmpeg-user
> wrote:
>
> Might this be achieved simply by detecting the differences between adjacent
> frames?
Sleeping cat
Cut to:
Plant on windowsill
Bouke
> P
> ___
> ffmpeg-user mailing list
> ffmp
Well, sure, but, you know - several frames in a row.
Looking at compression performance would see what you just described as a lot
of activity, too.
I'm thinking of the minimum CPU approach.
On Wednesday 7 August 2024 at 10:12:30 BST, Bouke / Videotoolshed
wrote:
> On 7 Aug 2024, at
> > On 7 Aug 2024, at 11:04, Phil Rhodes via ffmpeg-user
> > wrote:
> >
> > Might this be achieved simply by detecting the differences between adjacent
> > frames?
>
>
> Sleeping cat
> Cut to:
> Plant on windowsill
> Bouke
Heh.
Interesting thought. Question is- how do you detect differences?
Rob Hallam wrote:
> I'd like to programmatically detect the 'busiest' parts of a video- ie
> the most visually active areas. I am leaving audio aside for the
> purposes of considering this.
>
> I figured it might be possible by looking at one / more of:
> [...]
> - frame differences -- cou
On Wed, 7 Aug 2024 at 10:56, Oliver Fromme wrote:
>
> Rob Hallam wrote:
> > I'd like to programmatically detect the 'busiest' parts of a video- ie
> > the most visually active areas. I am leaving audio aside for the
> > purposes of considering this.
> >
> > I figured it might be possible by l
