On Wed, Oct 14, 2015 at 21:09:01 +0200, Moritz Barsnick wrote:
> In its comments, notably "2014-04-10 07:14 UTC", using (c)vlc as a
> muxer is suggested. cvlc was not the solution we were looking for on
> this ffmpeg list though. ;)
Indeed, using clvc as a (re-)muxer instead of ffmpeg, my PVR/STB
On Wed, Oct 14, 2015 at 20:40:57 +0300, Claudiu Rad wrote:
> >> There used to be a patch (I am not sure on which mailing
> >> list, could have been avconv-devel or ffmpeg-devel) but
> > I'm off looking for this patch...
> did you find it?
Unfortunately, I didn't. If anyone could help looking...
I
On 9/26/2015 3:56 PM, Moritz Barsnick wrote:
On Sat, Sep 26, 2015 at 12:45:12 +, Carl Eugen Hoyos wrote:
Moritz Barsnick gmx.net> writes:
My PVR (or call it STB) likes neither AC-3 nor
dvb_subtitles when muxed by ffmpeg into an MPEG-TS
That is because FFmpeg writes a (general) transport
On Sat, Sep 26, 2015 at 12:45:12 +, Carl Eugen Hoyos wrote:
> Moritz Barsnick gmx.net> writes:
> > My PVR (or call it STB) likes neither AC-3 nor
> > dvb_subtitles when muxed by ffmpeg into an MPEG-TS
>
> That is because FFmpeg writes a (general) transport stream
> while your stb expects a
Moritz Barsnick gmx.net> writes:
> My PVR (or call it STB) likes neither AC-3 nor
> dvb_subtitles when muxed by ffmpeg into an MPEG-TS
That is because FFmpeg writes a (general) transport stream
while your stb expects a dvb stream (different standards).
There used to be a patch (I am not sure
On Sat, Sep 26, 2015 at 05:12:38 -0500, Mike Brown wrote:
> I just noticed that I am really, really, out-of-date. I've normally only
> been using it to extract pcm audio from a TS stream and haven't dealt with
> subtitles before.
Congratulations and kudos to you and a warning to all others who th
On Sat, Sep 26, 2015 at 04:35:44 -0500, Mike Brown wrote:
> On Sat, Sep 26, 2015 at 03:00:07PM +0530, Anshul wrote:
> > New thread please!
> I'm confused. It is a new mail list thread.
No, it isn't. You wrote a new mail as a reply to an existing thread.
View it in gmane and see the effect: People
Mike Brown mrvideo.vidiot.com> writes:
> As a side issue, how does one stop those
> annoying "frame=" lines?
-nostats
As said, please remember not to hijack threads, this
is considered rude everywhere!
Carl Eugen
___
ffmpeg-user mailing list
ffmpe
On Sat, Sep 26, 2015 at 05:02:37AM -0500, Mike Brown wrote:
> Mike Brown mrvideo.vidiot.com> writes:
> *
> BRN <126> ffmpeg -i BBC-AAC60-test.ts -map 0:0 -vcodec copy -map 0:1 -acodec
> ac3 -ab 640k -map 0:2 -scodec copy BBC-DD51-test.ts
> ffmpeg version N-52837-g399f6ef Copyright (c) 2000-20
Mike Brown mrvideo.vidiot.com> writes:
>> Here is the situation: the source is a BBC video
>> from freeview, which has AAC audio, specifically
>> AAC 6.0. I prefer AC3 5.1
>
>(This makes no sense.)
How does this not make any sense? AAC6.0 doesn't work with everything.
In my case, when I play
On Sat, Sep 26, 2015 at 03:00:07PM +0530, Anshul wrote:
>
>
> On 09/26/2015 02:38 PM, Mike Brown wrote:
[...]
>> MB
> New thread please!
I'm confused. It is a new mail list thread.
MB
--
e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII
6082066...@email.uscc.net (14
On 09/26/2015 02:38 PM, Mike Brown wrote:
Here is the situation: the source is a BBC video from freeview, which has
AAC audio, specifically AAC 6.0. I prefer AC3 5.1
So, here is the CLI:
ffmpeg -i inputfile.ts -map 0:0 vcodec copy -map 0:1 -acodec ac3 -ab 640 \
-map 0:2 -scodec copy outputfi
Mike Brown mrvideo.vidiot.com> writes:
> Here is the situation: the source is a BBC video
> from freeview, which has AAC audio, specifically
> AAC 6.0. I prefer AC3 5.1
(This makes no sense.)
> So, here is the CLI:
(Complete, uncut console output missing.)
Please provide the input file.
C
Here is the situation: the source is a BBC video from freeview, which has
AAC audio, specifically AAC 6.0. I prefer AC3 5.1
So, here is the CLI:
ffmpeg -i inputfile.ts -map 0:0 vcodec copy -map 0:1 -acodec ac3 -ab 640 \
-map 0:2 -scodec copy outputfile.ts
When I look at the output file with med
14 matches
Mail list logo
