Log in

View Full Version : StaxRip


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 [43] 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101

stax76
6th June 2017, 12:16
Be warned that mkvmerge subtitle cutting has limitations. Cutting in the middle of a line can break things.

Good to know, thanks.

craigpro
6th June 2017, 13:58
I'm not sure what you try to do, I would like to help but I'm pausing staxrip and doom9 for a week.

that's ok.. have a good rest :)

what I am trying to do is if I have a folder of 1080p rips and I want to resize the ENTIRE folder to 720p how do I do it please?

Currently I process each file separately in the folder.

Same goes if I just want to mux the video, but change the E-AC3 to AC3 or some other audio CODEC.

thank you.

RieGo
10th June 2017, 09:55
new: experimental AV1 codec support


using build 1.5.0.3 i can't find AV1 in the codec list. would like to try it out :)
Did I miss something?

Alexander
10th June 2017, 20:32
using build 1.5.0.3 i can't find AV1 in the codec list. would like to try it out :)
Did I miss something?

You can reset StaxRip settings
15930

stax76
11th June 2017, 09:42
using build 1.5.0.3 i can't find AV1 in the codec list. would like to try it out :)
Did I miss something?

It's because I avoid to reset user settings, in the video encoder menu go to: 'Edit Profiles' and choose 'Add' to only add the AV1 profile or Reset to reset all video encoder profiles.

what I am trying to do is if I have a folder of 1080p rips and I want to resize the ENTIRE folder to 720p how do I do it please?

There is: Source > right-click > Open > File Batch

mcjordan
11th June 2017, 10:40
From Rigaya with love... ;-)

NVEncC v3.09 - shortly
Update NVENC SDK to 8.0
Update ffmpeg dlls.
Add option to enable weighted prediction. (--weightp)
Please note this option will be disabled when B frame is in use.
Add support for 10bit depth HEVC HW decode.
Add avi file reader supporting YV12, YUY2, RGB input (imported from QSVEnc).
Now "--vbr-quality" can be set with floating point.
Remove "--enable-ltr" option, since LTR trust mode is told to be deprecated in future.
Enhance stability when using HW decoder.
Fix issue which subtitle was not copied properly in some occasions.
Fix app freeze issue when aborting from the app using vpy reader.

NVEnc 3.08
[NVEnc.auo / NVEncC common]
Updated NVENC SDK to 8.0.

Added option to enable weighted P-frame. (- weightp)
Unfortunately, it can only be used when there is no B frame ....

- Display the build version of Windows in the log.
- Fixed that there was a case that it was not possible to encode interleaved video with a height that can not be divided by 32.
- To be able to compile "Video Engine Load (VE)" of GPU-Z.
It is automatically acquired when GPU-Z is running in the background.

[NVEnc.auo]
- Added upper / lower limit / initial value setting of QP.
- Added VBR quality target setting.
- Updated simple installer.

[NVEncC]
- Supports HW decoding of 10 bit HEVC.
- Updated ffmpeg and related library dll.
- Improved stability during HW decoding.
- --vbr-quality corresponds to decimal point specification.
- Added avi file reader.
- Since the LTR Trust mode is scheduled to be deprecated in future, remove the --enable-ltr option.
- Fixed a problem that freezes when trying to interrupt encoding when using vpy reader.
- Fixed the case where copying of subtitles was not performed normally.

NVEnc 3.09
[NVEncC]
Fixed a picture breakdown when passing high bit depth y4m.

QSVEncC 2.65
Fixed a problem around the high bit depth pointed out.

[QSVEncC]
Fixed a picture breakdown when passing high bit depth y 4 m.
...I was completely forgotten y4m passing of high bit depth...

RieGo
11th June 2017, 14:51
It's because I avoid to reset user settings, in the video encoder menu go to: 'Edit Profiles' and choose 'Add' to only add the AV1 profile or Reset to reset all video encoder profiles.

Great! :thanks:

craigpro
11th June 2017, 15:20
From Rigaya with love... ;-)

NVEncC v3.09 - shortly


bother.. the display aspect ratio bug is not fixed :(

EDIT: it is, but it's not mentioned in the english changelog.

stax76
11th June 2017, 16:55
bother.. the display aspect ratio bug is not fixed :(

I already had a workaround added and then removed because it was fixed.

https://github.com/rigaya/NVEnc/issues/8

craigpro
12th June 2017, 06:11
I already had a workaround added and then removed because it was fixed.

https://github.com/rigaya/NVEnc/issues/8

awesome! thank you and thank you to Rigaya. I will wait for the next test build which has the updated files in it (I tried copying the 3.09 files over the 3.07 but it failed with this error message).

https://pastebin.com/z5WW0MtC

mcjordan
12th June 2017, 18:21
Same case. Confirmed.

stax76
12th June 2017, 18:22
3.10 fixes it.

mcjordan
12th June 2017, 18:41
Thank you, Frank.
That's on Rigaya's blog:

NVEnc 3.10
2017.06.12, 22:30
- Fix y4m delivery because it was broken even if it was 3.09.
- Fixed that sometimes error is returned under error code even if it ends normally.

craigpro
13th June 2017, 14:26
3.10 fixes it.

unfortunately not with the file set I was trying to compress :(

I think because the pixels are 920 x 716 (4:3 PAR), even though the DAR is set to 16:9 in the original file, the re-encoding is looking at the pixel resolution and setting the DAR from that.

I then did a test and disabled the Auto Aspect Ratio option in the Image / Options menu - but that also didn't work as the DAR was changed from 16:9 to 4:3

My third test was clicking the PAR in the menu and setting it to automatic 16:9 - unfortunately the output file DAR is still set to 4:3

Any other settings I should try? Thank you.

stax76
13th June 2017, 14:40
unfortunately not with the file set I was trying to compress :(

I think because the pixels are 920 x 716 (4:3 PAR), even though the DAR is set to 16:9 in the original file, the re-encoding is looking at the pixel resolution and setting the DAR from that.

I then did a test and disabled the Auto Aspect Ratio option in the Image / Options menu - but that also didn't work as the DAR was changed from 16:9 to 4:3

My third test was clicking the PAR in the menu and setting it to automatic 16:9 - unfortunately the output file DAR is still set to 4:3

Any other settings I should try? Thank you.

There is a issue with nvenc regardless of --sar or --dar is used, I've reported it to rigaya, it's probably a issue in the SDK, next staxrip build will have many new aspect ratio options including a option to set the dar with mkvmerge.

craigpro
13th June 2017, 15:31
There is a issue with nvenc regardless of --sar or --dar is used, I've reported it to rigaya, it's probably a issue in the SDK, next staxrip build will have many new aspect ratio options including a option to set the dar with mkvmerge.

thank you for your continued work and development on this program. when I can afford there will definately be beer money for you via paypal.

stax76
13th June 2017, 21:07
The build from today has some aspect ratio improvements that hopefully work better then the last build.

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

1.5.0.6 unstable test build



new: various new x265 options
new: various new aspect ratio features
update: x265 2.4+61
update: QSVEncC 2.66


1.5.0.4 unstable test build


new: Subtitle Edit added to Apps in main menu and to container options dialog
new: nvenc --weightp
tweak: in case the source image width/height isn't mod 4 staxrip writes crop to the crop section instead of the source section and adds a comment 'ensure mod 4'
tweak: main form layout and scaling improved and increased precession of several values
update: TIVTC 1.0.9
update: VapourSynth R38
update: x265 2.4+36
update: nvenc 3.10

Magik Mark
13th June 2017, 23:49
Stax,

What are these new x265 options?

stax76
14th June 2017, 00:13
Stax,

What are these new x265 options?

--refine-inter
--refine-intra
--refine-mv
--scale-factor

Sagaroth
14th June 2017, 07:04
Hi guys,

first I want to thank to Stax for this stunning app.

Second I've started to use the program this Monday, and I need "a help from a friend" :)

I'm not resizing or cropping, just re-encoding 1080p blu rays. I want to achieve the smallest possible size, but with good quality (let's say 90% from the original)

I'm using nvenc (if there is better hw encoder please suggest)
I'm asking people which already tested and knows the best possible settings to achieve this.
I've tested with HEVC VBRHQ, but I'm not happy with the results (In moving scenes allot of problems)

Then I've tested HEVC CQP 21;31;35 (what to raise/lower for better size/quality ratio) and the quality is much better, but still I think the detail is not good enough.

Also should I use aq, lookahead and what else should I configure, to achieve the desired results?

So please guys advice. (Maybe share some screens, settings or maybe a command line)
The most important for me is
Size/Quality ratio

Thank you and keep up the good work!

craigpro
14th June 2017, 16:08
The build from today has some aspect ratio improvements that hopefully work better then the last build.
1.5.0.6 unstable test build


test file output with the desired 16:9 DAR even though PAR is 4:3 - many thanks for that, I'll set a batch encode and check them in the morning.

thank you for your time and bug fixes.

craigpro
14th June 2017, 16:16
Second I've started to use the program this Monday, and I need "a help from a friend" :)

I'm not resizing or cropping, just re-encoding 1080p blu rays. I want to achieve the smallest possible size, but with good quality (let's say 90% from the original)

I'm using nvenc (if there is better hw encoder please suggest)


I use NVencc with mt GTX 1060 and I've been re-encoding my DVDs / Blurays to go on my NAS. A 720p source file of a 30 minute episode takes about 3 1/2 minutes to re-encode using the GTX 1060 and Staxrip.


I use IPB settings of CQP: I=21:P=23:B=25, quality preset, bitdepth 10, and my auto generated command line is:

--cqp 20:23:25 --codec h265 --preset quality --output-depth 10 --weightp --lookahead 16 --colormatrix auto --colorprim auto --transfer auto

I initially did a lot of frame by frame comparisons (using bit compare tools, not just using my eyes) and the above settings are acceptable FOR ME.

1.5GB episodes usually shrink down to about 700-800MB


One thing I don't do though is encode the audio channels - I just MUX the original audio - my ears are better at picking up compression than my eyes.

happy to accept criticism for my settings.

Natty
14th June 2017, 22:03
i have an urgent issue. 2 days back i was encoding a file and its audio was truehd+atmos 7.1 channel. mediainfo is here -> https://pastebin.com/umrfpaV6 . . . like always i set audio encoder to qaac and channels = original. but during encoding it converted the 7 gb truehd+atmos track to a flac file of only 2.5 gb 2 channel. and then to m4a audio of just 2 channels. i saw logs of my previous encodes and saw that my audios have been destroyed several times. for instance in one of the encodes dtshdma track of 4 gb was converted to 2 gb flac only... i solved my issue by selecting audio encoder to eac3to and channel = 7.1. it converted my 7gb truehd+atmos file to wav file of 10 gb. i used that wav file with qaac @ 7.1 @ tvbr 100 and it encoded it directly to m4a without converting it to flac. so finally i want to ask, can i set any option by which qaac first converts by audio to wav before converting it to m4a, or better yet convert the truehd+atmos track directly to m4a. thanks :)

stax76
14th June 2017, 22:12
What's the problem with having a intermediate FLAC file instead of a WAV file? There are issues with WAV like it can't hold much meta data and can only be 4GB large.

ENiGMA59
14th June 2017, 23:55
Hi Stax76

excuse me i search delete line , red surrounded

https://s18.postimg.org/9t1gghzll/delete_line.png

i use StaxRip x64 1.5.0.0 stable release ,

thanx in advance :thanks:

stax76
15th June 2017, 02:57
@ENiGMA59

Hi, I don't know about the second one, the first one is created with mkvmerge tags that you edit at: Container Options > Options > Tags

stax76
15th June 2017, 03:47
@Natty

In any case of a problem don't forget to post a full log file using pastebin (enable expiration after a month).

Natty
15th June 2017, 14:17
What's the problem with having a intermediate FLAC file instead of a WAV file? There are issues with WAV like it can't hold much meta data and can only be 4GB large.

problem was that flac was encoded at lower bitrate (smaller size) than the original file and i fear that it can lower my final m4a audio quality. and theres no problem in wav file, i got my wav file at 10 gb and the final m4a file sounded better. i will post logs of both cases where intermediate file was flac and where it was wav.

stax76
15th June 2017, 14:20
problem was that flac was encoded at lower bitrate (smaller size) than the original file and i fear that it can lower my final m4a audio quality. and theres no problem in wav file, i got my wav file at 10 gb and the final m4a file sounded better. i will post logs of both cases where intermediate file was flac and where it was wav.

FLAC is lossless so the quality is identical to the original, if needed I could add some option to decide if WAV or FLAC should be used for intermediate files and which app should be used to create the intermediate file, with my atmos test file ffmpeg isn't working correctly where eac3to encoded it fine.

ENiGMA59
15th June 2017, 15:08
Hi, I don't know about the second one, the first one is created with mkvmerge tags that you edit at: Container Options > Options > Tags

Thanx stax76 ,

i search also , the best template encoding TVRIP 720p

very big thanx stax76

ENiGMA59
15th June 2017, 15:29
@ENiGMA59

Hi, I don't know about the second one, the first one is created with mkvmerge tags that you edit at: Container Options > Options > Tags

merci stax76 ,

I search also the best template for TVRiP-720p :thanks:

in advance , upload .srip ^^ :p

stax76
15th June 2017, 15:32
Test Build

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://onedrive.live.com/redir?resid=604D4754F64B0ABC!4140&authkey=!ANUm9V3vTPmEFNI&ithint=folder%2c7z

1.5.0.7 unstable test build


new: Deblock VapourSynth plugin added: https://github.com/HomeOfVapourSynthEvolution/VapourSynth-Deblock/
new: basic new x264 GUI based on the same framework then all other codec GUIs, this will soon replace the old GUI
new: support for subtitle cutting
new: added setting to minimze processing window to task bar instead of the tray area
new: the options for --sar in the encoder options have now the same dropdown menu then the PAR menus in the main dialog
tweak: the option Fixed Bitrate was removed, if the bitrate or filesize is fixed depends now on what was edited last
update: masktools2 (AviSynth+) 2.2.10
update: mvtools (VapourSynth) 19

craigpro
15th June 2017, 15:49
Hi stax76 - just a feature idea - if there are subtitles in the folder where the source file is, could there be the option to MKVmerge them into the MKV output file?

I haven't tried encoding all of the problem 16:9 files as yet sorry, been a busy day.

stax76
15th June 2017, 16:02
Hi stax76 - just a feature idea - if there are subtitles in the folder where the source file is, could there be the option to MKVmerge them into the MKV output file?

StaxRip already does that for both audio and subtitle files but only if the filenames start the same, this should work:

24.mkv
24 English.srt
24 English.ac3

Yups
15th June 2017, 16:40
As a sidenote there is a new Media SDK for Intel available: https://software.intel.com/en-us/blogs/2017/06/09/whats-new-in-intel-media-sdk-2017-for-windows
https://software.intel.com/sites/default/files/mediasdk_release_notes.pdf

NikosD
15th June 2017, 16:57
It seems that new features are available to Skylake and Kabylake only.

Someone to inform rigaya in order to release a new QSVEnc version for the new MSDK.

stax76
15th June 2017, 17:01
Best address would probably be here: https://github.com/rigaya/QSVEnc/issues

NikosD
15th June 2017, 17:02
Or a direct email

ENiGMA59
15th June 2017, 17:19
Stax76 Private message , very important ;)

:thanks::thanks::thanks:

--------------------------------------

Hi Guy's , i search the best template for TVRiP-720p staxrip (.srip)

sample video :
http://www109.zippyshare.com/v/CBx3w6Xg/file.html
http://www109.zippyshare.com/v/DOTZdX4m/file.html

mediainfo : https://pastebin.com/2sb9aJEP

thanx in advance , upload .srip on @ zippy

stax76
15th June 2017, 18:36
@ENiGMA59

Except that truck drivers are usually not that attractive the file is nothing special. TS can processed in many different ways but many tools have issues with TS as it's very difficult to handle, besides the various free tools StaxRip includes there are two external tools known to handle TS very well, DGDecNV and TS-Doctor. Audio can just be muxed, you'll have to do some deinterlacing, there are some tutorials and a comparison tool (Tools > Advanced) which you can use to compare different filter and codec options, for questions about these options you can reach more members by creating a thread in the avisynth/vapoursynth and codec section in the forum.

Schattenspieler
16th June 2017, 07:53
…, you'll have to do some deinterlacing, …That shouldn't be the case, as 720p TV (DVB-C) material should be progressive (hence the p) and only 1080i (DVB-S) be interlaced. Can't remember ever having had a TV show in 720i. (Excluding scenes within a show, that should have been deinterlaced beforehand.) Though creating a new thread (or reviving an old one) is strongly recommended for any further questions related to that topic.

stax76
16th June 2017, 08:51
That shouldn't be the case, as 720p TV (DVB-C) material should be progressive (hence the p) and only 1080i (DVB-S) be interlaced. Can't remember ever having had a TV show in 720i. (Excluding scenes within a show, that should have been deinterlaced beforehand.) Though creating a new thread (or reviving an old one) is strongly recommended for any further questions related to that topic.

I'm not sure if the OP's question is problematic according to the forum rules since it's a scene release term and asks for best.

The specs of the sample are this:

https://pastebin.com/2sb9aJEP

Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate : 25.000 FPS
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : MBAFF
Scan type, store method : Separated fields
Scan order : Top Field First

Schattenspieler
16th June 2017, 12:01
Oh, well, I should have checked the samples, indeed! My bad. So it's most probably satellite footage @1080 in which case interlacing is to be expected (and obviously present), yes.

Khun_Doug
16th June 2017, 16:27
New Feature Suggestion ... When a 2 pass encode is being processed, have a mechanism to save the raw video from the first pass and then use that as the input to the second pass. This wold save CPU by not having to process the filter chain a second time.

stax76
16th June 2017, 17:16
New Feature Suggestion ... When a 2 pass encode is being processed, have a mechanism to save the raw video from the first pass and then use that as the input to the second pass. This wold save CPU by not having to process the filter chain a second time.

I'm not sure it's easy to do, are people already doing this with another app or manually?

sneaker_ger
16th June 2017, 17:25
Usually you do 3 passes then.
a: script to lossless or near-lossless intermediate
b: first pass read from a
c: second pass read from a

Natty
16th June 2017, 23:50
FLAC is lossless so the quality is identical to the original, if needed I could add some option to decide if WAV or FLAC should be used for intermediate files and which app should be used to create the intermediate file, with my atmos test file ffmpeg isn't working correctly where eac3to encoded it fine.

heres a short 26 sec sample of 7.1 TrueHD+Atmos Track for u so that u can test for yourself http://tinyurl.com/thdatmos
please conduct test in following conditions, it will take only 5 mins max in total.

1) where audio encoder is qaac, codec is aac and channels = original (FLAC Intermediate)

2) where audio encoder is eac3to, codec is aac and channels = original

3) where audio encoder is eac3to, codec is aac and channels = 7.1. (WAV intermediate)

4) where audio encoder is qaac, codec is aac, channels = 7.1 (use WAV intermediate file created in step (3) as source in this case, not the original "TrueHD+Atmos TEST.mka".

5) where audio encoder is qaac, codec is aac, channels = 7.1

p.s i only want to use qaac and i would want intermediate file as WAV. and also u would notice that channels are incorrectly encoded as 2 whereas the source is 7.1. :confused: :helpful:

stax76
17th June 2017, 11:03
Usually you do 3 passes then.
a: script to lossless or near-lossless intermediate
b: first pass read from a
c: second pass read from a

I'll take a look how this thing works in megui.

@Natty

Is there a practical reason you prefer WAV over FLAC? As far as I know lossless means absolutely bit-identical lossless, thing with WAV is it appears to be broken/messy to me.

The WAV format is limited to files that are less than 4 GiB, because of its use of a 32-bit unsigned integer to record the file size header (some programs limit the file size to 2 GB)[citation needed]. Although this is equivalent to about 6.8 hours of CD-quality audio (44.1 kHz, 16-bit stereo), it is sometimes necessary to exceed this limit, especially when greater sampling rates, bit resolutions or channel count are required. The W64 format was therefore created for use in Sound Forge. Its 64-bit header allows for much longer recording times. The RF64 format specified by the European Broadcasting Union has also been created to solve this problem.

FLAC (/ˈflæk/; Free Lossless Audio Codec) is an audio coding format for lossless compression of digital audio, and is also the name of the reference codec implementation. Digital audio compressed by FLAC's algorithm can typically be reduced to 50–60% of its original size[citation needed] and decompress to an identical copy of the original audio data.

Khun_Doug
18th June 2017, 17:15
Usually you do 3 passes then.
a: script to lossless or near-lossless intermediate
b: first pass read from a
c: second pass read from a

That's something I have done in the past. I confess I do not know how to do part 1, create the lossless output from the filters, using StaxRip. I have used another tool. My thought was to combine steps 1 and 2. Since the filters are already completed and the data has been processed pass 1, just save the data in a temporary lossless file. Pass 2 will read that temporary loessless file. After pass 2 then just delete the temporary lossless file.

It was just a thought. If someone can explain how to create the lossless part using StaxRip I would appreciate it. I am finding 2 pass encoding to be useful.

stax76
18th June 2017, 18:23
@Natty

I've made quite a few changes in the audio department and there will be more changes.

If something goes wrong you can load the project from: File > Recent and run the job a second time. If you use 'Just Mux' as video encoder it will search existing encoder output from a previous runs, only if it don't find any it will mux the source video. I plan to add a dialog that will ask what should be done if the output files already exists.

https://github.com/stax76/staxrip/blob/master/md/test-build.md