[k3b] [Bug 384566] New: K3b does not correctly determine the write speed of Blu-ray Discs

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=384566

            Bug ID: 384566
           Summary: K3b does not correctly determine the write speed of
                    Blu-ray Discs
           Product: k3b
           Version: 2.0.3
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: K3bSetup
          Assignee: k3b at kde.org
          Reporter: haman207 at gmx.fr
                CC: michalm at jabster.pl, trueg at kde.org
  Target Milestone: ---

When writing BD-R discs companies MIREX (others did not try to unnecessarily
inaccessible) k3b program oddly determines the recording speed. The
manufacturer stated that the discs can be recorded at a speed of 1x-4x and when
recording with Nero 16 (Win7) program and takes place.
http://savepic.net/9862368.htm
 And k3b maximum defined by a different recording speed.
http://savepic.net/9844960.htm
 Those 17000 kb/s are not 4 as indicated by the manufacturer and determines
inequality and 12.10x It does not depend on the iron (I have two different
drive) and Linux build (test).  Figured out, it is not buggy just another frame
of reference. Explain: speed 1x 2x 3x indicate how many times the data transfer
rate is greater than the reference 
for CD standard is 150Kb / s, for the DVD 1352 KB / s  
for Blu-ray 4500 Kb / s Actual speeds may vary slightly due to the features of
the equipment. And so if we take the speed which shows the inequality 17980 KB
/ s and divide it by 4 we get 4495 Kb / s, which is within the error, and the
same Blu-ray standard. But if we take the data from the K3b 17035 KB / s and
divide by the specified multiplier 12,30, we get 1384 Kb / s, which, taking
into account the standard errors of the same DVD.Of the above described infer
that K3b when calculating the speed record Blu-ray discs do not use the correct
standard and it's not a bug, but an oversight developers.
Actually the question, why?

-- 
You are receiving this mail because:
You are the assignee for the bug.