RipBot264 v1.18.3 - Simple and easy to use GUI -> IPOD . PSP . CONSOLES . BLURAY

[RCLapCar]

Wanted to report a bug in the latest version.

On the stream selection screen when I choose which audio tracks I want to use from the bluray playlist I want to convert I noticed the radio buttons for the audio three tracks (the ones that let you choose to demux, wave, flac or core) are interconnected. So if you pick 3 different audio streams you can only select the option on one of them and can't choose a different one for each audio track as the selection always moves to the last one you picked even if it's on a different audio track.

[guest]

Wanted to report a bug in the latest version.

On the stream selection screen when I choose which audio tracks I want to use from the bluray playlist I want to convert I noticed the radio buttons for the audio three tracks (the ones that let you choose to demux, wave, flac or core) are interconnected. So if you pick 3 different audio streams you can only select the option on one of them and can't choose a different one for each audio track as the selection always moves to the last one you picked even if it's on a different audio track.

Was it an issue with the previous build ??

[rp1989]

So a quick test comparing fps on 4k stuff using either the affinity mask or the avisynth-prefetch-threads setting them to 12 on my 16 core ryzens (1-3950x,3-5950x,1-7950x). About halfway thru a 4k movie once everything settles out, the total fps showing on the distributed encoding window are very similar between them. Within a couple fps in the 70-72 fps range. If these numbers hold up for 1080p stuff, this will help me out as I won't have to have 2 separate command batch files for the encoding servers and switch between them when doing 4k and anything else. I can just start everything with the prefetch numbers and be done with it. (720 and 1080 stuff runs much faster without the affinity mask set to 12 cores)

I encode everything to 10bit HEVC using default encoder settings with a CRF of 18

I have now switched over to using 3 SMDegrain scripts. In the past I was using just mdegrain3 with strengths of 200 for clean sources, 300 for light grain sources, and 400 for grainy sources. I did some testing and specifically comparing final file sizes, I now use the following SMDegrain scripts:
Clean sources - video=SMDegrain(video,tr=3,thSAD=300,thSADC=150,contrasharp=true,prefilter=1,refinemotion=true)
Light grain - video=SMDegrain(video,tr=4,thSAD=400,thSADC=200,contrasharp=true,prefilter=1,refinemotion=true)
Grainy - video=SMDegrain(video,tr=6,thSAD=600,thSADC=300,contrasharp=true,prefilter=2,refinemotion=true)

As I said, the end files sizes are very close to the corresponding mdegrain3 settings I had been using.

The biggest difference is in the speed increase using SMDegrain. I am seeing about a 40 - 60 % increase in fps using SMDegrain over mdegrain using comparable settings. 4k Forrest Gump with mdegrain was around 49-50 fps and with SMDegrain is 73-75 fps.

I did come across 1 movie that just would not run using SMDegrain, but did run using mdegrain, not sure what was up with that, so mdegrain is not completely dead

Hi, after some awesome guidance from @TDS I have switched over to using SMDegrain using PD build 5.0 (Thank you @Pauly Dunne for all your hard work on this and sharing with us). I haven’t had any other issues encoded over 15 films now but I have 3 movies I just cannot get SMDegrain to work. It seems to fail on the ‘Gathering Information’ stage and doesn’t create the ‘Info.txt’ file so the encoding client will not start. As soon as I switch over to Mdegrain, all 3 movies encode without any issues. Was there any solutions anyone found to this? PS i also tried a different source of one of the movies but still fails.

Movies SMDegrain fails on, source FGT:
Bad Boys 2 (2003)
Fantastic Four (2015)
Logan (2017)

[guest]

Hi, after some awesome guidance from @TDS I have switched over to using SMDegrain using PD build 5.0 (Thank you @Pauly Dunne for all your hard work on this and sharing with us). I haven’t had any other issues encoded over 15 films now but I have 3 movies I just cannot get SMDegrain to work. It seems to fail on the ‘Gathering Information’ stage and doesn’t create the ‘Info.txt’ file so the encoding client will not start. As soon as I switch over to Mdegrain, all 3 movies encode without any issues. Was there any solutions anyone found to this? PS i also tried a different source of one of the movies but still fails.

Movies SMDegrain fails on, source FGT:
Bad Boys 2 (2003)
Fantastic Four (2015)
Logan (2017)

Nice of you to say :)

Yeah, not too sure what's going on there, I haven't had that issue (but then I probably haven't got those video's)

All I can suggest is run it thru MKVToolNix, strip out everything but the video track, and see what RB does with it.

I quite often I only run video thru RB, and mux everything back, afterwards.

If that works, try it with the audio & sub's (if wanted), and try again.

Good luck.

[rp1989]

Nice of you to say :)

Yeah, not too sure what's going on there, I haven't had that issue (but then I probably haven't got those video's)

All I can suggest is run it thru MKVToolNix, strip out everything but the video track, and see what RB does with it.

I quite often I only run video thru RB, and mux everything back, afterwards.

If that works, try it with the audio & sub's (if wanted), and try again.

Good luck.

Yep tried strip out with just video only but no luck.

[rp1989]

Hi, after some awesome guidance from @TDS I have switched over to using SMDegrain using PD build 5.0 (Thank you @Pauly Dunne for all your hard work on this and sharing with us). I haven’t had any other issues encoded over 15 films now but I have 3 movies I just cannot get SMDegrain to work. It seems to fail on the ‘Gathering Information’ stage and doesn’t create the ‘Info.txt’ file so the encoding client will not start. As soon as I switch over to Mdegrain, all 3 movies encode without any issues. Was there any solutions anyone found to this? PS i also tried a different source of one of the movies but still fails.

Movies SMDegrain fails on, source FGT:
Bad Boys 2 (2003)
Fantastic Four (2015)
Logan (2017)

I seem to have cracked it! I had Autocrop set for all three files which was causing the failure. After turning this off all seems to be working fine with SMDegrain and the files containing video, audio and subs as I normally have.

[guest]

I seem to have cracked it! I had Autocrop set for all three files which was causing the failure. After turning this off all seems to be working fine with SMDegrain and the files containing video, audio and subs as I normally have.

Well done...did those movies need to be Autocropped ??

I haven't had any issues, tho.

[RCLapCar]

Was it an issue with the previous build ??

No. I usually have a couple months between uses of Ripbot and the last time I used it was probably around January/February. I was always able to select the options for each audio track independently. With the latest build you can only select an option for one audio track and the options for the other audio tracks get deselected.

[rlev11]

I've had some issues like that using smdegrain where it bombs out before starting the encode with the missing info.txt error. I usually always just do an auto-crop on everything. Don't have the exact cause but it seems to be something with the aspect ratio after the auto-crop takes place. Sometimes if the auto-crop brings up an odd ball aspect ratio, say like 2.395:1 instead of a normal 2.4:1 it happens. not all the time, but occasionally. Most of the time I can fix it with resizing to the closes standard aspect ratio which really doesn't effect the end result.

Or if it is something really not close to a standard after the autocrop that gives me an aspect ratio that when divided gives me a partial pixel height with a decimal point. If i custom resize it and round up or down on the height to a full number, I have had that work then as well. I have only had maybe a couple that just would not run with smdegrain, so i just ran them through mdegrain and called it a day.

[guest]

No. I usually have a couple months between uses of Ripbot and the last time I used it was probably around January/February. I was always able to select the options for each audio track independently. With the latest build you can only select an option for one audio track and the options for the other audio tracks get deselected.

That's interesting, so back then it would have been v1.26.3, and just recently there have been a few updates, some major, some minor and now it's v1.27.0.

Can you check what version you currently have ??

And I am assuming that you have autoupdate enabled...

Do you have access to the previous version, so you get this function back ??

I'd say that this is possibly something Atak will have to address.

[guest]

I've had some issues like that using smdegrain where it bombs out before starting the encode with the missing info.txt error. I usually always just do an auto-crop on everything. Don't have the exact cause but it seems to be something with the aspect ratio after the auto-crop takes place. Sometimes if the auto-crop brings up an odd ball aspect ratio, say like 2.395:1 instead of a normal 2.4:1 it happens. not all the time, but occasionally. Most of the time I can fix it with resizing to the closes standard aspect ratio which really doesn't effect the end result.

Or if it is something really not close to a standard after the autocrop that gives me an aspect ratio that when divided gives me a partial pixel height with a decimal point. If i custom resize it and round up or down on the height to a full number, I have had that work then as well. I have only had maybe a couple that just would not run with smdegrain, so i just ran them through mdegrain and called it a day.

Hi rlev11,

Welcome back, it's been just over 3 months...

Well, this is very interesting....

I also get that info.txt thing, too, occasionaly.

I tried a couple of things (just fiddle), I removed the Autocrop folder out of RipBot, and it still auto detected the size.

Removed AVSresize, same as above.

Removed Detect Borders, and when choosing the auto crop, instead of it "thinking about it", it just instantly showed the call in the video script window...#Crop
video=Crop(video,0,0,-0,-0)

Admittedly this is a bogus test, as it wasn't using SMDegrain, and the video didn't require auto resizing.

Just sayin' that those functions seem to be involved (or not) in the auto crop process, somehow.

[rp1989]

Does anyone have any ideas on how to deal with encoding 4K Dolby Vision + HDR10 hybrid sources please? I tried the below HEVC profile but it only outputs HDR10.

--level 6.2 --profile main10 --hdr10 --dolby-vision-profile 8.1 --hdr10-opt --output-depth 10 --ctu 64 --merange 57 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000

Tried the below too and again it just outputs HDR10 only.

--level 6.2 --profile main10 --output-depth 10 --ctu 64 --merange 57 --high-tier --vbv-bufsize 800000 --vbv-maxrate 800000

[guest]

Does anyone have any ideas on how to deal with encoding 4K Dolby Vision + HDR10 hybrid sources please? I tried the below HEVC profile but it only outputs HDR10.

--level 6.2 --profile main10 --hdr10 --dolby-vision-profile 8.1 --hdr10-opt --output-depth 10 --ctu 64 --merange 57 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000

Tried the below too and again it just outputs HDR10 only.

--level 6.2 --profile main10 --output-depth 10 --ctu 64 --merange 57 --high-tier --vbv-bufsize 800000 --vbv-maxrate 800000

Yeah, I have only just started experimenting with "special" x265 profile commands, and it's amazing what you can do with them.

You might need a profile a bit more like:-

--level 6.2 --profile main10 --hdr10 --hdr-opt --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc
--max-cll "4000,100" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(40000000,10)"
or
--level 6.2 --profile main10 --hdr10 --hdr-opt --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --chromaloc 2 --colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc
--max-cll "1000,400" --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,50)"

This is a good place to start:-
https://x265.readthedocs.io/en/master/cli.html

--max-cll <string>
Maximum content light level (MaxCLL) and maximum frame average light level (MaxFALL) as required by the Consumer Electronics Association 861.3 specification.

Specified as a string which is parsed when the stream header SEI are emitted. The string format is “%hu,%hu” where %hu are unsigned 16bit integers.
The first value is the max content light level (or 0 if no maximum is indicated), the second value is the maximum picture average light level (or 0). Applicable for HDR content.

Example for MaxCLL=1000 candela per square meter, MaxFALL=400 candela per square meter:

–max-cll “1000,400”
Note that this string value will need to be escaped or quoted to protect against shell expansion on many platforms. No default.

--master-display <string>
SMPTE ST 2086 mastering display color volume SEI info, specified as a string which is parsed when the stream header SEI are emitted. The string format is “G(%hu,%hu)B(%hu,%hu)R(%hu,%hu)WP(%hu,%hu)L(%u,%u)”
where %hu are unsigned 16bit integers and %u are unsigned 32bit integers. The SEI includes X,Y display primaries for RGB channels and white point (WP) in units of 0.00002 and max,min luminance (L) values in units of 0.0001 candela per meter square. Applicable for HDR content.

Example for a P3D65 1000-nits monitor, where G(x=0.265, y=0.690), B(x=0.150, y=0.060), R(x=0.680, y=0.320), WP(x=0.3127, y=0.3290), L(max=1000, min=0.0001):

G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)
Note that this string value will need to be escaped or quoted to protect against shell expansion on many platforms. No default.

--dolby-vision-profile <integer|float>
Generate bitstreams confirming to the specified Dolby Vision profile, note that 0x7C01 makes RPU appear to be an unspecified NAL type in HEVC stream. If BL is backward compatible,
Dolby Vision single layer VES will be equivalent to a backward compatible BL VES on legacy device as RPU will be ignored.

The value is specified as a float or as an integer with the profile times 10, for example profile 5 is specified as “5” or “5.0” or “50”.

Currently only profile 5, profile 8.1 and profile 8.2 enabled, Default 0 (disabled)

--dolby-vision-rpu <filename>
File containing Dolby Vision RPU metadata. If given, x265’s Dolby Vision metadata parser will fill the RPU field of input pictures with the metadata read from the file. The library will interleave access units with RPUs in the bitstream. Default NULL (disabled).

CLI ONLY

You might need to use a "tool" like this to extract the meta data...

https://forum.doom9.org/showthread.php?t=183479

You might be able to check the metadata info of the original file with "MediaInfo", and match it with the x265 profile....

Example:-

GoT HDR10

--colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(8500,39850)B(6550,2300)R(35400,14600)WP(15635,16450)L(10000000,20)


Old Guard DV

--colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "738,287

Just thinking out loud.

===========================================

I also know that "Ryushin" has done a bit with this, it would be nice if he joined in ???

Here's what he does to get the RPU.bin

https://forum.doom9.org/showthread.php?p=1977295#post1977295

===========================================

UPDATE:-

Here's some more info, after extracting the metadata / RFU from a DV movie (using the above "tool" DDVT)...

(I have to say it took me a little while to figure out how to use DDVT, being sort of a CLI app)

Basic profile:-

--level 6.2 --profile main10 --hdr10 --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --dolby-vision-rpu "x:\RPU.bin"
or
--level 6.2 --profile main10 --hdr10 --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --dolby-vision-profile "8.1" --dolby-vision-rpu "x:\RPU.bin"

x265 info (from Encoder Server window):-

--colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "738,287" --crf 16 --fps 24 --min-keyint 24 --keyint 240 --frames 2880 --sar 1:1 --level 6.2 --profile main10
--hdr10 --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --dolby-vision-rpu "x:\RPU.bin
or
--colorprim bt2020 --transfer smpte2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "738,287" --crf 16 --fps 24 --min-keyint 24 --keyint 240 --frames 2880 --sar 1:1 --level 6.2 --profile main10
--hdr10 --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --dolby-vision-profile "8.1" --dolby-vision-rpu "x:\RPU.bin

[rp1989]

Thanks for the detailed response @TDS. I take it there is no way RB can passthrough the DV metadata to the output automatically? For now I have successfully extracted and remuxed the DV RPU.bin using DDVT using the guidance from Ryushin.

[RCLapCar]

That's interesting, so back then it would have been v1.26.3, and just recently there have been a few updates, some major, some minor and now it's v1.27.0.

Can you check what version you currently have ??

And I am assuming that you have autoupdate enabled...

Do you have access to the previous version, so you get this function back ??

I'd say that this is possibly something Atak will have to address.

So I just got another update (still showing 1.27.0) and the issue appears to be fixed now. So all good.

[guest]

Thanks for the detailed response @TDS. I take it there is no way RB can passthrough the DV metadata to the output automatically? For now I have successfully extracted and remuxed the DV RPU.bin using DDVT using the guidance from Ryushin.

Well, now there are at least 2 ways to do this, then.

I have no idea how RB could passthru the DV metadata, that's something Atak would have to comment on.

However, if you're going to the "trouble" of extracting the rpu.bin with DDVT, it is then VERY easy to add that command to your x265 profile to have x265 & RB retain the DV metadata, which could be a "passthru" of sorts.

It's one less step than having to inject it after the encode....

[guest]

So I just got another update (still showing 1.27.0) and the issue appears to be fixed now. So all good.

I had to check after reading this, and sure enough...

So it's core, mpc & cutsub, no changelog :(

:thanks:

UPDATE:-

So you know I had to figure out what had changed here, and it's mixed reactions. :confused:

On one hand, Atak has changed how the Segments function works, in regards to Audio re-encoding. ;)

It no longer seems to prompt to re-encode, so I loaded a short sample with a TrueHD audio track, and I run it thru using X.X Copy, and after the encode its now FLAC. :scared:

Another strange behaviour was, it did NOT initiate DE, it was just a "simple/single" encode. :( :sly:

So then I tried a re-encode to AAC 7.1, and again, no DE, but it was changed to AAC 7.1. :rolleyes:

There's nothing on the other hand :D

[guest]

A 5 minute test of a DV movie:-

Original info:-

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L5@Main
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 5 min 0 s
Bit rate : 16.3 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0 (Type 2)
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.082
Stream size : 585 MiB (96%)
Language : English
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 738 cd/m2
Maximum Frame-Average Light Level : 287 cd/m2



After going thru RB with .rpu.bin being injected with x265:-
Using this x265 Profile:-
--level 6.2 --profile main10 --hdr10 --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000 --dolby-vision-profile "8.1" --dolby-vision-rpu "x:\RPU.bin"

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.2@High
HDR format : Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 5 min 0 s
Bit rate : 26.8 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.135
Stream size : 958 MiB (97%)
Title : The Old Guard (2020)
Writing library : x265 3.5+103-695dcf9be:[Windows][GCC 13.1.0][64 bit] 10bit
Encoding settings : TL:DR
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 738 cd/m2
Maximum Frame-Average Light Level : 287 cd/m2


After going thru RB with "standard" x265 settings:-
Using this x265 Profile:-
--level 6.2 --profile main10 --hdr10 --hdr10-opt --output-depth 10 --ctu 64 --high-tier --repeat-headers --vbv-bufsize 800000 --vbv-maxrate 800000

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Format profile : Main 10@L6.2@High
HDR format : SMPTE ST 2086, HDR10 compatible
Codec ID : V_MPEGH/ISO/HEVC
Duration : 5 min 0 s
Bit rate : 17.9 Mb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 10 bits
Bits/(Pixel*Frame) : 0.090
Stream size : 641 MiB (96%)
Title : The Old Guard (2020)
Writing library : x265 3.5+103-695dcf9be:[Windows][GCC 13.1.0][64 bit] 10bit
Encoding settings : TL:DR
Default : Yes
Forced : No
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : PQ
Matrix coefficients : BT.2020 non-constant
Mastering display color primaries : Display P3
Mastering display luminance : min: 0.0001 cd/m2, max: 1000 cd/m2
Maximum Content Light Level : 738 cd/m2
Maximum Frame-Average Light Level : 287 cd/m2

[rp1989]

Well, now there are at least 2 ways to do this, then.

I have no idea how RB could passthru the DV metadata, that's something Atak would have to comment on.

However, if you're going to the "trouble" of extracting the rpu.bin with DDVT, it is then VERY easy to add that command to your x265 profile to have x265 & RB retain the DV metadata, which could be a "passthru" of sorts.

It's one less step than having to inject it after the encode....

Yep makes sense, I will add the rpu.bin process to the x265 profile. Would just be great if RB could automate the process of extracting the rpu as part of the job preparation. Will wait and see if Atak has any comments on this.

[guest]

I loaded a 4K clip into RB, thought I'd check the autocrop, and it changed the top & bottom by 276 each, so I ended up with a 3840 x 1600. (in the video script)

Without the autocrop, it was 3840 x 2160.

Would setting it to 3840 x 2160 in the "Resize" override the "Crop" setting ?

So I processed both, and MediaInfo showed both of them as 3840 x 2160, and they looked exactly the same on the TV.

[Atak_Snajpera]

I had to check after reading this, and sure enough...

So it's core, mpc & cutsub, no changelog :(

:thanks:

UPDATE:-

So you know I had to figure out what had changed here, and it's mixed reactions. :confused:

On one hand, Atak has changed how the Segments function works, in regards to Audio re-encoding. ;)

It no longer seems to prompt to re-encode, so I loaded a short sample with a TrueHD audio track, and I run it thru using X.X Copy, and after the encode its now FLAC. :scared:

Another strange behaviour was, it did NOT initiate DE, it was just a "simple/single" encode. :( :sly:

So then I tried a re-encode to AAC 7.1, and again, no DE, but it was changed to AAC 7.1. :rolleyes:

There's nothing on the other hand :D

Let me know when ffmpeg has non-experimental 8 channel truehd encoder... the same story with DTS-MA.

DE won't be activated if video file is too short (for example less than 2 minutes)

[guest]

Let me know when ffmpeg has non-experimental 8 channel truehd encoder... the same story with DTS-MA.

DE won't be activated if video file is too short (for example less than 2 minutes)

Not sure if that's sarcasm...

Thing is, I don't/can't use TrueHD, or 7.1 FLAC, so I guess I'll be sticking with 7.1 AAC, seeing as 7.1 AC3 seems to be out of the question.

I used to convert THD to DTSHD using a few apps, turned out to be a time consuming process, for no real benefit.

I think you might have hit the nail on the head with the DE situation, I can't remember how long the test clips were, I generally do 5 minutes long, I will check, tomorrow.

UPDATE:-

Yes, what I'd done with DE was I DID load a 5 minute test clip, but then I cut it down too far with the Segments settings, it was only 50 seconds :(

[Ryushin]

Actually, any good video playback device will convert FLAC to LPCM. I've been using FLAC for any LPCM audio streams. Works wonderfully. Though .mov containers can't use FLAC as I've found out working with Topaz Video AI. So I need to mux FLAC in after Topaz is done with it.

So yea, Atak using FLAC is good idea. Though I think FFMPEG can encode DTS 5.1. So that could be a nice option. TrueHD to FLAC is a also good idea, since both of those are compressed lossless codecs. Though any good playback device will convert TrueHD to LPCM.

Atak, a request please to add FLAC as an encoding option in the GUI. FLAC is only available when initially demuxing from a disc source.

I too would like Atak to add Dolby Vision as demuxing option. There are a few steps involved and it is scriptable, but the work involved might not be worth it to Atak until it becomes more prevalent. About half of 4K movies I buy now are Dolby Vision. Interesting that DDVT is using Atak's cropping code.

[slalom]

Thing is, I don't/can't use TrueHD, or 7.1 FLAC, so I guess I'll be sticking with 7.1 AAC, seeing as 7.1 AC3 seems to be out of the question.
I think that's called EAC3 7.1

[guest]

I think that's called EAC3 7.1

No, I mean't ac3 7.1, e-ac3 is a different "animal"

[slalom]

ac3 7.1 doesn't exist

[guest]

Atak,

I have trying in vain to encode DV movies with RB, using custom x265 profiles, but they are just not compatible with my LG TV.

Please refer to some of my recent posts on this subject.

From what I've discovered, it seems that LG's & some Samsung TV's will not display DV that is in .mkv format, it will switch to HDR instead.

I downloaded a couple of LG DV test samples, which are in .ts format, and they play & display the Dolby Vision logo on the screen (just like HDR does)

Now, RB ONLY output's x265 in .mkv.....

Could you please consider adding .mp4 & maybe .ts, or .m2ts as output file options for x265, for those of us who probably need it for their viewing pleasure.

UPDATED with NEW INFO :)...

I have persisted with this, and very early this morning I had a much needed Win...

So again, I would like to repeat my request for more x265 output file options for these DV files.

So if you will, Mr Snajpera, could you PLEASE add the ability to output x265 files as .mp4, "mp4box" is already part of RB, and is available when using x264,

and more importantly, as .m2ts for x265 DV files, "tsmuxer" is also a part of RB, and is also available when using x264 (as AVCHD), but with x265 would be better to just output directly as .m2ts !!

[Ryushin]

Atak,

I have trying in vain to encode DV movies with RB, using custom x265 profiles, but they are just not compatible with my LG TV.

Please refer to some of my recent posts on this subject.

From what I've discovered, it seems that LG's & some Samsung TV's will not display DV that is in .mkv format, it will switch to HDR instead.

I downloaded a couple of LG DV test samples, which are in .ts format, and they play & display the Dolby Vision logo on the screen (just like HDR does)

Now, RB ONLY output's x265 in .mkv.....

Could you please consider adding .mp4 & maybe .ts, or .m2ts as output file options for x265, for those of us who probably need it for their viewing pleasure.

I'm probably going to open a can of worms, but here goes. I don't think Atak needs to support .ts files. He supports mkv which is the preferred container format by far and RB not support Dolby Vision yet. Just because your TV is does not understand Dolby Vision in a MKV container should not mean Atak needs to support a different hardly used container. My Sony Z9D also does not support DV in any kind file, only through a device that passes the Dolby Vision signal to it, such as a UHD disc player or nVidia Shield. TVs age and technology marches on. At some point, your TV needs to become a monitor as it's smart features age and is not compatible with the newer technology.

So do yourself a favor and get an nVidia shield and run Kodi, Plex, Emby, Jellyfin, or even VLC. The nVidia shield is one of the best smart video and audio platforms around. It's one very few that will pass through TrueHD Dolby Atmos and DTS:X.

[guest]

I'm probably going to open a can of worms, but here goes. I don't think Atak needs to support .ts files. He supports mkv which is the preferred container format by far and RB not support Dolby Vision yet. Just because your TV is does not understand Dolby Vision in a MKV container should not mean Atak needs to support a different hardly used container. My Sony Z9D also does not support DV in any kind file, only through a device that passes the Dolby Vision signal to it, such as a UHD disc player or nVidia Shield. TVs age and technology marches on. At some point, your TV needs to become a monitor as it's smart features age and is not compatible with the newer technology.

So do yourself a favor and get an nVidia shield and run Kodi, Plex, Emby, Jellyfin, or even VLC. The nVidia shield is one of the best smart video and audio platforms around. It's one very few that will pass through TrueHD Dolby Atmos and DTS:X.

That's a can of worms alright :)

Where there's a will, there's a way.

TBH, I doubt that Atak will go down the DV path either...the question has been asked many times, and still nothing, like SMDegrain.

I don't think my TV is too old yet...

I really can't utilise 7.1 audio anyway, due to my home theater setup.

You won't convince me to do all that streaming stuff, either.

If it doesn't work off a USB stick, I'm not interested.

====================================

I just checked how much a nVidia Shield is, the "good" one is around A$350....there's NO WAY.

I've tried Kodi, and didn't like that...so please stop suggesting these "streaming" options, it falls on deaf ears.

I haven't got a server system running 24/7....just not worth the expense, electricity cost's too much as it is, to me that's just such a waste of my money :(

All sorted, without the need of any streaming device. https://www.cosgan.de/images/midi/froehlich/a070.gif

[Boulder]

I've tried Kodi, and didn't like that...so please stop suggesting these "streaming" options, it falls on deaf ears.

Kodi is not a streaming solution. It plays back the file as it is without transcoding.

For anyone interested in playing with DV stuff, see https://discourse.coreelec.org/t/21-0-omega-alpha1-may-1st-2023/21471. There are now a couple of non-Shield devices that support Dolby Vision with the new alpha. I'm still running my trusty old Odroid N2 but once it passes on, I'll definitely invest in a DV-capable box.

[chainring]

FWIW, Kodi 21 will have native support for DV in MKV.

And, as Boulder wrote, Kodi isn't a streaming solution. There's add-ons to make it such, but those are not supported by the Kodi team. Kodi is a local file player, first and foremost. Whether that file is local to a NAS, a PC/Mac or a USB connected hard drive, that's the extent of Kodi's streaming.

[-QfG-]

The simpliest way to stream DV Files is a Nvidea Shield Pro 2019 + PLEX.

[userx]

Hi
After last update i'm not able to apply new jobs to the queue.
The Done-button is not clickable.
Can anybody help?


@ReinerSchweinlin
Thanks for the hint.
I have to open the avisynth window, click into any setting box e.g. Resize -> OFF to get the OK of avisynth window clickable, exit this window by OK. Afterwards the Done-Button is clickable again.

Edit:
When changing the output filename / path AFTER this workaround DONE gets disabled again.

Today i noticed an UI update (chapters, subtitles,..) but this long running bug still drives me crazy.
I just want to ask kindly if this could be fixed anytime in the future or am I the only one with this issue?

[guest]

Today i noticed an UI update (chapters, subtitles,..) but this long running bug still drives me crazy.
I just want to ask kindly if this could be fixed anytime in the future or am I the only one with this issue?

So does this happen with every Job ??

You asked about this quite some time ago, and Reiner suggested a work around

https://forum.doom9.org/showthread.php?p=1953258#post1953258

I too, have this happen randomly, and I do what Reiner suggested...I think it's just combo of the video file, or the script, or, who knows.

Might even be a free space thing, Temp folder....

Curious you mentioned a new update, and sure enough there is one.

[guest]

Can't really make out why these functions have been added.

A bit random, I haven't read anywhere where this has been suggested or asked for, when I think more "Container" options should be added for x265 output files...oh well.

I can sort of understand the "Chapters" option, but what's the "Attachments" all about ??

https://i.imgur.com/abnHJvp.jpg

[Atak_Snajpera]

I asked for that...

[guest]

I asked for that...

Well, so now I know why I didn't see any posts about asking for this :).

So in the "Attachments", is where you can now add "Covers", but what about the "Fonts", where & what does that change ??

[Atak_Snajpera]

Well, so now I know why I didn't see any posts about asking for this :)

You probably also didn't see any posts asking for Distributed Encoding in the past...

So in the "Attachments", is where you can now add "Covers", but what about the "Fonts", where & what does that change ??

Here is good example containing three custom fonts which are used by included subtitles (.ass)

https://www.mediafire.com/file/3cjutavpdqdi02w/%255BSS-Eclipse%255D_Kanon_-_Promo_%2528h264%2529_%255BE3CE768D%255D_%25281%2529.mkv/file

[guest]

You probably also didn't see any posts asking for Distributed Encoding in the past...

You're right, but that's a long time ago, and the best thing that you could have done...no one else has come close, or even tried....

So the Fonts are for subtitles, then ?? Just add fonts to the new Fonts folder ??

[Atak_Snajpera]

No! That folder contains font for RipBot264 application. It has nothing to do with subtitles.

Now you can create subtitles using your own fonts.
You first must prepare proper .ass/.ssa subtitle and then you add proper font file (*.ttf) as attachments to container

In that example it looks like this

[Script Info]
; Script generated by Aegisub v1.10
; http://www.aegisub.net
Title: Default-anamorphic Aegisub file
ScriptType: v4.00+
PlayResX: 640
PlayResY: 480
Audio File: ?video
Video File: Kanon-Promo4-TSraw-xvid-nobframes.avi
Video Aspect Ratio: 0
Video Zoom: 6
Video Position: 4179

[V4+ Styles]
Format: Name, Fontname, Fontsize, PrimaryColour, SecondaryColour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding
Style: Note,AvantGarde Bk BT Eclipse,22,&H00FFFFFF,&H0000FFFF,&H00393E3B,&H80393E3B,0,0,0,0,100,115,0,0,1,1.6,0,8,10,10,10,0
Style: Default-anamorphic,Quadrat-Regular Eclipse,29,&H00FFFFFF,&H00FFFFFF,&H00A0675F,&H80000000,0,0,0,0,100,121,0,0,1,1.5,2,2,10,10,10,0
Style: Default-alt-anamorphic,Quadrat-Regular Eclipse,29,&H00FFFFFF,&H00FFFFFF,&H00708E47,&H80000000,0,0,0,0,100,121,0,0,1,1.5,2,2,10,10,10,0
Style: Default,Arial,20,&H00FFFFFF,&H0000FFFF,&H00000000,&H00000000,0,0,0,0,100,100,0,0,1,2,2,2,10,10,10,0
Style: Rap,Continuum Medium,27,&H00927667,&H0000FFFF,&H00F7E8E0,&H00000000,0,0,0,0,100,120,0,0,1,2,0,9,10,10,5,0

https://i.postimg.cc/4xmV0jr3/Capture.png

[guest]

No! That folder contains font for RipBot264 application. It has nothing to do with subtitles.

Now you can create subtitles using your own fonts.
You first must prepare proper .ass/.ssa subtitle and then you add proper font file (*.ttf) as attachments to container


I always use .srt subs, the LG TV does not support pgs types.

I have added some different .ttf's to Fonts, and I don't understand what it's suppose to do....

[Atak_Snajpera]

Nevermind. Others who create text based subtitles .ass/.ssa (so called FanSub groups) with custom fonts will understand this feature.

[guest]

Nevermind. Others who create text based subtitles .ass/.ssa (so called FanSub groups) with custom fonts will understand this feature.

Ok, well thanks for the explanation, and now everybody else knows what it's for.

[guest]

So dare I ask, what are the chances of getting different container output files for x265 ??

[Atak_Snajpera]

You can already automatically remux .mkv to any container after finished job.
1) Enable in settings "RUN COMMAND SCRIPT AFTER FINISHED JOB"
2) Open "Job finished successfully.cmd" file in notepad and add last line

@REM ************* SUPPORTED EXTRA VARIABLES *************
@REM * *
@REM * %RIPBOT264TEMP% -> e.g. C:\Temp\Ripbot264temp *
@REM * %JOB% -> e.g. Job1 *
@REM * %INPUTFILEDIR% -> e.g. C:\InputVideoFiles *
@REM * %OUTPUTFILEDIR% -> e.g. C:\OutputVideoFiles *
@REM * %INPUTFOLDERNAME% -> e.g. InputVideoFiles *
@REM * %OUTPUTFOLDERNAME% -> e.g. OutputVideoFiles *
@REM * %INPUTFILENAME% -> e.g. InputVideoFile *
@REM * %OUTPUTFILENAME% -> e.g. OutputVideoFile *
@REM * %INPUTFILEEXT% -> e.g. avi *
@REM * %OUTPUTFILEEXT% -> e.g. mkv *
@REM * %YEAR% -> e.g. 2019 *
@REM * %MONTH% -> e.g. 01 *
@REM * %DAY% -> e.g. 31 *
@REM * %HOUR% -> e.g. 23 *
@REM * %MINUTE% -> e.g. 59 *
@REM * %SECOND% -> e.g. 00 *
@REM * %MILLISECOND% -> e.g. 999 *
@REM * *
@REM *****************************************************
@REM <INSERT YOUR SCRIPT HERE>

"C:\{PATH_TO_RIPBOT264}\Tools\ffmpeg\bin\ffmpeg.exe" -y -i "%OUTPUTFILEDIR%\%OUTPUTFILENAME%.%OUTPUTFILEEXT%" -c:v copy -c:a copy -c:s copy "c:\temp\%OUTPUTFILENAME%-test.mp4" 2> "c:\temp\log.txt"

3) save

Once job is completed that script will remux mkv to mp4 and save log.txt file.( may be handy if you want to check why file was not created by fffmpeg.exe)

You can use the same method to extract/inject DV to video file.

[guest]

You can already automatically remux .mkv to any container after finished job.
1) Enable in settings "RUN COMMAND SCRIPT AFTER FINISHED JOB"
2) Open "Job finished successfully.cmd" file in notepad and add last line

@REM ************* SUPPORTED EXTRA VARIABLES *************
@REM * *
@REM * %RIPBOT264TEMP% -> e.g. C:\Temp\Ripbot264temp *
@REM * %JOB% -> e.g. Job1 *
@REM * %INPUTFILEDIR% -> e.g. C:\InputVideoFiles *
@REM * %OUTPUTFILEDIR% -> e.g. C:\OutputVideoFiles *
@REM * %INPUTFOLDERNAME% -> e.g. InputVideoFiles *
@REM * %OUTPUTFOLDERNAME% -> e.g. OutputVideoFiles *
@REM * %INPUTFILENAME% -> e.g. InputVideoFile *
@REM * %OUTPUTFILENAME% -> e.g. OutputVideoFile *
@REM * %INPUTFILEEXT% -> e.g. avi *
@REM * %OUTPUTFILEEXT% -> e.g. mkv *
@REM * %YEAR% -> e.g. 2019 *
@REM * %MONTH% -> e.g. 01 *
@REM * %DAY% -> e.g. 31 *
@REM * %HOUR% -> e.g. 23 *
@REM * %MINUTE% -> e.g. 59 *
@REM * %SECOND% -> e.g. 00 *
@REM * %MILLISECOND% -> e.g. 999 *
@REM * *
@REM *****************************************************
@REM <INSERT YOUR SCRIPT HERE>

"C:\{PATH_TO_RIPBOT264}\Tools\ffmpeg\bin\ffmpeg.exe" -y -i "%OUTPUTFILEDIR%\%OUTPUTFILENAME%.%OUTPUTFILEEXT%" -c:v copy -c:a copy -c:s copy "c:\temp\%OUTPUTFILENAME%-test.mp4" 2> "c:\temp\log.txt"

3) save

Once job is completed that script will remux mkv to mp4 and save log.txt file.( may be handy if you want to check why file was not created by fffmpeg.exe)

You can use the same method to extract/inject DV to video file.

Ok, well that sounds like a plan, but what about remuxing to .m2ts with tsmuxer (or whatever) ?

Should be able to use x265 command to inject rpu.bin.

[Atak_Snajpera]

Regarding injecting rpu.bin you should ask -QfG- how to create proper command line
https://forum.doom9.org/showthread.php?t=183479

[guest]

Regarding injecting rpu.bin you should ask -QfG- how to create proper command line
https://forum.doom9.org/showthread.php?t=183479

Yes, I have been working with this a fair bit over the passed week or so, and have had contact with -QfG- and DDVT, and have figured out how to use that to create & inject rpu's, but you can inject them with x265 as well, so that would save an extra step in the process.

But just going back to my previous post, how to use tsmuxer to remux to .m2ts, instead of ffmepg to .mp4 ?

[Atak_Snajpera]

ffmpeg should also support .m2ts

[guest]

ffmpeg should also support .m2ts

So just changing this should work, then:-


"C:\{PATH_TO_RIPBOT264}\Tools\ffmpeg\bin\ffmpeg.exe" -y -i "%OUTPUTFILEDIR%\%OUTPUTFILENAME%.%OUTPUTFILEEXT%" -c:v copy -c:a copy -c:s copy "c:\temp\%OUTPUTFILENAME%-test.m2ts" 2> "c:\temp\log.txt"