# WMV High Profile - possible syntax error?
**URL:** https://discussion.mcebuddy2x.com/t/wmv-high-profile-possible-syntax-error/801
**Category:** Profiles
**Created:** [October 15, 2017, 5:21pm UTC](https://discussion.mcebuddy2x.com/t/wmv-high-profile-possible-syntax-error/801 "2017-10-15T17:21:56Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@d4d9d4](https://discussion.mcebuddy2x.com/u/d4d9d4)
#### Post date: [October 15, 2017, 5:21pm UTC](https://discussion.mcebuddy2x.com/t/wmv-high-profile-possible-syntax-error/801/1 "2017-10-15T17:21:57Z")
**Request Type:**
Error (possible)
**MCEBuddy Version and Type (32bit or 64bit):**
2.4.Beta8
**Operating System and Type (32bit or 64bit):**
Windows Server 2012 R2 64bit
**Summary of the problem or suggestion:**
When using WMV High - I ran into this from FFmpeg ?
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Please use -b:a or -b:v, -b is ambiguous
Is it possible you meant -b:v 4444444 ?
is this something I can update myself ? and try to help ?
**Screenshots:**
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Launching process C:\Program Files\MCEBuddy2x\ffmpeg\ffmpeg.exe
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Process arguments -hide\_banner -probesize 100M -analyzeduration 300M -threads 0 -drc\_scale 0.8 -y -i “F:\Conversion\__MCE\_Buddy\_Temp_\_\working0\Arrow (2012) - S06E01 - Fallout.ts” -ss 3 -vf hqdn3d,crop=1280:720:0:0 -vcodec wmv2 -b 4444444 -sn -acodec wmav2 -ab 192k -ac 2 -subq 1 -refs 1 -trellis 0 -b\_strategy 1 -me\_method dia -pass 1 -passlogfile “F:\Conversion\__MCE\_Buddy\_Temp_\_\working0\MCEBuddy2Pass.log” "F:\Conversion\__MCE\_Buddy\_Temp_\_\working0\Arrow (2012) - S06E01 - Fallout-converted.wmv"
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> UI Session Admin Process : True
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Starting process as a UISession process with Admin privileges. This requires atleast 1 user to be logged into the system (remote desktop or locally)
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Setting process priority to Normal
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Input #0, mpegts, from ‘F:\Conversion\__MCE\_Buddy\_Temp_\_\working0\Arrow (2012) - S06E01 - Fallout.ts’:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Duration: 00:38:41.74, start: 1.400000, bitrate: 15944 kb/s
–\> Video duration=2321.74
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Program 1
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Metadata:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> service\_name : Service01
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> service\_provider: FFmpeg
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream #0:0[0x100]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p(tv), 1280x720 [SAR 1:1 DAR 16:9], Closed Captions, 59.94 fps, 59.94 tbr, 90k tbn, 119.88 tbc
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream #0:10x101: Audio: ac3 ([129][0][0][0] / 0x0081), 48000 Hz, 5.1(side), fltp, 384 kb/s
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Please use -b:a or -b:v, -b is ambiguous
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> [asf @ 00000055f3b184c0] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Last message repeated 1 times
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Output #0, asf, to ‘F:\Conversion\__MCE\_Buddy\_Temp_\_\working0\Arrow (2012) - S06E01 - Fallout-converted.wmv’:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Metadata:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> WM/EncodingSettings: Lavf57.38.100
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream #0:0: Video: wmv2 (WMV2 / 0x32564D57), yuv420p, 1280x720 [SAR 1:1 DAR 16:9], q=2-31, 4444 kb/s, 59.94 fps, 1k tbn, 59.94 tbc
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Metadata:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> encoder : Lavc57.46.100 wmv2
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Side data:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> cpb: bitrate max/min/avg: 0/0/4444444 buffer size: 0 vbv\_delay: -1
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream #0:1(eng): Audio: wmav2 (a[1][0][0] / 0x0161), 48000 Hz, stereo, fltp, 192 kb/s
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Metadata:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> encoder : Lavc57.46.100 wmav2
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream mapping:
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream #0:0 -\> #0:0 (mpeg2video (native) -\> wmv2 (native))
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Stream #0:1 -\> #0:1 (ac3 (native) -\> wmav2 (native))
2017-10-15T10:12:40 MCEBuddy.AppWrapper.FFmpeg --\> Press [q] to stop, [?] for help
2017-10-15T10:12:41 MCEBuddy.AppWrapper.FFmpeg --\> frame= 0 fps=0.0 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A speed= 0x
2017-10-15T10:12:41 MCEBuddy.AppWrapper.FFmpeg --\> frame= 0 fps=0.0 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A speed= 0x
2017-10-15T10:12:42 MCEBuddy.AppWrapper.FFmpeg --\> frame= 0 fps=0.0 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A speed= 0x
2017-10-15T10:12:43 MCEBuddy.AppWrapper.FFmpeg --\> frame= 0 fps=0.0 q=0.0 size= 1kB time=00:00:00.00 bitrate=N/A speed= 0x
2017-10-15T10:12:43 MCEBuddy.AppWrapper.FFmpeg --\> frame= 9 fps=3.5 q=2.0 size= 45kB time=00:00:00.13 bitrate=2730.1kbits/s dup=1 drop=0 speed=0.0525x
2017-10-15T10:12:44 MCEBuddy.AppWrapper.FFmpeg --\> frame= 32 fps= 10 q=7.8 size= 460kB time=00:00:00.51 bitrate=7279.2kbits/s dup=1 drop=0 speed=0.169x
2017-10-15T10:12:44 MCEBuddy.AppWrapper.FFmpeg --\> frame= 51 fps= 14 q=9.9 size= 648kB time=00:00:00.83 bitrate=6355.3kbits/s dup=1 drop=0 speed=0.233x
---
### Author:  [@Goose](https://discussion.mcebuddy2x.com/u/Goose)
#### Post date: [October 15, 2017, 6:13pm UTC](https://discussion.mcebuddy2x.com/t/wmv-high-profile-possible-syntax-error/801/2 "2017-10-15T18:13:58Z")
This isn’t a bug, ffmpeg supports different commands. -b is valid and is used to represent -b:v, it’s just a warning. You can ignore it
What’s the issue you’re facing?
---
### Author:  [@d4d9d4](https://discussion.mcebuddy2x.com/u/d4d9d4)
#### Post date: [October 15, 2017, 10:02pm UTC](https://discussion.mcebuddy2x.com/t/wmv-high-profile-possible-syntax-error/801/3 "2017-10-15T22:02:41Z")
I was just trying out the various file formats to get a rough idea of timings to strip commercials/encode to a different file format from a 6.8GB .ts hdhomerun connect file. The WMV seem to take 2+ hours, when I am less on the others – just thought this was an apparent error message that could contribute to the longer run. I will avoid the WMV as I thought I am doing better with my other samples:
MKV High – 1G/1h23m, MKV Normal – 829KB/38min, MKV Unprocessed 4.1GB/23min, MKV HEVC 1.6GB/1h20min. Once I decide on the format I wish to utilize, then I intend to set and forget. Thanks again.
---
### Author:  [@Goose](https://discussion.mcebuddy2x.com/u/Goose)
#### Post date: [October 15, 2017, 10:54pm UTC](https://discussion.mcebuddy2x.com/t/wmv-high-profile-possible-syntax-error/801/4 "2017-10-15T22:54:18Z")
Taking this much time for WMV High is normal for a couple of reasons;
1. It’s a High quality profile, you really don’t need High quality profiles unless your have a specific need because it’s really cranks up the settings. Most cases Normal will suffice.
2. There’ no hardware acceleration available for WMV codecs so it’s up to the CPU