they are encrypted files, ffmpeg is not going to crack it
Audible AAX files are encrypted M4B files, and they can be decrypted by
specifying a 4 byte activation secret.
--
View this message in context:
http://ffmpeg-users.933282.n4.nabble.com/Converting-Audible-AAX-tp4673787p4674063.html
Sent
> On Jan 13, 2016, at 9:25 AM, Bouke / VideoToolShed
> wrote:
>> On Jan 13, 2016, at 14:17, Robert Krüger wrote:
>>
>> On Wed, Jan 13, 2016 at 12:53 PM, Christoph Gerstbauer <
>> christophgerstba...@gmail.com> wrote:
>>
>>> FFmpeg allows me to set a timecode of 24:00:00:00 and beyond.
>>>
>>
On 1/12/16, Elliott Balsley wrote:
> I realize that; I was merely asking if the display can be disabled
> according to user preference. When using a narrow Terminal window, the
> display is constantly overwritten, so this new change means a wider
> Terminal window of 100 chars is required.
I cou
I can think of two options, one is the "sdl out" filter, the other is
to split your output and write to .jpg files (you can overwrite a
single jpeg file) and display that as it changes. GL!
Note there is no "sdl audio out" filter (as far as I'm aware).
On 3/29/15, kevin wrote:
> I need to captur
Nope. -loglevel warning disables progress display, so I re-enable it with
-stats.
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Le duodi 22 nivôse, an CCXXIV, Etienne Desautels a écrit :
> After more tests I hit some problems with some videos:
> ffmpeg -hide_banner -i /mnt/archivescollection/test_file.iso -f null -af
> ebur128=peak=true:framelog=verbose -vf idet,cropdetect=0.12:2:1 -y /dev/null
> /mnt/archivescollection/
On 1/13/16, Greger Burman wrote:
> Ok, so the ffmpeg based player is buffering frames somewhere even though
> I'm telling it not to. This happens with h264 video but not with mjpeg.
> That suggests to me that the latency is caused by either the h264 decoder
> or the mpegts demuxer. I have also tri
On 13 January 2016 at 14:46, Carl Eugen Hoyos wrote:
> Jannes Faber gmail.com> writes:
>
> > Is there any way ffmpeg can deal with such a stream directly?
>
> I believe it deals fine with the stream;-)
>
Wow you're right! I just tried to play it from the file and it just works!
However, I just
> On Jan 13, 2016, at 14:17, Robert Krüger wrote:
>
> On Wed, Jan 13, 2016 at 12:53 PM, Christoph Gerstbauer <
> christophgerstba...@gmail.com> wrote:
>
>> FFmpeg allows me to set a timecode of 24:00:00:00 and beyond.
>>
>> e.g "-timecode 24:00:00:00"
>>
>> When I make an MXF D10 for example
On Wed, Jan 13, 2016 at 3:06 PM, Phil Rhodes
wrote:
> I'd be a very careful here.
> Linear timecode (which is fundamentally an audio signal) cannot represent
> a value of more than two in the tens-of-hours position, because only two
> bits are allocated to it. Although other systems may be more f
I'd be a very careful here.
Linear timecode (which is fundamentally an audio signal) cannot represent a
value of more than two in the tens-of-hours position, because only two bits are
allocated to it. Although other systems may be more forgiving, LTC is still
very commonly used.
Furthermore, the
x <94dlve1izy52e5t gmail.com> writes:
> ffmpeg -y -i http://192.168.0.11:8090/VIDEO_CAM1.mpg
> -itsoffset 1.0 -i http://192.168.0.11:8090/AUDIO.mp2
> -map 0:0 -map 1:0 test.mp4
Complete, uncut console output missing.
> However, I would like to make the synchronization
> automatic. Say, compar
Jannes Faber gmail.com> writes:
> Is there any way ffmpeg can deal with such a stream directly?
I believe it deals fine with the stream;-)
And even with your sed magic, I believe
that the trailing 0's do not disappear, so
remuxing may not have any advantages...
I opened #5154 for your issue,
Kachhawal, Vijay P optum.com> writes:
> $ sed -i 's/-lflite"/-lflite -lasound"/' configure
Did you try without the unneeded call to sed?
> Include the log file "config.log" produced by configure
> as this will help solve the problem.
Did you read this?
Please try "./configure", if it fails p
On Wed, Jan 13, 2016 at 14:17:43 +0100, Robert Krüger wrote:
> I wasn't able to find any official spec that says what the limit for the
> hour part is but since it in the general case does not define a time of day
> but an offset, why limit it to 25 hours and not use the full 100? On a
> side-note,
On Wed, Jan 13, 2016 at 12:53 PM, Christoph Gerstbauer <
christophgerstba...@gmail.com> wrote:
> FFmpeg allows me to set a timecode of 24:00:00:00 and beyond.
>
> e.g "-timecode 24:00:00:00"
>
> When I make an MXF D10 for example, the value of 24:00:00:00 is still in
> the file.
> Most but not all
FFmpeg allows me to set a timecode of 24:00:00:00 and beyond.
e.g "-timecode 24:00:00:00"
When I make an MXF D10 for example, the value of 24:00:00:00 is still in
the file.
Most but not all programs ignore this and display 00:00:00:00 correctly.
Here are some sample extractions of the timecod
Ok, so the ffmpeg based player is buffering frames somewhere even though
I'm telling it not to. This happens with h264 video but not with mjpeg.
That suggests to me that the latency is caused by either the h264 decoder
or the mpegts demuxer. I have also tried m4v instead of mpegts, with about
the s
18 matches
Mail list logo