Why is converting WMV to MP4 so slow?What is a Codec (e.g. DivX?), and how does it differ from a File Format...

What does it mean when multiple 々 marks follow a 、?

Silly Sally's Movie

Do f-stop and exposure time perfectly cancel?

Time travel short story where dinosaur doesn't taste like chicken

Is a lawful good "antagonist" effective?

The three point beverage

Force user to remove USB token

How could our ancestors have domesticated a solitary predator?

What to do when during a meeting client people start to fight (even physically) with each others?

Running a subshell from the middle of the current command

What is the blue range indicating on this manifold pressure gauge?

Gravity alteration as extermination tool viable?

Rejected in 4th interview round citing insufficient years of experience

What exactly is the purpose of connection links straped between the rocket and the launch pad

Is it illegal in Germany to take sick leave if you caused your own illness with food?

Confusion with the nameplate of an induction motor

Welcoming 2019 Pi day: How to draw the letter π?

Life insurance that covers only simultaneous/dual deaths

Is going from continuous data to categorical always wrong?

Playing ONE triplet (not three)

What is the likely impact on flights of grounding an entire aircraft series?

Is King K. Rool's down throw to up-special a true combo?

What has been your most complicated TikZ drawing?

Unreachable code, but reachable with exception



Why is converting WMV to MP4 so slow?


What is a Codec (e.g. DivX?), and how does it differ from a File Format (e.g. MPG)?Troubleshooting “stream 0 codec frame rate differs from container frame rate” when splitting AVI in ffmpegFFMpeg convert jpeg images to videoSet MP4 thumbnailProblems with frame rate on video conversion using ffmpeg with libx264Using ffmpeg to make a movie from png filesUsing ffmpeg to split mkv but get a few seconds video lost (cutting between keyframes without re-encoding?)Why does avconv change the fps when deinterlacing?How to multicast live H264 without transcoding?Issue in streaming to rtmp via ffmpegExtract closed captions (CC) From .mkv file interlaced in video stream













10















I am trying to convert a video from WMV to MP4 with FFmpeg but it takes couple of hours. If I try to convert it to AVI it only takes about 10-15 minutes.



ffmpeg version



ffmpeg version N-43206-gf857465
built on Aug 4 2012 16:10:39 with gcc 4.7.1 (GCC)


Conversion to MP4



ffmpeg -i input.wmv -vcodec libx264 output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03427620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03427620] profile High, level 3.1
[libx264 @ 03427620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to MP4 with copy



ffmpeg -i input.wmv -c:v:1 copy output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03437620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03437620] profile High, level 3.1
[libx264 @ 03437620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to AVI with copy



ffmpeg -i input.wmv -c:v:1 copy output.avi

Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
Output #0, avi, to 'output.avi':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
ISFT : Lavf54.22.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1280x720, q=2-31, 20
0 kb/s, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> mpeg4)


Are there some additional parameters I need to pass?










share|improve this question

























  • Of course it's faster if you're just copying the bitstream — with copy, you're not re-encoding anything. What hardware do you have, e.g. CPU? What's your OS and which version of FFmpeg is that?

    – slhck
    Aug 10 '12 at 8:44













  • @slhck: The computer is not very fast E5400 2.7GHz but why is it slow for mp4 while it is fast for avi?

    – Giorgi
    Aug 10 '12 at 9:04











  • I don't see any AVI output in your question. Could you update it with the full output?

    – slhck
    Aug 10 '12 at 9:07











  • @slhck: added avi output

    – Giorgi
    Aug 10 '12 at 9:19
















10















I am trying to convert a video from WMV to MP4 with FFmpeg but it takes couple of hours. If I try to convert it to AVI it only takes about 10-15 minutes.



ffmpeg version



ffmpeg version N-43206-gf857465
built on Aug 4 2012 16:10:39 with gcc 4.7.1 (GCC)


Conversion to MP4



ffmpeg -i input.wmv -vcodec libx264 output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03427620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03427620] profile High, level 3.1
[libx264 @ 03427620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to MP4 with copy



ffmpeg -i input.wmv -c:v:1 copy output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03437620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03437620] profile High, level 3.1
[libx264 @ 03437620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to AVI with copy



ffmpeg -i input.wmv -c:v:1 copy output.avi

Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
Output #0, avi, to 'output.avi':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
ISFT : Lavf54.22.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1280x720, q=2-31, 20
0 kb/s, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> mpeg4)


Are there some additional parameters I need to pass?










share|improve this question

























  • Of course it's faster if you're just copying the bitstream — with copy, you're not re-encoding anything. What hardware do you have, e.g. CPU? What's your OS and which version of FFmpeg is that?

    – slhck
    Aug 10 '12 at 8:44













  • @slhck: The computer is not very fast E5400 2.7GHz but why is it slow for mp4 while it is fast for avi?

    – Giorgi
    Aug 10 '12 at 9:04











  • I don't see any AVI output in your question. Could you update it with the full output?

    – slhck
    Aug 10 '12 at 9:07











  • @slhck: added avi output

    – Giorgi
    Aug 10 '12 at 9:19














10












10








10


2






I am trying to convert a video from WMV to MP4 with FFmpeg but it takes couple of hours. If I try to convert it to AVI it only takes about 10-15 minutes.



ffmpeg version



ffmpeg version N-43206-gf857465
built on Aug 4 2012 16:10:39 with gcc 4.7.1 (GCC)


Conversion to MP4



ffmpeg -i input.wmv -vcodec libx264 output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03427620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03427620] profile High, level 3.1
[libx264 @ 03427620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to MP4 with copy



ffmpeg -i input.wmv -c:v:1 copy output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03437620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03437620] profile High, level 3.1
[libx264 @ 03437620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to AVI with copy



ffmpeg -i input.wmv -c:v:1 copy output.avi

Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
Output #0, avi, to 'output.avi':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
ISFT : Lavf54.22.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1280x720, q=2-31, 20
0 kb/s, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> mpeg4)


Are there some additional parameters I need to pass?










share|improve this question
















I am trying to convert a video from WMV to MP4 with FFmpeg but it takes couple of hours. If I try to convert it to AVI it only takes about 10-15 minutes.



ffmpeg version



ffmpeg version N-43206-gf857465
built on Aug 4 2012 16:10:39 with gcc 4.7.1 (GCC)


Conversion to MP4



ffmpeg -i input.wmv -vcodec libx264 output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03427620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03427620] profile High, level 3.1
[libx264 @ 03427620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to MP4 with copy



ffmpeg -i input.wmv -c:v:1 copy output.mp4

libavutil 51. 66.100 / 51. 66.100
libavcodec 54. 49.100 / 54. 49.100
libavformat 54. 22.100 / 54. 22.100
libavdevice 54. 2.100 / 54. 2.100
libavfilter 3. 5.102 / 3. 5.102
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 15.100 / 0. 15.100
libpostproc 52. 0.100 / 52. 0.100
Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
[libx264 @ 03437620] using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle Cac
he64
[libx264 @ 03437620] profile High, level 3.1
[libx264 @ 03437620] 264 - core 125 r2208 d9d2288 - H.264/MPEG-4 AVC codec - Cop
yleft 2003-2012 - http://www.videolan.org/x264.html - options: cabac=1 ref=3 deb
lock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 m
e_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chro
ma_qp_offset=-2 threads=3 lookahead_threads=1 sliced_threads=0 nr=0 decimate=1 i
nterlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1
b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=15 scenec
ut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=
0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
Output #0, mp4, to 'output.mp4':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Stream #0:0: Video: h264 ([33][0][0][0] / 0x0021), yuv420p, 1280x720, q=-1--
1, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> libx264)


Conversion to AVI with copy



ffmpeg -i input.wmv -c:v:1 copy output.avi

Input #0, asf, from 'input.wmv':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
encoder : Lavf54.22.100
Duration: 01:14:23.06, start: 0.000000, bitrate: 324 kb/s
Stream #0:0: Video: msmpeg4 (MP43 / 0x3334504D), yuv420p, 1280x720, 15 tbr,
1k tbn, 1k tbc
Output #0, avi, to 'output.avi':
Metadata:
WMFSDKVersion : 12.0.7601.17514
WMFSDKNeeded : 0.0.0.0000
IsVBR : 0
ISFT : Lavf54.22.100
Stream #0:0: Video: mpeg4 (FMP4 / 0x34504D46), yuv420p, 1280x720, q=2-31, 20
0 kb/s, 15 tbn, 15 tbc
Stream mapping:
Stream #0:0 -> #0:0 (msmpeg4 -> mpeg4)


Are there some additional parameters I need to pass?







ffmpeg video-conversion mp4 wmv






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 10 '12 at 9:39









slhck

162k47448470




162k47448470










asked Aug 10 '12 at 7:47









GiorgiGiorgi

4592617




4592617













  • Of course it's faster if you're just copying the bitstream — with copy, you're not re-encoding anything. What hardware do you have, e.g. CPU? What's your OS and which version of FFmpeg is that?

    – slhck
    Aug 10 '12 at 8:44













  • @slhck: The computer is not very fast E5400 2.7GHz but why is it slow for mp4 while it is fast for avi?

    – Giorgi
    Aug 10 '12 at 9:04











  • I don't see any AVI output in your question. Could you update it with the full output?

    – slhck
    Aug 10 '12 at 9:07











  • @slhck: added avi output

    – Giorgi
    Aug 10 '12 at 9:19



















  • Of course it's faster if you're just copying the bitstream — with copy, you're not re-encoding anything. What hardware do you have, e.g. CPU? What's your OS and which version of FFmpeg is that?

    – slhck
    Aug 10 '12 at 8:44













  • @slhck: The computer is not very fast E5400 2.7GHz but why is it slow for mp4 while it is fast for avi?

    – Giorgi
    Aug 10 '12 at 9:04











  • I don't see any AVI output in your question. Could you update it with the full output?

    – slhck
    Aug 10 '12 at 9:07











  • @slhck: added avi output

    – Giorgi
    Aug 10 '12 at 9:19

















Of course it's faster if you're just copying the bitstream — with copy, you're not re-encoding anything. What hardware do you have, e.g. CPU? What's your OS and which version of FFmpeg is that?

– slhck
Aug 10 '12 at 8:44







Of course it's faster if you're just copying the bitstream — with copy, you're not re-encoding anything. What hardware do you have, e.g. CPU? What's your OS and which version of FFmpeg is that?

– slhck
Aug 10 '12 at 8:44















@slhck: The computer is not very fast E5400 2.7GHz but why is it slow for mp4 while it is fast for avi?

– Giorgi
Aug 10 '12 at 9:04





@slhck: The computer is not very fast E5400 2.7GHz but why is it slow for mp4 while it is fast for avi?

– Giorgi
Aug 10 '12 at 9:04













I don't see any AVI output in your question. Could you update it with the full output?

– slhck
Aug 10 '12 at 9:07





I don't see any AVI output in your question. Could you update it with the full output?

– slhck
Aug 10 '12 at 9:07













@slhck: added avi output

– Giorgi
Aug 10 '12 at 9:19





@slhck: added avi output

– Giorgi
Aug 10 '12 at 9:19










2 Answers
2






active

oldest

votes


















16














Stream copying



When you call -c:v:1 copy, FFmpeg will take the existing video bitstream and stream copy it. The video bitstream is just encapsulated in the outside container, e.g. WMV, AVI or MP4 – your actual video bitstream is msmpeg4 and will stay like this.



If you want to know more about what I'm talking about, see here: What is a Codec (e.g. DivX?), and how does it differ from a File Format (e.g. MPG)?



When copying the bitstream, FFmpeg doesn't need to actually decode and re-encode the actual video. It just needs to merge the video bitstream into a new container format, which is often a rather simple operation and therefore doesn't take long.



Encoding



In contrast to that, if you call -vcodec libx264 (or -c:v libx264, the syntax you should use because vcodec is deprecated), FFmpeg will be forced to decode the video bitstream from msmpeg4 to a raw format, then pipe it into x264, a H.264 encoder.



x264 is fast, but still, encoding video takes time – especially when it's 720p content. And it might take more than one hour, especially if your input is already longer than one hour. Also, your CPU might not be the fastest. This is the main reason older MPEG-4 Visual encoders like XviD are still around and very popular: They take less time to encode than H.264 codecs. They might not give you the best performance in terms of quality vs. file size, but they are fast.



That all being said: You can speed up x264 encoding by forcing a preset. Presets are encoder optimization settings and range from: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow. Your command could then look like this:



ffmpeg -i input.wmv -c:v libx264 -preset fast out.mp4


It should run faster than without the preset. The only drawback is that it doesn't achieve as good quality for the same compression rates in comparison to, for example, -preset veryslow.



Apart from that, there's not much you can do except for investing in a speedy CPU, and making sure you're running a recent build of FFmpeg with x264 support.



For more info see FFmpeg Wiki: H.264 Encoding Guide.






share|improve this answer


























  • Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

    – Giorgi
    Aug 10 '12 at 9:59











  • so which one the best for encoding, libx264 or h264?

    – Yohanes AI
    Jul 9 '18 at 9:55











  • @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

    – slhck
    Jul 9 '18 at 10:12











  • @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

    – Yohanes AI
    Jul 9 '18 at 10:26








  • 1





    @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

    – slhck
    5 mins ago



















2














AS I was playing (endless hours) with WMV->MP4 conversion, I found a superfast way to do it. But it has a price: a storage price. If you convert WMV to lossless, then from lossless to MP4, it does the full conversion in no time. But you need 100 times HDD space to store the lossless version, which is painful.



So it turns out you can chose from very slow or very HDD intensive versions of WMV->MP4 conversion and you have no other choice.



Converting a WMV to lossless AVI:
ffmpeg.exe -i screen.wmv -vcodec ffv1 screen.avi
Then converting lossless AVI to MP4 (or WebM, it doesn't matter)
ffmpeg.exe -i screen.avi screen.mp4



Superfast!






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f459896%2fwhy-is-converting-wmv-to-mp4-so-slow%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    16














    Stream copying



    When you call -c:v:1 copy, FFmpeg will take the existing video bitstream and stream copy it. The video bitstream is just encapsulated in the outside container, e.g. WMV, AVI or MP4 – your actual video bitstream is msmpeg4 and will stay like this.



    If you want to know more about what I'm talking about, see here: What is a Codec (e.g. DivX?), and how does it differ from a File Format (e.g. MPG)?



    When copying the bitstream, FFmpeg doesn't need to actually decode and re-encode the actual video. It just needs to merge the video bitstream into a new container format, which is often a rather simple operation and therefore doesn't take long.



    Encoding



    In contrast to that, if you call -vcodec libx264 (or -c:v libx264, the syntax you should use because vcodec is deprecated), FFmpeg will be forced to decode the video bitstream from msmpeg4 to a raw format, then pipe it into x264, a H.264 encoder.



    x264 is fast, but still, encoding video takes time – especially when it's 720p content. And it might take more than one hour, especially if your input is already longer than one hour. Also, your CPU might not be the fastest. This is the main reason older MPEG-4 Visual encoders like XviD are still around and very popular: They take less time to encode than H.264 codecs. They might not give you the best performance in terms of quality vs. file size, but they are fast.



    That all being said: You can speed up x264 encoding by forcing a preset. Presets are encoder optimization settings and range from: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow. Your command could then look like this:



    ffmpeg -i input.wmv -c:v libx264 -preset fast out.mp4


    It should run faster than without the preset. The only drawback is that it doesn't achieve as good quality for the same compression rates in comparison to, for example, -preset veryslow.



    Apart from that, there's not much you can do except for investing in a speedy CPU, and making sure you're running a recent build of FFmpeg with x264 support.



    For more info see FFmpeg Wiki: H.264 Encoding Guide.






    share|improve this answer


























    • Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

      – Giorgi
      Aug 10 '12 at 9:59











    • so which one the best for encoding, libx264 or h264?

      – Yohanes AI
      Jul 9 '18 at 9:55











    • @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

      – slhck
      Jul 9 '18 at 10:12











    • @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

      – Yohanes AI
      Jul 9 '18 at 10:26








    • 1





      @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

      – slhck
      5 mins ago
















    16














    Stream copying



    When you call -c:v:1 copy, FFmpeg will take the existing video bitstream and stream copy it. The video bitstream is just encapsulated in the outside container, e.g. WMV, AVI or MP4 – your actual video bitstream is msmpeg4 and will stay like this.



    If you want to know more about what I'm talking about, see here: What is a Codec (e.g. DivX?), and how does it differ from a File Format (e.g. MPG)?



    When copying the bitstream, FFmpeg doesn't need to actually decode and re-encode the actual video. It just needs to merge the video bitstream into a new container format, which is often a rather simple operation and therefore doesn't take long.



    Encoding



    In contrast to that, if you call -vcodec libx264 (or -c:v libx264, the syntax you should use because vcodec is deprecated), FFmpeg will be forced to decode the video bitstream from msmpeg4 to a raw format, then pipe it into x264, a H.264 encoder.



    x264 is fast, but still, encoding video takes time – especially when it's 720p content. And it might take more than one hour, especially if your input is already longer than one hour. Also, your CPU might not be the fastest. This is the main reason older MPEG-4 Visual encoders like XviD are still around and very popular: They take less time to encode than H.264 codecs. They might not give you the best performance in terms of quality vs. file size, but they are fast.



    That all being said: You can speed up x264 encoding by forcing a preset. Presets are encoder optimization settings and range from: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow. Your command could then look like this:



    ffmpeg -i input.wmv -c:v libx264 -preset fast out.mp4


    It should run faster than without the preset. The only drawback is that it doesn't achieve as good quality for the same compression rates in comparison to, for example, -preset veryslow.



    Apart from that, there's not much you can do except for investing in a speedy CPU, and making sure you're running a recent build of FFmpeg with x264 support.



    For more info see FFmpeg Wiki: H.264 Encoding Guide.






    share|improve this answer


























    • Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

      – Giorgi
      Aug 10 '12 at 9:59











    • so which one the best for encoding, libx264 or h264?

      – Yohanes AI
      Jul 9 '18 at 9:55











    • @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

      – slhck
      Jul 9 '18 at 10:12











    • @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

      – Yohanes AI
      Jul 9 '18 at 10:26








    • 1





      @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

      – slhck
      5 mins ago














    16












    16








    16







    Stream copying



    When you call -c:v:1 copy, FFmpeg will take the existing video bitstream and stream copy it. The video bitstream is just encapsulated in the outside container, e.g. WMV, AVI or MP4 – your actual video bitstream is msmpeg4 and will stay like this.



    If you want to know more about what I'm talking about, see here: What is a Codec (e.g. DivX?), and how does it differ from a File Format (e.g. MPG)?



    When copying the bitstream, FFmpeg doesn't need to actually decode and re-encode the actual video. It just needs to merge the video bitstream into a new container format, which is often a rather simple operation and therefore doesn't take long.



    Encoding



    In contrast to that, if you call -vcodec libx264 (or -c:v libx264, the syntax you should use because vcodec is deprecated), FFmpeg will be forced to decode the video bitstream from msmpeg4 to a raw format, then pipe it into x264, a H.264 encoder.



    x264 is fast, but still, encoding video takes time – especially when it's 720p content. And it might take more than one hour, especially if your input is already longer than one hour. Also, your CPU might not be the fastest. This is the main reason older MPEG-4 Visual encoders like XviD are still around and very popular: They take less time to encode than H.264 codecs. They might not give you the best performance in terms of quality vs. file size, but they are fast.



    That all being said: You can speed up x264 encoding by forcing a preset. Presets are encoder optimization settings and range from: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow. Your command could then look like this:



    ffmpeg -i input.wmv -c:v libx264 -preset fast out.mp4


    It should run faster than without the preset. The only drawback is that it doesn't achieve as good quality for the same compression rates in comparison to, for example, -preset veryslow.



    Apart from that, there's not much you can do except for investing in a speedy CPU, and making sure you're running a recent build of FFmpeg with x264 support.



    For more info see FFmpeg Wiki: H.264 Encoding Guide.






    share|improve this answer















    Stream copying



    When you call -c:v:1 copy, FFmpeg will take the existing video bitstream and stream copy it. The video bitstream is just encapsulated in the outside container, e.g. WMV, AVI or MP4 – your actual video bitstream is msmpeg4 and will stay like this.



    If you want to know more about what I'm talking about, see here: What is a Codec (e.g. DivX?), and how does it differ from a File Format (e.g. MPG)?



    When copying the bitstream, FFmpeg doesn't need to actually decode and re-encode the actual video. It just needs to merge the video bitstream into a new container format, which is often a rather simple operation and therefore doesn't take long.



    Encoding



    In contrast to that, if you call -vcodec libx264 (or -c:v libx264, the syntax you should use because vcodec is deprecated), FFmpeg will be forced to decode the video bitstream from msmpeg4 to a raw format, then pipe it into x264, a H.264 encoder.



    x264 is fast, but still, encoding video takes time – especially when it's 720p content. And it might take more than one hour, especially if your input is already longer than one hour. Also, your CPU might not be the fastest. This is the main reason older MPEG-4 Visual encoders like XviD are still around and very popular: They take less time to encode than H.264 codecs. They might not give you the best performance in terms of quality vs. file size, but they are fast.



    That all being said: You can speed up x264 encoding by forcing a preset. Presets are encoder optimization settings and range from: ultrafast, superfast, veryfast, faster, fast, medium, slow, slower, veryslow. Your command could then look like this:



    ffmpeg -i input.wmv -c:v libx264 -preset fast out.mp4


    It should run faster than without the preset. The only drawback is that it doesn't achieve as good quality for the same compression rates in comparison to, for example, -preset veryslow.



    Apart from that, there's not much you can do except for investing in a speedy CPU, and making sure you're running a recent build of FFmpeg with x264 support.



    For more info see FFmpeg Wiki: H.264 Encoding Guide.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited 6 mins ago

























    answered Aug 10 '12 at 9:37









    slhckslhck

    162k47448470




    162k47448470













    • Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

      – Giorgi
      Aug 10 '12 at 9:59











    • so which one the best for encoding, libx264 or h264?

      – Yohanes AI
      Jul 9 '18 at 9:55











    • @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

      – slhck
      Jul 9 '18 at 10:12











    • @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

      – Yohanes AI
      Jul 9 '18 at 10:26








    • 1





      @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

      – slhck
      5 mins ago



















    • Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

      – Giorgi
      Aug 10 '12 at 9:59











    • so which one the best for encoding, libx264 or h264?

      – Yohanes AI
      Jul 9 '18 at 9:55











    • @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

      – slhck
      Jul 9 '18 at 10:12











    • @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

      – Yohanes AI
      Jul 9 '18 at 10:26








    • 1





      @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

      – slhck
      5 mins ago

















    Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

    – Giorgi
    Aug 10 '12 at 9:59





    Thanks for the answer. I'm not sure if I was clear or not but if I use copy it is still very slow. I tried your command and it has processed only 4 second after 5 minutes. My video is about 75 minutes long and converting to avi takes only 15 minutes but mp4 takes several hours.

    – Giorgi
    Aug 10 '12 at 9:59













    so which one the best for encoding, libx264 or h264?

    – Yohanes AI
    Jul 9 '18 at 9:55





    so which one the best for encoding, libx264 or h264?

    – Yohanes AI
    Jul 9 '18 at 9:55













    @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

    – slhck
    Jul 9 '18 at 10:12





    @NPE There is no difference as ffmpeg by default uses libx264 when you specify ´h264` as the encoder.

    – slhck
    Jul 9 '18 at 10:12













    @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

    – Yohanes AI
    Jul 9 '18 at 10:26







    @slhck When I trying to use this parameter -y -i fileSource -s 1920x1080 -vcodec libx264 crf 20 fileOutput takes more than an hours. To make this faster, what a recommendation parameter should I add based on your experience? Does -preset fast parameter enough?

    – Yohanes AI
    Jul 9 '18 at 10:26






    1




    1





    @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

    – slhck
    5 mins ago





    @PeterCordes I changed it to fast. Some interesting statistics (if VMAF can be trusted here): streaminglearningcenter.com/blogs/…

    – slhck
    5 mins ago













    2














    AS I was playing (endless hours) with WMV->MP4 conversion, I found a superfast way to do it. But it has a price: a storage price. If you convert WMV to lossless, then from lossless to MP4, it does the full conversion in no time. But you need 100 times HDD space to store the lossless version, which is painful.



    So it turns out you can chose from very slow or very HDD intensive versions of WMV->MP4 conversion and you have no other choice.



    Converting a WMV to lossless AVI:
    ffmpeg.exe -i screen.wmv -vcodec ffv1 screen.avi
    Then converting lossless AVI to MP4 (or WebM, it doesn't matter)
    ffmpeg.exe -i screen.avi screen.mp4



    Superfast!






    share|improve this answer




























      2














      AS I was playing (endless hours) with WMV->MP4 conversion, I found a superfast way to do it. But it has a price: a storage price. If you convert WMV to lossless, then from lossless to MP4, it does the full conversion in no time. But you need 100 times HDD space to store the lossless version, which is painful.



      So it turns out you can chose from very slow or very HDD intensive versions of WMV->MP4 conversion and you have no other choice.



      Converting a WMV to lossless AVI:
      ffmpeg.exe -i screen.wmv -vcodec ffv1 screen.avi
      Then converting lossless AVI to MP4 (or WebM, it doesn't matter)
      ffmpeg.exe -i screen.avi screen.mp4



      Superfast!






      share|improve this answer


























        2












        2








        2







        AS I was playing (endless hours) with WMV->MP4 conversion, I found a superfast way to do it. But it has a price: a storage price. If you convert WMV to lossless, then from lossless to MP4, it does the full conversion in no time. But you need 100 times HDD space to store the lossless version, which is painful.



        So it turns out you can chose from very slow or very HDD intensive versions of WMV->MP4 conversion and you have no other choice.



        Converting a WMV to lossless AVI:
        ffmpeg.exe -i screen.wmv -vcodec ffv1 screen.avi
        Then converting lossless AVI to MP4 (or WebM, it doesn't matter)
        ffmpeg.exe -i screen.avi screen.mp4



        Superfast!






        share|improve this answer













        AS I was playing (endless hours) with WMV->MP4 conversion, I found a superfast way to do it. But it has a price: a storage price. If you convert WMV to lossless, then from lossless to MP4, it does the full conversion in no time. But you need 100 times HDD space to store the lossless version, which is painful.



        So it turns out you can chose from very slow or very HDD intensive versions of WMV->MP4 conversion and you have no other choice.



        Converting a WMV to lossless AVI:
        ffmpeg.exe -i screen.wmv -vcodec ffv1 screen.avi
        Then converting lossless AVI to MP4 (or WebM, it doesn't matter)
        ffmpeg.exe -i screen.avi screen.mp4



        Superfast!







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 7 '13 at 21:33









        Marcell FotiMarcell Foti

        1211




        1211






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f459896%2fwhy-is-converting-wmv-to-mp4-so-slow%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Why not use the yoke to control yaw, as well as pitch and roll? Announcing the arrival of...

            Couldn't open a raw socket. Error: Permission denied (13) (nmap)Is it possible to run networking commands...

            VNC viewer RFB protocol error: bad desktop size 0x0I Cannot Type the Key 'd' (lowercase) in VNC Viewer...