Hello everyone!
Metadata-related questions again :D
**Is there a way to map metadata values by their key?**
For example, I've got a bunch of MKVs with RIFF tag keys that are lost
when I convert into an MP4 container:
INAM (Title)
ICRD (Creation Date)
IARL (Archival location)
ITCH
Hello everyone :)
I just realized that when using the concat muxer (with a list of
filenames in a textfile), embedded metadata (title, date, etc) of the
source files is left behind and not copied through to the created output.
I understand that it's not trivial/clear to decide *which*
Hi Paul.
On 23.03.21 19:35, Paul B Mahol wrote:
On Tue, Mar 23, 2021 at 4:58 PM Peter B. wrote:
Thanks for the info.
What is the "fresh setts bitstream filter" - and could you point me to
an example how to use it in this case?
See the top of the page for general descrip
Hi Paul!
On 22.03.21 20:15, Paul B Mahol wrote:
It is warning for lazy devs.
If for any reason it errors in muxing stage, you may use fresh setts
bitstream filter to fix it.
Thanks for the info.
What is the "fresh setts bitstream filter" - and could you point me to
an example how to use it
. Fix your code
to set the timestamps properly
--
Whom is this warning for, and which "code" needs to be changed "to set
the timestamps properly"?
Any information is greatly appreciated :)
Thanks in advance!
Peter B.
FFmpeg commandline and complete
(EDL) [2], but I'd
already be happy for some rudimentary support like "start/stop/name".
I'd finally like to get rid of my yet-another-bash-wrapper hacks ;)
I'm grateful for any suggestions,
Peter B.
# Links:
[1]
https://ffmpeg.org/ffmpeg-formats.html#segment_002c-stream_005fse
On 10.10.20 15:15, Mark Himsley wrote:
On Fri, 2 Oct 2020 at 14:28, Tobias Rapp wrote:
ffmpeg -i $INPUT ... -pix_fmt +yuv420p \
-filter:v "format=pix_fmts=yuv420p,setrange=full,..."
@Tobias:
This is an interesting syntax. I haven't used that filter option before.
Thanks for the tip!
On 29.09.20 09:56, Christian Ebert wrote:
How about doing quick diagnosis with ffprobe before you start,
something like:
ffprobe -v error \
-print_format default=noprint_wrappers=1:nokey=1 \
-select_streams V -show_entries stream=pix_fmt
and make the command depend on the result?
Thanks for
Hi Paul! :)
On 24.09.20 09:55, Paul B Mahol wrote:
On Wed, Sep 23, 2020 at 11:31:43PM +0200, Peter B. wrote:
Hi Ted,
On 11.09.20 14:03, Ted Park wrote:
My problem is, that I have literally hundreds (actually more than 1000+) of
these H.264/yuvj420p files that are to be auto-converted
/ffmpeg), but I'd also be curious
about the status with AMD GPUs?
Thank you very much in advance!
Peter B.
--
# Some related links:
https://stackoverflow.com/questions/44510765/gpu-accelerated-video-processing-with-ffmpeg
https://www.phoronix.com/scan.php?page=news_item=FFmpeg-OpenVINO-GPU
https
changes to the archival
recordings.
That's also great fun, actually! :)
Still grateful for a "-pix_fmt +" suggestion :)
Thanks!
Peter B.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To
Hi again :)
I thought this was solved, but...
On 10.09.20 15:53, Paul B Mahol wrote:
On Tue, Sep 08, 2020 at 04:12:30PM +0200, Peter B. wrote:
Dear Paul,
On 07.09.20 23:57, Paul B Mahol wrote:
On Mon, Sep 07, 2020 at 11:20:10PM +0200, Peter B. wrote:
Thanks for pointing that out.
I've
Dear Paul,
On 10.09.20 15:53, Paul B Mahol wrote:
The streamhash matches, and the color interpretation metadata seems to be
identical to the source:
* Source video (h.264):
yuvj420p(pc, smpte170m/bt709/bt709)
* Target video (ffv1):
yuv420p(pc, smpte170m/bt709/bt709)
This is
Dear Paul,
On 07.09.20 23:57, Paul B Mahol wrote:
On Mon, Sep 07, 2020 at 11:20:10PM +0200, Peter B. wrote:
[...]
The source video is: yuvj420p(pc, smpte170m/bt709/bt709)
The output video is: yuv420p(pc, smpte170m/bt709/bt709)
What would be the right commandline to losslessly convert
-
regardless if I set the color range :(
Thanks in advance for any hints!
Peter B.
Here's what I've tried so far:
(Console output below)
//
FFMPEG="ffmpeg-4.3.1"
VIDEO_IN="../MVI_1522.MOV"
clear
$FFMPEG -i $VIDEO_IN -n -an -c:v ff
Dear Paul,
On 26.08.20 21:56, Paul B Mahol wrote:
On 8/25/20, Peter B. wrote:
I would be very interested in more information about these messages.
Especially regarding "parser not found for codec ffv1"?
That is only relevant for codecs that actually work only if parsers are ena
codec ffv1"?
Thank you very much in advance,
Peter B.
Complete commandline and (hopefully) uncut console output as follows:
// ---
ffprobe started on 2020-08-25 at 15:14:58
Report written to "ffprobe-20200825-151458.log"
Log level: 48
Command li
On 18/03/2020 14:29, Kieran O Leary wrote:
On Wed 18 Mar 2020, 12:54 Peter B., wrote:
Oh, and yes: absolutely correct! Color information is gone.
Is there any way that this kind of metadata can also be transferred -
even if I don't explicitely know it's there?
I raised this before and I think
Thanks Ulf, Thanks Paul!
On 18/03/2020 11:14, Paul B Mahol wrote:
On 3/18/20, Ulf Zibis wrote:
Hi Peter,
you can use "-map_metadata 0".
It copies all possible metadata from input to output.
"-map_metadata 0": Ah, how can I have overlooked that?
Thank you!
Now more metadata is present in
Hi everyone!
Is it possible to ask/force FFmpeg to keep as many metadata fields as
technically possible when transcoding or rewrapping?
I understand that not all (container-)formats support the same metadata
fields, but I've noticed for example that when rewrapping, not all
metadata fields
ole output) question scenarios.
Thank you very much!
Pb
On 07/11/2019 00:21, Carl Eugen Hoyos wrote:
Am Do., 7. Nov. 2019 um 00:09 Uhr schrieb Carl Eugen Hoyos :
Am Mi., 6. Nov. 2019 um 23:40 Uhr schrieb Peter B. :
Hashing for fixity and transfer-checking seems to be quite a bottleneck
for arc
Thank you very much in advance,
Peter B.
PS:
I also found a possibly related claim in a Stackoverflow answer that the
hashing functions are not implemented as fast as they could be:
https://stackoverflow.com/questions/16122067/md5-vs-crc32-which-ones-better-for-common-use/354
is a good number for most resolutions.
Nevertheless:
I guess you will need more cores to play that content.
Nice greetings!
Peter B.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, v
On 06/08/2019 13:31, Moritz Barsnick wrote:
> Yeah, too obvious. I was looking for "0:1", but the first digit is
> meaningless, and the second one is just the stream index (which I use
> to iterate anyway).
> I'll try to rework it to give the "hash" muxer a "-per_stream" boolean
> option, then I
Hi Paul!
On 05/08/2019 16:25, Paul B Mahol wrote:
> On Mon, Aug 5, 2019 at 4:16 PM Peter B. wrote:
>
>> [...]
>> For example, instead of "CRC32=" let's say:
>> "v:0:CRC32=...
>> v:1:CRC32=...
>> a:0:CRC32...
>> a:1:CRC32...
&g
Dear Moritz,
Thank you for your explanation!
On 03/08/2019 14:07, Moritz Barsnick wrote:
> I believe in using the right tools for the right tasks. If it can be
> glued together with a script, why worry about modifying an existing
> program to do the same?
I completely agree, but... ;)
One
Hi everyone :)
I assume no answer means there's no option to do that.
Would anyone be willing to implement it?
And how much could that approximately cost?
Thank you very much in advance,
Peter B.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On 29/07/2019 15:48, Reindl Harald wrote:
>
> Am 29.07.19 um 11:51 schrieb Peter B.:
>> Just to be noted:
>> This use case is merely using PHP as scripting language instead of e.g.
>> BASH. No Apache, no webserver, just PHP locally. This also means that
>> I'
On 29/07/2019 04:48, Jim DeLaHunt wrote:
> On 2019-07-27 11:33, Peter B. wrote:
>> …[snip]… I was also wondering if all of the information PHP wiki
>> article is still
>> up-to-date, since it was last modified 5 years ago?
>>
>> …[snip]…
>> # Links:
ause PHP is insecure but because the power of shell commands and
> power always brings responsibility
I'm aware of PHP's shortcomings, but this is not a web application and
it only runs locally.
Thanks again for your time and for somewhat confirming my approach!
Nice greetings,
Peter
iki article is still
up-to-date, since it was last modified 5 years ago?
Thank you very much in advance!
Peter B.
# Links:
[1] https://trac.ffmpeg.org/wiki/PHP
[2] http://ffmpeg.org/ffmpeg-all.html#Generic-options
___
ffmpeg-user mailing list
ffmpeg-u
to do the actual validation?
Kind regards,
Peter B.
___
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...@ffmpeg.org with subject "unsubscribe".
ible to do that?
Thank you very much in advance,
Peter B.
___
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...@ffmpeg.org with subject "unsubscribe".
lists LPCM as supported audio codec [4] in
MP4.
Experience has shown that "if FFmpeg can't/won't do it - there's a good
reason" :)
May I ask what that reason is?
Thank you very much in advance for any insights,
Peter B.
# Links
[1]
https://stackoverflow.com/questions/17651975/una
On 28/06/2019 00:32, Moritz Barsnick wrote:
> There's also the "hash" muxer with various hash functions (and its
> alias muxer "md5").
> $ ffmpeg -i input -map 0:a -c:a copy -f hash -
> or
> $ ffmpeg -i input -map 0:a -c:a copy -hash md5 -f hash -
> if you prefer MD5.
Ooooh! Excellent!
Didn't
On 26/06/2019 01:22, Carl Eugen Hoyos wrote:
> Am Mi., 26. Juni 2019 um 00:11 Uhr schrieb Peter B. :
>
>> So, instead of specifying "-f s16le" or "-f s24le", is there something
>> like "-f rawaudio"?
> Yes, there is a muxer that happily
eems to do the trick.
But according to the "audio types" documentation [1] it seems I have to
know define the (and therefore already know) the format.
So, instead of specifying "-f s16le" or "-f s24le", is there something
like "-f rawaudio"?
I'm grateful fo
Hi everyone :)
I already tried searching the web for this, but couldn't find any useful
answers (that didn't just cover the start timecode metadata):
-
Can I use FFmpeg to export (*) the (even non-continuous) data/timestamps
from a timecode track (TC track) e.g. from MOV,
On 20/05/2019 10:41, Carl Eugen Hoyos wrote:
> Am Do., 16. Mai 2019 um 00:03 Uhr schrieb Peter B. :
>
>> [matroska,webm @ 0x3f0c600] Element at 0xb3f8d1b ending at 0xb3f92ea
>> exceeds containing master element ending at 0xb3f8d15
> The message is the result of a demuxer c
,
Peter B.
## Links:
[1] https://mediaarea.net/MediaConch
[2]
https://superuser.com/questions/1425822/element-exceeds-containing-master-element-ffmpeg
Commandline and console output here:
*
$ ffmpeg-git -i 12bit.mkv -filter_complex "asetnsamples=48000" -
w could I retain all possible information (including boring metadata
:P) from the source in the rewrapped target?
Thank you very much in advance,
Peter B.
-- Links:
[1] https://trac.ffmpeg.org/wiki/Map#Example4
Commandline and complete uncut console output:
*
Hi Sean,
This ratio also seems a bit suspicious to me...
Could you try FFV1 without 2pass?
Did you do a framemd5 comparison to check if nothing was lost during
transcoding?
Nice greetings,
Peter
On 09/05/2019 02:01, sean darcy wrote:
> I've got a bunch of old movies I'm reencoding and
Hello everyone :)
I'm trying to create different encoding/wrapper combinations for a DV
source material (PAL, interlaced, BFF).
When I convert it to H.264 in MP4, the "scan type/scan order"
information seems to get lost if untreated, or reverts to TFF even if it
says "bottom coded first
On 06/05/2019 21:54, Reindl Harald wrote:
> https://trac.ffmpeg.org/wiki/CompilationGuide
If you only want to use the executables (not the libraries) you might
also try the "static builds":
https://johnvansickle.com/ffmpeg/
I'm quite happily using them alongside Debian/Ubuntu's repo versions.
I'm not sure if ffmpeg-user is actually the right place for this, since
it's a packaging issue.
Plus: I cannot reproduce your problem (Xubuntu 16.04.3, 64bit).
I guess you've got a typo: "jonathon" vs "jonathonf"?
$ sudo add-apt-repository ppa:jonathon/ffmpeg-3
wondering if there's a nice way to tell FFmpeg:
Convert any source audio format to PCM - but keep the same bits as the
source file had?
Currently I'm pre-sorting files manually in 16 or 24 bit and then
hardcoding "-c:a" accordingly...
Thank you
On 28/03/2019 21:38, Carl Eugen Hoyos wrote:
>> I've noticed that the big green "Download" button on ffmpeg.org [1] says:
>> "ffmpeg-4.1.2.tar.bz2"
>>
>> ...but points to:
>> https://ffmpeg.org/releases/ffmpeg-4.1.tar.bz2
> That's currently being discussed on the development mailing list.
Good evening :)
I've noticed that the big green "Download" button on ffmpeg.org [1] says:
"ffmpeg-4.1.2.tar.bz2"
...but points to:
https://ffmpeg.org/releases/ffmpeg-4.1.tar.bz2
Is that on purpose?
Nice greetings,
Peter
== References:
[1] https://ffmpeg.org/download.html
Hi Christoph :)
I second Reto regarding looking into RAWcooked for this use case.
Nice greetings,
Pb
On 11/02/2019 14:54, Reto Kromer wrote:
> Carl Eugen Hoyos wrote:
>
>> Iirc, here is a tool by Jerome that does act like a file
>> archiving system for dpx files (and uses ffv1 internally).
>
Hi Carl Eugen :)
On 25/01/2019 20:12, Carl Eugen Hoyos wrote:
> (Please do not compress compressed files and no, I don't think
> an md5 sum is necessary in this case, if it is necessary you can
> put it in your email)
You're absolutely right of course.
I usually don't compress compress files
pening here, and how to skip that extra rewrapping step?
Thank you very much in advance for any ideas/help :)
Peter B.
I've created a sample (with "dd") of the first few MB to recreate the issue:
http://download.das-werkstatt.com/pb/contribs/files/bad_timing-MPEGTS.tar.bz2
Commandli
Hi Ben,
On 07/12/18 19:23, Benjamin Turkus wrote:
> Any advice or thoughts—about what's going on with these files, or a
> different transcoding approach—would be appreciated. Rights issues could
> make sharing samples a little tricky, but I might be able to make it happen.
Sorry I can't provide
On 09/11/18 16:09, Carl Eugen Hoyos wrote:
> 2018-11-09 13:21 GMT+01:00, Peter B. :
>> [...]
>> https://trac.ffmpeg.org/ticket/6103
>>
>> [...]
>> Shall I post my findings there?
> The ticket does look incomplete.
Does it look better now? ;D
(Posted commandl
Just seen there's already an issue for this:
https://trac.ffmpeg.org/ticket/6103
"When trying to set the audio track metadata language to 'und'
(undefined) ffmpeg switches to 'eng' (English)"
Shall I post my findings there?
Nice greetings,
Pb
___
o639_to_lang", but how do I trigger it to be used?
Grateful for any help :)
Thanks in advance,
Peter B.
Here's commandline and complete, uncut console output to reproduce it:
// --
$ ffmpeg -y -f lavfi -i "sine=frequency=1000:duration=1" -c:a pcm_s
On 31/10/18 15:43, Tobias Rapp wrote:
> Maybe try to double-check the generated MXF file using MediaInfo or
> MxfDump. As far as I know field order is derived from the generic
> picture essence descriptor in MXF.
Thanks for the tip, but I've already tried with Mediainfo before posting
here:
"Scan
Hi Carl,
On 31/10/18 13:28, Carl Eugen Hoyos wrote:
> From a quick look, interlaced mxf is only supported for selected
> codecs (that support interlaced encoding), not for j2k
Thanks for the quick-look-reply!
Interesting/good to know. Is this an MXF-specification thing or an
(ffmpeg)
result "behave" properly, I'd be
very grateful :D
Thanks in advance,
Peter B.
Here's the commandline and uncut console output:
--
$ ffmpeg-git -f lavfi -i testsrc=size=720x576:rate=3/1001 -c:v
libopenjpeg -pix_fmt yuv422p10le -t 1 -an -top 1 delme.mx
Hi Reto,
On 24/07/18 21:47, Reto Kromer wrote:
> We do rewrap ProRes into Matroska. Which is the reason for transcoding
> it to FFV1?
...I guess the usual "way out" of proprietary formats?
As well as format normalization (to have less mixed codecs).
I guess ;)
@Wen/Kieran: Correct?
Cheers!
Pb
On 10/05/18 23:02, Carl Eugen Hoyos wrote:
> Piotr kindly confirmed that the file is valid, I sent a patch that
> skips the unknown extradata.
Saw it own ffmpeg-devel@ :)
Will try it as soon as possible and report back.
> Is is possible that we talked about file(s) with changing codecs
> that
On 08/05/18 00:31, Carl Eugen Hoyos wrote:
> 2018-05-07 23:39 GMT+02:00, Peter B. <p...@das-werkstatt.com>:
>
>> http://download.das-werkstatt.com/pb/contribs/files/c210.avi.7z
> This file was written using libavformat which does not support
> writing Canopus C210, pleas
Hi everyone :)
I just received a 10 bit uncompressed file, encoded in something called
"C210" (*).
When I transcode or play it, there's a horizontal pixel shift.
Here's a screenshot:
http://download.das-werkstatt.com/pb/contribs/files/c210_offset.png
Recent ffmpeg is able to read this file
On 2018-03-12 11:50, Paul B Mahol wrote:
> prores_aw gonna be removed.
Interesting.
Will the alias "-c:v prores" then point to "prores_ks"?
Thanks,
Pb
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
On 2018-03-12 00:50, Moritz Barsnick wrote:
> On Sun, Mar 11, 2018 at 09:33:29 +0100, Peter B. wrote:
>
>> 2) Docs say "profile/quantmat" is "integer", but only list strings:
>>
> You can use the strings instead of
On 2018-03-11 10:29, Carl Eugen Hoyos wrote:
> 2018-03-11 9:33 GMT+01:00 Peter B. <p...@das-werkstatt.com>:
>
>> When I looked at the documentation [1], there are 2 encoders mentioned:
>> * prores-aw
>> * prores-ks
>>
>> It says to use "-vcode
Hi :)
For testing purposes, I tried to encode a ProRes file using ffmpeg
(current git HEAD).
I have 2 questions about the FFmpeg docs about ProRes [1]:
1) Docs mention 2 encoder names, but only "prores" works:
When I looked at the documentation [1],
se stop laughing.
What do you mean with "you're not prepared for the cheat sheet version"?
Would be good to get feedback what's clear/unclear/missing so docs can
be improved :)
Regards,
Peter B.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ff
On 2017-12-13 21:23, Dima Ballin wrote:
> Greetings all,
> I am new to ffmpeg. I've read about how to export H.264 files from Premiere
> Pro via ffmpeg, but I was wondering if it's also possible to export a movie
> as FFV1?
As Carl Eugen already said, please post this question/request at
Premiere
On 03/22/2017 09:06 PM, Dave Rice wrote:
>> On Mar 22, 2017, at 3:31 PM, Peter B. <p...@das-werkstatt.com> wrote:
>>
>> How can I tell ffprobe to tell me the (frame/time-)position of that error?
> There's a related patch in
> http://ffmpeg.org/pipermail/ffmpeg-devel/
in advance,
Peter B.
Here's the command:
//
$ ffprobe -i input.ts -select_streams v:0 -show_frames
//
Here's the console output:
(I've "compressed" a repeating err
e Internet, but couldn't find anything suitable.
Thank you very much in advance,
Peter B.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@
On 06/12/2016 05:57 PM, Carl Eugen Hoyos wrote:
> If uncompressed video is acceptable for you, I may not understand
> your question: I believe the reason why ffv1 is discussed is that
> uncompressed video is generally not acceptable.
Uncompressed is indeed acceptable, but there are many
filesystem overhead, independent of compression size.
I will get back in more detail to your question as early as possible.
Kind regards,
Peter B.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
To u
On 04/26/2016 08:49 AM, Kal Sze wrote:
> And what is the valid number of slices when encoding as FFV1 level 3?
> The wiki says 4, 6, 9, 12, 16, 24, or 30; but I have not seen ffmpeg
> complain if I try to specify something like 25 slices for a 512x424
> video. Does ffmpeg just coerce the value to
On 12/13/2015 11:49 PM, Carl Eugen Hoyos wrote:
>> I was mainly looking for a way to normalize the format/behavior of the
>> audio track, because it couldn't be opened properly in NLEs or most
>> players it was opened with.
> I still don't think this is true (just disable libfaad in all these
>
On 12/03/2015 03:26 PM, Carl Eugen Hoyos wrote:
>> The error it returned seemed more like an invalid input, rather than a
>> non-specification conform output choice:
>> [quote]
>> [aac @ 0x37a4720] channel element 2.0 is not allocated
>> Error while decoding stream #0:1: Invalid data found
On 12/08/2015 04:15 PM, Dave Rice wrote:
>> It is indeed possible to decode back to DPX- I've losslessly
>> compressed 10bit RGB DPX to FFV1.mkv and back with matching framemd5s
>> all the way. It's a beautiful thing.
> But it's some context loss. For instance if the source DPX is logarithmic I'd
On 11/30/2015 01:52 AM, Carl Eugen Hoyos wrote:
> On Monday 30 November 2015 12:09:41 am Peter B. wrote:
>> $ ffmpeg -i esdn_audio_problem-20151128.ts -c:v copy
>> -c:a pcm_s16le output.ts
> pcm is not an allowed audio codec for mpeg-ts, this is a limitation
> of the spec
On 11/26/2015 04:36 PM, Christoph Gerstbauer wrote:
> color format has your DPX original source?
> RGB 10bit? Linear or logarithmic?
>
> And which color format has the FFv1?
Christoph Gerstbauer's questions are good.
As far as I know, you might need to provide additional details when
transcoding
On 09/13/2015 08:24 PM, Reto Kromer wrote:
> Peter B. wrote:
>
>> The value of "bpr" seems to stand for bits_per_sample.
> "bits_per_raw_sample" is the number of bits for each sample,
> commonly 8, 9, 10 or 16.
Ah! &quo
Hello :)
I've added information to the wiki [1] about reading FFV1 encoding
parameters from existing files.
The value of "bpr" seems to stand for bits_per_sample.
What does the abbreviation "bpr" stand for exactly?
Thanks in advance,
Pb
== References:
[1]
On 09/13/2015 08:21 PM, Francois Visagie wrote:
>> == References:
>> [1] https://trac.ffmpeg.org/wiki/Encode/FFV1
> How about also specifying default values? Sorry for not addressing your
> original question; I don't know either.
Nice idea, but since current output for different FFV1 versions
I've just received a request, regarding an error message when converting
from h264/PCM/MOV to FFV1/PCM/AVI.
The transcoding doesn't start and exits with the following error message:
[quote]
"Assertion s->bits_per_raw_sample >= 8 failed at
On 09/09/2015 03:15 PM, Moritz Barsnick wrote:
> On Wed, Sep 09, 2015 at 12:56:31 +, Carl Eugen Hoyos wrote:
>> Peter B. das-werkstatt.com> writes:
>>
>>> ffmpeg version N-73648-g90dd6ad
>> How should we fix this?
>>
>> Of course it is nuisan
On 08/05/2015 03:34 PM, Kieran O'Leary wrote:
Here was my command line:
ffmpeg -i Sequence.01.mov -f framemd5 Sequence.01.framemd5 -c:v h264 -c:a
copy Sequence.01.mkv -f framemd5 Sequence.01h264.framemd5
It produced identical framemd5s. Is it possible to get ffmpeg to produce a
framemd5
On 07/25/2015 11:53 AM, MrNice wrote:
The standard approach to this kind of issue is to use (as close to)
losslessly encoded intermediate files as possible. I.e. either use a
codec designed for lossless encoding such as HuffYUV, or use something
like x264 with lossless settings.
Why do you
On 03/09/2015 09:35 PM, Dave Rice wrote:
Using framemd5 verification after ffv1 encoding, I’ve found about 3
frames that weren’t lossless. This is out of probably millions of
frames, but computer problems happen. In all of the cases the a local
computer was using an input and an output that
On 01/02/2015 01:31 PM, Zsolt wrote:
[...] So far UT-Video seemed to be the fastest.
Interesting.
I haven't had time to check out UT-Video yet, and my last knowledge was
that most of the information about it is in Japanese only :(
I'd be curious to hear about your experiences with it.
Testing
On 12/29/2014 04:34 AM, Jason Freets wrote:
So yes, I'm not at all saying that there is anything wrong with FFV1.
Carl was guessing correctly - and I'm indeed happy to hear that there's
nothing wrong with FFV1 :)
Yet, I find this thread incredibly interesting.
Especially the Little/Big Endian
Dear Jason,
I haven't done much with RGB 10bit yet, but I'm working with FFV1 a lot,
so if you send me a sample and your commandlines, I could take a look.
Late Merry-Christmas to you :)
Peter
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
On 11/30/2014 04:31 PM, kranthi kumar wrote:
This is very Important to me, for playing or receiving live streaming
videos from YouTube .So,please tell me How to play YouTube videos using
FFplay.
For the non-commandline, non-FFmpeg side of things:
VLC can play Youtube links directly:
Media
On 09/17/2014 04:27 PM, tim nicholson wrote:
Try using a simpler ffprobe command and compare like with like.
Your example includes a complex filter chain and not all filters
multi-thread afaik.
That's a good point.
I'll try that.
Thanks!
Pb
___
On 08/15/2014 06:46 PM, Moritz Barsnick wrote:
BTW, the codec being lossless doesn't mean the video size needs to be
the same, varying compression is certainly a feature.
You're right that lossless encoding can still have different filesizes -
*but* depending on the encoding options [1].
I
93 matches
Mail list logo
