BD Rebuilder Beta - Bug Reports Only

[Easy4Breezy]

I've also read that it is important to have the original iso or the bdmv on a different drive while extracting, could this also be something I could try?
Or doesn't make it a difference at all?
Thanks!

Oh and right before a second I read that PowerDVD could be the issue..
MPC-HD is the best alternative isn't it?

[Mark_Venture]

Just some feedback on BD Rebuilder v0.50.12

(not related to BD Rebuilder directly, but worth mentioning...) When first unzipping, Symantec Antivirus deleted X265.exe as containing a virus, THEN prompted me (no option to ignore). After fixing that (restoring and telling SAV to ignore the file from now on) I tried to run MI5 to test subs. SAV also complained about X264.exe but its pop up allowed me to ignore, and BD-RB ran fine the rest of the way.


MI5's forced subs work fine after using BD-RB v0.50.12 doing Alt Movie Only MKV.

[Easy4Breezy]

can confirm that
bitdefender also alterted a virus, but I think we can trust you ;)
the strange thing is, that it only alerts when using bdrebuilder as admin

[jdobbs]

Just some feedback on BD Rebuilder v0.50.12

(not related to BD Rebuilder directly, but worth mentioning...) When first unzipping, Symantec Antivirus deleted X265.exe as containing a virus, THEN prompted me (no option to ignore). After fixing that (restoring and telling SAV to ignore the file from now on) I tried to run MI5 to test subs. SAV also complained about X264.exe but its pop up allowed me to ignore, and BD-RB ran fine the rest of the way.


MI5's forced subs work fine after using BD-RB v0.50.12 doing Alt Movie Only MKV.My suggestion: Get a better anti-virus package. When your A/V software starts interfering with your operations -- it's no better than a virus. AVG works great -- and it is available in a freeware version. It also tells me that both X265 and X264 are safe.

You can always download X264 from here (http://komisar.gin.by/) (I always use the Komisar build). You can get the latest release of X265 from here (https://builds.x265.eu/).

[jdobbs]

Hey, I was just trying the new version with that same HEVC file (MKV) that I did before and asked about. But, it LOOKS like it is doing the exact same thing...??? After extracting the A/V files, it also began 'converting into a compatible format' Isn't this newer version simply supposed to create a Pseudo folder and THEN later during the actual encode, do whatever conversions that it needs to do?

Did I miss something...?

Yep, I just checked the Temp/Import folder, and it LOOKS like after extracting the HEVC file it is definitely creating a new x264 file.

Hmmmmm....???I just tested it again. I imported an HEVC MKV file -- and there was no conversion.

1. Are you sure the source is HEVC? It's not XVID or some other format?
2. Are you sure you are using the correct version of BD-RB?

It's easy to tell that it hasn't been converted. After the import BD-RB will show the source (in the streams list) as HEVC.

[Lathe]

I just tested it again. I imported an HEVC MKV file -- and there was no conversion.

1. Are you sure the source is HEVC? It's not XVID or some other format?
2. Are you sure you are using the correct version of BD-RB?

It's easy to tell that it hasn't been converted. After the import BD-RB will show the source (in the streams list) as HEVC.

Yeah, DL'd the newest version. It imports the HEVC which does show in the Import/Temp folder and then immediately afterward it takes a while to convert to the 'compatible' format and then creates a new, fairly large x264 file in the same folder. No big deal though... I can still use the resultant x264 file anyway, and this is only the 2nd time I've ever done this, and I don't really see myself using this particular feature very often.

I was just more curious really as to how BDRB dealt with the HEVC file, but regardless how it does it, the result is just fine.

Thanks JD!

[Lathe]

My suggestion: Get a better anti-virus package. When your A/V software starts interfering with your operations -- it's no better than a virus. AVG works great -- and it is available in a freeware version. It also tells me that both X265 and X264 are safe.

Yeah, I dumped Norton A/V about 12 years ago. The footprint and resources it used were HUGE! I've been using AVAST, which is free for years, and it NEVER interferes with anything...

[DoctorM]

A question. I have a foreign language film I'd like to rebuild using Quick Menu. Is it possible to set a default subtitle track as on or is that option only available if you use 'Movie Only'?

[jdobbs]

A question. I have a foreign language film I'd like to rebuild using Quick Menu. Is it possible to set a default subtitle track as on or is that option only available if you use 'Movie Only'?Right now it is only available in movie-only mode. I'm not sure how much work it will be, but I'll put the capability for Quick-Play mode on my to-do list.

[DoctorM]

Right now it is only available in movie-only mode. I'm not sure how much work it will be, but I'll put the capability for Quick-Play mode on my to-do list.

Thanks. I didn't know if I was doing something wrong or if it was a deliberate decision.

[colinhunt]

jdobbs, can you give me your educated guess on what might be causing the following peculiar problem?

Encode (Full Backup, with some audiotracks usually blanked out) runs and finishes without reported errors in log but output is undersized; sometimes by a couple of gigabytes, sometimes by more than 10 gigabytes. On inspection, one or more .m2ts files are clearly smaller than they should be. Target Size being BD-25 or Custom has no effect on this; problem occurs with both settings.

MediaInfo reports the expected, original runtime for undersized .m2ts files, but playing the files shows that the movie or episode in question is cut short. For example, a 45-minute episode of a TV show runs for 24 minutes and ends without warning in the middle of a sentence. Opening the output in BDInfo and selecting the corresponding playlist displays the shorter, actual runtime for both the playlist (for example 00501.mpls) and the linked .m2ts file.

This has happened several times in the past couple of months, on 0.50.11 and now on 0.50.12. It is not caused by a bad rip; I've played the source files on software players to check. There's nothing out of the ordinary in BD-REBUILDER.LOG, no mention of any issues or errors what-so-ever. Inspect gives me 10 x OK, no warnings.

Any ideas, theories?

[jdobbs]

Are you overclocked? The only thing I could imagine is if X264 is crashing mid-encode -- and the only time it ever seems to crash is on an overclocked system that is pushing it a bit too far. You might also want to try cleaning your heatsink -- as overheating is usually the issue.

[colinhunt]

Are you overclocked? The only thing I could imagine is if X264 is crashing mid-encode -- and the only time it ever seems to crash is on an overclocked system that is pushing it a bit too far. You might also want to try cleaning your heatsink -- as overheating is usually the issue.
Thanks for the reply. No, not overclocked at all. I'll check for overheating. But wouldn't x264 crashing in mid-encode result in "Encoding failed" error or something like that?

update: 65 minutes of Prime95, all cores at 100% the whole time. CoreTemp reports the hottest core reached a temp of 61 degrees Celsius, less than half an hour into the run. TjMax for Xeon X5660 is 96 degrees Celsius. I don't think this rig is anywhere near overheating.

[jdobbs]

Prime95 does not compare to X265. If you go back through this thread you'll find examples too numerous to mention in which Prime95 found nothing but the processor was overheating with X264.

I'm not saying overheating is your problem -- but I am saying Prime95 won't find it if it is.

BTW, maximum operating temperature for a Xeon X5660 (from what multiple sites say) is 81.3 degrees C.

[colinhunt]

Prime95 does not compare to X265. If you go back through this thread you'll find examples too numerous to mention in which Prime95 found nothing but the processor was overheating with X264. I'm not saying overheating is your problem -- but I am saying Prime95 won't find it if it is. BTW, maximum operating temperature for a Xeon X5660 (from what multiple sites say) is 81.3 degrees C.
Be that as it may, I don't think this is related to overheating. I've done several successful backups during the past couple of months, too. And wouldn't x264 crashing stop the entire backup process with an error message in the log?

[jdobbs]

Be that as it may, I don't think this is related to overheating. I've done several successful backups during the past couple of months, too. And wouldn't x264 crashing stop the entire backup process with an error message in the log?Not necessarily. A crash of that type can prevent the executing program from returning an error code. I've seen it happen exactly like this before in cases of overclocking/overheating. I'd guess there may be other things that could cause it as well (such as memory failure/overheating, etc).

All I can say is that in every case I can remember where this symptom was reported it was related to system instability -- not BD-RB -- and no one else is reporting this issue right now, which seems to support that theory. That's pretty much all I have to go on.

[Lathe]

I was curious (again...) how would BDRB handle a movie file that had a 7.1 FLAC lossless audio file? Say that I imported it. What would it do with the audio?

I KNOW that this is not pertinent to the official Blu-ray standard, but as far as I can tell, if I want to make a FLAC 7.1 audio file 'legal' the only choice that I can see is to convert it using UsEac3to to PCM. But, FWIW, it makes the audio file pretty big, and the bit rate goes up from about 5000 to 9000, which I am sure is overkill.

Any thoughts...?

Thanks!

[colinhunt]

A crash of that type can prevent the executing program from returning an error code. I've seen it happen exactly like this before in cases of overclocking/overheating.
I ran another Full Backup last night. CoreTemp logged CPU temperatures for the session, and the hottest core reached 57 degrees Celsius. Judging by the output size this backup finished successfully.

I have a theory for what might have caused the problems described earlier. Does BD-RB check in any way that the OS managed to read the entire file during x264 encoding? For example, does it compare source file's number of frames to output's number of frames?

[jdobbs]

I was curious (again...) how would BDRB handle a movie file that had a 7.1 FLAC lossless audio file? Say that I imported it. What would it do with the audio?

I KNOW that this is not pertinent to the official Blu-ray standard, but as far as I can tell, if I want to make a FLAC 7.1 audio file 'legal' the only choice that I can see is to convert it using UsEac3to to PCM. But, FWIW, it makes the audio file pretty big, and the bit rate goes up from about 5000 to 9000, which I am sure is overkill.

Any thoughts...?

Thanks!BD-RB will only import: DTS, AC3, AAC, PCM, MPEG-Layer 3 (MP3), MPEG-Layer 2, and MPEG-Layer 1 audio.

[Lathe]

BD-RB will only import: DTS, AC3, AAC, PCM, MPEG-Layer 3 (MP3), MPEG-Layer 2, and MPEG-Layer 1 audio.

Ah, didn't know that. Thanks!

[jdobbs]

Ah, didn't know that. Thanks!There are actually several kinds of DTS and AC3 that are supported (e.g. the HD extensions). I just didn't want to list them.

[Sharc]

My source is a captured .avi, captured from tape. Video is huffyuv lossless compressed (9GB for 7 minutes video), audio is LPCM stereo. The .avi file is playable with SW player; video and audio are in sync.

Import of the .avi in BD-RB works fine, temporary .mkv container is correctly generated and playable. But when trying to extract the streams from the .mkv BD-RB exits with an error:

[22:34:32] Importing AVI: CAPTURE_(2016-01-29_AT_22-22-57)
- Preparing AVI for processing...
- Collecting audio/video streams from source...
[22:42:05] ERROR: Collecting video file streams. Aborted.
Any idea what could be wrong?

Edit:
I stay corrected: Video is not huffyuv but is uncompressed "YUV 4:2:2 as for UYVY but with different component ordering within the u_int32 macropixel" (MediaInfo).
I try again with huffyuv now .....

Edit2:
No joy with huffyuv. From MediaInfo:
Format : HuffYUV
Format version : Version 2
Codec ID : HFYU
Duration : 7mn 25s
Bit rate : 61.1 Mbps
Width : 720 pixels
Height : 576 pixels
Display aspect ratio : 5:4
Frame rate : 25.000 fps
Standard : PAL
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 8 bits
Scan type : Interlaced

[Lathe]

There are actually several kinds of DTS and AC3 that are supported (e.g. the HD extensions). I just didn't want to list them.

That's cool, thanks Bro!

[jdobbs]

Currently supported video imports are: AVC/H.264, HEVC/H265, VC-1, MPEG-1, MPEG-2, XVID, and several DIVX formats. I could easily support more as long as I know the MediaInfo signature and it's supported by LAVF. But frankly the ones I have cover about 99% of typical video files.

[Lathe]

Currently supported video imports are: AVC/H.264, HEVC/H265, VC-1, MPEG-1, MPEG-2, XVID, and several DIVX formats. I could easily support more as long as I know the MediaInfo signature and it's supported by LAVF. But frankly the ones I have cover about 99% of typical video files.

Dude, your program does so DAMN much and is so awesome, I almost hafta change my pants every time I use it! :D

Seriously, THANK GOODNESS the days are behind me where I would spend hours and hours and hours trying to figure out re-authoring programs like Hybrid and such. What a PAIN that was. Now, with BDRB I can EASILY do bloody everything I want to do without having to sweat a cryptic interface or endless confusing parameters. It does just the RIGHT amount of stuff!

BTW, just a quickie...

Is there anyway for the Quck Play menu to show more characters or longer titles? I am SO bloody verbose in my file naming that it usually gets truncated a little. Not really that important, but I'd thought I'd ask...

Thanks!

[Sharc]

Currently supported video imports are: AVC/H.264, HEVC/H265, VC-1, MPEG-1, MPEG-2, XVID, and several DIVX formats. I could easily support more as long as I know the MediaInfo signature and it's supported by LAVF. But frankly the ones I have cover about 99% of typical video files.
@jdobbs
I understand that your comment refers to my .avi import question (http://forum.doom9.org/showpost.php?p=1755297&postcount=23573), right? Apparently the (lossless) HUFFYUF video is currently not supported for import, correct?
I can try to capture the tape to one of the supported formats. Actually I hate the idea to capture real-time and compress on the fly (poor quality or dropping frames due to CPU overload).
Well, using BD-RB for archiving my video tapes is certainly somewhat special, but at least PayPal could drop their concerns and sleep more quietly.... :D

[jdobbs]

@jdobbs
I understand that your comment refers to my .avi import question (http://forum.doom9.org/showpost.php?p=1755297&postcount=23573), right? Apparently the (lossless) HUFFYUF video is currently not supported for import, correct?
I can try to capture the tape to one of the supported formats. Actually I hate the idea to capture real-time and compress on the fly (poor quality or dropping frames due to CPU overload).
Well, using BD-RB for archiving my video tapes is certainly somewhat special, but at least PayPal could drop their concerns and sleep more quietly.... :DI'll create a HUFFYUF video file and do some testing. It shouldn't be hard add it. When I capture from video tape I use MPEG-2 at a very high bitrate in realtime.

[Sharc]

I'll create a HUFFYUF video file and do some testing. It shouldn't be hard add it. When I capture from video tape I use MPEG-2 at a very high bitrate in realtime.
Thanks for looking at it. But don't invest too much time as this tape archiving application of BD-RB might be of limited value to other users, I am afraid. I can do it manually, but BD-RB is so convenient ...... :)

[AmigaFuture]

I'll create a HUFFYUF video file and do some testing. It shouldn't be hard add it. When I capture from video tape I use MPEG-2 at a very high bitrate in realtime.

Same here! I don't do a lot of it anymore since I've processed most of my tapes, and tossed them..but it is a very cool feature with multiple uses. BD Rebuilder is really good at that. Tip of my Cap to you.

[Lathe]

Another semi-related query...

I want to back up my STAR TREK: TNG Blu-rays, but, especially with the first few seasons, I don't really care for or want to back up very many of the episodes. I have AnyDVD which in cases with films, I would simply decrypt the disc to my HDD and then use BDRB to do whatever I wanted to do.

But, since I only want a few episodes off of the DL BD-50 discs that the episodes come on, do I still HAVE to rip the entire 45 Gigs or so to my HDD before I can select the few episodes that I want to keep or back up? In other words, have any of you here ever had that situation where you only wanted a small part of a large disc like that? And, is there ANY other way just to extract the episodes that I want WITHOUT having to take a whole hour a disc to rip the WHOLE disc to my HDD using AnyDVD? Is it possible to have AnyDVD running in the background and would it decrypt 'on the fly' so to speak while I could somehow select only certain episodes?

I don't suppose I could have AnyDVD running in the background and then just use BDRB to select the few episodes that I want straight from the disc to back up...?

Appreciate any thoughts or suggestions...

[jdobbs]

If I understand you correctly... yes, but it takes a couple steps. You can point BD-RB to the discs (one at a time, with AnyDVD running) and select the episodes during import. Then you put the imported structures together in a folder, and re-import (combining them into an entire season).

[Lathe]

If I understand you correctly... yes, but it takes a couple steps. You can point BD-RB to the discs (one at a time, with AnyDVD running) and select the episodes during import. Then you put the imported structures together in a folder, and re-import (combining them into an entire season).

Ah, good, that will save some time! :)

So, if I understand correctly... I import, say, one episode from season 1. Will that supposedly just be one m2ts file on the disc, do you think? And then BDRB will create a BDMV folder for THAT episode, right? And then I do this with whatever episodes I want and then combine (import) the BDMV folders for each episode into what BDRB will then create as a playable disc with however many episodes, right?

And, I can do ALL this simply while AnyDVD is running in the background...? That would be awesome, thanks!

[MrVideo]

I import, say, one episode from season 1. Will that supposedly just be one m2ts file on the disc, do you think?

Normally, for TV season release, it is one M2TS file per episode. I've yet to see a release that has seamless branching for episodes.

And then BDRB will create a BDMV folder for THAT episode, right? And then I do this with whatever episodes I want and then combine (import) the BDMV folders for each episode into what BDRB will then create as a playable disc with however many episodes, right?

A Blu-ray disc can only have a single BDMV directory. All of the wanted M2TS files will have to be combined into a single directory. Sounds like BDRB will handle that just fine.

Keep in mind, after recompressing to a decent value, you'll only get about 4-5 episodes per disc. You can double that if you really recompress.

[Lathe]

Normally, for TV season release, it is one M2TS file per episode. I've yet to see a release that has seamless branching for episodes.



A Blu-ray disc can only have a single BDMV directory. All of the wanted M2TS files will have to be combined into a single directory. Sounds like BDRB will handle that just fine.

Keep in mind, after recompressing to a decent value, you'll only get about 4-5 episodes per disc. You can double that if you really recompress.

Thanks kindly for the further details. Good to know that the episodes are single m2ts files, that helps!

Being such a TREK fan, I probably won't be compressing at all, and I will be keeping full HD audio. I'll likely just do 2 full episodes per single layer disc, maybe 3 if the single episodes come to about 7-8 Gigs each.

I'm just relieved that I don't HAVE to rip the whole dang 45 Gig disc just to get a few episodes. That first season is a real stinker, and the 2nd one isn't a whole hell of a lot better (NOT a real Pulaski fan... :) )

[MrVideo]

I'm just relieved that I don't HAVE to rip the whole dang 45 Gig disc just to get a few episodes.

But you pretty much do. A majority of a disc is the episodes. If you want all of the episodes on a particular disc, you will be ripping pretty much all of it. If you only want a single episode, then ya, a lot less work.

Not sure why it is called ripping when all you are really doing is copying files from the disc to the HDD. Unlike CDs, where you have to convert from the CD data content to a WAV file (or other audio format). With Blu-ray discs, what you see is what you get.

Good thing they tend to have the episodes on a disc in sequence, from lowest M2TS number to the highest M2TS number. To be safe, you will need to look at the M2TS file and look for the episode name. At least TNG has episode titles in the episodes.

[jdobbs]

Good thing they tend to have the episodes on a disc in sequence, from lowest M2TS number to the highest M2TS number. To be safe, you will need to look at the M2TS file and look for the episode name. At least TNG has episode titles in the episodes.There are many discs where the M2TS sequencing doesn't match the order. BD Rebuilder does analysis to determine and present episodes in the proper order wherever it can -- such as using "Play All" playlist ordering, or the order they are found in navigation command lists. It does similar analysis on DVD imports. No algorithm is perfect -- but it does pretty well.

Will that supposedly just be one m2ts file on the disc, do you think?Episodes don't have to be in a single M2TS for BD-RB, it constructs them into one when it imports.

Not sure why it is called ripping when all you are really doing is copying files from the disc to the HDD.That certainly isn't true with a BD-RB import (as opposed to a traditional "rip"). You have to create a new menu, new playlists, and even reconstruct the M2TS when they are segmented. It's even more true when importing from DVD to BD format. BD-RB also can combine multiple discs into a single structure.
I'll likely just do 2 full episodes per single layer disc, maybe 3 if the single episodes come to about 7-8 Gigs each.Of course it's up to you, but I'd recommend reencoding them to fit more on a disc. You'll find that in most cases the original discs are poorly coded and use way too much bitrate. Often it's just to require a double layer disc (to make it harder to copy). People are also easily impressed with "sets" of BDs that look like they're getting a lot for their $100+. BDs are cheap to manufacture after they've been authored. Run an episode through X264 using a low CRF (like 18) and you'll find that they shrink considerably without noticeable loss.

[MrVideo]

Of course it's up to you, but I'd recommend reencoding them to fit more on a disc. You'll find that in most cases the original discs are poorly coded and use way too much bitrate. Often it's just to require a double layer disc (to make it harder to copy). Run an episode through X264 using a low CRF (like 18) and you'll find that they shrink considerably without noticeable loss.

I agree. I do a lot of x264 encoding using 4Mbps and the results are very impressive. That lets you put a lot onto a Blu-ray. :D

[Lathe]

Of course it's up to you, but I'd recommend reencoding them to fit more on a disc. You'll find that in most cases the original discs are poorly coded and use way too much bitrate. Often it's just to require a double layer disc (to make it harder to copy). People are also easily impressed with "sets" of BDs that look like they're getting a lot for their $100+. BDs are cheap to manufacture after they've been authored. Run an episode through X264 using a low CRF (like 18) and you'll find that they shrink considerably without noticeable loss.

Hmmm, that's right; I seem to remember you saying this before about television episodes particularly. I had forgotten. Appreciate the reminder. It WOULD be interesting to see how an 18 CRF encode would turn out. I didn't realize that they 'Pad' the bit rate so much!

[jdobbs]

I wouldn't be surprised if it is less than 1/4 the original size. I personally did some of the STNG discs -- and put an entire season on one DL Blu-Ray with excellent results. When I reencoded for my Serviio streaming server at a CRF of 23 -- an entire season took about 25GB.

[KaraokeAmerica]

So.....because I don't really understand.....the higher the CRF, the higher the quality and the less compression is used? Am I using the right terms here?

[HWK]

So.....because I don't really understand.....the higher the CRF, the higher the quality and the less compression is used? Am I using the right terms here?

Nope, it is other way around. CRF values range from 0-51. closer to 0 higher quality and less compression applied.

[Lathe]

I wouldn't be surprised if it is less than 1/4 the original size. I personally did some of the STNG discs -- and put an entire season on one DL Blu-Ray with excellent results. When I reencoded for my Serviio streaming server at a CRF of 23 -- an entire season took about 25GB.

Wow, that is quite impressive; thanks for letting me know!

So.....because I don't really understand.....the higher the CRF, the higher the quality and the less compression is used? Am I using the right terms here?

From what I've read, for HD sources about 18 is considered pretty high quality without getting too extreme or having huge file sizes. As JD mentioned above, he used 23 and was happy with it. I would say that within that range is probably what most people use for fairly high quality. I think I read somewhere that 16 is supposed to be perceptually identical. But, I'm quite SURE that a lot of this also depends on the source and other factors too...

[Sharc]

I wouldn't be surprised if it is less than 1/4 the original size. I personally did some of the STNG discs -- and put an entire season on one DL Blu-Ray with excellent results. When I reencoded for my Serviio streaming server at a CRF of 23 -- an entire season took about 25GB.
I usually put 6 episodes on a BD25, with nice quick menus.
Or even a full season (10...12 episodes) on a BD25 at 1440x1080 or 1280x720 resolution. No family member (blind tetst) has ever complained about inferior quality in any respect :cool:

Since lately I have also been trying x265@CRF 23...25 for streaming from the NAS to the SmartTV. Results are surprisingly good, with another 30 .... 40% reduction in file size.

[jdobbs]

Wow, that is quite impressive; thanks for letting me know!



From what I've read, for HD sources about 18 is considered pretty high quality without getting too extreme or having huge file sizes. As JD mentioned above, he used 23 and was happy with it. I would say that within that range is probably what most people use for fairly high quality. I think I read somewhere that 16 is supposed to be perceptually identical. But, I'm quite SURE that a lot of this also depends on the source and other factors too...18 is really close to a perfect reproduction. The default CRF for X264 is 23 -- which is generally considered the best balance of compression and quality. So if you are using 18, you are leaning heavily toward quality.

[Knightmire]

I've been waiting a while on this "bug" report and since there is still no mention of it here I decided it's my turn to bring one up. I'm honestly not sure if it's an actual bug or just incompatible files but hopefully there's a simple answer I just haven't figured out. So here goes...

While trying to make a disc of some 1080p shows with BD50.11, I found I kept getting this "demuxing error". Log of the error here:

[00:22:32] Importing MKV: 01._BKNY
- Collecting audio/video streams from source...
- Converting codec to compatible format...
[00:37:16] ERROR: Incompatible stream (1920x1088) detected. Aborted.

As you see, it took 15 mins to process this file only to spit it out at the end where it would normally proceed to the next file or build the temp structure. I thought perhaps one of the other helper tools needed updating so I've since tried new copies of LAV and even tinkered with FFDSHOW but always getting this same error. When BD50.12 came out I tried these files yet again and same error. Not sure what to do with these things as other encoding programs just throw out different errors, even though the files play perfectly fine.

These videos are HEVC MKV and they are indeed at a resolution of 1920x1088 with an AC3 audio track. Is know that's sort of an odd resolution but is it causing the problem? I seem to see a lot of small variations like this on shows and movie MKVs lately but this is the first time BD has rejected them in this manner. I am using the latest bdrebuilder and the helper programs that are currently linked on the first post here. I can follow up with more info if you'll tell me what you need to know.

Any help appreciated, even if it's just some alternate program to convert these files to something BD can handle. Thanks!

[gonca]

Can you post a mediainfo report of the MKV so we can see the stream types

[jdobbs]

The 1088 height is definitely the reason it failed. BD-RB will accept 1920 with values less than 1080p and assumes black borders have been removed, but not 1920 with a height of greater than 1080.

The time is likely in the extraction (using MKVEXTRACT), although that seems like a lot.

[Knightmire]

Alright, managed to track down an h265->264 re-encoder that worked and fixed the resolution on these files. I had to do the first 8 of them on this show but the other 5 were a lower resolution (1904x1017) and they had no problems. Well beside the odd 15 minute "Converting codec to compatible format..." step per file. Everything working as it should now. Thanks for the help and this is still some great software, thanks jdobbs!

PS..
If anyone reads this and has a similar issue; I ended up using a program called SuperC to re-encode these MKVs to 1920x1080. It's a pretty decent free program and only took about 10 mins per file. Once you get passed the horrendous mine field of an installer anyways! I think it tried to install like 10 different pieces of additional unwanted software, so I had to really read each screen to make sure I didn't allow anything. Made it through unmolested. :)

[KaraokeAmerica]

PS..
If anyone reads this and has a similar issue; I ended up using a program called SuperC to re-encode these MKVs to 1920x1080. It's a pretty decent free program and only took about 10 mins per file. Once you get passed the horrendous mine field of an installer anyways! I think it tried to install like 10 different pieces of additional unwanted software, so I had to really read each screen to make sure I didn't allow anything. Made it through unmolested. :)

Is this the program?

http://www.erightsoft.com/SUPER.html

If not, can you please share a link?

Also, SuperC doesn't seem to be an option, but Ninite is a pretty good service to get many "freeware" packages without the junkware usually bundled. Perhaps they will add this to their stable at some point:

https://ninite.com/

[Knightmire]

Is this the program?

http://www.erightsoft.com/SUPER.html

If not, can you please share a link?

Also, SuperC doesn't seem to be an option, but Ninite is a pretty good service to get many "freeware" packages without the junkware usually bundled. Perhaps they will add this to their stable at some point:

https://ninite.com/


That's the one alright. Yeah, it took me a little hunting to find the download link too. Had to go to products and download then follow another link from there. Anyways, it's on this page here. It's a blue link near the bottom. It's not pretty but did what I needed. Hopefully I won't need it very often. Good luck :)

http://www.erightsoft.com/Superdc.html