Where is the working directory of BD-RB??

[The_Unknown]

Hello,

of course I know I have to specify a working directory in the main window of BD-RB. But when I - after some hours of encoding and before the process is done - look inside that directory there's only about 2 GBytes of data. If this is the only working directory and BD-RB doesn't use any other (hidden one) on my hard drive, how could that be (when keeping in mind, that I'm processing a Blu-Ray with about 45 GB of data)???

BTW: Why does the inspect.exe check if the MPEG2-encoding setting is set correctly? Is this necessary for converting BD50's to BD25's?

Thanks!

Bye The_Unknown

[jdobbs]

The working folder will become at least as large as the selected output, sometimes twice as large -- it grows over the course of the processing.

MPEG-2 decoding is necessary for BD backup, as some factory discs still use MPEG-2. It's used often in extras, and there are some discs where even the HD source is encoded with MPEG-2 (it's completely acceptable by the BD standard). I believe the blu-ray version of "REDS" was an example if my memory serves me correctly.

[The_Unknown]

So BD-RB really does no work outside of the working directory I specified? I ask this because I'm working on a normal 1 TB HDD and my system is on an 90 GB SSD (which is quiet small ;)).

And do you also have an answer to my other question (MPEG2...)?

[jdobbs]

So BD-RB really does no work outside of the working directory I specified? I ask this because I'm working on a normal 1 TB HDD and my system is on an 90 GB SSD (which is quiet small ;)).

And do you also have an answer to my other question (MPEG2...)? See my answer above (I added more). Everything happens in the working folder except changes to INI files (which is in the BD-RB folder).

[The_Unknown]

Thanks for your answer. Now it's clear ;)

One last question: In the main BD-RB-topic here on the message board I couldn't find information which codec to use for the MPEG2 setting: libavcodec or libmpeg2?

Edit: One more last question (;)): Is it planned to have GPU-support in the future to make the encoding faster? Because at the moment it takes about 6 hours for one BD50->BD25 :(

[jdobbs]

Thanks for your answer. Now it's clear ;)

One last question: In the main BD-RB-topic here on the message board I couldn't find information which codec to use for the MPEG2 setting: libavcodec or libmpeg2?

Edit: One more last question (;)): Is it planned to have GPU-support in the future to make the encoding faster? Because at the moment it takes about 6 hours for one BD50->BD25 :( I have no current plans for GPU support, my thought is that it's too restrictive (certain chipsets) and I like to write things that will run in any environment. The reencoding times depend a lot on the amount of total content on the source and processor speed. Anywhere from 3 hours to 6 hours sounds about right. The bottom line is that there is a whole lot of processing involved in HD>

[The_Unknown]

Too bad :-(

And what about the MPEG2-Codec (look above please)?

[jdobbs]

Too bad :-(

And what about the MPEG2-Codec (look above please)?Either codec works fine.

[tapidlittle]

I have a similar question here.

When it's demuxing the AV streams, we can see the audio files (.AC3 or .DTS), we also see the video files (.VC1 I think).

Once it's start the compression, I don't see the original video file anymore, only the new one, where goes the original video file?

thank you.

[jdobbs]

I have a similar question here.

When it's demuxing the AV streams, we can see the audio files (.AC3 or .DTS), we also see the video files (.VC1 I think).

Once it's start the compression, I don't see the original video file anymore, only the new one, where goes the original video file?

thank you. I extract the video file so I can get an accurate size to determine if I can keep it without reencoding. If it is too large to keep intact, I remove it so the space is available for encoding. It could also be kept if LAVF is selected as the input file for encoding.

[tapidlittle]

I extract the video file so I can get an accurate size to determine if I can keep it without reencoding. If it is too large to keep intact, I remove it so the space is available for encoding. It could also be kept if LAVF is selected as the input file for encoding.

thanks for the info.

About the LAVF option, any benefits using this? hard drive space is not an issue for me.

[jdobbs]

thanks for the info.

About the LAVF option, any benefits using this? hard drive space is not an issue for me. It's usually slightly faster. If you're on a 64 bit operating system it will also automatically switch to the 64 bit version of X264 (included in with BD-RB) -- which can also be faster.

[tapidlittle]

It's usually slightly faster. If you're on a 64 bit operating system it will also automatically switch to the 64 bit version of X264 (included in with BD-RB) -- which can also be faster.

thanks I will try that.

[xterminater]

hi jdobbs... so wat purpose does the LAVF function served if you're on 64 bit OS compared to 32 bit besides the slight speed increase?

[jdobbs]

When I said "slight" I was talking about LAVF. Depending upon your system the 64 bit version can sometimes result in a significant speed increase (not always, though). Other than speed, you pretty much get the exact same output using 64 and 32 bit.

LAVF uses the internal frame-serving of X264 rather than AVISYNTH, HAALI, and FFSHOW. It would be ideal if it did everything, as it could prevent the complexity involved with helper apps -- but it doesn't (e.g. VC-1 interlaced streams) so sometimes even when you have it selected BD-RB may not be able to use it.