Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am unsure as to whether this is the appropriate region to place this document but am curious about something involving audio recording. The problem is complete destruction of synthetic music recorded in different applications being run on various settings, the results being very horrible overall.
From what I have come to understand this is primarily the result of the CPU levels involved not being in accordance with the standard Linux kernel. If it is of any relevance what I am recording from is a typical stereo cable run between a synthesizer and PC audio in. I am positive it is not the hardware at fault either as I have tried this with numerous cables, and have done the same routine with a game boy running LSDj rather than the synth.
From what I have read so far this has been a problem for many with the best solution being switching to a kernel with real time patches?
What I am wondering is just how well the real time kernel patches included in the 64 Studio distribution work to defeat these issues, and if it is worth my installing it. Is it perhaps comparable to the results I might receive recording on a MS box. Alternatively are these patches something that can be used like an add on to my current operating system without causing any problems in its functioning or is an entirely new distro a better choice?
Because, if you think your problem is being caused by your CPU being overloaded, you might be able to solve the problem by "unloading" the CPU before you try to do audio stuff. I. e. you might be able to kill certain processes or applications, which will free up memory and CPU time, before you try to do your audio work.
I suspect you might have something else that is wrong though. Do you mean you cannot record any audio successfully on the system? Or are the files you end up with corrupt? How are you attempting to record the sound? Which application are you using?
Hello, thank you for responding. So far I've tried recording under various settings in Audacity, and another simplistic application called QaRecord, among others to a lesser extent. The actual recording is being accomplished, it's just takes place in a manner such that the resulting wav files are so overflowing with cracks and hissing that no level of editing is capable to drown them out. It does this to such a degree that often times entire instruments will just be turned to static in the file.
I am somewhat familiar with the aspect of CPU overload as you speak of it here and went so far as to experiment with the principal in recording with minimal activity on the system, and also with my set up as it normally is. After comparing the recordings the difference is definitely noticeable but it did not remedy the problem I'm afraid. Would you able to provide me with any bash commands I might use to temporarily halt all other activity temporarily and then reverse when I am done recording. Even if I do end up installing 64 Studio I'm sure such a thing would be useful to have at my disposal in the future.
As for the hardware I've been just been using a standard 1/8'' stereo cable jacked into the back PC audio-in port. The instruments used including a XioSynth-25 as well as different Nintendo game boy consoles running LSDj. Regardless of what is being recorded from the results seem to be the same across the board.
I have now remedied the situation in full by booting a live CD of S64, as the program within are completely functional for recording in this disc booted mode, and as I generally save everything to my usb pen to begin with everything works out just fine this way. Thank you for your input Rylan76.
Cool, glad you got it working. I'm not sure what was wrong, I once had the same problem you describe and it turned out to be very simple - my audio cable running to the mike jack on my SBLive 5.1 had broken down inside (due to age and too much bending back and forth of the cable). I was using it to record voice, if you moved your head even slightly while recording (i. e. moving the cable and disturbing it) you'd get the pops and crackles and hisses you referred to.
Anyway, hope you can now successfully do what you want to do!
I'm afraid I spoke somewhat prematurely in regards to the functionality of Studio 64 off running off of a live disk. Unfortunately my connection is wireless and I could not do the full install as many disto's I would like to be using as primary systems are not familiar with the router I have set up. Shortly after my last post I began seeking other alternatives and managed to obtain a Win XP ISO, flash it to DVD and went about installing it as a third partition which I only intended to have active in the rare periods I wanted to record music. However after the install I learned that the Windows boot loader does not play well with LILO, as my other Linux partitions were destroyed by Windows XP.I've now Mandriva 2010 re-installed and am about to install the XP within a virtual box just to see if its supposed prowess in the field of audio development holds true as an emulated system. It seemed relatively lower end to me though and not notable fast in any way, but I'm going to try it anyways. In any case I doubt it can hurt anything from within the confines of a VB. If this attempt does not work right off the back I'm resuming my search for any driver that might make Debian usable over my D-link router, or bringing my box to the home of someone with a live feed I can plug into just to get S-64 fully installed.
Any links or suggestions, I have already tried carrying in a Madwifi package and every relevant driver I could sink my claws into via usb pen. I have a strong feeling there must be something I have not tried yet.