![]() > # from /etc/grub.d and settings from /etc/default/grub > # It is automatically generated by grub-mkconfig using templates > sectors/track, 121601 cylinders, total 1953525168 sectors Units = > Partition Start Sector End Sector # of Sectors System /dev/sda1 > Partition Boot Start Sector End Sector # of Sectors Id System > sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 > sectors/track, 15566 cylinders, total 250069680 sectors Units = > Boot files: /boot/grub/grub.cfg /etc/fstab > Boot files: /Windows/System32/winload.exe > Boot sector info: No errors found in the Boot Parameter Block. ![]() > Boot sector type: Windows Vista/7: NTFS > Mounting failed: mount: unknown filesystem type '' => Windows is installed in the MBR of /dev/sdb. > => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at This is the output of bootinfoscript: > Boot Info Script 0.61 ![]() I have Ubuntu 12.10 and Windows 7 installed somewhere on the same drive. It is probably worth mentioning that the BIOS uses UEFI to manage it's booting. I have tried both boot-repair and sudo update-grub to no avail. But I can't boot into Windows because I don't see it in the GRUB. It is still worthwhile playing with the settings and listening to the results while setting it up though.When I turn on the computer, I can see the GRUB and boot into Ubuntu. This can be worked around by processing with the sound turned off. It refuses to continue, but can still be stopped and restarted from the beginning (without losing the settings). I have found one bug in the Linux version - sometimes processing stops when the sound is turned on to listen to samples. Until recently, I was running Clickrepair under *******, but now (at last!) I have it running on my new PC under Ubuntu. If you want the best results, you need to experiment with different settings, often for each LP. There is a learning curve for ClickRepair, don't expect to master it in one hour. The results are, in my opinion, excellent. I find it takes up to 1/2 hour to process an LP, sometimes more in a bad case. This way the repairs are completely undetectable. This way the start and finish points for the worst clicks can be adjusted manually before making the repair. I find it best to set "automatic" to around 80 or 90. ClickRepair is brilliant at correcting faults, but not so good at selecting the best start and finish point for each repair. Don't expect to let it run on fully automatic if you want first class results. I have found, though, that it is best to use some manual intervention unless you have a really pristine LP. With care, all trace of clicks can be removed, the sound is clearer, and there is no loss of brilliance. I have been running ClickRepair for several years now, and I have used it to process the sound from approaching 100 LPs. Thanks for your comments btw, appreciated. Yes and it is not of the quality of any of the others I have noted. Yes, though the one in the repo works with the Ubuntu sound server and the changelog does not warrant my changing distro for the minor improvements mentioned.Īnd btw have you tried the noise removal in Audacity? ![]() You'll probably have to compile it manually, but it might be worth the effort. I see that the ( GWC ) version in the Ubuntu repository is not the latest, so you might have a look at the latest versionĪnd check the changelog for improvements made. I had heard reports on WinForums of acceptable auto-mode from Click-Repair and am interested to hear if users of the Linux version have the same to say. Manual de-clicking takes soooo looonnngggg. It, and most others, fall short when used in auto-mode. GWC is a fine app and used for Manual restoration is as good as any I have tried. On the homepage there are lots of restoration tips.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |