VidCoder: Alternative HandBrake GUI for Windows

[Ruriko]

You mean burn them into the picture? Select the "burn in" checkbox next to that setting.

The only problem is I can't pick English & burn in :(

[RandomEngy]

It's been added to the Beta version. You can wait for the feature to appear in Stable or switch to it.

[pearlblack15]

Hi, a quick question about quick sync support in VidCoder: Does it support encoding in 32 bit windows? Because, according to handbrake site, it says it will only support the 64 bit version. However, I remember I used QSV on VidCoder and successfully encoded a test file but unfortunately I had been failing ever since. It no longer encodes and the vidcoderworker.exe terminates unexpectedly. Therefore I checked the handbrake site for information and read the following page: https://trac.handbrake.fr/milestone/QuickSync%20Beta.

I tried again with H.264 encoded files to re-compress again with QSV (since the page said, it could only decode H.264 although I am not sure what decoding has to do with encoding. The decoding part should be have carried out by other codecs prior to encoding by QSV.) and it failed again.
Throw some light as to what is the system requirement to implement QSV encoding.

Thank you. Great and easy application btw :)

[RandomEngy]

You encoded some stuff with QSV in VidCoder? I haven't done any work to support it (don't have hardware to test with). I guess it shows up in the video encoder list for you?

[therube]

> * Added elapsed encode time to log.

Thank you :o.

[therube]

Unicode (file/path name) support ?

[RandomEngy]

Looks like they just submitted a patch to fix it: https://trac.handbrake.fr/changeset/5798 I'll make sure I encode to UTF-8 and everything is working when I get a chance.

[pearlblack15]

You encoded some stuff with QSV in VidCoder?....... I guess it shows up in the video encoder list for you?

Yes, like I said. I even compared the two videos. While the encoding was faster by few seconds for QSV, the quality of the video was slightly lower than x264 CPU encoding (with default settings, same bitrate, 2 pass encoding). May be some internal settings had an effect on overall quality/speed. Mediainfo showed slightly different results like 2 ReFrames(qsv) vs 4(x264). Anyway, that was the first and last time I had with QSV. I had deleted the stuffs so now I cannot give any evidence to my claim lol

And yes, it lists QSV on video encoder list.
Thank you for clarification btw. Looking forward to use QSV soon in VidCoder (x86).

[skanskan]

Hello

Nice to find good software like this, and free.
Could you please enable the option to type an exact number for the output fps.
Now you have to select among several values, but you can't select for example 1fps, that could be useful for test and compatibility purposes, and in my case I like to encode some videos with very low framerate because they are tutorials with few movement.

regards

[RandomEngy]

Released VidCoder 1.5.7 Beta (https://vidcoder.codeplex.com/releases/view/113094):

* Updated HandBrake core to SVN 4819.
* About dialog now pulls down HandBrake version from the DLL.
* Added a confirmation dialog to Stop if the encode has been going on for more than 5 minutes.

* Fixed handling of unicode characters for input and output filenames. We now encode to UTF-8 before passing to HandBrake.
* Fixed a crash in the queue multiple titles dialog.
* Added code to rescue tool windows which get placed outside of the visible screen area.

I still need a bit more time to work on the bigger changes to accommodate the hardware acceleration stuff.

[mike20021969]

Using Windows XP SP3, I get this error when launching 1.5.7 Beta:

Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "VidCoder.Services.IUpdater", name = "(none)".
Exception occurred while: Calling constructor VidCoder.Services.Updater().
Exception is: ResolutionFailedException - Resolution of the dependency failed, type = "VidCoder.Services.ILogger", name = "(none)".
Exception occurred while: Calling constructor VidCoder.Services.Logger().
Exception is: TypeInitializationException - The type initializer for 'HandBrake.Interop.HandBrakeUtils' threw an exception.
-----------------------------------------------
At the time of the exception, the container was:

Resolving VidCoder.Services.Logger,(none) (mapped from VidCoder.Services.ILogger, (none))
Calling constructor VidCoder.Services.Logger()

-----------------------------------------------
At the time of the exception, the container was:

Resolving VidCoder.Services.Updater,(none) (mapped from VidCoder.Services.IUpdater, (none))
Calling constructor VidCoder.Services.Updater()
---> Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "VidCoder.Services.ILogger", name = "(none)".
Exception occurred while: Calling constructor VidCoder.Services.Logger().
Exception is: TypeInitializationException - The type initializer for 'HandBrake.Interop.HandBrakeUtils' threw an exception.
-----------------------------------------------
At the time of the exception, the container was:

Resolving VidCoder.Services.Logger,(none) (mapped from VidCoder.Services.ILogger, (none))
Calling constructor VidCoder.Services.Logger()
---> System.TypeInitializationException: The type initializer for 'HandBrake.Interop.HandBrakeUtils' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'hb.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at HandBrake.Interop.HbLib.HBFunctions.hb_global_init()
at HandBrake.Interop.HandBrakeUtils..cctor() in d:\docs\projects\HandBrakeSVN\win\CS\HandBrake.Interop\HandBrakeInterop\HandBrakeUtils.cs:line 64
--- End of inner exception stack trace ---
at HandBrake.Interop.HandBrakeUtils.add_MessageLogged(EventHandler`1 value)
at VidCoder.Services.Logger..ctor(ILogger parent, String baseFileName) in d:\docs\projects\VidCoder\VidCoder\Services\Logger.cs:line 36
at BuildUp_VidCoder.Services.Logger(IBuilderContext )
at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
--- End of inner exception stack trace ---
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
at Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name, ResolverOverride[] resolverOverrides)
at Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, ResolverOverride[] overrides)
at VidCoder.Services.Updater..ctor() in d:\docs\projects\VidCoder\VidCoder\Services\Updater.cs:line 59
at BuildUp_VidCoder.Services.Updater(IBuilderContext )
at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
--- End of inner exception stack trace ---
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
at Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name, ResolverOverride[] resolverOverrides)
at Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, ResolverOverride[] overrides)
at VidCoder.App.OnStartup(StartupEventArgs e) in d:\docs\projects\VidCoder\VidCoder\App.xaml.cs:line 108
at System.Windows.Application.<.ctor>b__1(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

I've gone back and re-installed 1.5.6 Beta which is working fine.

[therube]

> Using Windows XP SP3, I get this error when launching 1.5.7 Beta:

Confirmed.

> * Fixed handling of unicode characters for input and output filenames.

Thank you :).

[RandomEngy]

Hmm. It's failing because it says it can't find hb.dll, but it seems to be included in both the x86 and x64 installers. Do you see hb.dll in c:\Program Files\VidCoder-Beta ?

[jkauff]

Works fine in Win 7 64-bit, if that helps.

[mike20021969]

Hmm. It's failing because it says it can't find hb.dll, but it seems to be included in both the x86 and x64 installers. Do you see hb.dll in c:\Program Files\VidCoder-Beta ?

Yes, it's there.

(The only way I can get 1.5.7 to launch is by using hb.dll from 1.5.6 beta but there's no point in doing that).

Edit: I just noticed something regarding HandBrake svn5819 and svn5823 - the program is falling to launch correctly. It's just an empty interface. Maybe that has something to do with it. I'll mention this error on their forum.

http://i59.photobucket.com/albums/g302/mike20021969/HandBrake_20131008_15h10m11s_001_HandBrake_zpsb4237691.jpg (http://s59.photobucket.com/user/mike20021969/media/HandBrake_20131008_15h10m11s_001_HandBrake_zpsb4237691.jpg.html)

[jkauff]

This has got to be an XP issue. HandBrake svn5819 works fine for me on Win 7, I was using it just last night. Of course, that's the 64-bit version, I'm guessing you're using the 32-bit.

[mike20021969]

This has got to be an XP issue... I'm guessing you're using the 32-bit.

That's correct.

EDIT - s55 over at HandBrake forums thinks there's possibly a bug with XP:
https://forum.handbrake.fr/viewtopic.php?p=131729#p131729

[sr55]

Actually looks like there are several issues.

First, it won't work on systems without the OpenCL runtimes. Second we are now using API's not available on windows XP.

The former will have to be fixed, the latter is more problematic and given that XP is dying off now, it doesn't make a lot of sense to spend loads of time trying to fix it if there isn't an easy solution. So this ones a wait and see.

[mike20021969]

So, just scrap Windows XP and move on :p.

It's the second most used operating system - and probably still will be when even Microsoft stop support for it.

Even the latest Adobe Photoshop 12 is supported on XP.

It'll be a shame if a workaround for VidCoder/Handbrake cannot be found or implemented.

[Guest]

Guys, let's not start a debate on operating systems here. Such posts are OT in this thread and may incur strikes. Thank you.

[Guest]

Struck for rule 3. Want more?

[mike20021969]

FYI, the changelog notice of SVN 5827

Yes, I read that earlier.

So the current VidCoder 1.5.7 beta wont work on XP.
The wording suggests support can be fixed, but whether they will fix it or not is currently up in the air :(

[RandomEngy]

Released VidCoder 1.5.8 Beta (https://vidcoder.codeplex.com/releases/view/113406):

* Added hardware acceleration options: Bicubic OpenCL scaling algorithm, QSV decoding/encoding and DXVA decoding.
* Updated HandBrake core to SVN 5834.
* Updated VidCoder setup icon.

* Fixed crash when choosing the mp4v2 container on x86 and opening on x64.

Warning: the hardware acceleration features require specific hardware or file types to work correctly:
* QSV: Need an Intel processor that supports Quick Sync Video encoding, with a monitor hooked up to the Intel HD Graphics output and the latest drivers.
* DXVA decoding: Only supports certain file types and codecs, such as H.264, VC1, WMV3 and MPEG 4 in an AVI container.
* OpenCL: The Bicubic scaling only works properly if you have an AMD graphics card. Otherwise it crashes.

Also if QSV support is totally broken I apologize, I don't have compatible hardware so I'm kind of writing it blind.

[jkauff]

Also if QSV support is totally broken I apologize, I don't have compatible hardware so I'm kind of writing it blind.
Don't worry, we'll let you know. :p

[jkauff]

QSV works! VidCoderWorker.exe never exceeded 12% CPU usage encoding a 35GB BR source file (averaged about 9%). Total encode time at High Profile preset 1500 kbps (which is what I use for my iPhone): 00:19:51. File size estimate was way off, though. Vidcoder estimated 3.5GB, but the finished file was under 2GB.

One difference I noticed is that you're supporting all three levels of QS (Speed, Balanced, Quality) while the Handbrake UI now stops at Balanced. I don't know if Quality actually works or if it's still Balanced. IIRC, the Handbrake devs said the difference wasn't really noticeable, so they eliminated Quality--at least in the UI.

[pearlblack15]

QSV doesn't work in Windows 7 SP1 x86 system. VidCoderWorker.exe terminates with the following two error in event viewer:

Faulting application name: VidCoderWorker.exe, version: 1.5.8.0, time stamp: 0x525aeb8b
Faulting module name: hb.dll, version: 0.0.0.0, time stamp: 0x5258be44
Exception code: 0xc0000005
Fault offset: 0x003587fc
Faulting process id: 0x17c8
Faulting application start time: 0x01cec8e8ed2259e0
Faulting application path: D:\Program Files\VidCoder-Beta\VidCoderWorker.exe
Faulting module path: D:\Program Files\VidCoder-Beta\hb.dll
Report Id: 3d01bac0-34dc-11e3-883c-90004ef4876d


Application: VidCoderWorker.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 04D787FC

[RandomEngy]

QSV works! VidCoderWorker.exe never exceeded 12% CPU usage encoding a 35GB BR source file (averaged about 9%). Total encode time at High Profile preset 1500 kbps (which is what I use for my iPhone): 00:19:51. File size estimate was way off, though. Vidcoder estimated 3.5GB, but the finished file was under 2GB.

One difference I noticed is that you're supporting all three levels of QS (Speed, Balanced, Quality) while the Handbrake UI now stops at Balanced. I don't know if Quality actually works or if it's still Balanced. IIRC, the Handbrake devs said the difference wasn't really noticeable, so they eliminated Quality--at least in the UI.

Cool. I'll do the same and get rid of Quality in the next release (until it becomes useful).

[Ruriko]

I get error when opening vidcoder using v1.5.8
Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "VidCoder.Services.IUpdater", name = "(none)".
Exception occurred while: Calling constructor VidCoder.Services.Updater().
Exception is: ResolutionFailedException - Resolution of the dependency failed, type = "VidCoder.Services.ILogger", name = "(none)".
Exception occurred while: Calling constructor VidCoder.Services.Logger().
Exception is: TypeInitializationException - The type initializer for 'HandBrake.Interop.HandBrakeUtils' threw an exception.
-----------------------------------------------
At the time of the exception, the container was:

Resolving VidCoder.Services.Logger,(none) (mapped from VidCoder.Services.ILogger, (none))
Calling constructor VidCoder.Services.Logger()

-----------------------------------------------
At the time of the exception, the container was:

Resolving VidCoder.Services.Updater,(none) (mapped from VidCoder.Services.IUpdater, (none))
Calling constructor VidCoder.Services.Updater()
---> Microsoft.Practices.Unity.ResolutionFailedException: Resolution of the dependency failed, type = "VidCoder.Services.ILogger", name = "(none)".
Exception occurred while: Calling constructor VidCoder.Services.Logger().
Exception is: TypeInitializationException - The type initializer for 'HandBrake.Interop.HandBrakeUtils' threw an exception.
-----------------------------------------------
At the time of the exception, the container was:

Resolving VidCoder.Services.Logger,(none) (mapped from VidCoder.Services.ILogger, (none))
Calling constructor VidCoder.Services.Logger()
---> System.TypeInitializationException: The type initializer for 'HandBrake.Interop.HandBrakeUtils' threw an exception. ---> System.DllNotFoundException: Unable to load DLL 'hb.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at HandBrake.Interop.HbLib.HBFunctions.hb_global_init()
at HandBrake.Interop.HandBrakeUtils..cctor() in d:\docs\projects\HandBrakeSVN\win\CS\HandBrake.Interop\HandBrakeInterop\HandBrakeUtils.cs:line 64
--- End of inner exception stack trace ---
at HandBrake.Interop.HandBrakeUtils.add_MessageLogged(EventHandler`1 value)
at VidCoder.Services.Logger..ctor(ILogger parent, String baseFileName) in d:\docs\projects\VidCoder\VidCoder\Services\Logger.cs:line 36
at BuildUp_VidCoder.Services.Logger(IBuilderContext )
at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
--- End of inner exception stack trace ---
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
at Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name, ResolverOverride[] resolverOverrides)
at Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, ResolverOverride[] overrides)
at VidCoder.Services.Updater..ctor() in d:\docs\projects\VidCoder\VidCoder\Services\Updater.cs:line 59
at BuildUp_VidCoder.Services.Updater(IBuilderContext )
at Microsoft.Practices.ObjectBuilder2.DynamicMethodBuildPlan.BuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.BuildPlanStrategy.PreBuildUp(IBuilderContext context)
at Microsoft.Practices.ObjectBuilder2.StrategyChain.ExecuteBuildUp(IBuilderContext context)
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
--- End of inner exception stack trace ---
at Microsoft.Practices.Unity.UnityContainer.DoBuildUp(Type t, Object existing, String name, IEnumerable`1 resolverOverrides)
at Microsoft.Practices.Unity.UnityContainer.Resolve(Type t, String name, ResolverOverride[] resolverOverrides)
at Microsoft.Practices.Unity.UnityContainerExtensions.Resolve[T](IUnityContainer container, ResolverOverride[] overrides)
at VidCoder.App.OnStartup(StartupEventArgs e) in d:\docs\projects\VidCoder\VidCoder\App.xaml.cs:line 108
at System.Windows.Application.<.ctor>b__1(Object unused)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

[mike20021969]

I get error when opening vidcoder using v1.5.8

You're not using Windows XP by any chance are you?

[Ruriko]

You're not using Windows XP by any chance are you?

No this is windows server 2008 32bit. I can't open the later versions after 1.5.6 Beta

[mike20021969]

No this is windows server 2008 32bit. I can't open the later versions after 1.5.6 Beta

Does the latest HandBrake nightly work?

http://handbrake.fr/nightly.php

If it doesn't work, then the problem lies with HandBrake.

If HandBrake does work, the problem is probably with VidCoder.

[Ruriko]

oh thanks I was able to fix it by installing handbrake and it told me i was missing a dll file while vidcoder never told me

[therube]

> i was missing a dll file

Which file?

[Ruriko]

> i was missing a dll file

Which file?

it was opencl.dll

[RandomEngy]

Released VidCoder 1.5.9 Beta (https://vidcoder.codeplex.com/releases/view/113705):

* Added Rip DVD and Rip Blu-ray AutoPlay actions for Windows: now you can have VidCoder start up and scan a disc when you insert it. Go to Start -> AutoPlay to set it up.
* Added error message for Windows XP users rather than letting it crash.
* Removed "quality" preset from list for QSV as it currently doesn't offer much improvement.
* Changed installer to ignore version number when copying files over. Should reduce the chances of a bug from me forgetting to increment a version number.

* Fixed crash when VidCoder is run from a folder other than the program folder.

[mike20021969]

* Added error message for Windows XP users rather than letting it crash.


I'd put a message on the download page stating that 1.5.6 was the last version that supports Windows XP.

There's really no point in finding this out after it's been downloaded, successfully installed then launched :(

[RandomEngy]

I don't want to put it on the download page since I would have to add that warning on every release. I've updated the main page to mention that the recent betas are not compatible with XP.

[MaistroX]

I will try to go for a Swedish translation on my free time! :)

[RandomEngy]

I will try to go for a Swedish translation on my free time! :)

Tack!

[Ruriko]

My original mkv file plays a subtitle on default but when I convert it doesn't play the subtitle cause it isn't marked on default so I have to manually enable it. Is there a way to make vidocoder set a subtitle on default?

[RandomEngy]

Check the "Default" checkbox in the subtitle dialog? Or burn it into the picture.

[Ruriko]

Check the "Default" checkbox in the subtitle dialog? Or burn it into the picture.

But I can't checkbox the default if I'm batch encoding :(

[RandomEngy]

Ahh so you want another option in Automatic Subtitle Selection to mark the chosen subtitle as "default". I can put that on the backlog.

[RandomEngy]

Released VidCoder 1.5.10 Beta (https://vidcoder.codeplex.com/releases/view/114025):

* Broke out all the encoder-specific passthrough options into their own dropdown. This should make what they do a bit more clear and clean up the codec list a bit.
* Updated HandBrake core to SVN 5855.

I'm hoping due to https://trac.handbrake.fr/changeset/5844 we fix some of the "missing hb.dll" crashes on Windows 7.

[sr55]

That patch will not fix the missing dll errors. There is still a fair amount of work to be done.

I also still haven't had a chance to look at if we'll return support for XP.

[therube]

RFE: Estimated Output File Size (in particular with CQ, crf=)


Obviously if you're using Target Size or ABR, you're basically going to know the size ahead of time.
With CQ though you are not.
But at the same time, once an encode starts, you very quickly can come up with an estimated output file size, that should be fairly accurate, based on % complete & bytes output up to point in time.

And of course you could "manually" look & see, oh 10% complete, 100 KB output so far, so when I'm done I'm likely to be right around 1 GB.

But if VidCoder presented that to you, its that much easier.

Comes in helpful when you're experimenting.
Trying to find the "right" output settings. Say your first encode is with a crf=20 & right off the bat you're seeing you're going to end up ~1GB, but you say, that's more bytes then I wanted to spend, so I'll bump the crf= to say 24, & accept some quality loss, to get a reduced file size.

To me, having this estimate available could allow you to circumvent a "miscue" without having to wait for the full encode to finish.

[RandomEngy]

I'll have to see if that's information possible to obtain while the encode is happening. If I find a way I'll put it in the encode details window I have planned.

[sr55]

The Divide size by time approach isn't very accurate unless you have a consistent source. Few people do so it can be very mis-leading.

I implemented it for HandBrake a while ago but never committed it because it gave numbers that were not even remotely close to accurate for a lot of my sources. It wasn't until late on in the encode did the number start becoming realistic.

The problem is, content complexity changes thoughout most videos, and can change quite substantially. Dark or complex action scene, camera pans etc can take 2, 3, 4... times the bitrate to encode for example than a simple low motion scene.

If you use bitrate viewer, you can see the effect different content has on bitrate. http://www.winhoros.de/docs/bitrate-viewer/download.html

[mike20021969]

I also still haven't had a chance to look at if we'll return support for XP.

Please update this thread if you do.

[jkauff]

Please update this thread if you do.
I think "we" refers to the Handbrake team. I'm sure there's a discussion about XP going on in the HB forums, you might want to keep an eye on what's happening over there.