> You are trying to convert a RAW 1080p @ 60fps (1988671 kb/s) stream to
> h.264 504p @ 30fps (2100Kb/s), the raspberry PI *DOES NOT* have the
> CPU power and the USB bus cant handle 248.583875 Mbytes/s
Thanks Tom, how did you calculate the 248.583875 Mbytes/s?
> Please remember that this list is about the ffmpeg software, it's not a
> general video processing list.
>
> z!
Thank you Carl for your reply.
(apologies for any misused of the list)
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
Am Sa., 16. Mai 2020 um 22:02 Uhr schrieb Edward Park :
> I think this might have been a typo? in vf_colorkey.c:48 the "diff"
> isn't normalized to 0 - 1, but to 0 - 3.
> double diff = sqrt((dr * dr + dg * dg + db * db) / (255.0 * 255.0));
>
> changing it to
> double diff = sqrt((dr * dr + dg *
Hi,
I think this might have been a typo? in vf_colorkey.c:48 the "diff" isn't
normalized to 0 - 1, but to 0 - 3.
double diff = sqrt((dr * dr + dg * dg + db * db) / (255.0 * 255.0));
changing it to
double diff = sqrt((dr * dr + dg * dg + db * db) / (3 * 255.0 * 255.0));
seems to fix it for me.
Am Sa., 16. Mai 2020 um 21:06 Uhr schrieb Carl Zwanzig :
>
> On 5/16/2020 11:05 AM, Carl Eugen Hoyos wrote:
> > My personal experience, note that nothing above points to using msvc.
>
> Just wanted to know if there some technical reasons I'd overlooked, doesn't
> sound like it.
>
> Some other OS
On 5/16/2020 11:05 AM, Carl Eugen Hoyos wrote:
My personal experience, note that nothing above points to using msvc.
Just wanted to know if there some technical reasons I'd overlooked, doesn't
sound like it.
Some other OS projects that incorporate ffmpeg libs do use msvc, such as
CasparCG.
Am Sa., 16. Mai 2020 um 20:03 Uhr schrieb Carl Zwanzig :
>
> On 5/16/2020 10:53 AM, Carl Eugen Hoyos wrote:
> > Probably unrelated: I strongly suggest to use wsl to compile
> > FFmpeg for Windows.
>
> Not to disagree, but what forms that preference?
My personal experience, note that nothing above
On 5/16/2020 10:53 AM, Carl Eugen Hoyos wrote:
Probably unrelated: I strongly suggest to use wsl to compile
FFmpeg for Windows.
Not to disagree, but what forms that preference?
(I use mingw wherever possible and msvc when forced (and from the command
line, if possible). And I'm sure I've
Am Sa., 16. Mai 2020 um 19:51 Uhr schrieb Forough Majidi via
ffmpeg-user :
>
> On my system nvidia drivers is installed and I installed
> mingw-w64-x86_64-opencl-icd-git
> and I built FFmpeg as following:
> 1-x86-x64 cross tools command prompt for VS 2019 run as administrator and
> Open mingw64
On my system nvidia drivers is installed and I installed
mingw-w64-x86_64-opencl-icd-git
and I built FFmpeg as following:
1-x86-x64 cross tools command prompt for VS 2019 run as administrator and Open
mingw64 from the command prompt
2-cd c:\ffmpeg_test\ffmpeg
3-./configure -- toolchain=msvc
Yes, Carl, this looks very similar indeed... Good thing they have been
notified, it's a very weird issue.
‐‐‐ Original Message ‐‐‐
On Saturday, May 16, 2020 7:01 PM, Carl Eugen Hoyos wrote:
> Am Sa., 16. Mai 2020 um 17:30 Uhr schrieb Crazy Red Elephant via
> ffmpeg-user
Am Sa., 16. Mai 2020 um 18:11 Uhr schrieb John Riselvato
:
>
> On Sat, May 16, 2020 at 12:03 PM Carl Eugen Hoyos
> wrote:
>
> > Am Sa., 16. Mai 2020 um 17:52 Uhr schrieb John Riselvato
> > :
> > >
> > > This is a known bug.
> >
> > Would you mind defining "known"?
> As in it's not the first time
On Sat, May 16, 2020 at 12:03 PM Carl Eugen Hoyos
wrote:
> Am Sa., 16. Mai 2020 um 17:52 Uhr schrieb John Riselvato
> :
> >
> > This is a known bug.
>
> Would you mind defining "known"?
>
> Please find out what top-posting means and avoid it here.
>
> Carl Eugen
>
Am Sa., 16. Mai 2020 um 17:30 Uhr schrieb Crazy Red Elephant via
ffmpeg-user :
>
> Is it just me or the devs forgot letter "c" somewhere in the code of the new
> build of ffmpeg? When dealing with a .m3u8 file, I'm getting errors like
> "Unable to open resource: cmy_actual_filename.ts" while
Am Sa., 16. Mai 2020 um 17:52 Uhr schrieb John Riselvato
:
>
> This is a known bug.
Would you mind defining "known"?
Please find out what top-posting means and avoid it here.
Carl Eugen
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
This is a known bug. You'll just have to use it multiple times before you
get it to actually remove all the colors.
http://johnriselvato.com/ffmpeg-how-to-remove-all-colors-except-one-from-a-video/
On Sat, May 16, 2020 at 3:41 AM Michael Koch
wrote:
> Hi,
>
> I just found out that the colorhold
Am 16.05.20 um 17:30 schrieb Crazy Red Elephant via ffmpeg-user:
> Is it just me or the devs forgot letter "c" somewhere in the code of the new
> build of ffmpeg? When dealing with a .m3u8 file, I'm getting errors like
> "Unable to open resource: cmy_actual_filename.ts" while there's no letter
Is it just me or the devs forgot letter "c" somewhere in the code of the new
build of ffmpeg? When dealing with a .m3u8 file, I'm getting errors like
"Unable to open resource: cmy_actual_filename.ts" while there's no letter "c"
before my filenames in any of the filenames in my chunklist. One of
Am Do., 14. Mai 2020 um 21:50 Uhr schrieb Gabriel Balaich
:
>
> So just read a question on stack exchange in-which someone was experiencing
> something similar to me, it looked like the issue may have been the audio
> codec being used was limited to one thread for processing, here is the
>
Hi,
I just found out that the colorhold filter doesn't behave as described.
In the documentation is written:
similarity
Similarity percentage with the above color. 0.01 matches only the exact
key color, while 1.0 matches everything.
But when I use similarity=1.0, it matches a wide range of
20 matches
Mail list logo
