Re: [FFmpeg-user] builds for Windows
On 02-09-2020 11:53 pm, Michael Koch wrote: "ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be removed." Any idea where we can get builds for Windows after this date? I plan to provide 64-bit static builds starting the 18th. Will update doc with link once I make arrangements. Gyan ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] Problem about duration value of converted mp3 file
Thank you for your interest The contents requested for confirmation have been retested and confirmed. This is the result of recording a wav file on an Android device and converting it on Windows PC. The length of the original file is 26:39, and the result of converting it to the default option is 25:47, which is displayed in Windows Explorer and the file size is 4,686KB. If this is converted using the -b:a 96k option, it has the same length as the original 26:39 and the file size is 18,740KB. I checked and played both the original file and the converted file using ocenaudio SW, it marked as 26:39 and played. However, the converted file by default is displayed in the time of 25:47 in Media Player and played. Below is the console output I tested. I don't find any difference. = defalut converting test = ffmpeg.exe -i 1.wav 1_default.mp3 ffmpeg version git-2020-08-28-ccc7120 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 10.2.1 (GCC) 20200805 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --enable-librav1e --enable-libsvtav1 --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf libavutil 56. 58.100 / 56. 58.100 libavcodec 58.101.100 / 58.101.100 libavformat58. 51.101 / 58. 51.101 libavdevice58. 11.101 / 58. 11.101 libavfilter 7. 87.100 / 7. 87.100 libswscale 5. 8.100 / 5. 8.100 libswresample 3. 8.100 / 3. 8.100 libpostproc55. 8.100 / 55. 8.100 Guessed Channel Layout for Input Stream #0.0 : mono Input #0, wav, from '1.wav': Duration: 00:26:39.00, bitrate: 256 kb/s Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 16000 Hz, mono, s16, 256 kb/s Stream mapping: Stream #0:0 -> #0:0 (pcm_s16le (native) -> mp3 (libmp3lame)) Press [q] to stop, [?] for help Output #0, mp3, to '1_default.mp3': Metadata: TSSE: Lavf58.51.101 Stream #0:0: Audio: mp3 (libmp3lame), 16000 Hz, mono, s16p Metadata: encoder : Lavc58.101.100 libmp3lame size=4685kB time=00:26:39.01 bitrate= 24.0kbits/s speed= 426x video:0kB audio:4685kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 0.004690% = 96k converting test = ffmpeg.exe -i 1.wav -b:a 96k 1_96k.mp3 ffmpeg version git-2020-08-28-ccc7120 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 10.2.1 (GCC) 20200805 configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --enable-librav1e --enable-libsvtav1 --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf libavutil 56. 58.100 / 56. 58.100 libavcodec 58.101.100 / 58.101.100 libavformat58. 51.101 / 58. 51.101 libavdevice58. 11.101 / 58. 11.101 libavfilter 7. 87.100 / 7. 87.100 libswscale 5. 8.100 / 5. 8.100 libswresample 3. 8.100 / 3. 8.100 libpostproc55. 8.100 / 55. 8.100 Guessed Channel Layout for Input Stream #0.0 : mono Input #0, wav, from
Re: [FFmpeg-user] builds for Windows
Anyone got any idea why? This could be a pretty significant pain. P On Wednesday, 2 September 2020, 19:56:45 BST, Vincent Torri wrote: Hello On Wed, Sep 2, 2020 at 8:29 PM Michael Koch wrote: > > "ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be > removed." > > Any idea where we can get builds for Windows after this date? for the Enlightenment project, i have written a small tool to compile from source its dependencies, including ffmpeg. I provide no binaries, only a tool to compile ffmpeg and its dependencies note that the tool compile only shared libraries tell me if that interests you regards Vincent Torri ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] builds for Windows
On 9/2/2020 11:31 AM, Carl Eugen Hoyos wrote: Am Mi., 2. Sept. 2020 um 20:29 Uhr schrieb Michael Koch : "ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be removed." Any idea where we can get builds for Windows after this date? The FFmpeg project only provides source code, no builds. An absolutely correct reply that doesn't actually answer the question asked. However, since the ffmpeg project _does_ list places to download pre-built versions (including zeranoe), it's rational to ask on this list. Is anyone going to take up the task? The compute part is covered but I don't have sufficient space or bandwidth to serve as a build distribution platform. z! ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] builds for Windows
Hello On Wed, Sep 2, 2020 at 8:29 PM Michael Koch wrote: > > "ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be > removed." > > Any idea where we can get builds for Windows after this date? for the Enlightenment project, i have written a small tool to compile from source its dependencies, including ffmpeg. I provide no binaries, only a tool to compile ffmpeg and its dependencies note that the tool compile only shared libraries tell me if that interests you regards Vincent Torri ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] builds for Windows
Am Mi., 2. Sept. 2020 um 20:29 Uhr schrieb Michael Koch : > > "ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be > removed." > > Any idea where we can get builds for Windows after this date? The FFmpeg project only provides source code, no builds. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] builds for Windows
"ffmpeg.zeranoe.com will close on Sep 18, 2020, and all builds will be removed." Any idea where we can get builds for Windows after this date? Michael ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ? About ffmpeg's prores implemention
On 9/2/20, Philippe Laterrade wrote: > Hi Paul, > > You're right. > It's just, I didn't find anything relevant to really adjust the output bit > rate. > Perhap's I missed something...somewhere. http://ffmpeg.org/ffmpeg-codecs.html#ProRes See bits_per_mb option. This is only for prores_ks encoder. If you use another, the default prores (prores_aw) encoder, in that case there is no any options to set, and encoder happily writes files that may be a lot bellow or above desired bitrate. > > Thank's for your help. > BR > Pilippe > > > > > > > -Message d'origine- > De : ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] De la part de Paul > B Mahol > Envoyé : mercredi 2 septembre 2020 18:08 > À : FFmpeg user questions > Objet : Re: [FFmpeg-user] ? About ffmpeg's prores implemention > > On 9/2/20, Philippe Laterrade wrote: >> Hi Valentin, >> >> I made some tests very recently with several qcsale value, but never >> reached >> exactly the bit rate specs announced by Apple. Did anyone has already >> success to get those specs? > > Next time specify what you actually tried. > > qscale is not for reaching specific bitrate. It solely purpose is to > give you best quality under variable bitrate, whatever that means. > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
[FFmpeg-user] ffmpeg NVENC won't run
Hello everyone,
I've installed Cuda toolkit, Nvidia driver and compiled ffmpeg,
installation went smoothly. all seems to be loaded but trying to run it
starts and stucks, no error messages but won't go any further, even on a
very basic command w/o NVENC. What can be wrong?
lealpa@cuda7:~$ sudo /home/lealpa/bin/ffmpeg -i udp://230.8.0.7:10008
teste.mp4
ffmpeg version N-98962-g0271098 Copyright (c) 2000-2020 the FFmpeg
developers
built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04)
configuration: --prefix=/home/lealpa/ffmpeg_build
--pkg-config-flags=--static
--extra-cflags=-I/home/lealpa/ffmpeg_build/include
--extra-ldflags=-L/home/lealpa/ffmpeg_build/lib --extra-libs='-lpthread
-lm' --bindir=/home/lealpa/bin --enable-gpl --enable-gnutls --enable-libass
--enable-libfdk-aac --enable-libfreetype --enable-libmp3lame
--enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libx265 --enable-nonfree
libavutil 56. 58.100 / 56. 58.100
libavcodec 58.101.101 / 58.101.101
libavformat58. 51.101 / 58. 51.101
libavdevice58. 11.101 / 58. 11.101
libavfilter 7. 87.100 / 7. 87.100
libswscale 5. 8.100 / 5. 8.100
libswresample 3. 8.100 / 3. 8.100
libpostproc55. 8.100 / 55. 8.100
lealpa@cuda7:~$ nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2017 NVIDIA Corporation
Built on Fri_Nov__3_21:07:56_CDT_2017
Cuda compilation tools, release 9.1, V9.1.85
Wed Sep 2 15:57:19 2020
+-+
| NVIDIA-SMI 440.64.00Driver Version: 440.64.00CUDA Version: 10.2
|
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr.
ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute
M. |
|===+==+==|
| 0 GeForce GTX 105... Off | :01:00.0 Off |
N/A |
| 36% 34CP0N/A / 75W | 0MiB / 4038MiB | 1%
Default |
+---+--+--+ffmpeg
version N-98962-g0271098 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04)
configuration: --prefix=/home/lealpa/ffmpeg_build
--pkg-config-flags=--static
--extra-cflags=-I/home/lealpa/ffmpeg_build/include
--extra-ldflags=-L/home/lealpa/ffmpeg_build/lib --extra-libs='-lpthread
-lm' --bindir=/home/lealpa/bin --enable-gpl --enable-gnutls --enable-libass
--enable-libfdk-aac --enable-libfreetype --enable-libmp3lame
--enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264
--enable-libx265 --enable-nonfree
libavutil 56. 58.100 / 56. 58.100
libavcodec 58.101.101 / 58.101.101
libavformat58. 51.101 / 58. 51.101
libavdevice58. 11.101 / 58. 11.101
libavfilter 7. 87.100 / 7. 87.100
libswscale 5. 8.100 / 5. 8.100
libswresample 3. 8.100 / 3. 8.100
libpostproc55. 8.100 / 55. 8.100
Hyper fast Audio and Video encoder
usage: ffmpeg [options] [[infile options] -i infile]... {[outfile options]
outfile}...
Thanks!
LP
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ? About ffmpeg's prores implemention
Hi Paul, You're right. It's just, I didn't find anything relevant to really adjust the output bit rate. Perhap's I missed something...somewhere. Thank's for your help. BR Pilippe -Message d'origine- De : ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] De la part de Paul B Mahol Envoyé : mercredi 2 septembre 2020 18:08 À : FFmpeg user questions Objet : Re: [FFmpeg-user] ? About ffmpeg's prores implemention On 9/2/20, Philippe Laterrade wrote: > Hi Valentin, > > I made some tests very recently with several qcsale value, but never reached > exactly the bit rate specs announced by Apple. Did anyone has already > success to get those specs? Next time specify what you actually tried. qscale is not for reaching specific bitrate. It solely purpose is to give you best quality under variable bitrate, whatever that means. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ? About ffmpeg's prores implemention
On 9/2/20, Philippe Laterrade wrote: > Hi Valentin, > > I made some tests very recently with several qcsale value, but never reached > exactly the bit rate specs announced by Apple. Did anyone has already > success to get those specs? Next time specify what you actually tried. qscale is not for reaching specific bitrate. It solely purpose is to give you best quality under variable bitrate, whatever that means. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ? About ffmpeg's prores implemention
On 8/31/20, Edward Park wrote: > Hi, > >> Again just typical FUD from same person. > > I'm not sure what you are referring to, what's there to spread fud about?? Closely read your text that you removed out. > >> It is obviously slower, hahaha. > > > What is, AME or one of the prores encoders included in FFmpeg? I mean > obviously it'd depend on the job and hardware but for what it's worth I > compared prores_ks with xq and it took around twice the wallclock time. > It did indeed take way more than twice the cpu time though, but if its > output has problems then the whole point is moot :/ Your comparison is not scientifically proven and thus is highly personally biased. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ? About ffmpeg's prores implemention
Hi Valentin, I made some tests very recently with several qcsale value, but never reached exactly the bit rate specs announced by Apple. Did anyone has already success to get those specs? BR. Philippe -Message d'origine- De : ffmpeg-user [mailto:ffmpeg-user-boun...@ffmpeg.org] De la part de Valentin Schweitzer Envoyé : mercredi 2 septembre 2020 17:29 À : ffmpeg-user@ffmpeg.org Objet : Re: [FFmpeg-user] ? About ffmpeg's prores implemention On 31/08/2020 10:41, Phil Rhodes via ffmpeg-user wrote: > I honestly can't remember most of what that does but the number after > "-qscale:v" controls overall bitrate from 1 to 31. Reducing it increases > bitrate (obviously!) and if you set it very low, it may create files that are > wildly out of specification that Apple decoders may not like. Hi, I think i may be able to clear up the behavior of qscale a little. According to https://trac.ffmpeg.org/wiki/Encode/MPEG-4 qscale behaves similar to the quantization parameter in h264. That parameter is pretty well explained here: https://www.pixeltools.com/rate_control_paper.html but in short: The quantization parameter basically tells an encoder how much detail can be "thrown away" during encoding. So if the parameter is lower, more detail is preserved, if it's higher, more is thrown away, which leads to a higher or lower bitrate respectively. This is not the most detailed explanation, but I hope it helps to clear up why a lower number leads to a higher bitrate. Hope that helps, Valentin ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] ? About ffmpeg's prores implemention
On 31/08/2020 10:41, Phil Rhodes via ffmpeg-user wrote: > I honestly can't remember most of what that does but the number after > "-qscale:v" controls overall bitrate from 1 to 31. Reducing it increases > bitrate (obviously!) and if you set it very low, it may create files that are > wildly out of specification that Apple decoders may not like. Hi, I think i may be able to clear up the behavior of qscale a little. According to https://trac.ffmpeg.org/wiki/Encode/MPEG-4 qscale behaves similar to the quantization parameter in h264. That parameter is pretty well explained here: https://www.pixeltools.com/rate_control_paper.html but in short: The quantization parameter basically tells an encoder how much detail can be "thrown away" during encoding. So if the parameter is lower, more detail is preserved, if it's higher, more is thrown away, which leads to a higher or lower bitrate respectively. This is not the most detailed explanation, but I hope it helps to clear up why a lower number leads to a higher bitrate. Hope that helps, Valentin ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
Re: [FFmpeg-user] seeking not working as expected
On Sun, Aug 30, 2020 at 03:44:15PM -0600, Mike Brown wrote: > On Sun, Aug 30, 2020 at 09:36:42PM +0200, Carl Eugen Hoyos wrote: > > Am So., 30. Aug. 2020 um 21:32 Uhr schrieb Mike Brown : > > > > > > I'm using a Zeranoe 64-bit Windows build, ffmpeg version > > > git-2020-06-28-4cfcfb3 on Win7. > > > > > > I am trying to split DV-AVI files, using > > > https://trac.ffmpeg.org/wiki/Seeking as my guide. > > > For example, I want to extract a segment from 4h54m24s to 4h57m08s into > > > its own file. > > > > > > The following syntax works great, but is, as promised by the wiki, > > > painfully slow: > > > > > > ffmpeg -i splitme.avi -ss 4:54:24 -t 2:44 -c copy -y out.avi > > > > > > The wiki suggests that the following should work too, but much faster: > > > > > > ffmpeg -ss 4:54:24 -i splitme.avi -t 2:44 -c copy -y out.avi > > > > > > It definitely starts fast, but unexpectedly, it produces a segment from > > > 0:08:21 to, well, I don't know because my disk filled up, so it was many > > > hours > > > long! > > > > > > Am I doing something wrong? > > > > Complete, uncut console output missing. > > (Feel free to press q before your disk is full.) > > OK, I pressed q after 11900 frames (requested duration 2:44 should only yield > ~4915 frames). I've also tried this same command line with more verbose time > specs (04:54:24.0 and 00:02:44.0), but it made no difference. > > I:\video workspace\captures>ffmpeg -loglevel debug -ss 4:54:24 -i splitme.avi > -t 2:44 -c copy -y 34.avi > ffmpeg version git-2020-06-28-4cfcfb3 Copyright (c) 2000-2020 the FFmpeg > developers > built with gcc 9.3.1 (GCC) 20200621 > configuration: --enable-gpl --enable-version3 --enable-sdl2 > --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass > --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame > --enable-libopencore-amrnb --enable-libopencore- > amrwb --enable-libopenjpeg --enable-libopus --enable-libshine > --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora > --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp > --enable-libx264 --enable-libx265 --enable-libxml > 2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp > --enable-libvidstab --enable-libvmaf --enable-libvorbis > --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid > --enable-libaom --enable-libgsm --disable-w32threads --enable > -libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va > --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth > --enable-libopenmpt --enable-amf > libavutil 56. 55.100 / 56. 55.100 > libavcodec 58. 93.100 / 58. 93.100 > libavformat58. 47.100 / 58. 47.100 > libavdevice58. 11.100 / 58. 11.100 > libavfilter 7. 86.100 / 7. 86.100 > libswscale 5. 8.100 / 5. 8.100 > libswresample 3. 8.100 / 3. 8.100 > libpostproc55. 8.100 / 55. 8.100 > Splitting the commandline. > Reading option '-loglevel' ... matched as option 'loglevel' (set logging > level) with argument 'debug'. > Reading option '-ss' ... matched as option 'ss' (set the start time offset) > with argument '4:54:24'. > Reading option '-i' ... matched as input url with argument 'splitme.avi'. > Reading option '-t' ... matched as option 't' (record or transcode "duration" > seconds of audio/video) with argument '2:44'. > Reading option '-c' ... matched as option 'c' (codec name) with argument > 'copy'. > Reading option '-y' ... matched as option 'y' (overwrite output files) with > argument '1'. > Reading option '34.avi' ... matched as output url. > Finished splitting the commandline. > Parsing a group of options: global . > Applying option loglevel (set logging level) with argument debug. > Applying option y (overwrite output files) with argument 1. > Successfully parsed a group of options. > Parsing a group of options: input url splitme.avi. > Applying option ss (set the start time offset) with argument 4:54:24. > Successfully parsed a group of options. > Opening an input file: splitme.avi. > [NULL @ 00448580] Opening 'splitme.avi' for reading > [file @ 00449e80] Setting default whitelist 'file,crypto,data' > [avi @ 00448580] Format avi probed with size=2048 and score=100 > [avi @ 0044a080] use odml:1 > [avi @ 00448580] ODML index invalid > st:1 removing common factor 4 from timebase > [avi @ 00448580] ODML index invalid > [avi @ 00448580] Before avformat_find_stream_info() pos: 34816 bytes > read:688128 seeks:6 nb_streams:2 > [avi @ 00448580] parser not found for codec dvvideo, packets or times > may be invalid. > [avi @ 00448580] parser not found for codec pcm_s16le, packets or > times may be invalid. > [avi @ 00448580] parser not found for codec dvvideo, packets or times > may be invalid. > [avi @ 00448580] parser not found for codec pcm_s16le, packets or > times may be
