Bug 384443 - [MATSHITA BD-MLT UJ240AS] It does not record its maximum speed
Summary: [MATSHITA BD-MLT UJ240AS] It does not record its maximum speed
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-06 18:57 UTC by Cristian Aravena Romero
Modified: 2022-12-10 05:14 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
k3b.txt (74.42 KB, text/plain)
2017-09-06 18:57 UTC, Cristian Aravena Romero
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cristian Aravena Romero 2017-09-06 18:57:18 UTC
Created attachment 107725 [details]
k3b.txt

Hello,

I'm doing some tests and it does not record to 6x.

Regards,
--
Cristian
Comment 1 Leslie Zhai 2017-09-07 02:06:07 UTC

*** This bug has been marked as a duplicate of bug 380067 ***
Comment 2 Thomas Schmitt 2017-09-07 13:07:44 UTC
Hi,

the low effective speed is not a bug but a feature of formatted BD-R
media. During writeing the freshly written blocks are read and compared
with the data which are still in the drive buffer. This frequent change
between writing and reading slows down overall speed. Especially if
reading is not very successful. I.e. very low effectiive speed indicates
a bad relation between drive and medium and announces failure to come soon.

  https://bugs.kde.org/attachment.cgi?id=107725
looks like good relation for 4x speed and mediocre for 6x speed.

You may ask the drive with an unused medium for the speed list by

  dvd+rw-mediainfo /dev/sr0

which will reply something like

   Write Speed #0:        8.0x4495=35968KB/s
   Write Speed #1:        6.0x4495=26976KB/s
   Write Speed #2:        4.0x4495=17984KB/s

-------------------------------------------------------------------------

Defect management can be avoided on BD-R media by adding

  -use-the-force-luke=spare=none

to the list of extra options for growisofs. It will then skip formatting
the BD-R medium before writing begins.

In my olde Debian 8 K3B this would be:

  Pulldown menu: Settings
    Item: Configure K3B
      Side bar icon: Programs
        Tab: User Parameters 
          Line: growisofs
            Click at column: Parameters
              Write the text: -use-the-force-luke=spare=none

The BD-R will have full nominal capacity and will be burnt at increasing
speed up to reaching full nominal speed near the end.
Noise might be substantial.

On BD-RE it cannot be avoided to format the medium. Above option might or
might not lead to full speed. The medium will have nominal capacity.
The only way to bring BD-RE to full speed is the option

  stream_recording=on

of backend program cdrskin (or command -stream_recording of xorriso,
or burn option Stream Recording in Xfburn).

Have a nice day :)

Thomas
Comment 3 Thomas Schmitt 2017-09-07 13:10:18 UTC
I meant "the only sure way to bring BD-RE to full speed".
Some few drives burn at full speed if there is no Spare Area with replacement
blocks.
Comment 4 Justin Zobel 2022-11-10 08:51:46 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-25 05:17:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-12-10 05:14:35 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!