Am 26.09.18 um 21:27 schrieb Carl Eugen Hoyos:
This is not unexpected.
Feel free to try even higher bit-rates or main10 profile.
Yes, main10 gives little bit nicer results. It seems to me there is a
bitrate limit. If I use 3k for example (same as source) ffmpeg
everages to 22000k. How to
On my MacBook Pro I tried GPU accelerated videotoolbox HEVC encoding. It
is indeed very fast. Sadly, the default video quality is very poor, but
increasing the bit-rate enhances the quality.
/$ ffmpeg -i video_in.mkv -acodec copy -vcodec hevc_videotoolbox -b:v
6000k -tag:v hvc1 -profile:v main v
Am 05.05.18 um 23:45 schrieb Lou Logan:
> Both, kind of. I assume the following commit from today fixed the segfault
> you experienced:
> https://git.videolan.org/?p=ffmpeg.git;a=commit;h=c1b282dc74d801f943db282e89f7729e90897669
Yes it does. 4.0 with patch:
$ ffmpeg -i Alchemy_edit.flac -strict
Am 05.05.18 um 23:45 schrieb Lou Logan:
> Both, kind of. I assume the following commit from today fixed the segfault
> you experienced:
> https://git.videolan.org/?p=ffmpeg.git;a=commit;h=c1b282dc74d801f943db282e89f7729e90897669
>
> But the encoder does not support 96000:
> $ ffmpeg -h encoder=dts
I do have a 96000 Hz FLAC file which I would like to convert to DTS and
preserve the sample rate. But it seems only 41000 and 48000 is supported.
$ ffmpeg -i Alchemy_edit.flac -strict -2 -acodec dts -ar 96000 -f spdif
Alchemy_96edit.spdif
ffmpeg version 4.0 Copyright (c) 2000-2018 the FFmpeg deve
Am 30.04.18 um 20:10 schrieb Carl Eugen Hoyos:
> Then you need something like --extra-ldflags=-L/opt/local/lib
Thanks, this did the trick! Now it builds as expected. Yippee! But why
does an older ffmpeg build without this extra-ldflag?
Am 30.04.18 um 20:10 schrieb Carl Eugen Hoyos:
> I was unde
Am 29.04.18 um 16:31 schrieb Carl Eugen Hoyos:
> Where is libsoxr.a installed?
There is an /opt/local/lib/libsoxr.dylib. Macports did not install me an
libsoxr.a
Am 29.04.18 um 16:31 schrieb Carl Eugen Hoyos:
> Just curious: Does this work?
I have adopted this from the non-official build at
ht
Am 29.04.18 um 00:06 schrieb Lou Logan:
> Why do you have so many dependencies? Are you trying to enable everything? If
> yes, why?
>
> Keep things simple and just enable what you need.
I do. This dependencies are so many, because I need them for other
projects. There are not all related to FFmpe
Can nobody help me with my problem? I am really lost here.The only thing
I didn't try until now is to install the dependencies via Homebrew
instead of Macports. But this should not make a difference, I think.
Am 26.04.18 um 20:16 schrieb Nomis101 π:
> I had a similar problem some time
Am 10.10.16 um 21:19 schrieb Cley Faye:
> βOthers might be more knowledgeable about the specifics of mac dev.
> environments, but it seems that pkg-config is not available.
> There seem to be support for pkg-config in homebrew.
Yes, I also found this out just now. Installing pkg-config via Macport
I don't know what was happening, but I'm not able anymore to build
ffmpeg. It was working nicely since a few weeks (I don't know what I
have done to break it). I'm on Mac OS X 10.12. I've tried with the
latest git version of ffmpeg. Normally I install any dependencies via
Macports which is not a pr
Am 25.08.16 um 19:34 schrieb Nomis101 π:
> Am 24.08.16 um 22:49 schrieb Carl Eugen Hoyos:
>> Please test current FFmpeg.
> $ lldb -- ./ffmpeg_g -i /Users/Downloads/Test.mp4
> (lldb) target create "./ffmpeg_g"
> Current executable set to './ffmpeg_g' (x86_64
Am 24.08.16 um 22:49 schrieb Carl Eugen Hoyos:
> Please test current FFmpeg.
$ lldb -- ./ffmpeg_g -i /Users/Downloads/Test.mp4
(lldb) target create "./ffmpeg_g"
Current executable set to './ffmpeg_g' (x86_64).
(lldb) settings set -- target.run-args "-i" "/Users/Downloads/Test.mp4"
(lldb) run
Proc
Am 24.08.16 um 20:05 schrieb Carl Eugen Hoyos:
> I suspect (not osx atm):
> $ lldb ffmpeg_g
> and then on the prompt:
> r -i foo.mp4
OK, I found out how it works. I'm getting this output:
/$ lldb -- ./ffmpeg_g -i /Users/Downloads/Test.mp4 //
//(lldb) target create "./ffmpeg_g"//
//Current executab
Am 24.08.16 um 19:53 schrieb Carl Eugen Hoyos:
> Does lldb show anything useful?
I don't know. What would be the lldb corresponding of
$ gdb --args ./ffmpeg_g -i foo.mp4
?
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/li
Am 24.08.16 um 07:23 schrieb Carl Eugen Hoyos:
>> > OK, I did lots of different builds now. And the suspicious option is
>> > --enable-lto. I can remove all other options, no difference. But if I
>> > remove --enable-lto, than I do not see the Segmentation fault issue
>> > anymore.
> Did you verify
Am 23.08.16 um 21:11 schrieb Moritz Barsnick:
> Go into the build directory, and launch your ffmpeg command as:
>
> $ gdb --args ./ffmpeg_g -i foo.mp4
I did this. First, I had to install gdb via Macports, because it gets
not installed anymore with Apple Developer Tools. But I think the output
is no
Am 23.08.16 um 20:49 schrieb Carl Eugen Hoyos:
>> What option is most likely to cause this?
> This is what I would like you to tell us so we can find out if there is a
> bug that can be fixed within FFmpeg.
This will mean I need to do several builds and leave out another of my
options every time. T
Am 23.08.16 um 08:56 schrieb Carl Eugen Hoyos:
> Please test a current snapshot (I don't think we support
> releases on osx) and please test with "./configure && make ffmpeg",
> I cannot reproduce on Linux.
> In case this hasn't been said: Crashes are always important.
OK, I've tested with the vers
Am 22.08.16 um 21:22 schrieb Moritz Barsnick:
> It seems like you may have a bad build of ffmpeg.
>
> Can you provide a very small sample of the input to ffmpeg? For example here:
> https://datafilehost.com/
>
> Do you have the possibility to try a different build of ffmpeg?
Its my own build, it wo
I always get "Segmentation fault: 11" if I do the following. What does
"Segmentation fault: 11" mean?
STR:
1. Get any movie (some small file from youtube will also do), get
Handbrake (I'm using version 0.10.5 on Mac OS X).
2. Convert this movie with "Format: MP4 File" and "Video Codec: MPEG-4".
3.
Am 17.08.16 um 22:25 schrieb Carl Eugen Hoyos:
> Hi!
>
> 2016-08-17 20:52 GMT+02:00 Nomis101 π :
>> > 5. Open WAV file in VLC (I had to use --demux=ffmpeg to open it in VLC)
>> > 6. Play the file and note the longer duration and that file sounds slower
> What happ
Am 17.08.16 um 06:56 schrieb Peter White:
> I don't see where resampling could have happened, so my guess is that
> you are basically playing 48kHz audio at 44.1kHz. The difference in
> length sounds about right for that (48/44.1~=1.088).
> Do you hear a change in pitch as well?
You are right. It w
Am 16.08.16 um 22:26 schrieb Carl Eugen Hoyos:
> Thank you for the confirmation!
> Are you sure the quality is satisfying?
Interesting that you ask. I now had the time to listen to it more
closely. It does not sound that brilliant/clear like the original from
the Blu-ray, but it works.
But, I have
Am 11.08.16 um 12:20 schrieb Nomis101 π:
> Am 11.08.16 um 01:31 schrieb Carl Eugen Hoyos:
>> > $ ffmpeg -i input -strict -2 -acodec dts -f spdif out1.spdif
>> > or (much better because it involves no experimental encoding!):
>> > $ ffmpeg -i dts_input -a
Am 11.08.16 um 01:31 schrieb Carl Eugen Hoyos:
> First thing: There is a reason for "-strict -2"!
I know, but ffmpeg is the only DTS encoder I have on my Mac. So, no big
choice.
Am 11.08.16 um 01:31 schrieb Carl Eugen Hoyos:
> $ ffmpeg -i input -strict -2 -acodec dts -f spdif out1.spdif
> or (m
Am 10.08.16 um 20:05 schrieb Moritz Barsnick:
> I'm still confused at to what this file really is. ;-)
As I read on wikipedia and some forums, a DTS bitstream, based on the
Coherent Acoustics compression algorithm, is actually encapsulated in
each PCM audio track, which is a "pseudo 2-channel wav".
I've tried a combination of both current suggestions, but this gives me
an error:
/$ ffmpeg -i /Volumes/Macintosh/EREDV946.flac -strict -2 -c:a dts -ar
44100 -b:a 1411k -sample_fmt fltp -tag:a 0x0001
/Volumes/Macintosh/EREDV946.wav
ffmpeg version 3.1.1 Copyright (c) 2000-2016 the FFmpeg developers
Hi, ffmpeg user list. I have a problem that I can not solve and hope you
can help me.
I found out, that I can listen to 5.1 surround music over iTunes /
Airplay if the music is an dts-encoded WAV file (44.1 kHz, 16 Bit). This
means I have to convert all my surround music, mostly *.dts, *.flac or
*
29 matches
Mail list logo