2017-11-06 11:50 GMT+01:00 Paul B Mahol :
> On 11/5/17, Carl Eugen Hoyos wrote:
>> 2017-10-09 0:24 GMT+02:00 Carl Eugen Hoyos :
>>> 2017-10-07 16:51 GMT+02:00 Carl Eugen Hoyos :
2017-10-01 18:23 GMT+02:00 Carl Eugen Hoyos :
> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>
>> The
On 11/5/17, Carl Eugen Hoyos wrote:
> 2017-10-09 0:24 GMT+02:00 Carl Eugen Hoyos :
>> 2017-10-07 16:51 GMT+02:00 Carl Eugen Hoyos :
>>> 2017-10-01 18:23 GMT+02:00 Carl Eugen Hoyos :
2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
> The existing amr demuxer does not allow reading stream
2017-10-09 0:24 GMT+02:00 Carl Eugen Hoyos :
> 2017-10-07 16:51 GMT+02:00 Carl Eugen Hoyos :
>> 2017-10-01 18:23 GMT+02:00 Carl Eugen Hoyos :
>>> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>>>
The existing amr demuxer does not allow reading streams,
it requires the 3GPP-conforming file
2017-10-07 16:51 GMT+02:00 Carl Eugen Hoyos :
> 2017-10-01 18:23 GMT+02:00 Carl Eugen Hoyos :
>> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>>
>>> The existing amr demuxer does not allow reading streams,
>>> it requires the 3GPP-conforming file header.
>>> Attached patch allows reading amrnb and
2017-10-01 18:23 GMT+02:00 Carl Eugen Hoyos :
> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>
>> The existing amr demuxer does not allow reading streams,
>> it requires the 3GPP-conforming file header.
>> Attached patch allows reading amrnb and amrwb from (live)
>> streams, fixes ticket #6678.
>
On Wed, Oct 04, 2017 at 01:07:34AM +0200, Carl Eugen Hoyos wrote:
> 2017-10-04 1:00 GMT+02:00 Michael Niedermayer :
> > On Tue, Oct 03, 2017 at 12:02:23AM +0200, Carl Eugen Hoyos wrote:
> >> 2017-10-02 23:47 GMT+02:00 Carl Eugen Hoyos :
> >> > 2017-10-02 23:02 GMT+02:00 Michael Niedermayer :
> >> >
2017-10-04 1:00 GMT+02:00 Michael Niedermayer :
> On Tue, Oct 03, 2017 at 12:02:23AM +0200, Carl Eugen Hoyos wrote:
>> 2017-10-02 23:47 GMT+02:00 Carl Eugen Hoyos :
>> > 2017-10-02 23:02 GMT+02:00 Michael Niedermayer :
>> >> On Sun, Oct 01, 2017 at 06:23:50PM +0200, Carl Eugen Hoyos wrote:
>> >>> 2
On Tue, Oct 03, 2017 at 12:02:23AM +0200, Carl Eugen Hoyos wrote:
> 2017-10-02 23:47 GMT+02:00 Carl Eugen Hoyos :
> > 2017-10-02 23:02 GMT+02:00 Michael Niedermayer :
> >> On Sun, Oct 01, 2017 at 06:23:50PM +0200, Carl Eugen Hoyos wrote:
> >>> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
> >>>
> >
2017-10-02 23:47 GMT+02:00 Carl Eugen Hoyos :
> 2017-10-02 23:02 GMT+02:00 Michael Niedermayer :
>> On Sun, Oct 01, 2017 at 06:23:50PM +0200, Carl Eugen Hoyos wrote:
>>> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>>>
>>> > The existing amr demuxer does not allow reading streams,
>>> > it require
2017-10-02 23:02 GMT+02:00 Michael Niedermayer :
> On Sun, Oct 01, 2017 at 06:23:50PM +0200, Carl Eugen Hoyos wrote:
>> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>>
>> > The existing amr demuxer does not allow reading streams,
>> > it requires the 3GPP-conforming file header.
>> > Attached patc
On Sun, Oct 01, 2017 at 06:23:50PM +0200, Carl Eugen Hoyos wrote:
> 2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
>
> > The existing amr demuxer does not allow reading streams,
> > it requires the 3GPP-conforming file header.
> > Attached patch allows reading amrnb and amrwb from (live)
> > stream
2017-09-27 18:08 GMT+02:00 Carl Eugen Hoyos :
> The existing amr demuxer does not allow reading streams,
> it requires the 3GPP-conforming file header.
> Attached patch allows reading amrnb and amrwb from (live)
> streams, fixes ticket #6678.
New patch with auto-detection attached, passes probech
Hi,
On Wed, Sep 27, 2017 at 2:10 PM, Carl Eugen Hoyos
wrote:
> 2017-09-27 20:09 GMT+02:00 Carl Eugen Hoyos :
> > 2017-09-27 19:46 GMT+02:00 Ronald S. Bultje :
>
> >> It's intruiging that the existing demuxer (as you mentioned,
> >> it expects a prefix) works with unicast but not
> >> multicast i
2017-09-27 20:09 GMT+02:00 Carl Eugen Hoyos :
> 2017-09-27 19:46 GMT+02:00 Ronald S. Bultje :
>> It's intruiging that the existing demuxer (as you mentioned,
>> it expects a prefix) works with unicast but not
>> multicast input.
>
> I don't think this is correct (as in: "This is impossible") but
>
2017-09-27 19:46 GMT+02:00 Ronald S. Bultje :
> @Carl Eugen: I've read the bug report.
Thank you; sorry that imo, this cannot help in this case;-(
The relevant issue is that live streams or truncated
amr files cannot be handled by the existing demuxer
although they work if the properties are forc
Hi guys,
On Wed, Sep 27, 2017 at 1:32 PM, wm4 wrote:
> On Wed, 27 Sep 2017 19:22:37 +0200
> Carl Eugen Hoyos wrote:
>
> > 2017-09-27 19:08 GMT+02:00 wm4 :
> > > Maybe you could get back to the technical discussion
> >
> > I wish this were so easy with you:
>
> Well, it certainly isn't with you
On Wed, 27 Sep 2017 19:22:37 +0200
Carl Eugen Hoyos wrote:
> 2017-09-27 19:08 GMT+02:00 wm4 :
> > Maybe you could get back to the technical discussion
>
> I wish this were so easy with you:
Well, it certainly isn't with you.
___
ffmpeg-devel mailin
2017-09-27 19:08 GMT+02:00 wm4 :
> Maybe you could get back to the technical discussion
I wish this were so easy with you:
You first wrote:
> That seems particularly pointless, since the user has
> to force the demuxers.
If I understand this sentence correctly, you agree with me
that it should
On Wed, 27 Sep 2017 19:04:26 +0200
Carl Eugen Hoyos wrote:
> 2017-09-27 19:02 GMT+02:00 wm4 :
> > On Wed, 27 Sep 2017 19:00:04 +0200
> > Carl Eugen Hoyos wrote:
> >
> >> 2017-09-27 18:58 GMT+02:00 wm4 :
> >>
> >> > It may be better for you not committing anything if you don't know what
> >>
2017-09-27 19:02 GMT+02:00 wm4 :
> On Wed, 27 Sep 2017 19:00:04 +0200
> Carl Eugen Hoyos wrote:
>
>> 2017-09-27 18:58 GMT+02:00 wm4 :
>>
>> > It may be better for you not committing anything if you don't know what
>> > commit messages are.
>>
>> I assume this is how you interpret our code-of-condu
On Wed, 27 Sep 2017 19:00:04 +0200
Carl Eugen Hoyos wrote:
> 2017-09-27 18:58 GMT+02:00 wm4 :
>
> > It may be better for you not committing anything if you don't know what
> > commit messages are.
>
> I assume this is how you interpret our code-of-conduct
> to which you agreed?
>
> Watch you
2017-09-27 18:58 GMT+02:00 wm4 :
> It may be better for you not committing anything if you don't know what
> commit messages are.
I assume this is how you interpret our code-of-conduct
to which you agreed?
Watch your tongue, Carl Eugen
___
ffmpeg-devel
On Wed, 27 Sep 2017 18:47:16 +0200
Carl Eugen Hoyos wrote:
> 2017-09-27 18:40 GMT+02:00 wm4 :
> > On Wed, 27 Sep 2017 18:08:19 +0200
> > Carl Eugen Hoyos wrote:
> >
> >> Hi!
> >>
> >> The existing amr demuxer does not allow reading streams, it requires
> >> the 3GPP-conforming file header.
> >
2017-09-27 18:40 GMT+02:00 wm4 :
> On Wed, 27 Sep 2017 18:08:19 +0200
> Carl Eugen Hoyos wrote:
>
>> Hi!
>>
>> The existing amr demuxer does not allow reading streams, it requires
>> the 3GPP-conforming file header.
>> Attached patch allows reading amrnb and amrwb from (live) streams,
>> fixes tic
On Wed, 27 Sep 2017 18:08:19 +0200
Carl Eugen Hoyos wrote:
> Hi!
>
> The existing amr demuxer does not allow reading streams, it requires
> the 3GPP-conforming file header.
> Attached patch allows reading amrnb and amrwb from (live) streams,
> fixes ticket #6678.
>
> Please comment, Carl Eugen
Hi!
The existing amr demuxer does not allow reading streams, it requires
the 3GPP-conforming file header.
Attached patch allows reading amrnb and amrwb from (live) streams,
fixes ticket #6678.
Please comment, Carl Eugen
From 1b548fbd47f521d0c2a7b443ac2b1f2925e8bb41 Mon Sep 17 00:00:00 2001
From:
26 matches
Mail list logo