|
Audio
Feb 15, 2011 12:10:36 GMT -5
Post by pharrisire on Feb 15, 2011 12:10:36 GMT -5
While knos was making the boot-able stick, I listened to an audio track. It was kinda jumpy, so I'm guessing the making-boot-able-stick process is very cpu intensive? It would probably help to shut off all that psychedelic visualization stuff, but I haven't yet figured out to get just audio without the extra visual effects. But I do have audio on the desktop - now if I could only get it on the laptop....
|
|
|
Audio
Feb 15, 2011 20:27:51 GMT -5
Post by Kevin McAleavey on Feb 15, 2011 20:27:51 GMT -5
While knos was making the boot-able stick, I listened to an audio track. It was kinda jumpy, so I'm guessing the making-boot-able-stick process is very cpu intensive? It would probably help to shut off all that psychedelic visualization stuff, but I haven't yet figured out to get just audio without the extra visual effects. But I do have audio on the desktop - now if I could only get it on the laptop.... In order to ensure that the stick is made properly and includes every single piece of every file, we use a special internal copy function in the kernel that can hit 100% CPU during very large files. This is inevitable owing to the way that the special cpio copy operation works and it is prioritized over anything the desktop is doing. While it's copying those last four VERY huge files, it can actually stop the desktop cold with only very short and infrequent allowances for the desktop to run at all while it's doing that. We warn about that when the stick-making process begins and there's no way around that since it's done in the kernel itself which has the priority while the stick is being made. No way around that though ...
|
|