Bug 384566 - K3b does not correctly determine the write speed of Blu-ray Discs
Summary: K3b does not correctly determine the write speed of Blu-ray Discs
Status: RESOLVED DUPLICATE of bug 380064
Alias: None
Product: k3b
Classification: Applications
Component: K3bSetup (show other bugs)
Version: 2.0.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-10 16:44 UTC by haman207
Modified: 2017-11-15 19:20 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description haman207 2017-09-10 16:44:39 UTC
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?
Comment 1 Leslie Zhai 2017-09-11 02:28:12 UTC
Hi haman,

Please try https://download.kde.org/stable/applications/17.08.1/src/k3b-17.08.1.tar.xz v2.0.x was not be maintained any more.

Regards,
Leslie Zhai
Comment 2 haman207 2017-09-11 11:09:35 UTC
Thanks for the clarifications. But in the Ubuntu 16.04 ppa there is only version 2.0.3.
And I do not know how to install the method you proposed.
Since this error is not critical, I will stop on this version.
Tell me please in the latest version of the bug fixed?
Comment 3 haman207 2017-09-11 14:34:17 UTC
I installed ubuntu on 17.04. in her ppa contains a version of k3b 17.04
The situation has not changed.
Comment 4 Leslie Zhai 2017-09-12 07:16:26 UTC
Hi Cristian,

Could you help haman to build K3B git to test? thanks a lot!

Regards,
Leslie Zhai
Comment 5 Cristian Aravena Romero 2017-09-12 11:13:18 UTC
Hello Haman,

# su -c "grep '^deb ' /etc/apt/sources.list | \
sed 's/^deb/deb-src/g' > /etc/apt/sources.list.d/deb-src.list"

# apt update -y

https://askubuntu.com/questions/212027/getting-build-dependencies-and-source-by-default
# apt-get build-dep k3b

== Compiling ==
# git clone git://anongit.kde.org/k3b
# cd k3b
# mkdir build
# cd build
# cmake ..
# make
# make install

Regards,
--
Cristian
Comment 6 haman207 2017-09-12 12:14:47 UTC
Thank you. Now there is no time, but as time appears, I will check and report the result.
Comment 7 Cristian Aravena Romero 2017-09-12 12:55:40 UTC
(In reply to Leslie Zhai from comment #4)
> Hi Cristian,
> 
> Could you help haman to build K3B git to test? thanks a lot!



Hello Leslie Zhai,

Thanks for the consideration :-)

Regards,
--
Cristian
Comment 8 haman207 2017-11-12 01:43:04 UTC
Kind time of day
there was a time and I installed the version on August 17, 2003 nothing has changed.
Comment 9 haman207 2017-11-12 01:46:16 UTC
Sorry Google translator has substituted the date in the place of the version.
Installed version 17.08.03 nothing has changed.
Comment 10 Leslie Zhai 2017-11-12 03:30:27 UTC

*** This bug has been marked as a duplicate of bug 380064 ***
Comment 11 haman207 2017-11-15 19:20:04 UTC
Thank you. I read it. Understood. The bug is gone.