Written by animaniac the 13 Jan 09 at 08:25.

Make a totem plug-in that temporarily lowers read speed during playback of cd/dvd media.

it should not be to hard, take little code here and there then automate it (i lack the 1337n355 to do it unfortunately):

theres two commands that do this already,
http://blog.mfuchs.org/?p=15

and two programs, one that as far as i can tell runs from the terminal and one kde native,
http://linux.softpedia.com/get/System/Hardware/cdspeed-15269.shtml
http://nixbit.com/cat//utilities/set-cd-rom-speed/

the point is to make it work the "ubuntu way", easily.

Make a totem plug-in that temporarily lowers read speed during playback of cd/dvd media. it should not be to hard, take little code here and there then automate it (i lack the 1337n355 to do it unfortunately): theres two commands that do this already, http://blog.mfuchs.org/?p=15 and two programs, one that as far as i can tell runs from the terminal and one kde native, http://linux.softpedia.com/get/System/Hardware/cdspeed-15269.shtml http://nixbit.com/cat//utilities/set-cd-rom-speed/ the point is to make it work the "ubuntu way", easily.

Written by oliver-joos the 19 Nov 09 at 19:46.

The driver behind /dev/cdrom should lower or raise the drive speed as needed. To achieve this it could take into account the number of bytes in its read-ahead buffer. And it could count the bytes per second he delivers (averaged over several seconds). Then it's possible to set the optimal speed.

Unfortunately the possible speed settings for a drive depend on vendor, product and media type. So I propose to have safe defaults and to implement a user-space tool to acquire the optimal values. This tool could also measure the speed for minimal latency when an idle drive is accessed. (It may be faster to fetch directory entries if the drive does not have to spin up to full speed first!)

The tool stores the optimal speed table in a human-editable file in /etc/ and sends them through /proc/ to the driver upon each media insertion, suspend/resume or reboot.

The driver behind /dev/cdrom should lower or raise the drive speed as needed. To achieve this it could take into account the number of bytes in its read-ahead buffer. And it could count the bytes per second he delivers (averaged over several seconds). Then it's possible to set the optimal speed. Unfortunately the possible speed settings for a drive depend on vendor, product and media type. So I propose to have safe defaults and to implement a user-space tool to acquire the optimal values. This tool could also measure the speed for minimal latency when an idle drive is accessed. (It may be faster to fetch directory entries if the drive does not have to spin up to full speed first!) The tool stores the optimal speed table in a human-editable file in /etc/ and sends them through /proc/ to the driver upon each media insertion, suspend/resume or reboot.