BD Rebuilder Beta - Bug Reports Only

[jdobbs]

Uh huh... Uh... it's called 'Irony' mate :DI, Rony... sounds like a movie title.

[AmigaFuture]

Uh huh... Uh... it's called 'Irony' mate :D

I'm not a believer of irony, mate...that's too shallow for me. ;-)

But now that we know your name, Rony...

[AmigaFuture]

Oppps..Dobbs sort of beat me to it. Ha!

[Lathe]

There are just TOO damn many clever people here... http://lathe-of-heaven.com/no.gif

[gonca]

There are just TOO damn many clever people here... http://lathe-of-heaven.com/no.gif

793 posts and nothing meaningful or useful as of yet :cool:

[Lathe]

793 posts and nothing meaningful or useful as of yet :cool:

Hmmm... do you guys smell something...?

[gonca]

794 and rising

[Blurayhd]

Hi Jdobbs I don´t know why on some Bluray encodings I get this message? sorry guys the screen capture is in Spanish (my first language)


http://img.fenixzone.net/i/TE9CWRa.jpeg


And this is the log

[02/10/18] BD Rebuilder v0.50.25
[12:35:10] Source: LES_MISERABLES_25TH_00005
- Input BD size: 43,16 GB
- Approximate total content: [02:49:52.098]
- Target BD size: 22,95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:35:14] PHASE ONE, Encoding
- [12:35:14] Processing: VID_00007 (1 of 2)
- [12:35:14] Extracting A/V streams [VID_00007]
- [12:44:39] Reencoding video [VID_00007]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23,976fps, 119.784 frames
- Bitrate: 12.137 Kbs
- [12:44:39] Reencoding: VID_00007, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.50.25
- Windows Version: 6.2 [9200]
- Working Path Free Space: 88,50GB
- AVISYNTH Version: 2.6.0.6, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[13:28:11] - Failed video encode, aborted


So I don´t know what is wrong and how to get a solution?

I hope im doing well posting image and log

[gonca]

Are you overclocked
How are your temps
That is a x264 crash

[Blurayhd]

Are you overclocked
How are your temps
That is a x264 crash

No, I don´t I never do any overclock just in case it helps my processor is i7 2700k

Can be the problem if I use an SSD por encoding?

Anyway I hope there´s can be a solution?

[jdobbs]

No, I don´t I never do any overclock just in case it helps my processor is i7 2700k

Can be the problem if I use an SSD por encoding?

Anyway I hope there´s can be a solution?When X264 crashes it is highly likely you are overheating. I'd check your processor's heatsink and see if it is clogged with dust.

[Blurayhd]

When X264 crashes it is highly likely you are overheating. I'd check your processor's heatsink and see if it is clogged with dust.

I have an watercooling system, I check frecuently the system and the liquid of course.

And this computer I use for gaming too and noo problems

Could be anything else?

What do you recommend?

[jdobbs]

I have an watercooling system, I check frecuently the system and the liquid of course.

And this computer I use for gaming too and noo problems

Could be anything else?

What do you recommend?Not likely. Other software (even overclock testing software) just doesn't stress your system like X264. It's the ultimate test. The only other possibility I can think of might be memory overheating. You could try cleaning that as well. If you look back through this thread you'll find other similar reports, and I'm pretty sure every one of them was caused to overheating.

Try getting some software (like "Core Temp" or "CPUID HW Monitor") and monitor the temps while you are encoding.

Does your watercooling system have a radiator? I know I have to vacuum mine out regularly or my system overheats.

[Blurayhd]

Not likely. Other software (even overclock testing software) just doesn't stress your system like X264. It's the ultimate test. The only other possibility I can think of might be memory overheating. You could try cleaning that as well. If you look back through this thread you'll find other similar reports, and I'm pretty sure every one of them was caused to overheating.

Try getting some software (like "Core Temp" or "CPUID HW Monitor") and monitor the temps while you are encoding.

Does your watercooling system have a radiator? I know I have to vacuum mine out regularly or my system overheats.

Thank you Jdobbs, always you are there tryng (or trying, sorry) to solve problems.

And I have one more question, there´s a way to clean up Bd rebuilder, avisint and the others tools so I can install everything again without re install the OS?

I have 32gb on my system but maybe re installing all related to Bd rebuilder?

Please dont get my wrong thanks to you BD rebuilder exist, I just need to see the problem

[Blurayhd]

Not likely. Other software (even overclock testing software) just doesn't stress your system like X264. It's the ultimate test. The only other possibility I can think of might be memory overheating. You could try cleaning that as well. If you look back through this thread you'll find other similar reports, and I'm pretty sure every one of them was caused to overheating.

Try getting some software (like "Core Temp" or "CPUID HW Monitor") and monitor the temps while you are encoding.

Does your watercooling system have a radiator? I know I have to vacuum mine out regularly or my system overheats.

Dear Jdobbs I tried encoding the same Bluray movie but this time with another computer just in case and I get the same problem

I dont know what to do

[jdobbs]

Dear Jdobbs I tried encoding the same Bluray movie but this time with another computer just in case and I get the same problem

I dont know what to doAre you sure the source isn't corrupt?

[jdobbs]

I just wanted to give everyone an update on the UHD capability. I have BD-RB working. It can import 2160p MKVs etc. It can do full backups and movie-only backups of non-protected UHD-BD sources. But... I am having a lot of trouble with audio/video sync after TSMUXER muxes them. I can't blame TSMUXER, however, because MKVMERGE has the same issue after muxing. It may be some inconsistency in the HEVC stream generated by X265, or possibly FFMPEG (used for frame serving) could be losing frames... I really don't know. I don't think it is the audio, as it doesn't necessarily get reencoded, and it is handled no differently than with previous BD-RB versions.

I haven't figured out why this is happening yet, but if and when I do I'll release a test version here on Doom9. The biggest problem is that it takes anywhere between 10 and 18 hours for my system to do a full movie (even at the fastest encode speed and using one-pass ABR)... so you can only do so much in a day.

I think I'll do a couple encodes using AVISYNTH just to eliminate the FFMPEG possibility -- but even if it works correctly that's not a long term solution as it would also be losing the HDR and 10 bit attributes during encode.

[Acerjen]

I just wanted to give everyone an update on the UHD capability. I have BD-RB working. It can import 2160p MKVs etc. It can do full backups and movie-only backups of non-protected UHD-BD sources. But... I am having a lot of trouble with audio/video sync after TSMUXER muxes them. I can't blame TSMUXER, however, because MKVMERGE has the same issue after muxing. It may be some inconsistency in the HEVC stream generated by X265, I really don't know. I don't think it is the audio, as it doesn't get reencoded, and it is handled no differently than with previous BD-RB versions.

I haven't figured out why this is happening yet, but if and when I do I'll release a test version here on Doom9. The biggest problem is that it takes anywhere between 10 and 18 hours for my system to do a full movie (even at the fastest encode speed and using one-pass ABR)... so you can only do so much in a day.


I have a system setup with a Ryzen 1700 (8-Core) running at 3.9 GHz. If you want some help getting some UHD testing done, let me know. Thank you for a great program.

Later,
Acerjen

[LowDead]

I have a system setup with a Ryzen 1700 (8-Core) running at 3.9 GHz. If you want some help getting some UHD testing done, let me know. Thank you for a great program.

Later,
Acerjen

I too got a new rig for UHD encoding. Intel i7 6 core 8700K @3.7GHz with Nvidia 1060 gfx and 32gb ram. Doing Men in Black now down to BD50 under 30 minutes using the gfx card hardware decoding and encoding. Haven't tried software encodes on this CPU yet, but will probably be quite fast too. So count me in if you need testers.

Have nice day!

//LD

[kufo]

Thanks for the backup, jdobbs. The issue with audio and video getting out of sync, was discussed in Redfox before. I read about that, obout two weeks before.
I'll be patient...
Thanks for your great work
anyway!

[jdobbs]

Thanks for the backup, jdobbs. The issue with audio and video getting out of sync, was discussed in Redfox before. I read about that, obout two weeks before.
I'll be patient...
Thanks for your great work
anyway!Did anyone come to any conclusion?

[Lathe]

Did anyone come to any conclusion?

Yeah...

gonca is a wee wee head... http://lathe-of-heaven.com/yes.gif

[MrVideo]

Suggestion mode: Allow DTS audio for background music.

Thanks.

[jdobbs]

I just wanted to give everyone an update on the UHD capability. I have BD-RB working. It can import 2160p MKVs etc. It can do full backups and movie-only backups of non-protected UHD-BD sources. But... I am having a lot of trouble with audio/video sync after TSMUXER muxes them. I can't blame TSMUXER, however, because MKVMERGE has the same issue after muxing. It may be some inconsistency in the HEVC stream generated by X265, or possibly FFMPEG (used for frame serving) could be losing frames... I really don't know. I don't think it is the audio, as it doesn't necessarily get reencoded, and it is handled no differently than with previous BD-RB versions.

I haven't figured out why this is happening yet, but if and when I do I'll release a test version here on Doom9. The biggest problem is that it takes anywhere between 10 and 18 hours for my system to do a full movie (even at the fastest encode speed and using one-pass ABR)... so you can only do so much in a day.

I think I'll do a couple encodes using AVISYNTH just to eliminate the FFMPEG possibility -- but even if it works correctly that's not a long term solution as it would also be losing the HDR and 10 bit attributes during encode. It looks as though frames are being added during the encode process (FFMPEG?). I just ran the original and the output from the encode through AVISYNTH using StackVertical() and the new encode slowly lags more-and-more behind the original as it plays (at the same frame rate). Because of the apparent addition of frames, the total length of the new encode is 31 seconds longer than the original on the test I'm doing. I'm now running the exact same encode using AVISYNTH as the frame server rather than FFMPEG. I'll see what happens in about 15 hours or so.

If I'm lucky I may find that its caused by my use of the "-r" option in FFMPEG... but that'll take another encode as well.

[kufo]

Did anyone come to any conclusion?

@jdobbs
Unfortunately, I can not find the post anymore. I'm afraid it was deleted ... How does it look if MKV is selected as the output format?
I remember it was related to the output format. Details were as far as I remember not mentioned. That's probably a secret from Elby CBD.
It is about 2 weeks (may be 3 weeks) ago that I have read the post. I'm sorry that I can not say more about that.

If I'm lucky I may find that its caused by my use of the "-r" option in FFMPEG... but that'll take another encode as well.

I hope this is the solution to the problem.

[jdobbs]

@jdobbs
Unfortunately, I can not find the post anymore. I'm afraid it was deleted ... How does it look if MKV is selected as the output format?
I remember it was related to the output format. Details were as far as I remember not mentioned. That's probably a secret from Elby CBD.
It is about 2 weeks (may be 3 weeks) ago that I have read the post. I'm sorry that I can not say more about that.

If I'm lucky I may find that its caused by my use of the "-r" option in FFMPEG... but that'll take another encode as well.

I hope this is the solution to the problem.No. That wasn't the problem. In fact the problem persists even if I frame serve with AVISYNTH. So that eliminates FFMPEG as the culprit. That points to X265 as the source of the problem. I even removed all options from the X265 command line and used the default settings --- and it still appears that frames are being added. The original video gradually gets out of sync with the newly encoded video when I play them back together in AVISYNTH.

Not sure how I am going to fix this -- my next step will be to see if there is anything documented as a bug fix and try a newer X265 version.

[gonca]

I just wanted to give everyone an update on the UHD capability. I have BD-RB working. It can import 2160p MKVs etc. It can do full backups and movie-only backups of non-protected UHD-BD sources. But... I am having a lot of trouble with audio/video sync after TSMUXER muxes them. I can't blame TSMUXER, however, because MKVMERGE has the same issue after muxing. It may be some inconsistency in the HEVC stream generated by X265, or possibly FFMPEG (used for frame serving) could be losing frames... I really don't know. I don't think it is the audio, as it doesn't necessarily get reencoded, and it is handled no differently than with previous BD-RB versions.

I haven't figured out why this is happening yet, but if and when I do I'll release a test version here on Doom9. The biggest problem is that it takes anywhere between 10 and 18 hours for my system to do a full movie (even at the fastest encode speed and using one-pass ABR)... so you can only do so much in a day.

I think I'll do a couple encodes using AVISYNTH just to eliminate the FFMPEG possibility -- but even if it works correctly that's not a long term solution as it would also be losing the HDR and 10 bit attributes during encode.

Vapoursynth allows retention of HDR10 metadata
This app allows for the addition of HDR10 metadata to the hevc stream
https://github.com/SK-Hardwired/nv_hevc_hdr_patcher

@Lathe
Weak, very weak
About your limit I guess

[gonca]

@jdobbs
What happens to the sync if you re encode to MKV?

[MrVideo]

@jdobbs
What happens to the sync if you re encode to MKV?
MKV is a wrapper, so that is not going to make a difference.

[Lathe]

MKV is a wrapper, so that is not going to make a difference.

DOHHHHHH!

... and WHO is outta their league now...? :D

[gonca]

MKV is a wrapper, so that is not going to make a difference.

Would eliminate TsMuxer as the issue, process of elimination

Note
I am re encoding UHD to MKV and I have no sync issues
Using DGIndexNV, Vapoursynth and NVEnc

@Lathe
That would be you!!!:D
797 and climbing

[kufo]

MKV is a wrapper, so that is not going to make a difference.

In CBD it did make a diffrence. Maybe it was software related, but output to MKV was playing fine for me.

[MrVideo]

Maybe I should have added some fine print. jdobbs indicated that it is an encoder issue, therefore no matter what wrapper is used, it isn't going to make the encoder issue go away. As the old saying goes, crap in, crap out.

[MrVideo]

On a different note, I went looking for an option that would cause the background for the menu to loop if it contains audio, but I didn't find it. Is there one?

[jdobbs]

Would eliminate TsMuxer as the issue, process of elimination

Note
I am re encoding UHD to MKV and I have no sync issues
Using DGIndexNV, Vapoursynth and NVEnc

@Lathe
That would be you!!!:D
797 and climbingIt does the exact same think in MKV.

[jdobbs]

On a different note, I went looking for an option that would cause the background for the menu to loop if it contains audio, but I didn't find it. Is there one?Sorry, but no. That has been on the "to do" list for a long time.

[SquallMX]

No. That wasn't the problem. In fact the problem persists even if I frame serve with AVISYNTH. So that eliminates FFMPEG as the culprit. That points to X265 as the source of the problem. I even removed all options from the X265 command line and used the default settings --- and it still appears that frames are being added. The original video gradually gets out of sync with the newly encoded video when I play them back together in AVISYNTH.

Not sure how I am going to fix this -- my next step will be to see if there is anything documented as a bug fix and try a newer X265 version.

Handbrake produces properly sync re-encodes with HDR, I think it uses FFMPEG too.

[MrVideo]

Sorry, but no. That has been on the "to do" list for a long time.
OK. Thanks, just making sure.

[gonca]

@jdobbs
x265 version
2.6+31-3712d13c09bf

test 1
script
import vapoursynth as vs
core = vs.get_core()
core.avs.LoadPlugin(r'C:\Program Files (Portable)\dgdecnv\x64 Binaries\DGDecodeNV.dll')
clip = core.avs.DGSource(r'I:\Morgan.dgi', fieldop=0, fulldepth=True)
clip.set_output()


cmd line
"xxxx\avs2pipemod\avs2pipemod64.exe" -y4mp | "C:\Program Files (Portable)\x265\x265.exe" --crf 18 --preset ultrafast --profile main10 --level-idc 5.1 --output-depth 10 --frames 0 --y4m --output W:\TEMP\yyy.hevc -

test 2
same script
cmd line
"xxxx\avs2pipemod\avs2pipemod64.exe" -y4mp | "C:\Program Files (Portable)\x265\x265.exe" --crf 18 --preset ultrafast --profile main10 --level-idc 4.1 --output-depth 10 --hdr --uhd-bd --frames 0 --y4m --output W:\TEMP\yyy.hevc -

results
original 14400 frames
test 1 14400 frames
test 2 14400 frames

same frame count, no extra frames

[staina]

In Windows 10 don't go choose item

Use DirectshoeSource for frame serving

where make mistakes? Help thank you Staina

[jdobbs]

In Windows 10 don't go choose item

Use DirectshoeSource for frame serving

where make mistakes? Help thank you StainaYou have to install LAV Filters for Directshow to be available. See step 2A in the first post of this thread.

[jdobbs]

Update: I believe I've gotten past the sync issues on UHD-BD backups. I'll know after a couple of full encodes (10-18 hours each). It turns out it was poor attention to detail on my part. I went back and started over, testing every type of encoding sequence -- only to be perplexed when an AVISYNTH encode was in-sync. Apparently I'd done something in my first go-around that made me think it was out of sync also. That pointed to FFMPEG -- and I discovered it was an error in the way I used "-r " in the command line. It looks like a lot of time was wasted on this one due to my own mistakes... but I'll know for certain after this next round of encodes is done.

With a little luck I will be able to post a UHD-BD test version some time this week.

[Lathe]

Update: I believe I've gotten past the sync issues on UHD-BD backups. I'll know after a couple of full encodes (10-18 hours each). It turns out it was poor attention to detail on my part. I went back and started over, testing every type of encoding sequence -- only to be perplexed when an AVISYNTH encode was in-sync. Apparently I'd done something in my first go-around that made me think it was out of sync also. That pointed to FFMPEG -- and I discovered it was an error in the way I used "-r " in the command line. It looks like a lot of time was wasted on this one due to my own mistakes... but I'll know for certain after this next round of encodes is done.

With a little luck I will be able to post a UHD-BD test version some time this week.

Thanks Boss!

[kufo]

Glad to her this. Little mistake, big impact. I really want to know, what your new encode will bring.

[Ch3vr0n]

I'd love to see NVEnc support :D Hardware decoding and encoding for 3D discs ^^

[drmih]

Update: I believe I've gotten past the sync issues on UHD-BD backups. I'll know after a couple of full encodes (10-18 hours each). It turns out it was poor attention to detail on my part. I went back and started over, testing every type of encoding sequence -- only to be perplexed when an AVISYNTH encode was in-sync. Apparently I'd done something in my first go-around that made me think it was out of sync also. That pointed to FFMPEG -- and I discovered it was an error in the way I used "-r " in the command line. It looks like a lot of time was wasted on this one due to my own mistakes... but I'll know for certain after this next round of encodes is done.

With a little luck I will be able to post a UHD-BD test version some time this week.

If using LAV will it be possible to get the CUDA acceleration using GPU as I'm not sure I want to go back to 1 day encodes?

[kufo]

If using LAV will it be possible to get the CUDA acceleration using GPU as I'm not sure I want to go back to 1 day encodes?
A one day encode is even better, than a fault. We all have to do some testing when the new version will ne introduced.

[jdobbs]

If using LAV will it be possible to get the CUDA acceleration using GPU as I'm not sure I want to go back to 1 day encodes?Yes, for frame serving. You can tell LAV to use it in the Video Configuration dialog.

[jdobbs]

A one day encode is even better, than a fault. We all have to do some testing when the new version will ne introduced.I added a test mode that limits any M2TS to the first 10 minutes so testing can be done without the huge time investment.

[jdobbs]

I'd love to see NVEnc support :D Hardware decoding and encoding for 3D discs ^^I haven't been following NVEnc, since my NVIDIA video card is older. How do you use it now? Via FFMPEG?