Aurdor clicking issue

  • socphoenix
Posted: Mon, 03/10/2008 - 14:31
I recently tried to use Aurdor as a multi-track recording, layering the recording so I didn't have to do a whole song at once, and I noticed this really annoying click at the beginning and end of the audio files. I tried to cut it out, but it always happens anyway. Would anyone happen to know how to get rid of these clicks? I know that Adobe Audition occasionally gets quieter clicks that are similar that come out when the file is burned to a CD. Not sure if this is the same kind of thing. Thanks for the help! Michael -}SoC{phenix www.teamsoc.net

problems solved (not usre how I fixed Jack, though)

  • socphoenix
  • 03/07/08
  • Fri, 03/14/2008 - 02:49
I recently got the click out of my projects, and realized what it was. I was recording something really quite, and if there is not enough sound, you can hear the click, which is probably true of any audio system. For instance, the wave track wasn't even visible in the editor window. That was the reason that i could hear the clicks (I think Quentin's idea helped, though). As for Jack, though, I'm still not sure what caused it. I think I may have fixed it when I finally got the QT I had been trying to install, even though the "environmental variables" never got set right. I could not get Jackctl to acknowledge that I have new enough drivers, but it fixed every problem I had with Jack even before it had just stopped working. So I guess I must have accidentally done something to QT. Thanks for all the help, Michael -}SoC{phenix www.teamsoc.net

Restore...

  • Quentin Harley
  • 05/24/07
  • Tue, 03/11/2008 - 06:47
In Linux, you can either just uninstall the app, or reinstall. Luckily Linux does not have the annoying registry found in the "Other OS". You might have problems because of two instances of jackd being installed. The version bundled with 64studio at the moment is quite stable, and the problem is almost definitely with the onboard sound and the settings for it. Sorry... You *can* make it work, but there is always some compromise.

more bad news (for me)

  • socphoenix
  • 03/07/08
  • Tue, 03/11/2008 - 05:26
It has actually stopped giving me that error, to be replaced by another one. I use a Realtec AC'97 onboard card right now, since my wonderful high-school budget cannot afford to go out and buy any good equipment right now. I tried to update Jack, which is probably why the new error is coming up, so I will paste the error, and then retrace all that I did (plz bear with me, I am a complete Linux noob, and I honestly am kinda confused when I see a huge error file, or stuff reacts adversely to something that would work fine with Windows). The error file looks like this: Creating link /home/michael/.kde/socket-64studio. 01:15:41.861 Startup script terminated with exit status=256. 01:15:41.861 JACK is starting... 01:15:41.861 /usr/bin/jackd -R -dalsa -r48000 -p512 -n4 -D -Chw:0 -Phw:0,0 01:15:41.863 JACK was started with PID=12957 (0x329d). ALSA: final selected sample format for capture: 32bit little-endian ALSA: use 4 periods for capture ALSA: final selected sample format for playback: 32bit little-endian ALSA: use 4 periods for playback 01:15:48.027 Could not connect to JACK server as client. Please check the messages window for more info. Cannot read socket 65 0 (Success) Cannot read socket 65 0 (Success) JackSocketClientChannel read fail Cannot open qjackctl-12880 client pthread_cond_timedwait error usec = 5000000 err = Connection timed out Driver is not running Cannot create new client Poll client error err = No such file or directory Client not opened 01:15:49.875 JACK is stopping... jack main caught signal 15 Now what I had done was to update Jack with Jackctl from the help file on Jack, so I donwloaded the updated QT and attempted to install it, getting errors in make and make install. They had to do with missing files, so I'm assuming that QT didn't change any files. Same with the Jack installation. When it didn't see QT 4.1, it exited before installation. Another good question would be is there a system restore option, where all the dumb mistakes I made can be undone like Windows?

Hardware & Settings

  • Quentin Harley
  • 05/24/07
  • Tue, 03/11/2008 - 04:15
Please let us know what audio hardware you are using, and also give us the settings you use in Jack Control. There are some combinations that needs precise setting to get right... Booting every 5 minutes is not why you want to use 64studio. I can have my system running for days if needs be. I regularly do 3hr+ multi track recordings.

Ardour clicks

  • socphoenix
  • 03/07/08
  • Tue, 03/11/2008 - 03:56
your method fixed the problem, although Ardour 2.3 still had the clicks from my files I had already done :( I do have one other problem, which I would like to put up here to save forum space, and look at little less annoying.... Jack has been freezing up on me, stopping itself with the following note in messages: JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected 23:34:10.565 Audio connection graph change. 23:34:10.594 Audio connection change. 23:40:27.189 Audio connection graph change. 23:40:27.264 MIDI connection graph change. 23:40:31.780 MIDI connection graph change. 23:40:31.899 MIDI connection change. 23:40:32.184 Audio connection graph change. 23:40:49.395 Audio connection graph change. 23:40:49.579 Audio connection change. 23:41:04.281 Audio connection graph change. 23:41:04.445 Audio connection change. 23:43:18.698 Audio connection graph change. jackd watchdog: timeout - killing jackd 23:49:30.512 Client deactivated. 23:49:30.513 JACK was stopped successfully. 23:49:30.513 Post-shutdown script... 23:49:30.513 killall jackd 23:49:30.514 Shutdown notification. zombified - calling shutdown handler cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) cannot send request type 7 to server cannot read result for request type 7 from server (Broken pipe) 23:49:30.518 MIDI connection graph change. jackd: no process killed 23:49:30.728 Post-shutdown script terminated with exit status=256. Is there a way to get rid of this? I am having to reboot the computer like every five minutes from this. I think it may have to do with Jack setting I used to get lower latency, will be seeing if that solves the problem.

Ardour clicks

  • Quentin Harley
  • 05/24/07
  • Mon, 03/10/2008 - 17:18
There was a ticket open at ardour for this problem. I don't know if it is fixed in ardour 2.3 yet, but there is a workaround. The clicks only appear if a earlier clip is higher than a later one - that is, the end is exposed. This happens if you move a earlier clip, and you have "Last moved is higher" activated - (Default) In the options settings somewhere, you can specify that later clips are always higher. I used this workaround, and I do not have any problems with clicks. I am not in front of my system at the moment, but if someone has not pointed you in the right direction before I am, I post the right place. Try it and give us a shout. The guys at Ardour are working hard to get everything 100%, (or 99.95%) and we should see a new release of ardour soon. Cheers,