|
Avid Pro Audio CommunityHow to Join & Post Community Terms of Use Help Us Help YouKnowledge Base Search Community Search Learn & Support |
#11
|
||||
|
||||
Re: Error message on line 994
Hey
You wrote: I'm running 2019.6 with HD Driver 2019.6. So goto applicationsand Avid and find the folder and use uninstall HD driver.
__________________
Best Regards Christopher #thestruggleisreal South Side Music Group WEBHOME |
#12
|
||||
|
||||
Re: Error message on line 994
Quote:
You might also uninstall Avid Link(just as a "hail Mary"). Sadly, running Pro Tools on a PC laptop is pretty much a crapshoot(unless that specific model is known to work). If you don't specifically need Pro Tools, you could try Reaper or Presonus Studio One(both are very capable programs)
__________________
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 |
#13
|
|||
|
|||
Re: Error message on line 994
I'd also like you to be telling us the exact name of the Playback engine you are selecting in Pro Tools and all the other choices you get in that dialog screen.
Quote:
Keep ASIO4ALL off your system, you don't need it, and its possible to get things misconfigured there that can cause problems. As multiple people have pointed out now windows laptops (and desktops) are a crap shoot. Sometimes that is down to specific hardware, but sometimes that is all the crapware and bad drivers packaged by the OEM. When you installed Windows before did you do what I suggested and do a clean install from Microsoft installers and manually install any needed drivers? That means carefully picking the bare minimum of drivers to install to get working (like a graphics driver if needed) and not letting Windows automatically install stuff and certainly not using OEM recovery partitions etc. And then only installing Pro Tools and the ILM driver and your interface driver and testing if that works at all. Do not install *anything* else. Even if doing this means you buy a new Windows license (ideally Windows 10 Pro to make disabling auto updates easy). The effort to try doing stuff like that this may not be worth it, it may be more cost effective to just get rid of that laptop if no other options work. And all this for Pro Tools First? Pro Tools First was supposed to be easier to work with Windows audio devices, Avid failed there. Unless you need to use Pro Tools First I'd just give up on that and try another DAW, not all DAWs require an ASIO driver and most other low-end DAW are a simple/rbetter packaged/more reliable to get started with that Pro Tools First. I'd look at Reaper for example. |
#14
|
|||
|
|||
Re: Error message on line 994
My computer is brand new!
Bought in May 2020 without nothing else installed. I have just unboxed it. Cortana, Skype, McAfee... come with the original package. As hardware I can see : Realtek ASIO when nothing is plugged When i plug the Behringer 202HD, I can see : Realtek ASIO and UMC202 ASIO Nothing else installed. Everything crashes... Tested all your hints. No solution. |
#15
|
|||
|
|||
Re: Error message on line 994
Quote:
I've said multiple times now all that included crapware may be the problem. You have *not* tried doing a clean Windows install. If you have tried everything else your options are: 1. Download a windows installer from Microsoft and try that, not the Dell crap you are wasting your time with. 2. Switch to another DAW. 3. Open a trashcan and deposit the Dell laptop. |
#16
|
|||
|
|||
Re: Error message on line 994
This is scary since I have a new XPS 13 coming. BUT that being said, I have an older Lenovo that was workiing fine and all of a sudden it's not. This is some kind of design flaw that is not being accounted for properly. I'll post back when and if I resolve the issue on my Lenovo and when and if it works on my Dell.
I'm using a Focusrite 8i6 (3rd gen) currently. And to Avid, I am about to purchase thsi software (using PT First currently) and this isn't promising. Quote:
|
#17
|
||||
|
||||
Re: Error message on line 994
Cockos Reaper and Presonus Studio One are both solid alternatives to Pro Tools and are far less hardware-dependent Unfortunately, Pro Tools is not for the faint of heart, but in truth, all the major DAWs are very capable
__________________
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 |
#18
|
|||
|
|||
Re: Error message on line 994
Quote:
Many problems are self inflicted by users, especially not making sure all their software, Windows, interface drivers, third party plugins are compatible, and not doing proper Pro Tools systems optimization (read under "help us help you" up the top of every DUC web page). Unfortunately Pro Tools is very fickle, it's a real-time latency sensitive application with lot of old legacy code hanging around. Just about every Windows OEM PC is different from others because of hardware differences and the amount of crapware, including AV software, OEMs install. So that helps cause a mess... Avid can't test/know this stuff works great on every PC/OEM combination out there. Personally I could not waste my time with many typical Windows OEM PCs. The first thing I would do is wipe the machine and do a full clean Windows install. The best Windows PCs for Pro Tools are either ones you build yourself (or have built for you) based on proven build configs on DUC, or you buy from a specialist builder like https://www.pro-tools-pc.com. Now for less demanding stuff many PCs will work, you typically run into problems as you need to push more demanding sessions/plugin processing/low-IO buffer performance. Windows Laptops seem worse here than desktops, you should plan on testing this and if you have serious problems be ready to return the laptop within the return period. |
#19
|
|||
|
|||
Re: Error message on line 994
I still have this problem sometimes, but I've found out why I have it, so maybe you're having the same problem and this will help. Windows is greedy, it will grab the first interface it wants for it's default sounds "ding" before anything else gets a chance to allocate an interface. I have two interfaces connected that I use for different purposes. One is a little Focusrite Scarlette and the other is a more elaborate MOTU. When I boot Windows it will randomly grab an interface, be it the Scarlett, the MOTU, or the one that's attached to the motherboard. ProTools gives me a hard time if Windows has already taken the interface I want to use, so I have to go in and open Window's mixer, change it's interface, and then re-boot ProTools and start over. There's probably some way to change these in the OS defaults, but I haven't figured out how and it's annoying, especially if I'm trying to get right to work. Good luck and I hope this helps!
__________________
Andy Profane |
#20
|
||||
|
||||
Re: Error message on line 994
Go to Control Panel>Sound and choose the interface you want for Windows sounds/audio in the Playback and Record tabs, normally your onboard soundcard, and be sure what you chose is designated as the Default Device. Then in both those tabs, Disable anything else. Be sure to check these settings after any Windows update as an update can sometimes revert them.
Then, when opening Pro Tools, hold down the "N" key as you start PT so the Playback Dialogue Window is shown and chose the interface you want to use.
__________________
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 |
Thread Tools | Search this Thread |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Help for Error Message - Assertion in "..\Mdie_TrackPlayer.cpp", line 476 | lbpease | Pro Tools 10 | 7 | 01-05-2014 12:15 PM |
OMF Import Error Message, Line 162 | pseradarian | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 2 | 03-05-2012 03:04 PM |
What do I do? Error Message: "CNeolnode.cpp", line 1242 | naterothstein | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 1 | 01-10-2008 02:41 PM |
Error message CNeolOBLock.cpp line 164 | bseamus37 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Mac) | 4 | 10-07-2007 09:14 AM |
Error message: Assertion in line 1358 | Holly73 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 0 | 09-02-2006 09:19 AM |