Log in

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


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 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 [298] 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429

steferrari
30th April 2017, 17:39
Try taking a clean 19.6 and only copy the ffms from 19.5 (v2.20)
I was getting weird video output with the newest ffms, but not the preview field for the crop.

No difference, unfortunately.

byteshare
1st May 2017, 02:39
No difference, unfortunately.

Does it work for you with a clean (no updates) 19.5?

steferrari
1st May 2017, 13:21
Does it work for you with a clean (no updates) 19.5?

I just tried and yes... it works!
But when it does the updates, the problem comes back immediately.

So I assume that this issue is 100% caused by something in 19.6 then.

BlockABoots
1st May 2017, 16:41
Im not sure if this is an issue with RipBot or AviSynth but have noticed that once i have edited (Avisynth) and encoded (ripbot) that when i watch back the file that my mic audio has become slightly distorted and crackly at random times will be ok one second and then the next will start having issues. I have watch the raw file and this doesnt have these issues at all. Any ideas what the cause of this could be?

byteshare
1st May 2017, 16:57
I just tried and yes... it works!
But when it does the updates, the problem comes back immediately.

So I assume that this issue is 100% caused by something in 19.6 then.

For me the issue was ffms, but for you it sounds like something else.
I'd try to take a clean 19.6 (a straight download http://www.mediafire.com/file/1x2cuqbhbx9xpn3/RipBot264v1.19.6.7z)
and start replacing the plugins 1 by one from a clean 19.5 with out updates in the \Tools\AviSynth plugins until you find the plugin issue. Once you find the issue let us know.

byteshare
1st May 2017, 16:58
Im not sure if this is an issue with RipBot or AviSynth but have noticed that once i have edited (Avisynth) and encoded (ripbot) that when i watch back the file that my mic audio has become slightly distorted and crackly at random times will be ok one second and then the next will start having issues. I have watch the raw file and this doesnt have these issues at all. Any ideas what the cause of this could be?

Which version of RipBot are you using?

BlockABoots
1st May 2017, 17:16
Which version of RipBot are you using?

Its 1.19.6

BlockABoots
1st May 2017, 17:39
Also does Ripbot have issues with video files that have been captured with variable frame rate (like Nvidia's ShadowPlay uses) ?

steferrari
1st May 2017, 18:00
For me the issue was ffms, but for you it sounds like something else.
I'd try to take a clean 19.6 (a straight download http://www.mediafire.com/file/1x2cuqbhbx9xpn3/RipBot264v1.19.6.7z)
and start replacing the plugins 1 by one from a clean 19.5 with out updates in the \Tools\AviSynth plugins until you find the plugin issue. Once you find the issue let us know.

I just did that and nothing changed... really strange. :confused:
Then I tried again with 19.5 and everything is fine!

There must be something else in 19.6 that causes this issue.

Edit: I even tried to replace the whole Tools folder with the one from 19.5 but the problem was still there!

byteshare
1st May 2017, 19:04
Its 1.19.6
Try it on 1.19.5 without updates to see if it is something in the new version.
Also does Ripbot have issues with video files that have been captured with variable frame rate (like Nvidia's ShadowPlay uses) ?
I haven't had too many issues with frame rate stuff in RipBot but when I do I use this AVISynth script to output timestamps to mux back in with MKVtools and it fixes my problems:
LoadPlugin("..Where ever you have your install of RipBot..\ffms2.dll")
FFVideoSource("C:\Video.mkv",timecodes="C:\Video.mkv.avs_timecodes.txt")
To be clear the Video.mkv in this example is the original source file and not the encoded file. You'll mux the *.txt into the encoded file.

I just did that and nothing changed... really strange. :confused:
Then I tried again with 19.5 and everything is fine!

There must be something else in 19.6 that causes this issue.

Edit: I even tried to replace the whole Tools folder with the one from 19.5 but the problem was still there!
Hmmm...Since I changed out my ffms2 (with the version from 19.5) I get black previews on the crop preview. I wasn't having an issue though with the default 19.6. Something for the Dev to look into, which was already mentioned about switching back to the older ffms for video and the newer ffms for audio.

guest
3rd May 2017, 04:23
Another substantial update today, peep's :)

steferrari
3rd May 2017, 10:03
My blank video margins problem is still there though.

soneca
5th May 2017, 04:01
Hi Atak,

Today I had to make a small edition in Sony Vegas/Frameserver using RipBot to render and I got the same screen. What had never happened.

https://s20.postimg.org/d5z1vzq31/ripbot.png

https://s20.postimg.org/wcc8z66kt/ripbot1.png

byteshare
5th May 2017, 08:05
Hi Atak,

Today I had to make a small edition in Sony Vegas/Frameserver using RipBot to render and I got the same screen. What had never happened.

https://s20.postimg.org/d5z1vzq31/ripbot.png

https://s20.postimg.org/wcc8z66kt/ripbot1.png

If you're trying 19.6 for the first time, run the updater again to get another version change that might fix your issue. Fixed mine, but some others are saying they are still having the crop preview issue.

steferrari
5th May 2017, 10:33
Looks like everything works fine for me now!
I just ran RipBot, it automatically made an update and the problem seems to be gone. :)

jlpsvk
5th May 2017, 12:07
--profile main10 --output-depth 10 --level-idc 5.1 --amp --aq-mode 3 --qg-size 64 --vbv-bufsize 160000 --vbv-maxrate 160000 --me star --max-merge 5 --rc-lookahead 40
--lookahead-slices 4 --ref 5 --min-keyint 24 --keyint 240 --no-strong-intra-smoothing --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 --max-cll "1132,923" --no-deblock --no-sao --high-tier --no-info

Results in:
B(7500 was unexpected at this time.

What now? :( Command works with standalone command line.

soneca
5th May 2017, 12:34
If you're trying 19.6 for the first time, run the updater again to get another version change that might fix your issue. Fixed mine, but some others are saying they are still having the crop preview issue.

It was already updated.
This error is only occurring via Frameserver.

Atak_Snajpera
5th May 2017, 16:01
Soneca.
http://i.cubeupload.com/AhZwSK.png

soneca
5th May 2017, 17:28
Hello Atak,
Was actually disabled but still not working. I have now tested it with version 1.19.5 and it works normally.

soneca
6th May 2017, 00:38
Thank you, problem fixed! :)

jlpsvk
6th May 2017, 11:26
@Atak_Snajpera

What about this http://forum.doom9.org/showthread.php?p=1806163#post1806163 ? Any suggestion?

Atak_Snajpera
6th May 2017, 14:59
I guess command line is too long for .cmd file.

soneca
6th May 2017, 18:49
Hi Atak,

Editing today a few chapters extracted from blu-ray in Sony Vegas the autocrop has again troubled, does not crop the video via FrameServer and hangs, I have to force the closing of RipBot264. While in version 1.19.5 this again does not occur.

https://s20.postimg.org/p8dqbuqq5/ripbot.png

jlpsvk
6th May 2017, 23:34
I guess command line is too long for .cmd file.

from command line with x265 it's working OK.

Atak_Snajpera
7th May 2017, 13:05
from command line with x265 it's working OK.

What happens if you manually execute jobx_EncodeVideo.cmd

jlpsvk
7th May 2017, 15:15
What happens if you manually execute jobx_EncodeVideo.cmd

It works OK. It's happens only with Distributed Encoding enabled.

jlpsvk
9th May 2017, 13:18
Atak_Snajpera
What ports are used on the "server" side for distributed encoding? I want to make this work across firewall, as I have 1gbit fiber-optic line between the sites (i have physical access and admin over both end firewalls - on windows machines firewalls are disabled). Microsoft networking is working, I can access shared directories from the "remote machine" on which encodingserver.exe is running to main machine running RipBot264. Also ports 1000-1010 are forwarded from remote to RipBot machine...but still not successfull. On remote end, in Encoding Server windows I am getting
Socket error # 10060
Connection timed out
Access violation at address 004C6268 in module "Encodingserver.exe". Read of address 00000098

Atak_Snajpera
9th May 2017, 15:06
https://forum.doom9.org/showthread.php?p=1762596#post1762596
https://forum.doom9.org/showthread.php?p=1762732#post1762732

jlpsvk
9th May 2017, 16:05
Atak_Snajpera
Thanks. :) Will try. What about that encoding command, which is not working in distributed encoding?

Atak_Snajpera
9th May 2017, 16:13
Like I said. Most likely command line is too long for .cmd file.

jlpsvk
9th May 2017, 16:18
Atak_Snajpera
But the setting is working in standalone mode.

Regarding those firewall... tried it.. both ports 1000-1010 are bi-directional accessible, the same with windows networking ans file sharing. but still not working. :(

EDIT: It works now. :) Created a floating rules on firewalls, so no NAT and everything is working. :)

essential
15th May 2017, 15:17
I did a search first and read though a bunch of posts but didn't find an answer. I figured out a way that works well to use Ripbot and keep chapters with bluray's but I can't figure out how to keep DVD chapters with Ripbot. My resulting file never retains the chapter points. Are there certain steps to maintain chapter points? The VOBs, played directly in VLC have the chapter points, but those same VOBs loaded into Ripbot lose them during encode.

byteshare
15th May 2017, 20:06
I did a search first and read though a bunch of posts but didn't find an answer. I figured out a way that works well to use Ripbot and keep chapters with bluray's but I can't figure out how to keep DVD chapters with Ripbot. My resulting file never retains the chapter points. Are there certain steps to maintain chapter points? The VOBs, played directly in VLC have the chapter points, but those same VOBs loaded into Ripbot lose them during encode.
Have you tried exporting the video from VOBs to MKV with MakeMKV first? This is my usual process.

byteshare
15th May 2017, 22:10
Not sure if this would apply to AVISynth+, but I found a chat about making AVISynth 2.6 portable: http://forum.doom9.org/showthread.php?t=167868
Thought is might help you if you wanted to make RipBot more portable.

essential
16th May 2017, 02:52
Have you tried exporting the video from VOBs to MKV with MakeMKV first? This is my usual process.

No, originally I just copied the DVD to my HD then loaded the first VOB into Ripbot and it did the rest.

I just tried using MakeMKV. Two things ... first the DVD source is interlaced and I'd use the inverse telecine + restore 23.976 option, when I load the resulting mkv from MakeMKV, the deinterlace option isn't delectable anymore, does MakeMKV take care of the interlaceing during its process?

Second, the resulting encoded MKV does indeed retain the chapters now, but if I skip ahead at all in the video, the audio/video sync goes out of whack. This doesn't happen at all when encoding straight from the VOBs. My original encode is basically perfect except for the lack of chapters.

I ended up finding this site, "chapterdb.org" and found a chapter file for my movie and used mkvtoolnix to save it to the mkv. This is a solution, but still unsure why Ripbot isn't able to use the chapter marks from the original VOB files.

byteshare
16th May 2017, 17:14
If you're not already, I'd use QTGMC in RipBot for the interlaced material. Under settings > "Use QTGMC deinterlacer instead of Yadif"
You can force the QTGMC when in batch mode by setting Deinterlace to "TFF -> 25 FPS/30FPS"
or editing the video script and putting this in there (copy/past) under #Deinterlace:
Loadplugin("C:\RipBot\Tools\AviSynth plugins\Repair\RepairSSE2.dll")
Loadplugin("C:\RipBot\Tools\AviSynth plugins\RemoveGrain\RemoveGrainSSE2.dll")
Loadplugin("C:\RipBot\Tools\AviSynth plugins\nnedi3\nnedi3.dll")
Loadplugin("C:\RipBot\Tools\AviSynth plugins\masktools\masktools2.dll")
Loadplugin("C:\RipBot\Tools\AviSynth plugins\mvtools\mvtools2.dll")
Import("C:\RipBot\Tools\AviSynth plugins\UniCode\QTGMC-3.33.avsi")
video=QTGMC(video,Preset="Medium",FPSDivisor=2)
Only change the path from "C:\RipBot" to where you are running RipBot from.

You might have loaded the DVD incorrectly if you weren't getting chapters in the MKV from MakeMKV, which should be coming along after you've encoded the video in RipBot.

As for the video/audio being out of sync not sure since RipBot should be making a "video.mkv.ffindex" in the job folder that it uses to mux back in to correct that sort of thing. You could try manually remuxing it in to make sure that is happening and/or see if that file is being generated. Did you check the outputed MKV from MakeMKV? It could also be just the actual audio file, try muxing in the audio from the source MKV from MakeMKV to see where the issue is happening. I get audio issues sometimes with RipBot, which is why I personally usually just copy the audio or use a 2nd application to process the audio. It doesn't always happen but I've had it happen enough that I changed my work flow.

Nice find on that site though. I hadn't heard of it before.

essential
16th May 2017, 21:39
If you're not already, I'd use QTGMC in RipBot for the interlaced material. Under settings > "Use QTGMC deinterlacer instead of Yadif"
You can force the QTGMC when in batch mode by setting Deinterlace to "TFF -> 25 FPS/30FPS"
or editing the video script and putting this in there (copy/past) under #Deinterlace:

Only change the path from "C:\RipBot" to where you are running RipBot from.

You might have loaded the DVD incorrectly if you weren't getting chapters in the MKV from MakeMKV, which should be coming along after you've encoded the video in RipBot.

As for the video/audio being out of sync not sure since RipBot should be making a "video.mkv.ffindex" in the job folder that it uses to mux back in to correct that sort of thing. You could try manually remuxing it in to make sure that is happening and/or see if that file is being generated. Did you check the outputed MKV from MakeMKV? It could also be just the actual audio file, try muxing in the audio from the source MKV from MakeMKV to see where the issue is happening. I get audio issues sometimes with RipBot, which is why I personally usually just copy the audio or use a 2nd application to process the audio. It doesn't always happen but I've had it happen enough that I changed my work flow.

Nice find on that site though. I hadn't heard of it before.

Thanks for the reply byte, yea I've never changed anything on the settings screen. I'm assuming QTGMC is better or faster than the Yadif? I wonder why QTGMC isn't the default heh, I've done a lot of videos with Yadif.

Not sure the issues. I just copied the entire original DVD to my HD after removing copy protection (old DVD, nothing recent). It plays just fine from my HD, and loads into VLC with menus and everything (only loaded VTS_01_1.vob into Rip).

The encode from the resulting MakeMKV file is fine timing wise unless I skip forward, then it looses it. If i just let it play from the beginning it never looses sync.

Oh well, it's not a big deal now, between that site and their piece of software "ChapterGrabber.5.4" I can always get or create my own chapters and insert them into the MKV after Ripbot is done. I've gone back and looked at a lot of my old encodes based on DVDs and none have chapters, so I don't think that has ever worked for me, but I'm just realizing it now.

byteshare
17th May 2017, 16:47
I'm assuming QTGMC is better or faster than the Yadif?

The encode from the resulting MakeMKV file is fine timing wise unless I skip forward, then it looses it. If i just let it play from the beginning it never looses sync.
QTGMC is slower for sure, but way better results.
Weird that you're only losing sync after skipping. I'm not sure what is causing your issue in this case.

byteshare
26th May 2017, 17:47
Not sure if this would apply to AVISynth+, but I found a chat about making AVISynth 2.6 portable: http://forum.doom9.org/showthread.php?t=167868
Thought is might help you if you wanted to make RipBot more portable.
Found something awesome today that I needed to share and hope gets implemented by default into RipBot.
As long as your on AVISynth+ r2440 or higher (I'm on r2455) you should be able to really speed up your encode times if using MDegrain or QTGMC.
Normal MDegrain in RipBot (right now) looks like:
Loadplugin("C:\RipBot264v1.19.6\Tools\AviSynth plugins\mvtools\mvtools2.dll")
SetFilterMTMode("DEFAULT_MT_MODE", 2)
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400)
But adding SetFilterMTMode("DEFAULT_MT_MODE", 2) and Prefetch(8) makes a big difference. I was useing DE mode with 4 nodes on a local machine to use full CPU but the new lines fix this.
Adding those lines I get:
Loadplugin("E:\!0-Trans\!2Tools\RipBot264v1.19.6\Tools\AviSynth plugins\mvtools\mvtools2.dll")
SetFilterMTMode("DEFAULT_MT_MODE", 2)
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400).Prefetch(8)
Happy encoding.
Update: For more info about MT Modes: https://gist.github.com/tp7/8899021

Atak_Snajpera
26th May 2017, 18:42
Found something awesome today that I needed to share and hope gets implemented by default into RipBot.
As long as your on AVISynth+ r2440 or higher (I'm on r2455) you should be able to really speed up your encode times if using MDegrain or QTGMC.
Normal MDegrain in RipBot (right now) looks like:
Loadplugin("C:\RipBot264v1.19.6\Tools\AviSynth plugins\mvtools\mvtools2.dll")
SetFilterMTMode("DEFAULT_MT_MODE", 2)
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400)
But adding SetFilterMTMode("DEFAULT_MT_MODE", 2) and Prefetch(8) makes a big difference. I was useing DE mode with 4 nodes on a local machine to use full CPU but the new lines fix this.
Adding those lines I get:
Loadplugin("E:\!0-Trans\!2Tools\RipBot264v1.19.6\Tools\AviSynth plugins\mvtools\mvtools2.dll")
SetFilterMTMode("DEFAULT_MT_MODE", 2)
super=MSuper(video,pel=2)
fv1=MAnalyse(super,isb=false,delta=1,overlap=4)
bv1=MAnalyse(super,isb=true,delta=1,overlap=4)
fv2=MAnalyse(super,isb=false,delta=2,overlap=4)
bv2=MAnalyse(super,isb=true,delta=2,overlap=4)
video=MDegrain2(video,super,bv1,fv1,bv2,fv2,thSAD=400).Prefetch(8)
Happy encoding.
Update: For more info about MT Modes: https://gist.github.com/tp7/8899021

Have you compared total encoding time with 4 nodes vs 1 node? Higher CPU usage does not always mean faster encoding time. I'm just curious now...
I used to experiment a little bit with MT modes in the past but then I realized that running multiple instances on the same PC was faster than spawning additional threads like you do.

byteshare
27th May 2017, 04:44
Have you compared total encoding time with 4 nodes vs 1 node? Higher CPU usage does not always mean faster encoding time. I'm just curious now...
I used to experiment a little bit with MT modes in the past but then I realized that running multiple instances on the same PC was faster than spawning additional threads like you do.
Yes, it is for sure faster than 1 thread 3-4 times faster (maybe default for non-DE mode?), but slightly slower depending on the source and filters I'm using than having 4 threads (vs 1) that are not MT. For some stuff I found it was as fast, but I don't think faster. I don't have the numbers and since it was within minutes I usually didn't care.
Was testing with MDegrain3, HQDering, and f3kdb on.
It does also use a lot less RAM though if that is a concern for anyone.
The main reason I looked into it was because I was trying to use MDegrain3, HQDering, and f3kdb with QTGMC and it was taking way longer (about 8 times longer) than doing QTGMC near lossless, and then reprocessing the video into HEVC with MDegrain3, HQDering, and f3kdb. I wouldn't normally do that but I was trying to isolate what was going on.
The one hiccup I have right now is how to put in the script for RipBot since in RipBot you don't group all of your load and "video=" commands AVISynth doesn't like putting ".Prefetch(8)" twice in the same script. Wasn't sure if I put it just in QTGMC (since it is first in the list) it is applying to the other filters.
Oh, and I should mention if I add in the prefetch info from within RipBot and by clicking on the AVISynth button in the edit menu, then showing the video script and after editing clicking okay the avs2avi.exe will take forever and a day but if I click the "X" it seems to work fine, not sure what the exe is doing.
I've been just editing the Job*.avs script directly because of the above.
Update: Ran some more tests...and a lot of videos would cut out early in the encode. Might have to stick with ST over MT for now.

george84
31st May 2017, 18:26
x265 version 2.4 has option --hdr-opt for HDR10 support.Please update RipBot.

byteshare
1st June 2017, 00:26
x265 version 2.4 has option --hdr-opt for HDR10 support.Please update RipBot.
You can manually update while you wait; what I usually have to do.

george84
1st June 2017, 07:41
You can manually update while you wait; what I usually have to do.

Thank you, this worked. I assumed it was a version specially built for RipBot.

byteshare
3rd June 2017, 17:41
Thank you, this worked. I assumed it was a version specially built for RipBot.
I think HandBrake is the only common encoder that makes it difficult to update HEVC.

george84
3rd June 2017, 19:04
I created my own profile to encode. I use MA10 profile andmodified command section to:

--profile main10 --output-depth 10 --hdr-opt --aq-mode 1 --aq-strength 2 --no-open-gop --colorprim bt2020 --transfer smpte-st-2084 --colormatrix bt2020nc --master-display "G(13250,34500)B(7500,3000)R(34000,16000)WP(15635,16450)L(10000000,1)" --max-cll "1000,200"

I would expect media info to display something like this:

...
Color range : Limited
Color primaries : BT.2020
Transfer characteristics : SMPTE ST 2084
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.0001 cd/m2, max: 1000.0000 cd/m2
Maximum Content Light Level : 1000 cd/m2
Maximum Frame-Average Light Level : 200 cd/m2


but mediainfo only shows:

Video
ID : 1
Format : HEVC
Format/Info : High Efficiency Video Coding
Codec ID : V_MPEGH/ISO/HEVC
Duration : 51 s 0 ms
Bit rate : 4 923 kb/s
Width : 3 840 pixels
Height : 2 160 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 24.000 FPS
Bits/(Pixel*Frame) : 0.025
Stream size : 29.9 MiB (97%)
Default : Yes
Forced : No


When doing playback on TV, then TV shows HEVC AAC 3840x2160 HDR BT.2020 as video characteristics and everything is Ok.

Is there a way to force RipBot so that mediainfo can discover and show the wanted information? (which is clearly somewhere hidden in video)

byteshare
3rd June 2017, 20:12
Is there a way to force RipBot so that mediainfo can discover and show the wanted information? (which is clearly somewhere hidden in video)
I believe the problem you're having is to do with MKVToolNix and HEVC (x265) 2.4+
You need to update the MKVToolNix RipBot uses: RipBot264\Tools\mkvtoolnix (need MKVToolNix 12.0+) or wait for Atak_Snajpera to push an update.

sneaker_ger
3rd June 2017, 20:25
There was a problem with mkvmerge 11.0, not related to x265. But RipBot should still be using mkvmerge 10.0?

byteshare
3rd June 2017, 20:40
There was a problem with mkvmerge 11.0, not related to x265. But RipBot should still be using mkvmerge 10.0?
I just checked to be sure and in my RibBot folder after all updates it is using MKVToolNix 11.0.0 and says the same under Settings > Tools
Update: I manually copied newer MKVToolNix (12.0.0) files into the RipBot264\Tools\mkvtoolnix folder. Did a quick test encode with HEVC 2.4+26 and media info correct after RipBot Muxed the pieces together.

george84
4th June 2017, 10:05
I just checked to be sure and in my RibBot folder after all updates it is using MKVToolNix 11.0.0 and says the same under Settings > Tools
Update: I manually copied newer MKVToolNix (12.0.0) files into the RipBot264\Tools\mkvtoolnix folder. Did a quick test encode with HEVC 2.4+26 and media info correct after RipBot Muxed the pieces together.

Thank you, this solution works for me.