StaxRip

[stax76]

Resetting the template and filters helped

It's very likely unrelated to filters and templates.

Can you also put progress bar in encoding audio streams?

It parses the output for a percent character so it really depends on the app and it can make a difference what settings are used such as piping because with piping the app cannot calculate the length unless it's passed manually which might not be supported. Which converter are you referring to?

[mparade]

Is DGDecNV supported as the video decoder (automatic dgi file creation etc. based on the source)?

[stax76]

@mparade

Please look at:

Filters > Source > Select source filter > Right-Click > Source > DGSource

Filters > Profiles > Source section

Main Menu > Tools > Settings > Preprocessing (previously Demuxing) > DGIndex/DGIndexNV/DGIndexIM > Edit

Main Menu > Tools > Settings > Source Filters > AviSynth > dgi/dgim

Main Menu > Tools > Settings > Source Filters > VapourSynth > dgi

Main Menu > Apps > Manage > enter DG in the search field

There are more places like the code editor has a context menu for most DGSource parameters.

You have to be careful with these settings, for instance while you can demux mkv/mp4 with DGIndexNV I don't recommend it, that's why the Preprocessing setting has two entries for DGIndexNV, it's configured to demux TS, the last build uses ffmpeg to re-mux TS to mkv, if you see that entry depends on which build created your defaults because when I change defaults most of the time I don't force a reset of the defaults, if you see the ffmpeg re-mux ts to mkv entry you have to disable it because DGDecNV has better TS handling.

[mparade]

Sounds interesting. I will give it a try.

May I update within StaxRip DGDecNV and x265 to the latest versions?
Does your program accept HDR content as an input (via Avisynth+ and DGDecNV (the latest DGDecNV version does support HDR10 and 12) I want to reencode them). May I use custom x265 command lines (may I add custom parameters to the command line)? I want to let the encoder know what HDR metadata is located in the source file).

Thanks for your help.

[stax76]

May I update within StaxRip DGDecNV and x265 to the latest versions?

You can update things, there is a feature to change version and path in the apps dialog (Main Menu > Apps > Manage).

The newest staxrip test build 1.6.1.5 includes the last stable x265 build 2.5+14

Does your program accept HDR content as an input (via Avisynth+ and DGDecNV (the latest DGDecNV version does support HDR10 and 12) I want to reencode them).

I don't have HDR hardware and don't encode a lot, if you find limitations and report them I usually build and release improvements within a few days.

May I use custom x265 command lines (may I add custom parameters to the command line)? I want to let the encoder know what HDR metadata is located in the source file).

StaxRip supports all encoder options of all encoders but there is always a custom option included just in case. Special or new things I don't know much about I usually implement as script first, have a look at:

Main Menu > Tools > Scripts

There is script called 'Convert Bluray (BT709) to 10bit 400nits (MaxFALL) HDR v3', the parameters are contributed by a user.

[RieGo]

Hello,

i'm having difficulties with one specific video file:
http://www18.zippyshare.com/v/yOhSh7CI/file.html (trimmed)

whenever i open it with staxrip vapoursynth, my staxrip just crashes completely. it's a ts-doctor generated ts file.
i tried muxing to mkv, i tried all source filters, i tried resetting settings and i even tried loading it as avi file by using avfs. (loading by avisynth works just fine)
other video files also work with staxrip / vapoursynth filters

does anybody have an explanation?

thanks

[stax76]

It works here, in the newest test build I changed the TS default handling, TS is now re-muxed to MKV with ffmpeg, you can find the build here:

https://github.com/stax76/staxrip/blob/master/md/changelog.md

Enable the new defaults here:

Main Menu > Tools > Settings > Preprocessing > Restore

DGDecNV is probably the best TS solution btw.

edit:

Log: https://pastebin.com/WZHVshQs

[RieGo]

ok, thanks.
it doesn't work with latest staxrip + default settings. it seems to be a problem with vapoursynth, as opening the vpy with mpc-hc also results in a crash...
i probably got something wrong with my python/VS installation

[stax76]

You are right, you can use LWLibavSource instead, I'll file a bug report.

[RieGo]

You are right, you can use LWLibavSource instead, I'll file a bug report.

fixed my problem. had an x86 python set as default :rolleyes:
thanks anyways!

[stax76]

OK, I had an error too but after a second try it was fine.

[mparade]

@Stax

HDR encoding seems to be working using the latest DGDecNV! Encoding seems to be ~35-40% faster than without GPU assistance for video decoding (on GTX 1060 6GB).
Nice job! More info only after testing the output on my HTPC and HDR OLED TV.

[aegisofrime]

Hi stax76.

I'm having some instances of StaxRip misinterpreting x265 returning "STATUS_WAIT_1" as an error and thus aborting the task. Based on my own analysis, STATUS_WAIT_1 (that's how I remember it, will grab a screenshot the next time I see it) might be returned when x265 is waiting for frames from the frameserver. This will occur with very heavy or slower scripts. The script itself is fine; I can simply start the encoding job again and most of the time it will encode fine. Could you disregard this status in future releases and stop StaxRip from aborting the encode job? I hope I'm making sense here. :p

[stax76]

Hi aegisofrime,

are you sure the x265 process is still alive when you get this error?

As far as I know you would only see such a error after the process was terminated.


@mparade

I'm working on something HDR related for the next build.

[mcjordan]

NVEnc 3.19

Changes in NVEnc 3.18
· Added automatic field shift. (vpp-afs)
· In case of interleave, various filters can process while maintaining the field.
Added the function to reflect rff appropriately and expand it to the field. (vpp-rff)
Fixed that abnormal termination might occur when converting yuv420 of high bit depth to p010.

Changes to NVEnc 3.19
[NVEnc.auo]
HEVC Enable to set frame type at encoder.

[stax76]

I've uploaded a maintenance build, nothing exciting due to lack of ideas. :)

Requirements

.NET 4.7 is required on systems prior Windows 10 Version 1703 (Creators Update)

https://www.microsoft.com/en-us/download/details.aspx?id=55170

Download

https://drive.google.com/open?id=0B-gPKiJYuKuITld4dzhuTC1WWWM

https://1drv.ms/f/s!ArwKS_ZUR01goCzIRemxotXY_zz-

1.6.1.6 unstable test build


new: various new resolutions added to the resize menu
new: transfer_characteristics added to mediainfo folder view
new: MediaInfo properties colour_primaries, transfer_characteristics and matrix_coefficients are read from the source file and the encoder switches --colorprim, --transfer and --colormatrix are set
new: NVEnc --vpp-rff and --vpp-afs switches added



fix: preview did not work with > 8 bit depth avs scripts
fix: incorrect VUI flags corected and all flags alphabetically sorted



usability: the preprocessing settings have better names and the dialog width adjusts automatically (https://github.com/stax76/staxrip/wiki/Screenshots#preprocessing)



change: improved discovery of required VapourSynth LoadPlugin/SourceFileLoader functions



new: VapourSynth plugin vsfft3dfilter added (https://github.com/VFR-maniac/VapourSynth-FFT3DFilter)



update: MediaInfo 0.7.99
update: mClean 1.7b
update: AVSMeter 2.6.5
update: NVEnc 3.19

[VfBFan]

The standby issue is gone.
But I have no idea why it is now working. :)

V1.6.1.5, all settings reseted -> works.

[mparade]

@stax

I would have some idea how to improve HDR encodes in your program (would be for not to set manually the mastering display parameters because calculating them manually is very time consuming). Unfortunately, the output 10-bit mkv file of your program has some decoding artifact so first of all I need to find out what is causing that:

http://www.mammutmail.com/hu/download/bdf08e075867514436013154b6fea0dd

1. It is encoded in the output (problem with DGDecNV);
2. It is a problem relating to the decoder (Lav filters etc.);
3. It is a problem relating to the renderer (madVR etc.);
4. It is a a problem relating to the display;

[stax76]

@mparade

First I wanted to support the mastering display parameters based on recent posts in the x265 thread but it was a little bit tricky. If you post your source media info and your resulting command line it will help me to code it.


@VfBFan

I hope it don't come back.

[mparade]

This is most probably the problem with:
1. It is encoded in the output (problem with DGDecNV);

[stax76]

You can report it here:

http://rationalqm.us/board/index.php

[mparade]

You can report it here:

http://rationalqm.us/board/index.php

I will be reporting the problem to Donald Graft urgently because I am quite sure it is a CUVID bug.

[mparade]

First I wanted to support the mastering display parameters based on recent posts in the x265 thread but it was a little bit tricky. If you post your source media info and your resulting command line it will help me to code it.



If media info tells:

Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : R: x=0.680000 y=0.320000, G: x=0.265000 y=0.690000, B: x=0.150000 y=0.060000, White point: x=0.312700 y=0.329000
Mastering display luminance : min: 0.0050 cd/m2, max: 4000.0000 cd/m2
Maximum Content Light Level : 4000 cd/m2
Maximum Frame-Average Light Level : 290 cd/m2


a sample command line would be according to x265 specs (16bit input is assumed via DGDecNV and if I understand the specs correctly):

--crf 24 --preset slow --tune grain --profile main10 --output-depth 10 --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,50)" --colorprim bt2020 --colormatrix bt2020nc --transfer smpte-st-2084 --range limited --max-cll "4000,290" --input-depth 16

[stax76]

Movie scene where a jukebox is spinning a stax record...

https://www.youtube.com/watch?v=97qA-Wr1SBU


@mparade

Thanks, it will definitively be supported in the next build (or one after).

[dvd_maniac]

Stax,
I upgraded to 1.6.0 and my batch script is broken again.
I opens a staxrip.exe but does not encode or create a temp folder. When I try to run the cli script manually it opens the select Avisynth source filter dialog box. How can I bypass this and set it to automatic for every run?

[stax76]

When I try to run the cli script manually it opens the select Avisynth source filter dialog box. How can I bypass this and set it to automatic for every run?

This dialog is only shown if the source filter is set to 'Manual', you can set it to 'Automatic'.

There is a project option on the misc tab that will hide any dialog, it's probably better to enable this only via CLI with following CLI switch: -SetHideDialogsOption:true

[mparade]

Thanks, it will definitively be supported in the next build (or one after).



Thank you. I am waiting for the CUDA bug to repair because I prefer GPU assisted decoding:

https://devtalk.nvidia.com/default/topic/1024038/video-technologies/nvdec-hevc-10-bit-decoding-is-broken/

[stax76]

Thank you. I am waiting for the CUDA bug to repair because I prefer GPU assisted decoding:

https://devtalk.nvidia.com/default/topic/1024038/video-technologies/nvdec-hevc-10-bit-decoding-is-broken/

The only other source filter that support hardware decoding is DSS2/DirectShowSource but it's probably 8-bit only.

[ABDO]

Hi frank, thank you for your hard work in staxrip, i have a question please, can i import image sequence to staxrip.

[stax76]

Hi, what kind of image and filename pattern do you have? One filter I found is this:

http://avisynth.nl/index.php/ImageSource

[ABDO]

thanks for your quick reply, my image is png or Bmp, i use adobe premiere pro to export it, and want to use staxrip to encode it because it much better in this case,the filename pattern is depend on the number of frams exported , if less than 3 digits from 1:100 ( 01-02-03-99), if larg than 3 digts then (001-002-003) and so on.

[stax76]

You can try to customize staxrip or write a avs/vpy script and open the script file as source file. I'll try to add direct support for image sequences. Would exporting it in a video format with adobe premiere not work?

[ABDO]

Would exporting it in a video format with adobe premiere not work? i can use adobe premiere to exporting it in a video, but the Problem is the (hevc encoder) in premiere is Useless, and give very bad result compara it (x265) in staxrip, would be great if you can get some time and effort to add this Feature dirctly to staxrip,Unfortunately i do not understand or use scripts :(

[StephanD]

Heyho,

Dunno if this was already reported, couldn't find anything in the search, but there is a mistake in the automatically created command line für AV1.

If you use the threads-flag, its automatically creating "t=x". This is not correct. There are two flags for it. If you use "--threads", you can use the "=". if you use the short "-t" it should be "-t x" without "=".

As this codec is still in progress, I wouldn't use the shortcodes, because it is not clear, if they remain in later versions.

For example you get a failure when using the "--best"-flag in your programm. In the latest repository of AV1 this flag is gone.

greetz

[mcjordan]

Updates

mClean v1.7c
* Slight adjustments and slightly better speed

NVEnc v3.20
Summary: Addition of automatic selection function of edge emphasis filter/device, correction of defects, etc.

Common
· If you do not specify otherwise, make device selection automatically when you execute.
In a multi-GPU environment, automatically determine the GPU to be used, especially when there is no designation of the device to be used.

The judgment standard is:
· Whether the specified encoding is possible (check codec, 8bit/10bit, YUV420/YUV444 etc)
· If --avhw is specified, it is possible to decode HW of the input file
· Low use rate of Video Engine
· Low GPU usage rate
· New generation of GPU
· People with a large number of GPU cores

The usage rate of the Video Engine and GPU usage rate are acquired by executing "nvidia -smi.exe -q" because the x64 version can not use the NVML library and the x86 version can not use NVML.
Nvidia-smi.exe is normally installed in "C:\Program Files\NVIDIA Corporation\NVSMI\nvidia-smi.exe" together with the driver.

· Added Unsharp filter. (-vpp-unsharp)
Unsharp filter for ordinary contour and detail emphasis (I think that's it). At first I tried using it because it is in the NPP library ... I tried it a lot but I thought that usage was bad after all, but it did not work well, so I decided to implement it myself with CUDA as there was no choice.

Parameters
-radius = <int> (default = 3, 1-9)
Scope of contour / detail detection. By setting it to a larger value, it will emphasize in response to a wider range of detail.

-weight = <float> (default = 0.5, 0-10)
Strength of contour and detail emphasis. By setting it to a larger value, it becomes strongly emphasized.

-threshold = <float> (default = 10.0, 0-255)
Threshold for contour and detail detection. Outline emphasis is performed on pixels having a difference equal to or larger than the threshold value.

Example: Somewhat stronger
-vpp-unsharp weight = 1.0

· Added edge level adjustment filter. (-vpp-edgelevel)
Added by adding CUDA as an edge level adjustment filter after Unsharp. The default value of the parameter is slightly weaker than the Aviutl version.

Parameters
-strength = <float> (default = 5.0, - 31-31)
Strength of contour emphasis. By setting it to a larger value, it will emphasize in response to a wider range of detail.

-threshold = <float> (default = 20.0, 0-255)
Noise threshold to avoid outline emphasis. As the larger the value, the larger the luminance change is treated as noise.

-black = <float> (default = 0.0, 0-31)
For the black part of the outline, shoot black more and emphasize the outline.

-white = <float> (default = 0.0, 0-31)
For white portions of the outline, shoot more whitely and emphasize the outline.

Example: Somewhat stronger (Aviutl version default)
-vpp-edgelevel strength=10.0, threshold=16.0, black=0, white=0

Example: Strengthening the black part of the outline
- vpp-edgelevel strength=5.0, threshold=24.0, black=6.0

NVEncC

· Fixed crop being doubled when using crop and resize when using avhw reader.

· Adjust the argument of --transfer to that used in x264 etc.
smpte-st-2048 -> smpte 2048
smpte-st-428 → smpte 428

[stax76]

@ABDO

I tried the filter, everything needs to be defined manually so it's too much work to integrate the filter in a way that things work as simple as opening a video file.

D:\Temp\aaa\test_000001.jpg
D:\Temp\aaa\test_003040.jpg

ImageSource("D:\Temp\aaa\test_%06d.jpg", 1, 3040, 25)

Maybe there is a easier way with ffmpeg or vapoursynth.

From a tool like premiere I would expect that it can export to a suitable video format.

@StephanD
@mcjordan

Thanks for reporting, I'll fix/update nvenc/aomenc support.

[ABDO]

ok, i will export video from premiere with ( AVC -H264 ) and it did Excellent job.thank you frank, always willing to help:thanks::)

[mcjordan]

Hmm... About new NVEnc 3.2.0
With this addition to my custom NVEnc profile aka
--vpp-unsharp radius=2,weight=0.65,threshold=20 --vpp-edgelevel strength=6.0,threshold=16.0,black=0,white=0
I've get a massive color shifting towards the red spectrum area.
Тhis is not observed when using any other --vpp filter.
Maybe I'm losing something somewhere...
---
Part of job processing info:
Input Info Avisynth 2.60(yv12)->p010 [AVX], 1920x816, 24000/1001 fps
Vpp Filters copyHtoD
cspconv(p010 -> yv12(16bit))
unsharp: radius 2, weight 0.6, threshold 20.0
edgelevel: strength 6.0, threshold 16.0, black 0.0, white 0.0
cspconv(yv12(16bit) -> p010)
---
Source media info:
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : Main@L4
Format settings : 2 Ref Frames
Format settings, CABAC : No
Format settings, RefFrames : 2 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 2 min 31 s
Width : 1 920 pixels
Height : 816 pixels
Display aspect ratio : 2.35:1
Frame rate mode : Constant
Frame rate : 23.976 (24000/1001) FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

Help me - where am I wrong?

[Schattenspieler]

…, but the Problem is the (hevc encoder) in premiere is Useless, and give very bad result compara it (x265) in staxrip, …You could also try to export using a lossless codec or maybe a codec with lossless settings. There are many threads on the topic over at Adobes site, like this one:

https://forums.adobe.com/message/7686319#7686319

[mcjordan]

NVEnc v3.2.1
* fix issue of vpp-unsharp, which made the color of output video becoming unstable, going either red or blue.

Problem of color shifting /my previous post/ is resolved.

[stax76]

Does the nvenc default --cuda-schedule sync make sense? I'm getting 100 fps more with --cuda-schedule auto, maybe I should change the staxrip default using auto instead of sync.

[Yanak]

Hello Stax,
Since 1.6.1.4 we have this change : "usability: preview starts with zoom for small resolutions "

What resolutions are resized exactly, does it work based on the display resolution & based on a percentage for the input resolution?

I would like to know if there is a way to disable this behavior, if there is maybe an option to not have the resizing and instead get the preview work like it used to work before, displaying the preview window at 100% scale unless too big for the screen display.

I liked the way it worked before, for let's say 640*480px footage the preview display was showing me what i will get in the end, zoomed at 100%.
For high resolutions the preview was downscaled and apparently keeping the zoom level i had set previously when the sizes were bigger than my desktop resolution.

Now i have to use the zoom+- each time for low resolutions videos and don't even know exactly when i am at 100% zoom to see final result as there is no indication of the zoom level in the preview, and the preview display for bigger resolutions ( 1080p input on 1080p screen ) seems smaller than what we used to get too.

If possible would be nice to not have the preview auto zoom for low resolution inputs, at least have an option to disable this behavior, and maybe keep the max zoom level in windowed mode like before, staying under the display resolution but getting a bigger preview than what seems to be now, have a full and clean view of my project while in preview windowed mode and maybe the zoom level applied on the preview displayed, maybe next to the frame position in the top window bar.

Thanks a lot Stax.

[Merlin93]

Hello. I have spent most of the night doing google searches and searches on this forum and have been unable to find my own answer, so I'm hoping someone here can help.

I am trying to use Staxrip to convert cropped 1080p videos to anamorphic 720p and running into issues. No matter what I do, it seems like I am unable to find an automated way to adjust the settings to allow cropped 1080p videos to fit into a 1280 x 720 container. This is super easy to do in Handbrake, but I'd like to use Staxrip for this.

As an example, I have a video I'm trying to convert which is 1920 x 1080 but has 134-pixel bars on the top and bottom (1920 x 812). If I convert it with Handbrake, I can set the storage size to 1280 x 720 and it will keep the same aspect ratio and encode the video with an anamorphic display resolution of 1702 x 720 (at PAR 270/203). I am having trouble doing the same thing with Staxrip.

Perhaps it's because I cannot specify the storage resolution, but when I move the slider (with or without control held down for anamorphic mode) it seems to always select square (or nearly square) pixels. If I manually adjust the PAR to 270/203 for example, I cannot find a legal range on the slider and the aspect ratio is off in preview (and DAR). I have tried manually calculating the DAR and PAR values, but it never works how I expect (and I know it's generally bad form to try to set PAR from DAR.) Ideally, I shouldn't be calculating these things by hand anyway, that is what software does best.

TL;DR is that I am looking for a way to specify the output resolution to be 1280 x 720 pixels while maintaining the same display aspect ratio / DAR. Ideally, Staxrip would adjust the display height to 720 pixels and calculate the proper PAR to make the display width make sense. It feels like I'm missing a setting or approaching it wrong since I'd think this would be easy to do this given the power of Staxrip. Not to mention most 480i/480p DVD videos are anamorphic to exceed the 720x480 limit, and this is basically the same kind of thing so I have to believe the software supports it. I'm just not doing it right.

I'm using the 1.6 stable build, btw.

Thanks!

[stax76]

Hi Yanak,

the calculation is based on the working area (screen size - task bar), it compares the working area width to the video width, if the video width is more then 90% of the working area width then it's down scaled to 90%, if it's less then 60% then it's up scaled. On my 4K display SD was tiny, I can probably add a setting for it.

[stax76]

@Merlin93

If I understand correctly then you want to disable: Options > Image > Aspect Ratio > Adjust height according to target display aspect ratio

Perhaps it's because I cannot specify the storage resolution, but when I move the slider (with or without control held down for anamorphic mode) it seems to always select square (or nearly square) pixels.

You can enter the storage resolution in the text fields or customize the resize menu. I'm not sure I understand what's your goal, maybe you or somebody else can explain it again. I always thought that staxrip handles AR better then megui or handbrake, there were hardly any bugs or requests in the last ten years.

[stax76]

@Yanak

The next build has a setting and better calculation that also works for ultra wide displays. The default value is 60%, it ensures either width or height are minimum 60% of the screen width or height.

[Merlin93]

@Merlin93

If I understand correctly then you want to disable: Options > Image > Aspect Ratio > Adjust height according to target display aspect ratio

You can enter the storage resolution in the text fields or customize the resize menu. I'm not sure I understand what's your goal, maybe you or somebody else can explain it again. I always thought that staxrip handles AR better then megui or handbrake, there were hardly any bugs or requests in the last ten years.Hello Stax. Thanks for the quick reply!

I looked at that flag in the options and I don't think that is what I need. I'm sure Staxrip can do what I need, but I'm just not sure how to do so.

To use my earlier example, I have a cropped 1080p video which is 1920 x 812, and I would like to resize that to 1280 x 720 while keeping the same display aspect ratio, which would result in an anamorphic display size of 1702 x 720. Handbrake does this in a really intuitive way. I just specify the Storage Size as 1280 x 720, make sure Keep Aspect Ratio is flagged, and it automatically calculates the proper Display Size (of 1702 x 720) and PAR (270 x 203) to keep the same display aspect ratio. I am looking for a means to do the same thing using Staxrip.

Basically, I was hoping to be able to specify the output (storage) resolution separately from the display resolution using the GUI in a way that it automatically determines the proper PAR for me. Failing that, perhaps the next best option is to be able to see both the storage and display size, so as I adjust the PAR/DAR values I can see how that will affect the display size. Though that would still mean having to manually calculate DAR/PAR values which isn't very intuitive.

When I change the size slider in Staxrip, it seems to change the storage (output) size, so if we call this a feature request, perhaps there could be a way for me to lock the storage size and toggle the slider to affect display size and have it automatically adjust PAR values based on the source display aspect ratio?

Does that help at all?

P.S., I notice that if I set the resize to 1280 x 720 while leaving the DAR value as is, Staxrip will select the same PAR value that Handbrake calculates, but shows a -24% in the error field so I assumed it wouldn't work. Perhaps that is what is throwing me off... how do I get rid of that error?

Thanks!

[Yanak]

Hi, just seeing the answers now, got no mail notifications for new answers as it does usually for some reasons, weird.

I understand now how it worked and indeed on a 4k screen it might look extremely tiny especially with old videos material that is in small resolutions mostly, in many cases it's better to have the 100% scale to clearly see things after filters and such applied, or a wide preview window displayed inside the display screen less the task bar when it's bigger resolution videos, to get close as possible to the final output, will test this once the new version is released.

Thanks a lot for the changes Stax, big respect for all you do for us, as always you are very kind to do some changes based on users feedback, hat down for all this.

[stax76]

@Merlin93

Above the resize slider there are two text boxes, one is called width and one is called height, double click in this text boxes using the left mouse button to enter a value, all you have to do is enter 1280 in the width text box and 720 in the height text box, that is everything.

If this text boxes are disabled then you have to enable a resize filter, there are three ways to do this, first using the filter list, second using the slider and third using the menu.

[Schattenspieler]

P.S., I notice that if I set the resize to 1280 x 720 while leaving the DAR value as is, Staxrip will select the same PAR value that Handbrake calculates, but shows a -24% in the error field so I assumed it wouldn't work. Perhaps that is what is throwing me off... how do I get rid of that error?If I'm not mistaken, that is no "error" in the usual sense of the word, but an information. It's showing you, by how much the (overall) AR is off compared to the source AR (including DAR and PAR). (For me non-square pixels were and still are just a lousy workaround.)
So, yes, from what I read here, that seems to be, what's throwing you off. Just ignore it and give it a try. If in doubt, just cut a sample of some seconds and encode it. You'll see. (:

edit: If you right-click on the "Error" field for the help text, it'll tell you: "Aspect Ratio Error". And that's what it is.