|
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
Clicks and co.. What's wrong?
Hello,
I'm a bit desperate.. I am working on a laptop bought 6 months ago (end of 2021), a Dell Precision, i7, 16go ram, Windows 10 pro, and this computer has a NVDIA Quattro 500 graphics card. I use Ableton Live, which runs without any problem (the CPU overhead goes up to 70% with a 256 buffer without me hearing any click or other playback error). For professional reasons, I had to switch to Pro Tools (one year Studio license). I use a Focusrite 6i8 3rd generation sound card connected to USB-C. But I've been using it for a few months now, and I've got some unwanted clicks. Even with a 20% CPU, these clicks happen quite regularly (sometimes nothing for 15 minutes, then it doesn't stop...) I followed AVID's advice to the letter regarding the optimization of Windows 10 to use Pro Tools. - I disabled all the so-called CPU optimization options in the BIOS (hyperthreading, voltage adjustment to save battery, etc.) - I have disabled all the peripherals that are not useful to me, network card, etc.. - I disabled the embedded sound card directly in the BIOS - I created a new user account in Windows (of course, this is useless) - It goes without saying that all drivers are up to date. - I disabled the Windows battery management Despite this, I still get these unwanted cracks. No matter how many times I turn the problem over, I don't understand what's wrong. My Windows installation is clean, no suspicious programs, and as I said, Ableton runs perfectly on the same machine! The disk usage indicator is at zero, I don't use many tracks at the same time. Some plug in (but the CPU stays under 25%) So, if someone has a clue that I haven't explored yet, I'd be extremely grateful! Have a nice day! PM |
#2
|
||||
|
||||
Re: Clicks and co.. What's wrong?
Hmmm, here are some thoughts:
1-Are the clicks random or actually part of the audio wave? 2-What are the specs of the drive you are recording to? 3-You didn't need to disable the on-board sound card in BIOS. What you do need to do is make sure that Windows is NOT using your interface as its default playback device(in Sound Properties) 4-Does the laptop have any standard USB ports? If it does, I would try connecting the interface that way(at least to see if it makes a difference) 5-You mention SOME of the recommended tweaks, but you didn't mention disabling Power Management on all USB ports(sometimes aka "USB Root Hub")in Device Manager.
__________________
HP Z4 workstation, Mbox Studio https://www.facebook.com/search/top/...0sound%20works The better I drink, the more I mix BTW, my name is Dave, but most people call me.........................Dave |
#3
|
||||
|
||||
Re: Clicks and co.. What's wrong?
Have a look at this thread and consider setting Processor Affinity.
Also look at the "Help Us Help You" link at the top of every Forum and post a Sandra Report.
__________________
Take your projects to the next level with a non-union national read at reasonable rates Demos: brucehayward dot com SonoBus Source-Connect: brucehayward Options for Remote Direction |
#4
|
|||
|
|||
Re: Clicks and co.. What's wrong?
What exact version of Pro Tools are you running?
What version of driver for your interface? And importantly, confirm you are not running ASIO4ALL. Lots of good advice sofar. You are unfortunately lost on some stuff here and you do need to get things you are doing right. You also do not mention the most basic very relevant info like IO buffer size or sample rate you are running Pro Tools at, or if you have ignore errors checked... if so uncheck that, you want to see any AAE error. What is disk cache set to? with small test sessions just set that to 1GB or so and let the session fully load (disk cache meter turns green and has significant free space) before starting to do anything. Looking at meters and % CPU rarely tells you anything useful and is likely a waste of time. That's been discussed to death on DUC before. Since the 6i8 has optical digital input...are you using that for anything? is that input set to be the clock source? if you are not using it disconnect anything connected there and make sure the clock source is set to internal in the 6i8. There are standard troubleshooting directions under "help us help you" up the top of every DUC web page. starting with trashing prefs--always start there, and especially trouble shooting plugins by moving aaxplugin files out of the plugin folder (and I would trash prefs again after doing that)--always suspect plugins, yes even ones installed but not being used. There is lots of standard troubleshooting stuff you don't seem to have tried... or if you have you need to tell us. Purchasing the PT Trasher app will make trashing stuff easier. http://www.pro-tools-pc.us/category-s/1514.htm Still stuck after working through all this describe all that standard troubleshooting you have done and what you saw (take notes as you go), and post a SiSoft Sandra report. Last edited by Darryl Ramm; 07-04-2022 at 02:30 PM. |
#5
|
||||||||
|
||||||||
Re: Clicks and co.. What's wrong?
Hello
Before, thank you for your answer. I detected a bit of mistrust on your part, which I can understand. But you should know that I have been looking for 6 months, and that posting my question here was the last resort. I'm familiar with the DAW pro environment, I've been working with Ableton for a long time, and a little bit of Cubase, on the same machine we're talking about here. Albee: Quote:
Quote:
Quote:
Quote:
Quote:
Darryl Ramm: Quote:
The driver is version 4.65.5, the latest one I think. But same remark: there was an update since and I had the same problem before. I also have a 2i2 first generation with which I have exactly the same problem. I don't have ASIO4ALL. Quote:
The disk cache is set to "Normal" but from experience I doubt that the problem comes from there. But I will do the test for the sake of awareness. The "ignore errors" box is unchecked. Quote:
The preferences and plug ins have been removed. Indeed, I forgot to tell you, but I really tried everything. I have read dozens of articles like "how to optimize windows 10 for audio, for pro tools" and all that goes with it. The thing that really pisses me off is that I have NO problems with other DAWs. Is spending most of your time fiddling with your computer part of the "classic" use of PT? (yes, there's a bit of irony in my question ) Thanks for taking the time to answer me and sorry for my incomplete question |
#6
|
|||
|
|||
Re: Clicks and co.. What's wrong?
I forgot to mention something important: even with a single audio track without effects/plug in, the problem is there!
So it has nothing to do with the size of the project. I posted a long answer but it's waiting for moderator aprobation. |
#7
|
|||
|
|||
Re: Clicks and co.. What's wrong?
Quote:
Plug-ins installed in Pro Tools but not being used are very capable of causing CPU problems. Again, you need to be following the standard troubleshooting approach. Have you moved *all* .aaxplugin files out of the plugin folder, trashed prefs and tested with that? And if that does not solve the issue then leave the other plugins uninstalled when you do other testing. |
#8
|
|||
|
|||
Re: Clicks and co.. What's wrong?
Quote:
Thank you for your kind reply. In a reply I posted a few hours ago (but which does not appear, I do not know the reason for this blocking), I explain that I have this problem since February, and that I have repeatedly carried out the procedures for resolving the problems. Removing plug ins? done! deleting preferences? done! I didn't mention it clearly in my initial post but I've done ALL the maneuvers mentioned here (I did the maneuver of changing the disk cache this afternoon, without result). Posting a message here is a last resort for me, don't think I'm going to ask you a question if the answer is on the first page found on google! Thanks |
#9
|
||||
|
||||
Re: Clicks and co.. What's wrong?
Make sure your laptop is plugged in or at least that the interface is on a powered USB hub. Trying to run a FR on battery power is not a good idea.
Increase the buffer size for your interface. FR has several interface drivers that can be accessed from PT Options menu. If you don't need to monitor through Pro Tools knock the buffer up high as you can. Do the affinity deal. It sometimes does nothing on big fast machines. On laptops it can be a life saver 16 GB is not really a lot for the latest versions of PT so you may consider upping it. On laptops with USB C an ultrafast thumb drive works better than trying to record to the system drive in most cases.
__________________
Dell XPS 8900 i7-6700K CPU @ 4.00GHz 64 Gig Memory:Seagate 2x 2TB, 4TB,500gb EVO OS Windows 10 pro PT 2023.3 Studio through an A&H Qu-32 |
#10
|
||||
|
||||
Re: Clicks and co.. What's wrong?
Quote:
Quote:
Quote:
Quote:
Thank you for these lines of thought but unfortunately the problem is always present. :-( |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
What am I doing wrong!!! | Kosta972 | General Discussion | 9 | 08-28-2012 08:41 PM |
What am I doing wrong??? | mnewb1 | Eleven Rack | 16 | 04-28-2011 04:53 AM |
Wrong file is being played and waveform is wrong | jmullins | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 0 | 04-30-2010 01:29 AM |
what did i do wrong? | lightning ad | Post - Surround - Video | 7 | 01-20-2004 02:51 AM |