BD Rebuilder Beta - Bug Reports Only

[Toilet-Duck]

Listen. You don't want to post logs, you don't want to post INSPECT results -- in other words you don't want to help. All you want to do is complain and post nonsense trying to make it seem as if you are right.

Here's a news flash for you: You're not.

I, and the others here, have no time for this nonsense. Either do what I say to correct your issue... or go away. Reinstall the apps I said.

It's simple. Your issue is YOUR issue. It affects no one else. C'mon -- a little logic wouldn't hurt, don't you think? All the "sighing" in the world doesn't make you any less wrong. It just makes you look more foolish.


My testimonials are the logs in its own right, but you and the likes don't seem to accept or care what i have found out about bdrb !!

Posting logs have done lil to no good in the past for me, been there done that !!

It alway's comes down to user error to you poeple !!

Well, iam done wasting time to search for logs everywhere just to get ignored / disregard by you and the like eventually !!

No, be glad i took atleast the time to post my bdrb experience/results so that you and others that may be in the same boat like me might learn something from my experience ...

Its not about right or wrong, but about comon sense !!

[gonca]

To whom it may concern (Toilet Duck)
Using latest BD_RB ... no issues
reporting issues -- I have reported issues in the past with the appropriate logs and jdobbs responded appropriately.
Is this a new user name your using because your writing style looks familiar, like the person who kept bringing up old change logs for DVD_RB to prove that it still has issues with multi angle titles

[jdobbs]

My testimonials are the logs in its own right, but you and the likes don't seem to accept or care what i have found out about bdrb !!

Posting logs have done lil to no good in the past for me, been there done that !!

It alway's comes down to user error to you poeple !!

Well, iam done wasting time to search for logs everywhere just to get ignored / disregard by you and the like eventually !!

No, be glad i took atleast the time to post my bdrb experience/results so that you and others that may be in the same boat like me might learn something from my experience ...

Its not about right or wrong, but about comon sense !!Your posts are useless. Your attitude sucks. You want to help in any way except post what is needed. Logs ignored? You've made a total of 5 posts -- all worthless rants -- and have never posted a single log.

Happy to see you go. Don't let the door hit you on your way out.

[Mikeyb123]

I hope this isn't too off topic but I wanted to apologize to jdobbs for the crass behavior of Toilet-Duck. He seems incapable of following directions from people who are trying to [I]help[I] him. If he isn't willing to take their advice then why bother asking for help? In every case where I have had a problem with BD-RB it was self inflicted and jdobbs bends over backwards to assist with problems. Then to be treated like he is some clueless noob. Have some respect for this very talented individual who has given of himself and created a brilliant program, not once, but twice in BD-RB and DVDRebuilder. Believe me, in every sense this is your problem. If you aren't going to take his advice then leave him alone!

[Ch3vr0n]

Also, if the app is so perfect why i do read many posts from members which not the least of all "chevron" stating that he/she went back to an previous beta release because of problems that has occured and couldnt be resolved unless he went back to an older build to accomplish an succesfull project.

Weird enough, i didn't read any reply from you @chevrons telling that his/her misconfigured system must be causing this !!



cherriepoppers,
toiletduck

I stated NO SUCH THING. I said something on YOUR system was causing the out of sync issues, not on mine. I also never said i went back to an older version to "fix" things, going back doesn't fix things, it avoids issues. Wanna know why i never said that, perhaps because i don't have out of sync issues and never have gone back.

Jdobbs doesn't have to tell me it might be because of my misconfigured system, because my system ISNT misconfigured. Don't twist my words mate. My helper aps are the correct versions, properly configured as per instructions, no additional codec packs installed and BDRB runs flawlessly. You'll end up on the losing side.

Now i'll say this one last time.

If you have sync issues then

1) post a log from an encode that has those issues
2) post the inspect results from BDRB > Help > Inspect

We can't help you until you provide us with the info we need to do it. If you still don't want to, well. Then as Jdobbs said, don't let the door hit you on the way out. Cause you'll have to update to a version beyond 47.07 eventually. It won't last forever.

[Lathe]

Just a quickie... Out of curiosity, I opened the vid.avs file during the first pass of an encode (perennially curious, what can I say :) ) Anyway, in that it says that it has loaded the frimsource.dll...??? Is that something that BDRB just does every time? I'm not processing a 3D film; it's just an old 2D Blu-ray. I'm not resizing or doing anything out of the ordinary; I was just really curious as to why it loaded this dll.

Oh, and I almost ALWAYS use internal LAVF for everything.

I guess I should add this too, just for clarity:

#Created by BD Rebuilder - v0.48.05 (beta)
LoadPlugin("C:\EXECUTABLES\BD-RBV04805\BD_Rebuilder\tools\frimsource.dll")
FRIMSource(codec="h264",filename="C:\_______MEDIA\__TSMUXER\BDMV\STREAM\00000.m2ts",
container="ts",platform="sw",num_frames=182568,cache=24)
ConvertToYV12().AssumeFPS(24000,1001)

Thanks!

[jdobbs]

Just a quickie... Out of curiosity, I opened the vid.avs file during the first pass of an encode (perennially curious, what can I say :) ) Anyway, in that it says that it has loaded the frimsource.dll...??? Is that something that BDRB just does every time? I'm not processing a 3D film; it's just an old 2D Blu-ray. I'm not resizing or doing anything out of the ordinary; I was just really curious as to why it loaded this dll.

Oh, and I almost ALWAYS use internal LAVF for everything.

I guess I should add this too, just for clarity:

#Created by BD Rebuilder - v0.48.05 (beta)
LoadPlugin("C:\EXECUTABLES\BD-RBV04805\BD_Rebuilder\tools\frimsource.dll")
FRIMSource(codec="h264",filename="C:\_______MEDIA\__TSMUXER\BDMV\STREAM\00000.m2ts",
container="ts",platform="sw",num_frames=182568,cache=24)
ConvertToYV12().AssumeFPS(24000,1001)

Thanks!BD-RB always creates an AVS, even if it isn't used. When LAVF is selected, it is created with FRIM. That's because LAVF is the default encode method when Directshow isn't installed. But... unless you are doing some kind of special resizing (like 16:9 conversion or widen) the AVS isn't used at all.

Just for the sake of better encoding, I'll look at changing it so that it uses Directshow when it is available and only FRIM when it isn't. Either way it doesn't matter 90% of the time -- because LAVF mode doesn't use it anyway.

[AmigaFuture]

Update to last post about my SSD. It seems to be related to heat(?). Usually my SSD is cool, but it is between 2 HDDs and I was keeping it pretty active... If repeatable, I'll update.

[jedihyte]

Hello,

When I add to the batch queue one or more jobs with the same quality settings, I see no issues. What I am having issues with if I add to the batch queue one quality setting, but then add another job with a different quality setting. The quality setting for one does not stick.

For example,

I added Ghostbusters with a Full backup, BD-25, Highest Quality to the batch. It started on the correct quality setting. See log (I aborted on purpose):

[22:33:13] PROCESSING BATCH FILE [1]
----------------------
[09/21/14] BD Rebuilder v0.48.05 (beta)
[22:33:14] Source: GHOSTBUSTERS
- Input BD size: 32.45 GB
- Approximate total content: [01:59:31.454]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]

>>> - Quality: Highest (Very Slow), ABR

- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[22:33:14] PHASE ONE, Encoding
- [22:33:14] Processing: VID_00002 (1 of 3)
- [22:33:14] Extracting A/V streams [VID_00002]
- [22:33:36] Reencoding video [VID_00002]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 6,863 frames
- Bitrate: 5,906 Kbs
- [22:33:36] Reencoding: VID_00002, Pass 1 of 1
[22:33:38]PHASE ONE aborted by user request
[22:33:38] BATCH ABORTED...
==========================
[22:33:39] END - BATCH SEQUENCE

But then I added another job for another blu-ray with Automatic settings, which sets it to Good Quality.
Batch tab looks like this:

+ GHOSTBUSTERS, Full-Backup, BD-25, Highest Quality
+ GODZILLA_1988, Full-Backup, BD-25, Good Quality

When I start the Batch Backup Ghostbusters starts encoding on Good Quality settings and not Highest Quality (I aborted):

[22:34:19] PROCESSING BATCH FILE [1]
----------------------
[09/21/14] BD Rebuilder v0.48.05 (beta)
[22:34:19] Source: GHOSTBUSTERS
- Input BD size: 32.45 GB
- Approximate total content: [01:59:31.454]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
>>> - Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Encoding cancelled.

[varekai]

Posting logs have done lil to no good in the past for me, been there done that !!
Are these your old logs? Zzzzzzzz...
http://i59.tinypic.com/2llow90.jpg

[varekai]

@jedihyte

Just a thought, maybe a bit awkward, but have you tried this:

--> Save each job to "Save Project" file (.epr)
--> Open project one by one and "Add Current Project to Batch Queue"

[Toilet-Duck]

If he isn't willing to take their advice then why bother asking for help?

I never asked for help, nor did i expect help from this place !!
I just wanted to tell the people what to expect from certain builds!!

Hell, i have pretty much solved every darn issue i have had with bdrb myself pretty much !!

Thanks but no thanks


I stated NO SUCH THING. I said something on YOUR system was causing the out of sync issues, not on mine. I also never said i went back to an older version to "fix" things, going back doesn't fix things, it avoids issues.

You never EVAR went back to an older build to avoid issues with the last build you dare to say !!? ...

Here's is what you NOT ONLY HAVE SAID/WROTE but have DONE to workarround an isue .. and i direct quote ↓

And pay attention to the line "swapped to 48.02" !!!

well it refuses on my end with 48.03 nothing changed except replacing the folder contents with that of the zip by copy/paste&replace. Copying the folder to like C:\ root doesn't help. Same trying a different ISO. Same thing reading directly from optical drive. Swap to 48.02. Problem solved on both iso reading and optical drive.

↑ be it as it may, one can cleary deduce from the logs you went from 48.03 to 48.02 for whatever reason may be !!


EDIT:

Hello,

When I add to the batch queue one or more jobs with the same quality settings, I see no issues. What I am having issues with if I add to the batch queue one quality setting, but then add another job with a different quality setting. The quality setting for one does not stick.

For example,

I added Ghostbusters with a Full backup, BD-25, Highest Quality to the batch. It started on the correct quality setting. See log (I aborted on purpose):



Now , i dont have any logs to back it up ! But same happend to me with bdrb 48.xx, i just forgot to add it to an long list with issues !!!

just happened to have done this same movie "ghost busters" in batch mode allong with 4 other movies using bdrb 47.07 succesfully .

The quality settings depending on the content (extras etc) of the bluray disks variated from high CQ to Highest and did stick in batch ..

Only thing is when you change any settings in option menu, you have to redo the whole thing and add new batch queue's !!

Stick to 47.07 for the time beeing i suggest..



cherriepoppers,
toiletduck

[Ch3vr0n]

I warned you not to twist my words, or you'd end up on the losing side. So without further adue lets get started shall we?


Here's is what you NOT ONLY HAVE SAID/WROTE but have DONE to workarround an isue .. and i direct quote ↓

And pay attention to the line "swapped to 48.02" !!!


Twist 1: If you had actually bothered to read the previous & followup replies by me and jdobbs you would have read that that issue was caused by a change JDOBBS made to BDRB by making frim the default rendered. IT WAS NOT AN ISSUE WITH MY SYSTEM

DING DING DING: you lose

Twist 2:

↑ be it as it may, one can cleary deduce from the logs you went from 48.03 to 48.02 for whatever reason may be !!

A REPLY is NOT A LOG. A log is what BDRB output's during encoding. Here's a small example

[09/01/14] BD Rebuilder v0.48.02 (beta)
[23:30:55] Source: DIVERGENT
- Input BD size: 44,69 GB
- Approximate total content: [04:34:45.388]
- Target BD size: 22,95 GB
- Windows Version: 6.0 [6002]
- MOVIE and MENUS mode enabled
- Auto Quality: Good (Very Fast), Two Pass
- Output folder: C:\BDRB Rebuilds\
- Decoding/Frame serving: DGDecNV [2-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640

Hmmz, what's that. Oh wait, an ENCODING LOG. Where did i find that? Oh wait in the file called BD-REBUILDER.LOG


DING DING DING. You lose AGAIN



EDIT:



Now , i dont have any logs to back it up ! But same happend to me with bdrb 48.xx, i just forgot to add it to an long list with issues !!!


Yes you do. Every disc you run BDRB writes the encoding output in a file called BD-REBUILDER.LOG which is located in your directory you specified under "Working Path"


Only thing is when you change any settings in option menu, you have to redo the whole thing and add new batch queue's !!


That's because those changes have an impact on disc output. They don't change any values on projects already added to the batch queue, only on NEW jobs you add to the queue


Stick to 47.07 for the time beeing i suggest..

Bad suggestion, 48.05 works just fine if your system's helper tools are correctly configured.

But then again we don't know yours are do we? As you still havent provide a single encoding log or inspect results so we can verify they are. If your helper tool settings would be correctly configured and you had sync issues with 48.05 THEN it could potentially be a bug (or in most cases usually a corrupt rip). However we can't verify they are or arent until you provide that encoding log and inspect results.


So quit beating around the bush and ranting.

Provide that encoding log, (from any version that "makes" you have sync issues) and the inspect results. Then come back, until you do. Quit polluting the debug thread with an issue that's likely not even a bug.

* closes door behind you *

[jdobbs]

Typical response. I've seen a hundred times.

I'm wrong and everyone knows it, so instead of admitting it I'm going to start writing multiple long diatribes explaining how right I am. I may even make up things or modify the facts to support me. No matter what, I have to somehow make it seem as if I'm right. The entire world may disagree with me but I'm obviously right. I didn't post any logs or useful information -- so I'll start calling my "testimonials" logs. I know my system is misconfigured because I did it my self -- so I can't post logs or inspect results. But that couldn't be the issue -- because I'm obviously right. The version works for everybody on the entire planet except for me -- but apparently they're too stupid to know it's not working, because I'm clearly right.Well, iam done wasting time to search for logs everywhere just to get ignored / disregard by you and the like eventually !!Promises, promises. I thought you were going away... but I should have known better, because you are convinced that somehow, despite the overriding and obvious facts -- you must be right. ????

Just go away. You are annoying and a burden to an otherwise productive thread. Every post makes you look a little more foolish.

Oh... and by the way, maybe you should learn that there is a such thing as a "paragraph". It's a new-fangled invention that combines related thoughts into a single unit to add clarity.

[jdobbs]

Here's where I must put on my moderator hat. The thread has been pulled way off topic (Toilet-Duck's responses have even managed to get me to violate the rule).

Now, though, I need to correct that. Any more off-topic discussion will be dealt with appropriately. Strikes may follow.

[jdobbs]

@jedihyte

I'll do some testing with BATCH processing and see if I can repeat your issue. It sounds like the quality variable isn't being properly read from the BATCH settings and it is keeping what was last set. I did some changes to the QUALITY variable recently -- so it's likely I've screwed it up somehow.

[DarWun]

@jedihyte

I'll do some testing with BATCH processing and see if I can repeat your issue. It sounds like the quality variable isn't being properly read from the BATCH settings and it is keeping what was last set. I did some changes to the QUALITY variable recently -- so it's likely I've screwed it up somehow.

I have seen the same behaviour. I posted about it back in January. Just in case it includes anything that might be useful in pinpointing the bug, this is a link to the post:

http://forum.doom9.org/showthread.php?p=1662166#post1662166

[jdobbs]

I have seen the same behaviour. I posted about it back in January. Just in case it includes anything that might be useful in pinpointing the bug, this is a link to the post:

http://forum.doom9.org/showthread.php?p=1662166#post1662166Thanks. I went through the code. This isn't something new -- it looks like it has been around awhile. I've fixed it for the next release.

[pretsam]

I recently tried to make a BD25 of 300 Rise of an Empire and Edge of Tomorrow, they both are out of sync. When I mux both movies to a .iso before I encode they are still fine but after BDRebuilder finishes they are out of sync. Both use DTSHD tracks. So, I also tried another movie I did that had TrueHD recently and it was fine. I tried both movies again and same results with being out of sync. Anyone experience this recently? Everything has been working fine for a long time but just noticed this recently so I went back to check other movies I did also but they all seem fine. I encoded from 2 different USB drives both times back to a sata. Thanks

[Options]
VERSION=0.48.0.2
MODE=3
ENCODE_QUALITY=5
ONEPASS_ENCODING=2
AUTO_QUALITY=0
QUICK_EXTRAS=0
TARGET_SIZE=24500
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=chi;eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=1
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=0
MOVIE_ONLY_LOOP=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
AUTO_BLANK=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24500
PRIORITY_CLASS=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
AUTO_BURN=0
RESIZE_1440=0
OUTPUT_3D=0
RESIZE_720=0
NEROAAC=0
SUPTITLE=0
IGNORE_3D=0
OUTPUT_SBS=0
VERBOSE_STATUS=1
ENCODER=0
DGDECIM=0
FRIMSOURCE=0
DECODER=1
[Paths]
SOURCE_PATH=E:\
WORKING_PATH=K:\BDREBUILD\

[Status]
LABEL=EDGE.OF.TOMORROW
VERSION=v0.48.02 (beta)
SOURCE_SIZE=27701661696
SOURCE_VIDEO_SIZE=27701661696
TARGET_SIZE=25690112000
REDUCTION=.927385233489785
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=chi;eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=-1
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00000]
AUDIO=1
PGS=1
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=25690112000
RATE=22356
SPLITS=1
NSIZE=0
FLINK=0
MLINK=0

[Status]
LABEL=300.RISE.OF.AN.EMPIRE
VERSION=v0.48.02 (beta)
SOURCE_SIZE=26889486336
SOURCE_VIDEO_SIZE=26889486336
TARGET_SIZE=25690112000
REDUCTION=.955396160379819
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=chi;eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=-1
SSIF_MODE=0
QUICK=0
ENCODE_STEP=0
COMPLETED=1
REBUILD_COMPLETE=1
[00000]
AUDIO=1
PGS=1000
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=25690112000
RATE=24873
SPLITS=1
NSIZE=0
FLINK=0
MLINK=0


[09/22/14] Checking System Settings
- BD-Rebuilder v0.48.02 (beta)
- Windows Version: 6.1 [7601]
- Working Path Free Space: 22.10GB
- AVISYNTH Version: 2.5.8.0, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[09/22/14] Systems Settings Check complete

[jdobbs]

@Toilet-Duck

Your were instructed to get back on topic by a moderator and were warned that a strike would follow. You ignored the instruction. Your posts have been removed and you have been issued a strike.

Stop now, or receive another strike.

[jdobbs]

I recently tried to make a BD25 of 300 Rise of an Empire and Edge of Tomorrow, they both are out of sync. When I mux both movies to a .iso before I encode they are still fine but after BDRebuilder finishes they are out of sync. Both use DTSHD tracks. So, I also tried another movie I did that had TrueHD recently and it was fine. I tried both movies again and same results with being out of sync. Anyone experience this recently? Everything has been working fine for a long time but just noticed this recently so I went back to check other movies I did also but they all seem fine. I encoded from 2 different USB drives both times back to a sata. Thanks Something is interfering with FFDSHOW. It's usually caused by another software package intercepting/overriding it or installation of a CODEC pack. Sometimes other software will make changes and not have the decency to tell you they are doing so.

Uninstall FFDSHOW AND HAALI and reinstall them. I would also advise you to update to the current version of BD-RB (see the first post of this thread). v0.48.2 wasn't a very solid release and was only out for four days before being replaced.

I've done "300 - Rise of an Empire" with no issues... but I'll run it again just to be sure. "Edge of Tomorrow" hasn't been released here yet.

[Sharc]

I recently tried to make a BD25 of 300 Rise of an Empire and Edge of Tomorrow, they both are out of sync. .......
Have your sources been pre-processed?

[jdobbs]

I recently tried to make a BD25 of 300 Rise of an Empire and Edge of Tomorrow, they both are out of sync. When I mux both movies to a .iso before I encode they are still fine but after BDRebuilder finishes they are out of sync. Both use DTSHD tracks. So, I also tried another movie I did that had TrueHD recently and it was fine. I tried both movies again and same results with being out of sync. Anyone experience this recently? Everything has been working fine for a long time but just noticed this recently so I went back to check other movies I did also but they all seem fine. I encoded from 2 different USB drives both times back to a sata. Thanks Something is interfering with FFDSHOW. It's usually caused by another software package intercepting/overriding it or installation of a CODEC pack. Sometimes other software will make changes and not have the decency to tell you they are doing so.

Uninstall FFDSHOW AND HAALI and reinstall them. I would also advise you to update to the current version of BD-RB (see the first post of this thread). v0.48.2 wasn't a very solid release and was only out for four days before being replaced.

I've done "300 - Rise of an Empire" with no issues... but I'll run it again just to be sure. "Edge of Tomorrow" hasn't been released here yet.I ran "300 - Rise of an Empire using your settings. It came out fine with no sync issues.

I think the reinstall should fix the problem -- as I can't repeat it. If you have any CODEC packs installed, I'd highly suggest you get rid of them, as they are know to cause issues like this.

[jdobbs]

I have updated the first post of this thread with a link to the most recent version of BD-RB (v0.49.01). Changes for this release:- Added H.264/HEVC encoding to the ALTERNATE
output routines. You can now backup a BD
to an MKV file using 30-35% less space
than H.264/AVC while maintaining the same
level of quality. Note: Playback of the
HEVC MKV file via MPC and some other
players may require installation of an HEVC
capable directshow filter. On such filter
can be found with a search for "libde265".
- Added a new "IMPORT_HEVC_INTACT" hidden
option. It will prevent conversion of HEVC
to H.264 during import. This should only
be used if you have a functional Directshow
filter for HEVC and M2TS splitting installed
on your system. See step 1A of README.TXT.
This hidden option's purpose is to prevent
loss of quality by reencoding twice (once
during import and once during backup).
- Added a new option to the Import/Quick-Play
setup dialog. You can now instruct BD-RB
to attempt to find menu background audio to
be used during DVD imports
- Corrected an issue in which resizing of an
interlaced source to progressive could,
under certain circumstances, use the wrong
default deinterlacing method.
- Made changes so that an existing undefined
language during DVD import will default to
"eng". This will prevent removal of those
an undefined audio track when "Import only
languages selected in SETUP dialog" is set
in the IMPORT setting dialog. Note: Some
commercial DVD discs fail to set a lang).
- Added a check so that primary video sources
that are detected as 480p/29.97 and 576p/50
are treated as 480i/576i to make them legal
for BD usage.
- Corrected an error in which 1080p subtitles
could be resized, even though the source is
already 1080.
- Corrected an issue in which the state of
the "Auto Quality" setting was overridding
the quality selection saved in a BATCH job.
- Upgraded HCENCODER (for DVD encodes) to the
most recent version. The older version is
no longer needed, as FFVideoSource is no
longer supported.
- Updated the included version of MKVMERGE to
an new version that supports H.265 (v7.1.0).
- Updated the included version of MKVEXTRACT
to an new version (v7.1.0).
- Updated the included version of X264.EXE to
the latest release (r2479).
- Updated the included version of X264-64.EXE
to the latest release (r2479).
- Other minor corrections and cosmetic fixes.Note that there have been changes to the installation procedures in the first post of this thread (Step 2) and the README.TXT file included in the ZIP file. BD-RB now supports directshow via LAVFilters as an alternative to HAALI and FFDSHOW. Also please note, that if you plan to use HEVC/H.265 in any way -- you really should install LAVFilters.

It's probable, unless some unforeseen issue arises, that future "installable" versions of BD-RB will install LAVFilters as its default.

[Ch3vr0n]

Yay, a new version :) First line on first post needs an update though ;) Sais "current version 48.05" :)

[jdobbs]

Yay, a new version :) First line on first post needs an update though ;) Sais "current version 48.05" :)Thanks. You'd think that as many times as I've updated that first post I'd learn how to do it right... ;)

[HWK]

jdobbs, if you install lav filters and launch BD-RB it ask user to configure system to use directshow filters, however even when BD-Rb run as admin it fails to configure system properly.

Launch again it does same thing.

On a related note I think mention of ffdshow is no longer relevant for time being on this screen

http://i57.tinypic.com/2zeigyw.png

[jdobbs]

jdobbs, if you install lav filters and launch BD-RB it ask user to configure system to use directshow filters, however even when BD-Rb run as admin it fails to configure system properly.

Launch again it does same thing.

On a related note I think mention of ffdshow is no longer relevant for time being on this screen

http://i57.tinypic.com/2zeigyw.pngUghh... I guess I missed that. I'll post another version shortly. In the meantime I disabled the download.

[jdobbs]

I can't repeat the error... Do you have FFDSHOW and HAALI installed, I'm not sure what you mean by "not relavent"?

When I right click on it and run it as admin (when I force this to pop up) it configures correctly and works ok?

Can you give me a specific set of steps to repeat it?

[jdobbs]

Is anyone else getting this error with the new version?

[HWK]

NO, ffdhow here and haali here. I am assuming if you had installed in past then this wouldn't happen.

Since I never installed before I am having issue.

[pretsam]

Have your sources been pre-processed?

None of them were.

I ran "300 - Rise of an Empire using your settings. It came out fine with no sync issues.

I think the reinstall should fix the problem -- as I can't repeat it. If you have any CODEC packs installed, I'd highly suggest you get rid of them, as they are know to cause issues like this.

No, other CODEC packs were installed that I've been aware of. But I did uninstall/reinstall HAALI and FFDSHOW and installed the new ver of BDR. In the process of testing now, will report back.

[soneca]

Is anyone else getting this error with the new version?

I could try but the download is disabled.

[HWK]

he disabled the download, In order to produce you need machine where ffdshow was never installed.

[soneca]

Ok, so it's not the case here.

[jdobbs]

NO, ffdhow here and haali here. I am assuming if you had installed in past then this wouldn't happen.

Since I never installed before I am having issue.No. I uninstalled and reset it to match a pristine system -- and it still works fine for me.

[jdobbs]

I could try but the download is disabled.I've reenabled the download... try it.

It sure seems to be working for me. If FFDSHOW isn't installed, it shouldn't even do that check????

[HWK]

Ok, let me check most likely anti virus is being nuisance.

[Update]

Indeed it was the case, sorry for trouble I may have caused.

[jdobbs]

he disabled the download, In order to produce you need machine where ffdshow was never installed.Is it possible there are some flags set in your registry that makes BD-RB think FFDSHOW is installed?

Look for HKEY_LOCAL_MACHINE\Wow6432Node\Gnu\ffdshow

[jdobbs]

Ok, let me check most likely anti virus is being nuisance.

[Update]

Indeed it was the case, sorry for trouble I may have caused.No problem. So everything is working correctly now?

[jdobbs]

None of them were.



No, other CODEC packs were installed that I've been aware of. But I did uninstall/reinstall HAALI and FFDSHOW and installed the new ver of BDR. In the process of testing now, will report back.Thanks. Keep me posted.

[HWK]

No problem. So everything is working correctly now?

so far, trying lav filters and hevc :) hopefully provide feedback once done.

[soneca]

Ok, let me check most likely anti virus is being nuisance.

[Update]

Indeed it was the case, sorry for trouble I may have caused.

:D Out of curiosity, what antivirus you using?

[HWK]

bitdefender and it is my fault since I set it to flag certain actions and forgot about it.

[jdobbs]

I'm still wondering how you would have even seen that message unless there were flags in the registry saying FFDSHOW was installed???

[Lathe]

BD-RB always creates an AVS, even if it isn't used. When LAVF is selected, it is created with FRIM. That's because LAVF is the default encode method when Directshow isn't installed. But... unless you are doing some kind of special resizing (like 16:9 conversion or widen) the AVS isn't used at all.

Just for the sake of better encoding, I'll look at changing it so that it uses Directshow when it is available and only FRIM when it isn't. Either way it doesn't matter 90% of the time -- because LAVF mode doesn't use it anyway.

Thanks kindly for the explanation. Just thought it was curious since I didn't THINK that I was using the FRIM frame server for anything that I knew of. And no, I almost never resize anything.

Oh, I think I see now what you mean. An AVS file is always made IN CASE any Avisynth stuff is required. And, at present the AVS file is created with FRIM, I see. I'm not conversant enough with this to know whether that would really make any difference, really, what makes the AVS file... I almost always choose the LAVF frame server though. Do I understand correctly that the newer version of BDRB does NOT install Direct show then and that is why it uses FRIM to create the AVS?

So, if I were to add some Avisynth code, which I sometimes do, would that really then make any difference WHAT makes the AVS file?

[HWK]

I'm still wondering how you would have even seen that message unless there were flags in the registry saying FFDSHOW was installed???

No idea, it was one of the rare occurrence.

[Lathe]

Update to last post about my SSD. It seems to be related to heat(?). Usually my SSD is cool, but it is between 2 HDDs and I was keeping it pretty active... If repeatable, I'll update.

Sort of related, I too found that the reason why my encodes were taking twice as long was because my CPU and possibly my SSD were running too hot. I changed a fan to exhaust OUT the air where I had it blowing in before, and that really did help to the extent that so far in like 4 days it has not frozen up at all, which it used to several times a day. However, Speccy tells me that the CPU is still WAY too hot, so I will have to have the guy who built it do something about that eventually. BUT... it did help my encode time a little by changing the fan. With HQ 2-Pass and all my 'Tweaks' the encode time went down from about 14 hours to a more decent 7-8, which is CLOSE to what it used to be. I'm getting at least about 6+ fps now as opposed to 2.xx.

[Lathe]

Are these your old logs? Zzzzzzzz...
http://i59.tinypic.com/2llow90.jpg

LOL Awesome! :D

[soneca]

I've reenabled the download... try it.

It sure seems to be working for me. If FFDSHOW isn't installed, it shouldn't even do that check????

Here, ffdshow installed without verification.

HEVC are using the medium preset, right?