On Wed, Aug 7, 2019 at 4:26 PM Moritz Barsnick wrote:
> On Wed, Aug 07, 2019 at 15:10:06 +0200, Peter B. wrote:
> > > I'll try to rework it to give the "hash" muxer a "-per_stream" boolean
> > > option, then I can (and must) reuse all the code.
> >
> > Wooow!
> > That'd be awesome!
>
> I sent a
On Wed, Aug 07, 2019 at 15:10:06 +0200, Peter B. wrote:
> > I'll try to rework it to give the "hash" muxer a "-per_stream" boolean
> > option, then I can (and must) reuse all the code.
>
> Wooow!
> That'd be awesome!
I sent a non-hackish implementation to Peter privately. I'll clean it
up and
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
On Tue, Aug 06, 2019 at 12:21:58 +0200, Paul B Mahol wrote:
> > I just couldn't quickly figure out how to prefix the stream specifiers
> > (e.g. 0:0, 0:1).
> Look how framehash does it?
Yeah, too obvious. I was looking for "0:1", but the first digit is
meaningless, and the second one is just the
On Tue, Aug 6, 2019 at 12:14 PM Moritz Barsnick wrote:
> On Tue, Aug 06, 2019 at 10:07:40 +0200, Paul B Mahol wrote:
> > If I understand correctly, basically need hash of each stream separately
> > (for framehash this already works).
> >
> > That is quite possible to be implemented. Feel free to
On Tue, Aug 06, 2019 at 10:07:40 +0200, Paul B Mahol wrote:
> If I understand correctly, basically need hash of each stream separately
> (for framehash this already works).
>
> That is quite possible to be implemented. Feel free to open feature request
> on FFmpeg bug tracker.
Just to show that
On Mon, Aug 5, 2019 at 11:13 PM Peter B. wrote:
> 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...
> >>
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...
>> a:2...
>> "
>>
> Hash muxer does not work like that.
Oh :(
>
On Mon, Aug 5, 2019 at 4:16 PM Peter B. wrote:
> 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
> >
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
On Fri, Aug 02, 2019 at 14:51:36 +0200, Peter B. wrote:
> I assume no answer means there's no option to do that.
No, there isn't.
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?
That
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 26/07/2019 22:54, Dennis Mungai wrote:
> You could use a muxer such as framemd5:
> https://ffmpeg.org/ffmpeg-formats.html#framemd5-1
Thanks for your reply, but I've been using framemd5 for years.
I meant, if there's a way that I don't have to code a script around the
ffmpeg call to do the
On Fri, 26 Jul 2019 at 21:02, Peter B. wrote:
> Hi everyone :)
>
> I was wondering if maybe there's a quicker way to verify lossless
> transcoding or container rewrapping than these 3 steps:
>
> 1. generate content hash during transcoding.
> 2. generate content hash of output file.
> 3.
Hi everyone :)
I was wondering if maybe there's a quicker way to verify lossless
transcoding or container rewrapping than these 3 steps:
1. generate content hash during transcoding.
2. generate content hash of output file.
3. diff source-hash with output-hash (using whatever diff-tool).
15 matches
Mail list logo