Hardware encoding still seems to be broken

[Nick Teeter]

I did not experience this error with 1.22, but I do experience it with 1.25, 1.26, and now 2.0.

See attached screenshot.  Simply trying to convert Wildlife.wmv to Wildlife.mp4:

 MediaInfo mediaInfo = new MediaInfo { InputFile = file };

                if (mediaInfo.Open())

                {

                    // Open a new transcoder

                    using (Transcoder transcoder = new Transcoder())

                    {

                        // Set the input file

                        MediaSocket input = MediaSocket.FromMediaInfo(mediaInfo);

                        transcoder.Inputs.Add(input);

                        // Set the output file

                        MediaSocket output = MediaSocket.FromPreset(Preset.Video.Generic.MP4.Base_H264_AAC);

                        output.File = outputFile;

                            // Force re-encoding

                            output.Pins[0].Params.Add(Param.ReEncode, Use.On);

                            // Enable hardware acceleration

                            output.Pins[0].Params.Add(Param.HardwareEncoder, HardwareEncoder.Auto);

                            (output.Pins[0].StreamInfo as VideoStreamInfo).FrameRate = 30.0;

                        transcoder.Outputs.Add(output);

                        if (transcoder.Open())

                        {

                            transcoder.Run();

                            transcoder.Close();

                        }

                    }

                }

[VK]

Can you post hardware details? Also OS version and driver version.

You can use:

Intel Processor Identification Utility (https://downloadcenter.intel.com/download/7838)

Intel Driver Update Utility(https://downloadcenter.intel.com/download/24345/Intel-Driver-Update-Utility).

[Nick Teeter]

Windows 7 Enterprise SP1

HP EliteBook 2570p

Intel Core i5-3360M 2.8 GHz

Intel HD Graphics 4000, 10.18.10.4226

[VK]

We are fixing this in 2.1.

[AVBlocks]

The issue turned out to be not so much with the i5-3360M, but with Windows 7. AVBlocks currently requires Direct X 11.1 in order to use Intel's hardware acceleration. This is being fixed now to work with older DirectX API.

[VK]

Fixed in AVBlocks 2.1.