BD-Rebuilder, Feature Requests

[chudm]

what about we can select what to include or not on the bluray? :) i meant like if we dont want the extras, but still want the menu, or just want some of the extras? doesnt seems to hard to do right?

[jdobbs]

what about we can select what to include or not on the bluray? :) i meant like if we dont want the extras, but still want the menu, or just want some of the extras? doesnt seems to hard to do right? I'll eventually add an option to blank them. But you first have to be able to view them so you know what you're blanking. I've started working on that but have hit a couple of snags.

[chudm]

I'll eventually add an option to blank them. But you first have to be able to view them so you know what you're blanking. I've started working on that but have hit a couple of snags.

yeap i was thinking about that, cause sometimes are too many clips that it will be very annoying to check one by one to see what does it have each one!

[tekmobile]

I'll eventually add an option to blank them. But you first have to be able to view them so you know what you're blanking. I've started working on that but have hit a couple of snags.


What kind of snags

Are you planning on just having some program launch, write your own preview player or just embedding something like MPC.

[jdobbs]

What kind of snags

Are you planning on just having some program launch, write your own preview player or just embedding something like MPC. I was going to just embed it in BD-RB (like I do in DVD-RB) using the media libraries already included in Windows.

The snag? Well... the DLL keeps crashing when I call it.

[HWK]

Not sure if this is good idea or not but I have seen tsmuxer doesn’t use more than one cpu core at given time. However today cpu have two to four cores. If tsmuxer instance is launched multiple time we can give each one different stream to extract. Also this would help with rebuilding for final output since we can build more than one stream at same time.

[tekmobile]

Not sure if this is good idea or not but I have seen tsmuxer doesn’t use more than one cpu core at given time. However today cpu have two to four cores. If tsmuxer instance is launched multiple time we can give each one different stream to extract. Also this would help with rebuilding for final output since we can build more than one stream at same time.

You would still be limited by your disk's performance and with the increased seek times would actually slow down the process.

[cybercurves]

Any chance you could add a little audio sound when the conversion is complete? Not that big of a deal, but it's always nice to hear a beep or some type of sound when something is finished.

[jdobbs]

Any chance you could add a little audio sound when the conversion is complete? Not that big of a deal, but it's always nice to hear a beep or some type of sound when something is finished. Sure.

[Wolfe999]

Don't remember in which version you had a very nice feature: BD showed the approximate bitrate the conversion would have once finished. Then you took it off. Would it be much of a hassle to add it again? Or it's still there hidden and I haven't seen it? :)

Edit: corrected typo

[tekmobile]

Don't remember in which version you had a very nice feature: BD showed the approximate bitrate the conversion would have once finished. Then you took it off. Would it be much of a hassle to add it again? Or it's still there hidden and I haven't seen it? :)

Edit: corrected typo

Do you mean verbose status reporting under the settings tab this states the approx bitrate

[GaPony]

Any chance you could add a little audio sound when the conversion is complete? Not that big of a deal, but it's always nice to hear a beep or some type of sound when something is finished.

How about a user configurable setting. I'd like to have a loudazzed siren when its complete! :D

I'm sure some people would like a ding and still others, nothing. ;)

[Wolfe999]

Do you mean verbose status reporting under the settings tab this states the approx bitrate

It might be. Don't know why, I have it unticked now. I'll check it now.
Thank you, tekmobile :D

[shon3i]

Hello jdobbs, as i alredy ask you here (http://forum.doom9.org/showthread.php?p=1319693#post1319693) about Level 4.0 comilance in BD Rebulder, i want to elaborate this. Since x264 can't fully produce Blu-Ray compilant stream at level 4.1, according original Blu-Ray specification, encoding only and only with level 4.1 require 4 or more slices. Level 4.0 is full blu-ray compilant only thing is different is that max bitrate drop from 40000 to 24000. Since both level 4 and 4.1 can have max buffer on 30000, which mean max 30mbps peak, quality won't drop by wide margin. You current buffer setting (25000) can hurt quality more than difference between level 4 and 4.1. Anyway x264 as very powerfull and quality at level 4 will be same. Finaly we find settings that are 100% compilant, i think is smarter for near future until x264 not make slices encoding.

I suggest you to add some hidden option and use 100% blu-ray compilant settings in this mode such as
Level 4
vbvmaxrate 24000
vbvbuffersize 30000
bframes=3
refs=4
no bpyramid
no mixedrefs
aud, nalhrd

strems generated with 100% compilant settings will be more usefull for authoring programs such sonic scenarist and others. Buffer 30000 are good for DVD media aslo there is no reason to change it because is compilant to BD 5/9 unless use strict AVCHD specs.

Thanks.

[Dark Shikari]

no mixedrefsIf you have no idea what you're talking about, please don't post.

[jdobbs]

@shon3i

I'm not trying to be confrontational, but I'd ask that you at least look at my BD-RB command lines before trying to correct them. The only downside to using Level 4.1 is the slice requirement -- and there is no known player that enforces that, so I made a decision to stick with it for the extra bitrate. I probably will decide to encode at Level 4.0 just so I can claim complete compliancy, but as of today it is a "much ado over nothing" argument that I've seen get much more attention than it's worth (IMHO).

I'd also add just for clarification that:

- Level 4.0 has a maximum rate of 25000 in High Profile (which is what BD uses), not 24000

- Level 4.1 has a maximum rate of 62500 in High Profile, the 40000 is a limitation of Blu-Ray, not the level

- The refs 4 is driven by resolution. And is only applicable to 1080p, 720p and below can be 5

I would also add that there are other requirements for Blu-ray, such as keeping the GOP length (keyframe spacing) under 1 second (which by the way is one I've seen violated the most in other suggested settings). You also have to severely lower the maximum bitrate when writing to AVCHD or BD-5/9, because the spin speed of a DVD won't handle 25000.

[shon3i]

- Level 4.0 has a maximum rate of 25000 in High Profile (which is what BD uses), not 24000

- The refs 4 is driven by resolution. And is only applicable to 1080p, 720p and below can be 5Sorry no, from ORIGINAL Blu-ray specs, document says

Maximum number of frames or complementary field pairs which are stored in DPB is restricted in
addition to ITU-T H.264 | ISO/IEC 14496-10.
�� In case of level 4.1 and 4
�� For 1920x1080: 4 (as defined in ITU-T H.264 | ISO/IEC 14496-10[11].)
�� For 1440x1080: 4
�� For 1280x720: 6
�� For 720x480 or 720x576: 6
�� In case of level 3.2 and 3.1
�� For 720x480 or 720x576: 6
�� In case of level 3
�� For 720x480:6
�� For 720x576: 5
• In case of level 4 and level 4.1, the size of CPB shall be less than or equal to 30000 [1000bits].

From bitrate table
40*1000 for level 4.1,
24*1000 for level 4

[jdobbs]

Sorry no, from ORIGINAL Blu-ray specs, document says I stand corrected on the 24000, I didn't realize the BD spec was different from the H.264 HiP/Level 4.0 spec (which is 25000). But, of course, I'm not using it as of right now so it really doesn't matter.

As for the other one, it pretty much substantiates exactly what I said.

[Chefkoch_ico]

Hi!

I set my PC mostly to standby when I am not using it.

Imgburn has a nice option where one can set the Shutdown action to for example: Shutdown, Standby, Hibernate, Restart.

Would be nice to see such an option in BD-RB.

I mentioned already in the bug thread, but its more of a feature wish:
a (hidden) option to not overwrite the VID_?????.avs files, if they already exist, would also be nice.

Bye

[Dark Shikari]

@shon3i

I'm not trying to be confrontational, but I'd ask that you at least look at my BD-RB command lines before trying to correct them. The only downside to using Level 4.1 is the slice requirement -- and there is no known player that enforces that, so I made a decision to stick with it for the extra bitrate.x264 supports slices, so might as well add them in now ;)

[jdobbs]

x264 supports slices, so might as well add them in now ;) Cool. :thanks:

[Capsbackup]

Would it be possible to include an elapsed time/running time along with ETA, similar to the frames encoded/total frames displayed?
This would be helpful trying to determine an estimate of the time it takes to reencode a certain size .m2ts, and projecting that to the remaining .m2ts files to reencode. Full movie backups and multi .m2ts movie only backups would be examples of where this could provide a useful estimate.

[Sharc]

@Capsbackup
You can get some additional status info by including in the [Options] section of the .ini SHOW_ENCODER=1

[DVD Maniac]

jdobbs,
On a recent update I noticed the following in the changes file -

"August 1st, 2009 - v0.26.01
- Added MKVMERGE.EXE and supporting code within
BD-RB to support reencoding of field-based sources
now no sources will be blanked automatically. My
thanks to apophis906 for pointing me in the right
direction."

Could you please clarify what this means, i'm assuming we are still a way off for title blanking as per DVD-RB function. For me this feature is much awaited and will allow custom backups, I just do movie only at the moment as a compromise but i'd like to keep the menu's, chapter searching and occasionally the odd feature. :)

[jdobbs]

I'll put it in eventually. The change you referenced was related to certain sources that would "die" each time you tried to encode them -- so there was no choice but to blank them. The thought was that the existing codecs couldn't handle them.

Then apophis906 posted that he was experimenting and found that if you converted them to MKV first they would successfully reencode. So I added MKVMERGE to the TOOLS folder fulfill that role.

Blanking is actually pretty easy to do, and I'll likely add it pretty soon. First, though, I have to implement some sort of playback function so you can know what you're about to blank without using some third party software.

[DVD Maniac]

I'll put it in eventually. The change you referenced was related to certain sources that would "die" each time you tried to encode them -- so there was no choice but to blank them. The thought was that the existing codecs couldn't handle them.

Then apophis906 posted that he was experimenting and found that if you converted them to MKV first they would successfully reencode. So I added MKVMERGE to the TOOLS folder fulfill that role.

Blanking is actually pretty easy to do, and I'll likely add it pretty soon. First, though, I have to implement some sort of playback function so you can know what you're about to blank without using some third party software.

Cool :) The Playback feature would be very useful but if there is an option to implement blanking without this feature more quickly i'm happy to locate them myself - easy enough job with TS Muxer etc :D

[Capsbackup]

@Capsbackup
You can get some additional status info by including in the [Options] section of the .ini SHOW_ENCODER=1

Thanks Sharc. I just thought it would be cleaner if it was just a part of BD-RB, and less obtrusive.

[Chefkoch_ico]

a (hidden) option to not overwrite the VID_?????.avs files, if they already exist, would also be nice.


jdobbs, am I on your ignore list? It seems I never get any reply from you, wheter I report a bug or a feature wish.

Dont get me wrong its of course your decission to answer or not. I even wrote you, theres no need to comment this, if you are not interested.

However, somehow I thought I would get at least a reply, since I have donated more than maybe 99% of all the BD-RB users (not donaters).

Best regards

[jdobbs]

jdobbs, am I on your ignore list? It seems I never get any reply from you, wheter I report a bug or a feature wish.

Dont get me wrong its of course your decission to answer or not. I even wrote you, theres no need to comment this, if you are not interested.

However, somehow I thought I would get at least a reply, since I have donated more than maybe 99% of all the BD-RB users (not donaters).

Best regards I don't have an ignore list. So, of course not. But you have to give me a break... I'm working on a lot of things at once. I prioritize based upon the seriousness of an issue at hand, and right now I'm concentrating on what seems to be some ugly issues with interlacing.

[Chefkoch_ico]

I don't have an ignore list. So, of course not. But you have to give me a break... I'm working on a lot of things at once. I prioritize based upon the seriousness of an issue at hand, and right now I'm concentrating on what seems to be some ugly issues with interlacing.

Thanks for the reply. My apologies. Good luck with the interlaced issues.

[MILLZY]

Option to output straight to ISO and not burn.

Thanks:thanks:

[GaPony]

BD-Rebuilder already doesn't burn... It can link to ImgBurn to burn to disc, but you can use ImgBurn to make your .iso if you want.

[jdobbs]

Option to output straight to ISO and not burn.

Thanks:thanks: I can put that as another option easy enough.

[MILLZY]

I can put that as another option easy enough.

Thanks.....

[GaPony]

That's not to say he will... :D

[Sharc]

@jdobbs
Have you ever thought of (or tried) anamorphic encoding for BD backups -- in addition to the 720p?
At a first glance it seems to be easy (?) and blu-ray specs compliant:
- Resize to 1440 x 1080 (instead of 1280 x 720)
- Add --sar 4:3 to the x.264 command line (instead of --sar 1:1)
I mention it because it would be a compromize between full HD backup and resizing to 720p, e.g. for backups on BD9.
Would it make sense? Or does it have many more implications and risks?

[stenews]

Hi jdobbs,
is it possible to resume a BD encoding task?
I mean, because of it takes so long time to complete a full encode, I'll be more than thank to you if you could build a new feature that gives us the capability to stop the process and restart it from where we leave.
I hope I state clearly my idea... :p

Bye,
Stefano.

[Sharc]

@stenews
Resuming from where it left is available since long. :rolleyes:
Try it yourself: Push the Abort button and then restart BD-RB. You will be asked if you want to resume the job or overwrite / clear the workfolders.

[stenews]

@Sharc
oh...gosh! I didn't know that :o
I'll give a try...but could you tell me if it works even after a full PC shot down?

Thanks,
Stefano

[jdobbs]

@Sharc
oh...gosh! I didn't know that :o
I'll give a try...but could you tell me if it works even after a full PC shot down?

Thanks,
StefanoYes, but... it will resume at the nearest clean stop point. For example if you were in the middle of a second pass of a segment at the time you aborted, it would restart at the beginning of that pass.

The reason I mention that is that sometimes a pass might take four hours -- so stopping/resuming at the halfway point would add two extra hours to the overall time.

[stenews]

@jdobbs
thanks for answering me:)
and so the best thing to do is always to stop it at the end of one encoded segment. isn't it?

P.S.
same thing when I use DVD-RB...right?

[jdobbs]

@jdobbs
thanks for answering me:)
and so the best thing to do is always to stop it at the end of one encoded segment. isn't it?

P.S.
same thing when I use DVD-RB...right? Exactly -- except the segments in DVD-RB are typically much shorter. The best time to stop is right after the end of either of the two passes (assuming two pass is selected).

[stenews]

Thanks a lot jdobbs, I appreciate that.
You're doing a really great job with those applications!

Bye,
Stefano.

[Sn8kbordin]

Ability to select different path for work files and final output.
This way the rebuild process will be sped up if its on 2 different drives.

Thanks jdobbs for your great work.

[turbojet]

From my experiences CRF saves bitrate for the main movie while retaining a certain level of quality and it also saves some time but the current quick CRF uses settings aren't so good for keeping quality. Any chance of having separate CRF quality options?

Also setting quick CRF results in much larger under/over sizing, usually 500-1500 MB for BD5/9 outputs. 2 pass on everything is usually within 200 MB in the latest versions for me. Can the CRF sizing be looked at?

Also would like to resize the extras to 480 or 720 but keep the main movie at 1080p with an option to set M2TS to not resize by right click. Another thing could be an auto-resize option which would encode the extras and then encode 3% or so (using selectevery) of the main movie at CRF 26 (adjustable in ini). If the bitrate is equal to or less than the bitrate calculated from the remaining space it would keep it at 1080p, if the bitrate is more then it resizes to 720p.

[Dark Shikari]

Why not do this, jdobbs?

1) use --pass 1 --slow-firstpass on the CRF pass
2) If it oversizes, run a second pass.
3) If not, you're done...

[jdobbs]

From my experiences CRF saves bitrate for the main movie while retaining a certain level of quality and it also saves some time but the current quick CRF uses settings aren't so good for keeping quality. Any chance of having separate CRF quality options?

Also setting quick CRF results in much larger under/over sizing, usually 500-1500 MB for BD5/9 outputs. 2 pass on everything is usually within 200 MB in the latest versions for me. Can the CRF sizing be looked at?

Also would like to resize the extras to 480 or 720 but keep the main movie at 1080p with an option to set M2TS to not resize by right click. Another thing could be an auto-resize option which would encode the extras and then encode 3% or so (using selectevery) of the main movie at CRF 26 (adjustable in ini). If the bitrate is equal to or less than the bitrate calculated from the remaining space it would keep it at 1080p, if the bitrate is more then it resizes to 720p.I'll add a hidden option to allow you to set the CRF value for the "quick" encodes. I'll look at the extra resizing and auto-size...

[jdobbs]

Why not do this, jdobbs?

1) use --pass 1 --slow-firstpass on the CRF pass
2) If it oversizes, run a second pass.
3) If not, you're done...Actually I'd planned to implement this on the one-pass CRF mode. It does a CRF size prediction followed by "--slow-firstpass" encode right now (so I can get the stats). The idea was to use the stats for a second pass in the event of an oversize -- but I hadn't gotten around to implementing yet.

[turbojet]

I'll add a hidden option to allow you to set the CRF value for the "quick" encodes. I'll look at the extra resizing and auto-size...

Do you mean QUICK_CRF? That worked last time I tried it but --preset ultrafast takes away a lot of the advantages of CRF especially when aiming for BD5/9. I'd be content with CRF using the same x264 settings from the quality settings option. Maybe better would be a separate good/better/high/highest quality setting for CRF.

Thanks for looking at the resizing, I'd really make use of resizing the extras to 720/480, most don't have the definition you'd except from HD, to make for a higher quality movie.

[Sharc]

..... I'd be content with CRF using the same x264 settings from the quality settings option.
I second this.

Btw I did some tests with resizing the main movie anamorphic to 1440x1080; --sar 4:3 as a 'compromize resolution' for BD5/9. Worked pretty well, including subtitles.