Problem with BD-Rebuiler

[TatanScorp]

I keep getting the message H.264(MPEG-4AVC) encoder has stopped working Failed video encode aborted

[gonca]

System overclocked?
Temps OK?

[TatanScorp]

Temps OK
System is overclocked to 4.6

[TatanScorp]

I use DVD-Rebuilder with setup fine with ProCoder 2

[Groucho2004]

I keep getting the message H.264(MPEG-4AVC) encoder has stopped working Failed video encode aborted
Post your problems in the BD Rebuilder bug report thread. Creating new threads for every little issue does not draw more attention.

[Groucho2004]

I use DVD-Rebuilder with setup fine with ProCoder 2
That doesn't mean anything. Put your CPU back to stock speed and try again.

[gonca]

That doesn't mean anything. Put your CPU back to stock speed and try again.

Try what Groucho2004 suggested

[Ch3vr0n]

x264 is an exteremly cpu intensive application. The slightest instability due to an overclock can cause it to fail. It has happened in the past. In pretty much ALL cases where it happened, the users scaled back their overclock (or removed it completely) and the problem went away. Scale back your OC, pretty much your only choice

[jdobbs]

The answer is exactly as recommended by Groucho2004 and Ch3vr0n. Other overclock stability tests (like Primexx) aren't good enough. A high-intensity encode with X264 is the only real test of system stability.

[TatanScorp]

I put Comp back to Stock and reinstalled all the software and am still getting the same message from Windows. BD shows Current Progress 100% and quits at Overall Progress "Failed Video Encode aborted

[Ch3vr0n]

Then provide an encode log and inspect results in the debug thread. We can't help you further without a full log. And keep your system at stock or a lower of.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[RobertM]

If it's at stock speed and it still fails then I'd go with a bad rip.

[TatanScorp]

I think you are right cause another disk is working "Blade Runner" Gran Torino is giving me fits

[jdobbs]

I'd still say it is a system instability. More often than not it is heat related. You may want to look at your CPU heatsink and see if it is clogged with dust. A bad rip may be possible, I guess -- but of all reports with that error, I'm pretty sure 100% were from system issues.

[TatanScorp]

I'm using a Thermalright Archon with push pull fan setup. My system doesn't overheat, ever. It's always within Intel specs for my Ivy chip.
How do I check for system instability?

[gonca]

I use a H100 with push pull. Every so often I have to clean it to keep the temps down. How do you know your system doesn't overheat, cpu, ram, drives, etc.
I responded to your initial post with a clue that you were overclocked, and asked about your temps. Monitor them during the encode to make sure. Even better, clean your fans,all of them, and your heatsink.

[jdobbs]

I'm using a Thermalright Archon with push pull fan setup. My system doesn't overheat, ever. It's always within Intel specs for my Ivy chip.
How do I check for system instability?It's possible other motherboard components or memory might cause instability. But most of the time it's the CPU.

[TatanScorp]

Does any og this help?

----------------------
[03/19/15] BD Rebuilder v0.50.04
[18:46:47] Source: GRAN_TORINO_00100
- Input BD size: 27.67 GB
- Approximate total content: [01:56:34.779]
- Target BD size: 23.05 GB
- Windows Version: 6.1 [7600]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[18:46:47] PHASE ONE, Encoding
- [18:46:47] Processing: VID_00004 (1 of 1)
- [18:46:47] Extracting A/V streams [VID_00004]
- [18:50:26] Reencoding video [VID_00004]
- Source Video: VC-1, 1920x1080
- Rate/Length: 23.976fps, 167,707 frames
- Bitrate: 25,467 Kbs
- [18:50:26] Reencoding: VID_00004, Pass 1 of 2
- Encode failed. Aborting.
- BD-Rebuilder v0.50.04
- Windows Version: 6.1 [7600]
- Working Path Free Space: 425.86GB
- AVISYNTH Version: 2.5.8.0, Ok
- LAVFILTERS: Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
++++++++++++++++++++++++++++++++++++++
[Status]
LABEL=GRAN_TORINO
VERSION=v0.50.04
SOURCE_SIZE=29708101632
SOURCE_VIDEO_SIZE=29708101632
TARGET_SIZE=24746393600
REDUCTION=.832984682311188
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=1.5
[00004]
AUDIO=10000
PGS=10001000
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=24746393600
RATE=25467
SPLITS=1
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[18:51:00] - Failed video encode, aborted

[RobertM]

Did you rip it again? If not, rip it again. Otherwise, rip it again.

[TatanScorp]

I don't get it. I'm still getting the errror message "H.264(MPEG-4AVC) encoder has stopped working Failed video encode aborted"
Here's the I don't get it part, I installed Handbrake and use the exact same enoder H.264 and it encodes just fine, with my CPU overclocked to and overclocked memory plus hyper threading turned on and same rip.
I wish I could get BD-Rebuilder to work but it hates my sysyem:) If it matters I'm using Intel HD Graphics

[jdobbs]

It's not BD-RB. That error is coming from X264. BD-RB just recognizes that it is happening and reports the error that X264 provided.

Your log shows you are using Directshow, so the graphics card shouldn't matter.

Try this;

When you run an encode, the command that was used is stored in a file called LASTCMD.TXT in the folder containing BD Rebuilder.

Open a DOS Command window and copy & paste the command (from LASTCMD.TXT) into it. Then run it and post the result.

I just noticed from your log that the encode is failing at about 1 minute into the encode. That's a little odd if it is a stability problem (normally you'd see it run for a few minutes before it fails, unless it is really unstable). Also post the contents of VID_00004.AVS so I can see if there is anything odd there.

[TatanScorp]

Well I re-installed BD-Rebuilder and everything else and it worked. I uninstalled Hanbrake to see if it put something on my computer that got BD working but BD-Rebuilder just finished re-encoding and all went well. go figure.

[jdobbs]

Well I re-installed BD-Rebuilder and everything else and it worked. I uninstalled Hanbrake to see if it put something on my computer that got BD working but BD-Rebuilder just finished re-encoding and all went well. go figure.Hmm.... I guess I'll have to mark that one up to voodoo.

[TatanScorp]

Well I spoke to soon cause now I'm getting the same error message. Something to do with kernelbase.dll

"C:\BD_Rebuilder\tools\x264.exe" "E:\1 WORKING\WORKFILES\VID_00004.AVS" --preset medium --bluray-compat --b-pyramid none --weightp 1 --qpmin=0 --bitrate 25465 --level 4.1 --qpfile "E:\1 WORKING\WORKFILES\VID_00004.CHP" --sar 1:1 --aud --nal-hrd vbr --pic-struct --vbv-bufsize 30000 --keyint 24 --min-keyint 1 --ipratio 1.1 --pbratio 1.1 --vbv-maxrate 35000 --threads auto --slices 4 --thread-input --stats "E:\1 WORKING\WORKFILES\VID_00004.AVS.264.stats" --pass 1 --output NUL

VID_00004.AVS.264 has 0 bytes in it, I guess blank
I have a Vid.00004 no AVS

#Created by BD Rebuilder - v0.50.05
DirectshowSource("D:\GRAN TORINO\BDMV\STREAM\00004.m2ts", fps=23.976, framecount=167707, audio=false)
ConvertToYV12().AssumeFPS(24000,1001)

Why would X.264 be a problem with BD-Rebuilder but not Handbrake?

[TatanScorp]

Well it's working now again. Before last time I added the AviSynth SupTitle dll's four of em into the Avisynth plugin folder after BD-Rebuilder was working and I git the X264 error message. I took them out now and BD-Rebuilder is working again. BD-Rebuilder has an option in settings for Sub titles and I can't use it cause it call's for one of the dll's in the AviSynth SubTitle plugin folder.

[jdobbs]

Well it's working now again. Before last time I added the AviSynth SupTitle dll's four of em into the Avisynth plugin folder after BD-Rebuilder was working and I git the X264 error message. I took them out now and BD-Rebuilder is working again. BD-Rebuilder has an option in settings for Sub titles and I can't use it cause it call's for one of the dll's in the AviSynth SubTitle plugin folder.With BD-RB you can put those DLLs anywhere, and then browse to them. But I'm not sure it will make a difference -- as I have all 4 of them installed in the AVISYNTH plug-in folder and it's working fine for me.

I'd download the SupTitle package again if I were you. It sounds like they might be corrupt.

What you are describing would explain why X264 was failing. It was probably at the first point that a forced subtitle was present in the stream (a minute or so into the video) -- and then SupTitle failed, making AVISYNTH kick an error which caused the X264 failure.

[Groucho2004]

Well it's working now again. Before last time I added the AviSynth SupTitle dll's four of em into the Avisynth plugin folder after BD-Rebuilder was working and I git the X264 error message. I took them out now and BD-Rebuilder is working again. BD-Rebuilder has an option in settings for Sub titles and I can't use it cause it call's for one of the dll's in the AviSynth SubTitle plugin folder.
You might want to try this tool (http://forum.doom9.org/showthread.php?t=170647) to check if something fishy is going on with your Avisynth install and/or plugins.