VidCoder: Alternative HandBrake GUI for Windows

[mike20021969]

I just have a quick query about encoding an MPEG2 video.

The video, from off-air freeview in the UK, is 16:9.
My Grabster AV400 USB capture records it as 720x576 in 4:3 - so it is squeezed.

Assuming there's no cropping & I don't want to lose resolution, would I be correct in saying I simply resize it to 1024x576?

Or should I keep it at 720x576 and set the pixel aspect ratio? (Although I tried to do this and cant seem to get the settings/values right).

Thanks.

[JohnAStebbins]

I just have a quick query about encoding an MPEG2 video.

The video, from off-air freeview in the UK, is 16:9.
My Grabster AV400 USB capture records it as 720x576 in 4:3 - so it is squeezed.

Assuming there's no cropping & I don't want to lose resolution, would I be correct in saying I simply resize it to 1024x576?

Or should I keep it at 720x576 and set the pixel aspect ratio? (Although I tried to do this and cant seem to get the settings/values right).

Thanks.
What you really want to do is modify the pixel aspect ratio. Using the HandBrakeCLI, it would look something like this:

HandBrakeCLI -i test.mpg -o test.mp4 -Z Normal --custom-anamorphic --pixel-aspect=64:45

[mike20021969]

HandBrakeCLI -i test.mpg -o test.mp4 -Z Normal --custom-anamorphic --pixel-aspect=64:45


OK - I got this to work in VidCoder :)
No cropping = no problem.

Now when I start cropping away black borders on 3 sides, it seems to throw the picture out of aspect, and 64:45 doesn't give me a 16:9 image.

I'm having to go with values 64:44 - does this seem the right thing to do? Although the preview looks OK, I'm not entirely sure I have a 16:9 result.

[RandomEngy]

Yes, the Level option is slated to be added with the other changes. It will be equivalent to the HandBrakeCLI --h264-level parameter.

[JohnAStebbins]

OK - I got this to work in VidCoder :)
No cropping = no problem.

Now when I start cropping away black borders on 3 sides, it seems to throw the picture out of aspect, and 64:45 doesn't give me a 16:9 image.

I'm having to go with values 64:44 - does this seem the right thing to do? Although the preview looks OK, I'm not entirely sure I have a 16:9 result.

You should not have to adjust the pixel aspect to compensate for cropping. I did a test with this command line to verify with the CLI

./HandBrakeCLI -i test.mkv -o test2.mkv -Z Normal --custom-anamorphic --pixel-aspect=64:45 --crop 100:100:0:0 --modulus 2

Activity log showing detailed settings used by hb are:

Input #0, matroska,webm, from 'test.mkv':
Duration: 00:48:06.80, start: 0.000000, bitrate: N/A
Stream #0.0(eng): Video: h264 (High), yuv420p, 720x576 [PAR 16:15 DAR 4:3], 25 fps, 25 tbr, 1k tbn, 50 tbc (default)
Stream #0.1(eng): Audio: ac3, 48000 Hz, 5.1, s16, 448 kb/s (default)
[11:08:35] scan: decoding previews for title 1
[11:08:35] scan: audio 0x1: AC-3, rate=48000Hz, bitrate=448000 English (AC3) (5.1 ch)
Scanning title 1...
[11:08:36] scan: 10 previews, 720x576, 25.000 fps, autocrop = 0/0/0/0, aspect 4:3, PAR 16:15
[11:08:36] scan: title (0) job->width:720, job->height:544
[11:08:36] libhb: scan thread found 1 valid title(s)
+ title 1:
+ stream: test.mkv
+ duration: 00:48:06
+ size: 720x576, pixel aspect: 16/15, display aspect: 1.33, 25.000 fps
+ autocrop: 0/0/0/0
+ chapters:
+ 1: cells 0->0, 0 blocks, duration 00:48:06
+ audio tracks:
+ 1, English (AC3) (5.1 ch) (iso639-2: eng), 48000Hz, 448000bps
+ subtitle tracks:
+ Using preset: Normal
[11:08:36] 1 job(s) to process
[11:08:36] starting job
[11:08:36] sync: expecting 72170 video frames
[11:08:36] work: only 1 chapter, disabling chapter markers
[11:08:36] job configuration:
[11:08:36] * source
[11:08:36] + test.mkv
[11:08:36] + title 1, chapter(s) 1 to 1
[11:08:36] + container: matroska,webm
[11:08:36] * destination
[11:08:36] + test2.mkv
[11:08:36] + container: Matroska (.mkv)
[11:08:36] * video track
[11:08:36] + decoder: h264
[11:08:36] + frame rate: same as source (around 25.000 fps)
[11:08:36] + filters
[11:08:36] + Framerate Shaper (0:27000000:1080000)
[11:08:36] + frame rate: same as source (around 25.000 fps)
[11:08:36] + Crop and Scale (720:376:100:100:0:0)
[11:08:36] + source: 720 * 576, crop (100/100/0/0): 720 * 376, scale: 720 * 376
[11:08:36] + custom anamorphic
[11:08:36] + storage dimensions: 720 * 376, mod 2
[11:08:36] + pixel aspect ratio: 64 / 45
[11:08:36] + display dimensions: 1024 * 376
[11:08:36] + encoder: H.264 (x264)
[11:08:36] + options: ref=1:weightp=1:subq=2:rc-lookahead=10:trellis=0:8x8dct=0
[11:08:36] + quality: 20.00 (RF)
[11:08:36] * audio track 1
[11:08:36] + decoder: English (AC3) (5.1 ch) (track 1, id 0x1)
[11:08:36] + bitrate: 448 kbps, samplerate: 48000 Hz
[11:08:36] + mixdown: Dolby Pro Logic II
[11:08:36] + encoder: AAC (faac)
[11:08:36] + bitrate: 160 kbps, samplerate: 48000 Hz
[11:08:36] reader: first SCR 0 id 0x1 DTS 0
[11:08:36] encx264: encoding with stored aspect 64/45
[11:08:36] encx264: Encoding at constant RF 20.000000
x264 [warning]: --psnr used with psy on: results will be invalid!
x264 [warning]: --tune psnr should be used if attempting to benchmark psnr!
x264 [info]: using SAR=64/45
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2
x264 [info]: profile Main, level 3.0
Encoding: task 1 of 1, 12.49 % (112.36 fps, avg 122.45 fps, ETA 00h08m36s)q

Encoding Quit by user command
Encoding: task 1 of 1, 12.53 % (112.36 fps, avg 122.45 fps, ETA 00h08m36s)[11:09:50] work: average encoding speed for job is 122.453987 fps
[11:09:50] sync: got 9041 frames, 72170 expected
[11:09:50] reader: done. 1 scr changes
[11:09:50] render: lost time: 0 (0 frames)
[11:09:50] render: gained time: 0 (0 frames) (0 not accounted for)
[11:09:50] h264-decoder done: 9067 frames, 0 decoder errors, 0 drops
x264 [info]: frame I:124 Avg QP:18.24 size: 20213 PSNR Mean Y:47.09 U:50.22 V:51.14 Avg:47.96 Global:47.33
x264 [info]: frame P:5261 Avg QP:21.16 size: 6843 PSNR Mean Y:44.14 U:47.87 V:48.73 Avg:45.08 Global:44.69
x264 [info]: frame B:3606 Avg QP:22.32 size: 1580 PSNR Mean Y:43.80 U:48.17 V:49.04 Avg:44.86 Global:44.04
x264 [info]: consecutive B-frames: 31.5% 41.8% 9.8% 16.9%
x264 [info]: mb I I16..4: 42.2% 0.0% 57.8%
x264 [info]: mb P I16..4: 24.2% 0.0% 4.6% P16..4: 33.2% 17.0% 8.6% 0.0% 0.0% skip:12.4%
x264 [info]: mb B I16..4: 2.6% 0.0% 0.1% B16..8: 20.3% 5.6% 0.5% direct:11.9% skip:59.1% L0:29.5% L1:51.4% BI:19.1%
x264 [info]: coded y,uvDC,uvAC intra: 39.5% 61.8% 19.1% inter: 18.7% 25.3% 1.0%
x264 [info]: i16 v,h,dc,p: 41% 23% 25% 12%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 25% 20% 24% 5% 6% 5% 6% 4% 4%
x264 [info]: i8c dc,h,v,p: 52% 18% 25% 5%
x264 [info]: Weighted P-Frames: Y:4.0% UV:2.5%
x264 [info]: SSIM Mean Y:0.9790401 (16.786db)
x264 [info]: PSNR Mean Y:44.045 U:48.025 V:48.886 Avg:45.033 Global:44.447 kb/s:983.29
[11:09:50] mux: track 0, 7623 frames, 34864074 bytes, 914.59 kbps, fifo 4096
[11:09:50] mux: track 1, 14294 frames, 6098213 bytes, 159.97 kbps, fifo 8192

The output looked fine. If the aspect were wrong, this would have made people look very fat.

[mike20021969]

You should not have to adjust the pixel aspect to compensate for cropping.

I thought that. But after cropping, the picture distorts:
3 screenshots below - No cropping , auto cropping, custom cropping.
There is definitely a difference between auto and custom if I leave the 64:45 setting alone.
It isn't a lot, but if you alternate between the auto and custom, you'll see the difference.
(Incidentally, I use custom cropping because the auto crop leaves soft edges).

And the Display and Storage values are all over the place in the cropped images.
What am I doing wrong?

No cropping:
http://i59.photobucket.com/albums/g302/mike20021969/NoCropping_Preview-Display1024x576-Storage720x576.jpg

Auto cropping:
http://i59.photobucket.com/albums/g302/mike20021969/AutoCropping_Preview-Display1001x560-Storage704x560.jpg

Custom cropping:
http://i59.photobucket.com/albums/g302/mike20021969/CustomCropping_Preview-Display1000x560-Storage688x560.jpg

Auto Vs Custom:
http://i59.photobucket.com/albums/g302/mike20021969/diffference.gif

[mike20021969]

Scrub that - I cant get this to work.

After cropping T=0, L=14, R=8, B=8, Modulus=2, PAR=64:45, I get a Display Resolution of 992x568.

That isn't 16x9.

*SIGH*

[JohnAStebbins]

Scrub that - I cant get this to work.

After cropping T=0, L=14, R=8, B=8, Modulus=2, PAR=64:45, I get a Display Resolution of 992x568.

That isn't 16x9.

*SIGH*

*After* cropping, you probably won't get exactly 16:9. The original, before cropping, was 16:9, so cropping is going to make it slightly different due to removal of the black boarders. The important thing is that the pixel aspect is correct. This is what determines if people look too fat or thin.

Although the pictures are a little useful. It would be far more useful if you posted activity logs for each. Then we could see the settings that are being applied. If nothing else, that will allow others to replicate the problem.

[mike20021969]

*After* cropping, you probably won't get exactly 16:9. The original, before cropping, was 16:9, so cropping is going to make it slightly different due to removal of the black boarders. The important thing is that the pixel aspect is correct. This is what determines if people look too fat or thin.

I think I get what you're saying.

Fogetting PAR for a second, if I crop the black borders then I resize to a widescreen dimension, e.g. 1024x576, I have distorted the video myself? :eek:

Going back and looking at the 1st image which isn't cropped is 16x9, but the (watchable) video within the black border ISN'T 16x9.

I now understand. Thanks.

[RandomEngy]

Is it possible to switch languages for VidCoder, or what did you mean with that?

Not yet, but it will be when the translation is finished and I release the next version. You'll be able to switch from English to German. And volunteers who want to translate it to other languages can do so.

[RandomEngy]

I talked to Rodeo about it. The current method isn't ideal for determining if a level is valid (when used with p-invoke) and discussed adding a simpler method to HB that should allow this.

[Rafales]

Hi,
Would like to know does this tool works with Windows 8 which comes with Dot Net Framework 4.5 (enabled by default)

[mike20021969]

Hi,
Would like to know does this tool works with Windows 8 which comes with Dot Net Framework 4.5 (enabled by default)

Why not try?

This from the VidCoder homepage...

Platform
VidCoder is built on .NET 4 Client Profile/WPF in C#.

It runs on any OS that supports .NET 4: Windows 7, Vista, XP, Server 2003 and Server 2008.

[RandomEngy]

Yeah it appears to be working fine in Windows 8. I believe the OS comes with .NET 4 pre-installed so if you don't need to do anything extra if you have Win 8.

[mike20021969]

Why are you "hiding" the Preview window in the Menu bar (Windows ---> Preview) ;)?

Wouldn't it be more intuitive if the Preview window could also be accessed via a button placed on the Main window for example?



Something like this you mean...? ;)

http://i59.photobucket.com/albums/g302/mike20021969/20121109_14h02m47s_002_VidCoder.jpg

[DJ-1]

Hi, I been using vidcoder for quite a while now, it's easily the best in terms of 'ease of use'.
I know that vidcoder is based on handbrake..... But I very rarely see handbrake updated...

Vidcoder main pro for me is...
All info contained in a single profile.... Whereas some GUIs will rather have the user set up video profile + audio profile other weird things & feels disjointed.

I have been trying Hybrid as it has a lot of extra advanced video filtering + extras, but isn't as easy to use...

It'd be great if handbrake did all the ultra advanced stuff & therefore keep the simplicity with it also...

[mike20021969]

But I very rarely see handbrake updated...

Try the "nightlies" if you want to try the latest HandBrake updates - note that they may not be as stable as the "official" releases (e.g. 0.9.8).

Nightlies here: https://build.handbrake.fr/view/Nightlies/job/Windows/

[RandomEngy]

@ "RandomEngy":

Some requests / questions:

Could you please add an option to the Preview window (Windows ---> Preview) to adjust the size of it? Something like:

Size:

1:1
100%
50%

and so on...

?

Maybe via a right click menu into the Preview window?

And could you also make the Preview window scrollable if the size of the Preview window would exceed the screen resolution?

Hmm. Currently the window layout is designed so that you can just keep the Preview window open somewhere and watch it change as you bring in new sources, etc. A function where the window itself changed size would be a bit disruptive because it would all the sudden be covering other windows. I will consider adding a switch to toggle between the current behavior and 1:1 with scrolling.

Also:

Why is seeking within the videofile only possible in "steps" in the Preview window? Could you possibly change it to make it possible to seek stepless?

I'm using what the HandBrake API gives me. As soon as they allow a smooth "seek to anywhere" feature I'll add it as well.

And something else:

Is it really necessary for the Encoding Settings window (Windows ---> Encoding Settings) to be a separate window being detached from the main window?

Why not integrate it into the Main window like the normal HandBrake GUI?

Thanks in advance ;).

The Encoding window is meant to be a place where you do optional 1-time setup work for your encoding settings. When you're ripping a large number of movies or doing other work, most of your time is spent in the main window: opening files, picking subtitles, managing queues, etc. By moving the encoding settings out, you get a much simpler main interface for everyday work and for people who just want to use a built-in preset.

If you like to fiddle with encoding settings a lot you can just leave the encoding settings window open beside the main one. There's no requirement to close it to interact with the main UI again.

Still looking forward to the next update by the way :):D;).

Cool. The translator I've been waiting on has either gotten really sick or is dragging his heels. I'll think about doing a release without the translation if I don't hear back from him.

[RandomEngy]

Released VidCoder 1.4.5 Beta (http://vidcoder.codeplex.com/releases/view/97530):

* Removed the old Advanced user interface and moved x264 preset/profile/tune there instead. The functionality is still available through editing the options string.
* Added ability to specify the H.264 level.
* Added ability to choose VidCoder's interface language. If you are interested in translating, we can get VidCoder in your language!
* Updated WPF text rendering to use the better Display mode.
* Updated HandBrake core to SVN 5045.
* Removed logic that forced the .m4v extension in certain cases.
* Increased max width of preset combo box.
* Changed VidCoder to be a single-instance program. Attempting to open it again will show the main window.
* Moved options storage to SQLite rather than the standard .NET user config. This means less chance for config settings to get corrupted.
* When doing batch file encodes, VidCoder now picks the default title to encode rather than just the first one every time (useful for ISOs).

* Fixed RF 0 showing (none) in number box.
* Fixed reported crash on closing.
* Fixed main UI not updating when output folder was picked in options.
* Fixed crash when you have two SRT subtitle tracks and mark one as default.

[RandomEngy]

Unfortunately you haven't moved the Quality settings from the Video panel to the Advanced panel though :(;).

And the quality settings now look a bit messed up in the Video panel, because the "2-pass Encoding" and "Turbo first pass" checkboxes are now on the left side under the Video settings and not under or next to the Quality settings, where they actually would belong.

So, a suggestion/request:

Would there be any chance you could also move the Quality settings from the Video panel to the Advanced panel?

Now that the old advanced settings have been removed from the Advanced panel, there would be enough space to move the Quality settings there as well?

And that leads to the next suggestion :D: What do you think about renaming the Advanced panel and calling it "Encoder" or "Encoder Settings" or something like that?

Having all encoder related settings under this panel (inlcuding Quality settings) would be appreciated.

I do have a lot more room now. But Quality is very much a basic setting that I want to be in the forefront. That is something you might fiddle with even if you never touch the profile/preset/tune/level stuff. And I'm not sure I could squeeze everything into the same tab.

But it looks like it's quite messed up :(;).

First of all, the H.264 Level dropdown menu offers incompatible levels.

An example:

If you want to encode at 1920x1080@30fps for example, the H.264 Level dropdown menu should only offer level 4.0 / 4.1 / 4.2 / 5.0 / 5.1 / 5.2.

But instead it offers every level from 1.0 to 5.2.

However, the dropdown menu is highlighting level 4.0 and 4.1 with black font in that case, the other levels are displayed in grey font.

But why only level 4.0 and 4.1? Level 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well.

Also: why are you just highlighting the levels with black font while still offering the other levels and only display them in grey font?

It would probably be better to not show incompatible levels at all, wouldn't it?

Also, it is very inconsistent with different resolutions and framerates.

Some examples:

1280x720@30fps: only level 3.2 / 4.0 / 4.1 are shown in black font, the other levels are shown in grey font (although level 3.1 / 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well)

1280x720@60fps: only level 4.0 / 4.1 are shown in black font, the other levels are shown in grey font (although level 3.2 / 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well)

1920x1080@30fps: only level 4.0 / 4.1 are shown in black font, the other levels are shown in grey font (although level 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well)

1920x1080@60fps: all levels are shown in grey font :confused: (although level 4.2 / 5.0 / 5.1 / 5.2 would be compatible)

3840x2160@30fps: all levels are shown in grey font :confused: (although level 5.1 / 5.2 would be compatible)

3840x2160@60fps: all levels are shown in grey font :confused: (although level 5.2 would be compatible)

Those are just some examples. Haven't tested it with other resolutions and framerates.

In VidCoder you edit the encoding preset, which is independent of the source material. The approach I take is not to remove incompatible settings, but to gray them out to let the user know they won't work with the current settings. That way they don't have their setting altered by loading the wrong video file. As for levels 4.2 and above being grayed out, that's a problem with the new HandBrake API. I'll talk to them about it and try to get it fixed.

[mike20021969]

* Removed the old Advanced user interface and moved x264 preset/profile/tune there instead. The functionality is still available through editing the options string.

That's all fine and good if you understand it. I don't.
I understand these drop down menu's:

http://i59.photobucket.com/albums/g302/mike20021969/Ashampoo_Snap_20121111_08h51m49s_001_Preset-854x480.jpg

But this now means nothing to me. I know nothing about what these "Additional advanced x264 options" entries mean:

http://i59.photobucket.com/albums/g302/mike20021969/Ashampoo_Snap_20121111_08h52m14s_002_---Preset-854x480---.jpg

I understand drop down menu's and the descriptions that show what they do when the mouse cursor is hovered by them.
I haven't got a clue about entering values.
If for example I wanted to alter the "motion estimation method" or "deblocking" well now I am screwed.

How do I know what to start writing in that box??

[RandomEngy]

I understand drop down menu's and the descriptions that show what they do when the mouse cursor is hovered by them.
I haven't got a clue about entering values.
If for example I wanted to alter the "motion estimation method" or "deblocking" well now I am screwed.

How do I know what to start writing in that box??

I would probably go back and ask you why you wanted to change the motion estimation method. Was it to change the encoding speed? To make it more compatible with a specific device? To make it better suited to a particular source? There's probably a preset/profile/tune setting that can help you accomplish your goals better than mucking with those advanced options. At least that's the opinion of the x264 developer himself.

But if you really want to get into that, you can read up on the options here: http://mewiki.project357.com/wiki/X264_Settings

And those are just two examples. In the first example level 3.1 is greyed out as well and in the second example level 3.2 is greyed out as well.

So, as you can see, it's not just levels 4.2 and above being greyed out :(;).

I see. I'll also bring that up when I catch Rodeo online.

[mike20021969]

you can read up on the options here: http://mewiki.project357.com/wiki/X264_Settings

That might as well be written in a foreign language :D
I'm still none the wiser about how to go about entering a value for a setting or what value I should choose if I could.

Thanks anyway.

[RandomEngy]

With the latest update you emptied the additional advanced x264 options string of the "Normal" global preset and set it to x264 Preset: Very Fast and Profile: Main. You probably did that because the "Normal" global HandBrake preset basically resembles x264 Preset Very Fast @ Main Profile, and because to make the additional x264 advanced options string not interfere with the x264 preset/tune/profile/level settings, didn't you ;)?

Just wondering though:

Is it really necessary to have the "Normal" and "High Profile" global HandBrake presets any longer?

What are they actually good for, now that users can specify all those things via the x264 preset/tune/profile/level settings?

So, why not remove the "Normal" and "High Profile" global HandBrake presets and replace them with a new global preset called "None" (or something like that) in which the x264 preset/tune/profile/level settings would all be set to "-None-" and "Automatic" (for H.264 Level) by default so that it would be up to the user to specify them via those settings?

And if, for whatever reason, you want the "Normal" and "High Profile" global presets to stay, would there be any chance you could at least add such a "None" global preset and make VidCoder default to it ;)?

On the subject of presets I've mostly just been following HandBrake, on the assumption that they know what they're doing. I guess the basic question is what kind of files do you want for a user that just boots up VidCoder and starts encoding things? Do you want files that are compatible with more devices or do you want files with less compatibility that use more encoding features and look nicer?

Have not really figured out anything rock-solid so I'm just going the safer route for now.

And could you please separate the global presets into "User Presets", "Regular" (if you leave the "Normal" and "High Profile" global presets) and "Devices", like it's done in the normal HandBrake GUI?

I've thought about that but it's really just a "nice to have" at this point. The built-in presets are already ordered that way and user presets are styled differently in the presets list. Maybe someday when I feel like completely re-writing the combobox control.

That might as well be written in a foreign language :D
I'm still none the wiser about how to go about entering a value for a setting or what value I should choose if I could.

Thanks anyway.

My main issue with the Advanced UI is that the mere fact of their existence invited people who didn't know anything about the setting to go in and fiddle with them. But if you don't have prior knowledge about all these very complicated settings you're almost certain to tweak something in a way that is unhelpful or just bad. 99.9% of users (including me!) are better off just not interacting with those settings in any way.

In other words, a user's lack of knowledge about Psychovisual Rate Distortion isn't really a problem because they don't need to know about it to do good encodes. The UI isn't making anything better by bringing this setting to the user's attention and trying to educate them about it.

The preset/profile/tune settings are far more helpful and putting them front and center is much more of a service to users. If you're upset about the lack of advanced UI I would focus on learning what these do first, before you go digging back into the thicket of specific, advanced x264 options.

[Rodeo]

If you want to encode at 1920x1080@30fps for example, the H.264 Level dropdown menu should only offer level 4.0 / 4.1 / 4.2 / 5.0 / 5.1 / 5.2.

But instead it offers every level from 1.0 to 5.2.

However, the dropdown menu is highlighting level 4.0 and 4.1 with black font in that case, the other levels are displayed in grey font.

But why only level 4.0 and 4.1? Level 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well.

[…]

1280x720@30fps: only level 3.2 / 4.0 / 4.1 are shown in black font, the other levels are shown in grey font (although level 3.1 / 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well)

1280x720@60fps: only level 4.0 / 4.1 are shown in black font, the other levels are shown in grey font (although level 3.2 / 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well)

1920x1080@30fps: only level 4.0 / 4.1 are shown in black font, the other levels are shown in grey font (although level 4.2 / 5.0 / 5.1 / 5.2 would be compatible as well)

1920x1080@60fps: all levels are shown in grey font :confused: (although level 4.2 / 5.0 / 5.1 / 5.2 would be compatible)

3840x2160@30fps: all levels are shown in grey font :confused: (although level 5.1 / 5.2 would be compatible)

3840x2160@60fps: all levels are shown in grey font :confused: (although level 5.2 would be compatible)

AFAICT, hb_check_h264_level() works just fine. For some reason VidCoder is calling it with either interlaced or fake_interlaced set to 1, which is consistent with all the results you posted above:

- 1280x720i requires level 3.2 (interlaced -> height must multiple of 32 -> encoded height 736 pixels)

- levels 4.2 and above do not support interlacing (forbidden)

[mike20021969]

My main issue with the Advanced UI is that the mere fact of their existence invited people who didn't know anything about the setting to go in and fiddle with them. But if you don't have prior knowledge about all these very complicated settings you're almost certain to tweak something in a way that is unhelpful or just bad. 99.9% of users (including me!) are better off just not interacting with those settings in any way.

Indeed. I suppose that's why the menu appeared when the mouse cursor approached advanced options to give users and idea as to what each did. And also many had a "default" value to put put it back should things not work out.

Not knowing what a previous string value was after changing it could also be troublesome for some!

Moving on... I'm on the latest beta and I appreciate the time and effort you put into VidCoder.

:thanks:

[RandomEngy]

Rodeo: you were spot on about the interlacing. I had made sure I was passing the correct bools into the interop function but had not realized that I messed up the bool -> int conversion for fake interlaced. Everything looks good now; will be fixed in next beta (and is fixed in the interop code I just checked in).

Well, you mentioned compatibility. But that rather would be something that would rather be of concern for the dedicated device presets like "Android Mid", "Android High" and so on (only to name a few), wouldn't it?

And, defaulting to a global preset called "None" with an empty additional advanced x264 options string and with x264 preset/tune/profile/level settings set to "-None-" and "Automatic" (for H.264 Level) wouldn't dramatically reduce compatibility, wouldn't it?

Instead of "None", maybe such a global preset could also be called "Scratchpad" (like in MeGUI for example) or something similar.

And, by the way, it would also be very much appreciated if Automatic Cropping would be disabled by default.

It would even be appreciated if you could add a third radio button to the Cropping options and call it "None" and default to that.

That question probably could also be formulated differently:

Would you want users being exposed to H.264 Main Profile by default in the year 2012 (almost 2013) :p;)?

Because that's what VidCoder is currently doing :eek:.

Wouldn't H.264 High Profile (what x264 currently is defaulting to) be more appropriate by now ;)?

I don't want to call a preset "None" because it isn't descriptive. I am thinking about changing "Normal" to use straight defaults for x264 and removing the "High Profile" preset. Also having a "scratchpad" doesn't really make sense because of the way VidCoder's presets work. You can always just play around and revert any changes if you want, or save them as a new preset.

About automatic cropping: What do you have against it? I don't see any major reason why it shouldn't be on by default. I'll think about adding that "None" cropping option; that seems reasonable enough. Would save a few clicks for people that want to turn cropping off.

Well, you could also assume that the x264 developers know what they are doing and default to their current defaults instead, namely: empty additional advanced x264 options string with x264 preset/tune/profile/level settings set to "-None-" and "Automatic" (for H.264 Level) in VidCoder, couldn't you :p:D;)?

The way the settings are now are just me assuming the HandBrake developers know what they're doing. But yeah, already covered this.

Bug report:

VidCoder crashes on start up when the "Remember previously used files and folders" option has been deactivated in the Advanced Options. Tested with VidCoder 1.4.5 Beta (x64).

Thanks for the report, will be fixed in next beta release.

And something else:

At the moment, the x264 Preset dropdown menu in VidCoder offers "-None-" and "Medium". But that's both basically the same. So, one of them would be redundant.

What you are currently listing as "Medium" is doing the following according to the VidCoder Log:

job configuration:
[...]
+ x264 preset: medium

But it shouldn't do that. Because:

Preset Medium = specifying no preset (using default x264 options)

;)

What you are currently listing as "-None-" is doing it correctly. What you are currently listing as "-None-" is Preset Medium, because it's specifying no preset and is using the default x264 options.

So, could you please remove what you are currently listing as "Medium" and rename "-None-" to "Medium (Default)"?

I don't really see what's incorrect about it. With "-None-", I am not passing any preset to x264. With "Medium" I'm passing a specific preset called "medium" to it. Are you saying that you get identical results when you use no preset and when you use "medium"? Will that always be the case? I made the UI this way in case the fallback preset in x264 changed to something other than "medium".

And something else:

Could you please rename the "-None-" entry in the x264 Tune dropdown menu from "-None-" to "None (Default)"?

Could you please rename the "-None-" entry in the H.264 Profile dropdown menu from "-None-" to "Automatic (Default)" or "Auto (Default)"?

Could you please rename the "Automatic" entry in the H.264 Level dropdown menu from "Automatic" to "Automatic (Default)" or "Auto (Default)"?

I had "-None-" as a choice for all of these because these are settings you can just leave off or specify a specific setting as you choose. I put the hyphens in there to set them apart from the other choices and communicate to the user that this is a safe place to let them stay if you don't want to fiddle with anything. Besides, if you were arguing for having a Medium (Default) preset choice, shouldn't the profile be High (Default) as well?

And something else:

It was mentioned a few posts back already, but, the "Preview" button on the Main Window disappears when the Preview Window is open. Why are you doing that ;)? It's a bit confusing.

Why not just make it grey out when the Preview Window is open? It's also greyed out on start up when no source file is loaded and the Preview Window is closed.

To save space and reduce visual clutter when the preview window is open. Why would you be confused about it not being there? Why would you be trying to open something that's already open?

Oh and by the way, thank you for all the feedback and the interest you've shown in improving VidCoder!

[RandomEngy]

Because the picture / the size / the resolution shouldn't be altered by default IMHO.

And furthermore: who is guaranteeing that the automatic cropping option will always work correctly?

By default, it should be up to the user to decide wether to activate cropping and/or altering the size/resolution IMHO.

By the way: "Strict" would be the correct Sizing option for always leaving the size/resolution untouched, or wouldn't it?

Then VidCoder should default to "Sizing ---> Strict" and "Cropping ---> None" by default IMHO.

Well "the resolution should not be altered by default" isn't really a reason, it's just restating the request.

https://trac.handbrake.fr/wiki/AnamorphicGuide

Loose anamorphic and automatic cropping produce results that encode well and have the correct aspect ratio. They make fine defaults.

Also asked about it on the HandBrake forums today, "Rodeo" already replied there, please read all the posts in the following thread starting with the following post:

https://forum.handbrake.fr/viewtopic.php?f=10&t=18133&p=118353#p118353

;)

The x264 Preset slider in his (not yet implemented) MacGUI patch over there:

https://reviews.handbrake.fr/r/280/s/20/

appears to have just 10 steps (with only "Medium"), and not 11 like the VidCoder x264 Preset dropdown menu (with "-None-" and "Medium").

Yeah, I saw that. And you're right; it's probably the best way to do it. I just put it off in favor of getting what I had out there.

No, because x264 does not specify H.264 High Profile by default.

It's just that x264 currently automatically defaults to H.264 High Profile because of the current x264 default options ("Preset Medium").

You can try it for yourself, some examples:

If you do not specify a H.264 profile and select x264 Preset Medium for example, then x264 will automatically encode @ H.264 High Profile.

And if you do not specify a H.264 profile and select x264 Preset Ultra Fast for example, then x264 will automatically encode @ H.264 Constrained Baseline Profile.

Or if you do not specify a H.264 profile and select CRF 0 for example, then x264 will automatically encode @ H.264 High 4:4:4 Predictive Profile.

And so on...

So, please rename the "-None-" entry in the H.264 Profile dropdown menu from "-None-" to "Automatic (Default)" or "Auto (Default)" ;).

Besides: Looking at the pictures of "Rodeo"s (not yet implemented) MacGUI patch mentioned above, it looks like he also named it "Automatic" ;).

Well if you use preset Ultra Fast and specify the High profile, it still produces H.264 Constrained Baseline Profile. That's because the High profile ensures it meets the profile and needs to make no changes because it already does. But I see what you mean about specifying RF 0. I'll probably just follow the HandBrake naming here.

PS: Also asked "Rodeo" about this on the HandBrake forums, please read all the posts in the following thread starting with the following post:

https://forum.handbrake.fr/viewtopic.php?p=118354&sid=01d7024b0657470355838fab6fc2614a#p118354

;)

Yeah I wasn't quite sure what to make of the other 3 "high" profiles. I'll add High 4:4:4 Predictive. Thanks for the heads-up.

PS: The following thread from today:

https://forum.handbrake.fr/viewtopic.php?f=26&t=25756

might be interesting for you ;).

It is... I like that LinGui mockup; maybe I can fit everything on the Video tab. Less tabbing around would be good.

[mike20021969]

Hi RandomEngy.

I like to have VidCoder "Play sound on completion" when encoding files.

I'm not really keen on the default supplied, so for a while I have been putting put my own .wav in the Program Files folder (renaming it "Encode_Complete.wav" so that it plays).

This works great but after installing a new version of VidCoder, the .wav I chose is overwritten with your default sound.

Would it be possible to add a browse button for the default sound and have this remembered after an update install?

Thanks.

[JohnAStebbins]

Just wanted to add my $0.02 to this discussion. If you are planning on eliminating the advanced panel, then you probably shouldn't have a "none" option for preset. "none" for tune seems like an obvious "yes". And I'm strongly in favor of an "auto" setting for profile and level since very few users will have any clue what to set these to.

Personally, I will continue to use the advanced panel for my own settings. I could munge a combination of preset and extra options to do what I want, but the advanced panel is far easier to use for my particular preferences.

If I were new to using x264, I would find the preset/tune/profile/level/options to be a great learning tool. But it's only helpful if you can see the end result option string (which will show in the advanced panel of HandBrake). Admittedly, the number of people that *want* to learn more is going to be small. But since the advanced tab already exists and noobs are under no compulsion to even look at it, I consider it worthy of keeping.

[RandomEngy]

Hi RandomEngy.

I like to have VidCoder "Play sound on completion" when encoding files.

I'm not really keen on the default supplied, so for a while I have been putting put my own .wav in the Program Files folder (renaming it "Encode_Complete.wav" so that it plays).

This works great but after installing a new version of VidCoder, the .wav I chose is overwritten with your default sound.

Would it be possible to add a browse button for the default sound and have this remembered after an update install?

Thanks.

Heh. That sound was a result of searching through hundreds of sounds and picking the least terrible one. If you've got a better one I'd consider it for default. I'll also put the ability to customize the sound on the backlog.

Just wanted to add my $0.02 to this discussion. If you are planning on eliminating the advanced panel, then you probably shouldn't have a "none" option for preset. "none" for tune seems like an obvious "yes". And I'm strongly in favor of an "auto" setting for profile and level since very few users will have any clue what to set these to.

Personally, I will continue to use the advanced panel for my own settings. I could munge a combination of preset and extra options to do what I want, but the advanced panel is far easier to use for my particular preferences.

If I were new to using x264, I would find the preset/tune/profile/level/options to be a great learning tool. But it's only helpful if you can see the end result option string (which will show in the advanced panel of HandBrake). Admittedly, the number of people that *want* to learn more is going to be small. But since the advanced tab already exists and noobs are under no compulsion to even look at it, I consider it worthy of keeping.

Hmm, okay. If I can get all the standard stuff moved over to the Video tab, bringing the advanced panel back makes more sense. It will be a place that only the brave will venture to.

[mike20021969]

I'll also put the ability to customize the sound on the backlog.
Great. (The one I currently replace your's with is AVG's scan_finish_threat_found.wav. It may be copyrighted and/or would require permission to use it in VidCoder. On the other hand, it's possible it might be royalty free).

If I can get all the standard stuff moved over to the Video tab, bringing the advanced panel back makes more sense. It will be a place that only the brave will venture to.

:goodpost:

[mike20021969]

It's about how VidCoder looks with Luna theme compared to Aero theme

In case it's relevant, I'm using Windows XP with the Silver "Colour scheme".

[RandomEngy]

I actually designed it under the Aero theme, I never meant for that bar to stand out; that's just an accident of how the themes look on other operating systems.

[RandomEngy]

Not really to me. The UI comes too close to the command bar; the Aero theme gives better margins on the buttons. Though it might look okay if the command bar extended all the way across the top and there was a bit more room. What particularly do you like about the coloring on that one?

[mike20021969]

Also in the Audio section, this needs changing too ;)

http://i59.photobucket.com/albums/g302/mike20021969/20121118_21h44m04s_001_Preset-854x480.jpg

[RandomEngy]

Bug report(s):

The Bitrate drop-down list in the VidCoder Audio panel always is offering bitrates of up to 1536 Kbps, even though some Audio Codecs usually don't support 1536 Kbps.

For MP3 for example, the maximum the Bitrate drop-down list should offer should be 320 Kbps.

The standard HandBrake GUI apparently does not have this bug.

Their bitrate choices are all dynamically created based on what file has been loaded, so they're always "correct" (except when a file hasn't been loaded yet).

I have a little tougher time since I try to display all bitrates that are valid for any source file (so as to not mess up someone's preset when they load the wrong file). I can still do something here; I'll code in some limits that I know exist, like for MP3 and AC3.

And something else:

In the Audio panel:

Please rename "AAC (faac)" to "AAC (FAAC)".

Please rename "AAC (ffmpeg)" to "AAC (Libav)".

Please rename "MP3 (lame)" to "MP3 (LAME)".

Please rename "AC3 (ffmpeg)" to "AC3 (Libav)".

In the Video panel:

Please rename "MPEG-2 (FFmpeg)" to "MPEG-2 (Libav)".

Please rename "MPEG-4 (FFmpeg)" to "MPEG-4 (Libav)".

All tested with VidCoder 1.4.5 Beta (x64).

Alright. Those all appear to be accurate changes. I'll make them.

Also in the Audio section, this needs changing too ;)

http://i59.photobucket.com/albums/g302/mike20021969/20121118_21h44m04s_001_Preset-854x480.jpg

Ahh, a casualty of my extracting everything to string resources. I'll get that fixed up.

[RandomEngy]

A suggestion/question:

Please take a look at those pictures over there:

https://reviews.handbrake.fr/r/280/s/20/

Do you notice how there is a "Toggle Presets" button in the upper right corner of the Main Window of the HandBrake MacGUI which apparently makes the Preset list pop in and out of the right side of the main window?

Do you think you could do something like that with the Encoder Settings in VidCoder as well?

Or with other words: would there be any chance you could implement such a "Toggle Encoding Settings" button for the VidCoder Main Window, which, if pressed, would make the Encoding Settings pop out of the bottom or the right side of the Main Window and make them go inside the Main Window again if pressed again, similar to how the Preset List is looking in the HandBrake MacGUI and maybe with a nice animation while popping in and out?

If yes: that would be appreciated :).

If no: would there be any chance you could at least make the Encoding Settings Window dockable to the Main Window, so it could be attached to the Main Window and would move together with the Main Window?

Thank you very much in advance.

No. The expandable tray is a native Mac GUI thing and it's a bit weird for Windows.

As far as docking, I've had vague plans to allow you to drag around the helper windows and do nicer things with them but WPF doesn't give you very much to work with. There's some solutions to do "docking" ala Visual Studio but those are a problem because VidCoder windows have minimum sizes and the docking systems I've seen don't support that. I don't think anything is going to happen with this anytime soon unless some great solution with no downsides comes up.

[RandomEngy]

Released VidCoder 1.4.6 Beta (http://vidcoder.codeplex.com/releases/view/97951).

* Brought back the x264 advanced options panel due to popular demand. Thank you for all the feedback.
* x264 Preset/Profile/Tune/Level has been moved back to the Video tab, along with a copy of the "extra options" string.
* Added Fast Decode and Zero Latency checkboxes to support multiple Tunes.
* Added cropping option "None".
* Audio bitrates that are incompatible with the encoder (such as MP3 > 320 kbps) are no longer preset on the list.

* Fixed crash on opening VidCoder after de-selecting "remember locations".
* Fixed problem with some H.264 levels getting incorrectly grayed out.
* Fixed problem where preview picture dimensions could "drift" when in Strict or Loose Anamorphic mode.
* Fixed "Video Codec" label in the audio tab.
* Renamed ffmpeg to Libav in encoder names to better reflect the library they're coming from, and improved capitalization of encoder libraries.

[mike20021969]

* Brought back the x264 advanced options panel due to popular demand.
* Fixed "Video Codec" label in the audio tab.

:thanks:

[RandomEngy]

Awesome. Although it looks quite crowded now.

But here is a suggestion/an example for how you could make it look less crowded:

At the moment the quality settings on the Video panel look like this:


O Target Size (MB) [Value]
O Avg Bitrate (kbps) [Value]
O Constant Quality [Value]
——————————————————————————————[]——————————————————————————————
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
High quality Low quality
[] 2-pass encoding
[]Turbo first pass


What do you think about changing it to this for example:


O Const. Quality (CRF) [Value]
HQ ———————————————————————————[]—————————————————————————— LQ

O Avg Bitrate (kbps) [Value] [] 2-pass encoding
O Target Size (MB) [Value] [] Turbo first pass


?

;)

That would save a lot of space and would make it look less crowded IMHO ;). Also, "Const. Quality (CRF)" should be at the top and "Target Size (MB)" at the bottom IMHO ;).

Those dashes "——————————————[]——————————————" in those "Code" boxes above are supposed to portray the CRF slider by the way :D;).

The visual "steps" which currently reside under the CRF slider (and which are portrayed as "||||||||||" in the first "Code" box), probably could be removed as well to save some more space and to make it look even less crowded (as illustrated in the second "Code" box).

I like having the phrases "High quality" and "Low quality" on the UI because they are descriptive and helpful, whereas HQ and LQ are less friendly acronyms. The quality slider may be the most important thing the average user will interact with and I want to make it a nice experience. Similarly I like the tick marks because they give the user an immediate sense of how finely-grained the slider is and they can tell how broad a movement they will need to make to get changes or how likely it is that they will be able to put the slider back in the same spot they left it. Plus if you cut the tick marks you only save like 3 pixels.

It is a little bit crowded, but I think that is mostly from the logical "areas" of the panel running together (Framerate, Quality, Passes, x264 options). I moved the controls around a bit and I think this is a bit nicer:

http://i.imgur.com/suRhE.png

Also:

The value boxes for "Avg Bitrate (kbps)" and "Target Size (MB)" should not disappear when "Const. Quality (CRF)" is selected. They should only be greyed out IMHO.

And the CRF slider and CRF value box should not disappear when "Avg Bitrate (kbps)" or "Target Size (MB)" are selected. They should only be greyed out IMHO.

It's done like that in the standard HandBrake GUI (things only get greyed out there, they don't disappear), and it looks and "feels" better that way IMHO.

One of the things I don't like about HandBrake is the large amount of controls that sit around grayed out. If they're not relevant to you at the moment they're just visual noise. It's only helpful to have them present and disabled if it gives you information you don't already have. Do you need to know what the average bitrate would start at if you selected it? I'm not sure that's the case here.

Also:

At the moment, the "Target Size (MB)" and "Constant Quality" value boxes have two clickable buttons to adjust the value. The "Avg Bitrate (kbps)" value box however does not have those buttons.

Please add those two buttons to the "Avg Bitrate (kbps)" value box as well for the purpose of consistency.

I like it better when neither the target size nor bitrate have the buttons. They aren't fields that I think would benefit too much from them, most of the edits are just going to be someone typing a number in.

Also:

It would be nice if you could also bring back titles for the three Video panel categorations, namely: "Video", "Quality" and "x264".

Maybe you could achieve that with the aforementioned space saving measures ;)?

There's no room and as mentioned before your space saving measures have other usability downsides.

And maybe also by somewhat reducing the height of the "More Settings" box if necessary?

You also have this blue "Input" bubble on the Video panel.

You probably could also save some more space by removing the "Type:" and "Codec:" rows from this bubble for example?

Those two rows do not necessarily show any valuable information IMHO. Especially the "Type:" row. It only shows "Type: File" :rolleyes::D (definitely a waste of space IMHO).

So, the "Codec:" and "Framerate:" rows or even the "Framerate:" row alone would probably be sufficient, don't you think ;)?

Reducing the "More Settings" box doesn't help since it's below the preset slider anyway.

The "Type" tells you DVD/Blu-ray/File. And we're not crunched for space in that column, so eliminating it wouldn't help.

[RandomEngy]

:confused:

What :confused:?

If you would reduce the height of the "More Settings" box so that it's bottom would not overcome the bottom of the H.264 Level drop-down list, then of course that would save some space, wouldn't it :confused:?

Because then you could move all of the new x264 controls a bit lower on the Video panel ;)?

It's the same in the LinGUI picture over there:

https://reviews.handbrake.fr/r/370/s/30/

The bottom of the "More Settings" box is lined up with the bottom of the H.264 Level drop-down list in that picture.

In VidCoder 1.4.6 Beta it's not lined up. The bottom of the "More Settings" box is exceeding the bottom of the H.264 Level drop-down list. If you would reduce the height of the "More Settings" box and would make it line up with the H.264 Level drop-down list, then that in turn would free up some space because it would allow to move all the new x264 controls a bit lower on the Video panel ;).

That's because that box is flexible: it gets bigger when you make the window bigger. But yeah I see what you mean about the space down there. Going to redo the grids there and make it less wonky.

Then why don't you make the "2-pass Encoding" and "Turbo first Pass" checkboxes disappear as well when "Constant Quality" is selected ;)?

Not a bad idea.

Ohh, the command bar ("Presetname / Save / Save As... / Rename / Delete / (Revert)") now looks much better with the Aero theme in that picture :):D;).

Will that be in the next update :)?

Yes. And here's another sneak peak at the next version:

http://i.imgur.com/ERhz7.png

Not happy with having to go to 2 rows for the controls but maybe I can do something about that later.

And, regarding the controls:

Well, the "2-pass Encoding" and "Turbo first Pass" checkboxes should not be positioned below the CRF slider IMHO. They do not belong there IMHO. They are related to "Avg Bitrate (kbps)" and "Target Size (MB)", not to CRF.

Why don't you put them at the right side next to "Avg Bitrate (kbps)" and "Target Size (MB)" like it was illustrated in that second "Code" box ;)? That would save a lot of space.

Example:

O Target Size (MB) [Value] [] 2-pass Encoding
O Avg Bitrate (kbps) [Value] []Turbo first Pass
O Constant Quality [Value]
—————————————————————————————[]—————————————————————————————
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
High quality Low quality

;)

But, well, all up to you of course ;).

Another good idea.

Here it is post-rejiggering:

http://i.imgur.com/iAweV.png

PS:

Just noticed:

The new "High 4:4:4 Predictive" entry in the H.264 Profile drop-down list does not fit into the drop-down list when selected.

It widens the H.264 Profile drop-down list and makes the two x264 Tune checkboxes and the "More Settings" box move to the right when selected.

The x264 Tune, H.264 Profile and H.264 Level drop-down lists also seem to be unnecessarily wide. The only entry that would require them to be this wide or even wider (see above) would be "High 4:4:4 Predictive".

Looks like there also would be an abbrevation:

"Hi444PP"

See:

http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Profiles

Just saying.

I don't think I'll use that. I'm okay with the box getting a bit bigger on that choice because I don't think it will be very common. The UI is flexible; it can handle it.

[RandomEngy]

Question:

VidCoder 1.4.6 Beta (x64) has an "Auto" entry in it's Audio Bitrate drop-down list.

HandBrake-svn5071_x86_64-Win_GUI however does not have an "Auto" entry in it's Audio Bitrate drop-down list.

How does the "Auto" setting in VidCoder work?

LibHB has a function called hb_get_default_audio_bitrate that I use.

And:

For "MP3 (LAME)" and "Vorbis (Vorbis)", VidCoder also allows to configure the Audio Quality instead of the Audio Bitrate. But it allows to configure the quality value in 0.5 steps. Is that even possible with LAME and Vorbis? Not quite sure, but shouldn't the steps actually be in 1.0 steps?

The granularity of these settings is something that I read out of the HandBrake library. I do not know for certain whether or not they're correct.

And, actually, after thinking about it again: what would the "High 4:4:4 Predictive" entry on the H.264 Profile drop-down list even be useful for at the moment ;)?



When the H.264 Profile drop-down list is set to "Automatic", that will make x264 encode with High 4:4:4 Predictive Profile anyway when CRF 0 is selected ;).

Therefore the "High 4:4:4 Predictive" entry on the H.264 Profile drop-down list might be a bit redundant at the moment ;)?

"High 4:4:4 Predictive" should rather not be in the drop-down list at the moment IMHO.

It looks like "Rodeo" hasn't added it to the drop-down list in his MacGUI patch either for aforementioned reasons, see:

https://forum.handbrake.fr/viewtopic.php?p=118365#p118365

But up to you of course.

I'm going to leave it there since it's a profile that might sometimes be applied to encoded videos.

By the way, are you still thinking about this:

It would definitely be appreciated.

Or have you already decided against it?

Decided against, for now after reading the HB team's take on the issue.

Bug report:

This one is a bit strange:

Adjusting sliders in VidCoder 1.4.6 Beta (x64) results in HDD starting to seek, even when no source file has been loaded :confused:.

It doesn't matter what slider and what panel. It happens with any panel and with any slider.

As soon as the slider starts to move, the HDD starts to seek. When the slider is stopped, the HDD usually stops to seek. But if you move a slider really quickly from one side to the other and back and forth and back and forth... a few times, the HDD starts to seek like mad over a long period of time, even after the slider has been put in a fixed position again :confused:.

This happend with versions prior to 1.4.6 Beta (x64) as well :confused:.

And it does not happen with HandBrake-svn5071_x86_64-Win_GUI :confused:.

Well, is there anything you can do about that ;)?

The hard drive seeking is not a bug to be fixed, it's just something your computer does. But yes you do get hard drive activity when you make any setting change because VidCoder automatically saves everything. If you are fiddling with something and the app crashes or your computer turns off, it will come back in exactly that way when you start up the program again.

The large amount of activity that continues for a while after moving the slider is something I can deal with. Currently it's just saving the settings in the background every time a change is made but I can make it so that if multiple changes come in while one operation is completing only the latest one will actually run. That will probably result in a lot less useless hard disk activity when you move sliders about or hold down the buttons on a number box.

Bug report:

There appears to be a GUI bug with the new "None" cropping option.

The "None" cropping option appears to work just fine on encoding, but:

As you know, the "Automatic" cropping option is set by default.

Now when you load a source file which HandBrake/VidCoder decides needs to be cropped automatically, then the green "Output" bubble on the Picture panel shows what the resolution is after automatic cropping.

All fine up to that point.

But if you then select the "None" cropping option, the resolution in the green "Output" bubble remains untouched. It still shows the same values as if the "Automatic" cropping option would be selected (although it is not selected).

However, as mentioned already, the "None" cropping option still seems to work just fine on encoding.

So it apparently is "just" a bug with the GUI (the green "Output" bubble is not following the "None" cropping option).

Still, would be nice if you could fix that ;).

PS:

Looks like it's the same with the "Custom" cropping option.

If you have switched from "Automatic" to "None", then the "Custom: Top / Right / Bottom / Left" values are set to "0" (zero), and if you then switch from "None" to "Custom", it will still show zero but the green "Output" bubble still shows the resolution values as if "Automatic" would be selected.

In short it probably could be described as: the values in the green "Output" bubble on the Picture panel are not updating correctly as they should according to the selected cropping option.

Well, you probably will understand better if you take a look at it yourself. Something seems to be broken there ;).

PPS: Tested with VidCoder 1.4.6 Beta (x64) and Anamorphic ---> Strict.

I see it; it should fixed in next version. Was a regression when I added the "None" cropping option.

Bug report:

Just noticed:

The Advanced panel of VidCoder 1.4.6 Beta (x64) is differing from the Advanced panel of HandBrake-svn5071_x86_64-Win_GUI in the following regard:

The "Partition Type" drop-down list in the Advanced panel of HandBrake-svn5071_x86_64-Win_GUI has the following entries:



The "Partition Type" drop-down list in the Advanced panel of VidCoder 1.4.6 Beta (x64) however has the following entries:



:confused:

Not sure though if VidCoder 1.4.6 Beta (x64) is at fault or if HandBrake-svn5071_x86_64-Win_GUI is at fault.

The advanced panel is just something I try to keep up to date with HandBrake. I bet it's just a recent change I haven't done yet. I'll make the update.

Feature request:

Please add a checkbox under Tools ---> Options... ---> Advanced to make it possible to deactivate and activate the Advanced x264 settings panel.

Deactivated = Advanced panel removed from Encoding Settings Window
Activated = Advanced panel not removed from Encoding Settings Window

Should the Advanced panel be deactivated by default or should it be activated by default? Well, you decide :D;).

Voting for having it deactivated by default though. That would definitely be appreciated.

Those who are in dire need of the Advanced panel and have whined about it's absence in 1.4.5 Beta could just go to Tools ---> Options... ---> Advanced and activate it via that checkbox IMHO. That would probably be an acceptable and "easy-peasy" step for those users if they are that advanced... :D;)

That way you also would make clear that you don't want the Advanced panel but at the same time would grant your users the choice to activate it if they really want to.

But, anyway, wether you make it deactivated by default or activated by default, having such a checkbox would be nice either way.

Therefore, please add it ;).

Well I still think that most people are going to be fine never touching an advanced option, but I think this arrangement accommodates these users just fine. They're on the Video tab and they've got everything they need to make good x264 encodes. Presets, profiles, tunes, levels and a box with some fiddly settings they don't need to care about. The settings that matter are there in the forefront and all the settings that they probably shouldn't do anything with are off in a tab labeled "Advanced". It's a conscious decision at that point to go over there and mess with things. I think these factors alone should be enough to keep most casual people from twiddling with them or feeling like they need to twiddle with them.

Given that, there's really no reason to have an option to turn it off. It's just a tab that doesn't get in your way if you don't use it. Maintenance isn't too bad since I've got a good system to let me easily tweak the choices and automatically construct the options string from them.

And:

Please add a checkbox under Tools ---> Options... ---> Advanced (or General) to make it possible to disable and enable the VidCoder splash screen on VidCoder start-up.

Impossible. The splash screen appears even before the .NET Runtime has loaded. If I used a different splash screen type, it would take longer to show up and mostly defeat the purpose of it.

And:

Please add a "Help ---> Check for Updates" entry to the menu bar of the Main Window (HandBrake-svn5071_x86_64-Win_GUI has such an entry in the menu bar as well).

VidCoder checks for updates when starting up and prompts you to install them when closing. You don't need to do any checking yourself. The reason HandBrake has this option is that its update system is worse and you need to install updates for it on your own.

I suppose I could add the feature as a security blanket but it's not very high on my priority list.

And:

If you don't mind then :o:

Please rename the "None" entry in the x264 Tune drop-down list to "None (Default)".

Please rename the "Automatic" entry in the H.264 Profile drop-down list to "Auto (Default)".

Please rename the "Automatic" entry in the H.264 Level drop-down list to "Auto (Default)".

That would be more consistent with the x264 Preset slider having "Medium (Default)".

Also every single drop-down list in the Advanced panel has "(Default)" written behind it's default setting as well.

So it would be appreciated if you could do it for the x264 Tune, H.264 Profile and H.264 Level drop-down lists as well.

Thank you very much in advance.

I've added (Default) to settings where it's not clear what the default is. It should be clear that "Automatic" or "None" are safe defaults when they are at the top of the list. Adding on the (Default) qualifier in this case just bloats the text and makes it less scannable.

This shows that you shouldn't thank people in advance because they might not do what you're asking!

[RandomEngy]

I've got a new wiki page up describing how to translate VidCoder to another language (http://vidcoder.codeplex.com/wikipage?title=Translating%20VidCoder). Looking for volunteers, particularly for Spanish and German. Had one guy but he's been missing for weeks now.

[RandomEngy]

The question/request arose, because, the way it's done in 1.4.6 Beta still is a bit "halfhearted" IMHO, especially if you do not plan to remove the Advanced panel in the long term.

Because, in no way do the "basic" x264 settings on the Video panel interact with the advanced x264 settings on the Advanced panel and vice versa. That somehow feels a bit "halfhearted".

The HandBrake GUI developers seem to think a bit further regarding that, read the following quote for example:


That's why the x264 Preset slider in their LinGUI picture also has an additional "Custom" entry for example, see:



Can you do something like that with VidCoder GUI as well? Making the "basic" x264 settings on the Video panel interact more with the advanced x264 settings on the Advanced panel and vice versa?

hb_x264_param_unparse was added in a checkin after the big title->job refactoring (https://trac.handbrake.fr/changeset/5058). I'll need to update the interop to handle those changes before I can do any more work with the advanced settings.

Ah, okay, that's basically just fine as well. Looks like that "Menu Bar ---> Help ---> Check for Updates" feature basically already is available but just located at "Tools ---> Options... ---> General".

Although, that "Version X has finished downloading and will install on exit" notification could be a bit more prominent and remain visible a little longer IMHO... It automatically disappears after just a few seconds...

Maybe make it a little bit more prominent and disappear only when the user has affirmed it?

The message stays in the log and pops up a dialog box when the program is closed. I think it's fine.

Could you possibly elaborate what you mean with that?

By "security blanket" I mean something that makes you feel better but doesn't really help solve anything.

[RandomEngy]

About adding controls to the Advanced panel, I'm a bit tired of poking controls around to make room. Why don't you submit a patch for fitting those VBV controls in? But please, no abbreviations.

Bug report:

Please just read the following thread over there:

https://forum.handbrake.fr/viewtopic.php?f=6&t=25837

;)

In VidCoder 1.4.6 Beta (x64), all the advanced x264 controls are displayed on the Advanced panel, even when "MPEG-4 (Libav)" or "MPEG-2 (Libav)" are selected on the Video panel.

In the standard HandBrake WinGUI that is not the case. In the standard HandBrake WinGUI the advanced x264 controls disappear from the Advanced panel when Video Codecs other than "H.264 (x264)" are selected on the Video panel.

Only a big text box (called "Advanced Query") remains on the Advanced panel in such a case in the standard HandBrake WinGUI.

I'll fix that for next version.

[RandomEngy]

Released VidCoder 1.4.7 Beta (http://vidcoder.codeplex.com/releases/view/98070):

* Added view modes to the Preview window. Now you can see the image in 1:1 or in "Corners" mode to show a close-up of cropping results.
* Added the ability to set a custom completion sound.
* Gave the encoding settings command bar a more distinctive background color and extended it to the whole width of the window. Added the preview button to the command bar.
* Rearranged UI in Video tab and added back the section headers.
* Added the "Most" choice for the advanced x264 analysis option.
* Updated HandBrake core to SVN 5071.

* Fixed excessive hard disk activity when quickly changing encoding settings by moving a slider or holding down a number box button.
* Fixed cropping output not updating when switching cropping modes (regression in 1.4.6).

[mike20021969]

* Added view modes to the Preview window. Now you can see the image in 1:1 or in "Corners" mode to show a close-up of cropping results.
This is a great feature.

* Added the ability to set a custom completion sound.

Many thanks for this :)

[fantasmanegro]

@RandomEnergy

can you put some pictures of the Gui in First Post

[RandomEngy]

Released VidCoder 1.4.8 Beta (http://vidcoder.codeplex.com/releases/view/98126):

* Fixed encode failures when including chapter markers (Regression in 1.4.7).