![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
#1
|
|||
|
|||
![]()
Is there anybody you got the some problem with the latest ASIO driver ???
Instaling the latest 002 rack driver and then Pro tools 9. If i play back the sessions under pro tools everthing is fine. When i launch cubase 6 and hit play the session sounds like trash. Like a tape that is too slow and distorted !!! I did everything. reinstalling the driver, config the controllpanel under cubase 6. nothing worked !!! But my itunes and system sound is normal !!! I decided to install the Beta driver from Pro tools 8.04. After installing i launch pro tools ( fine ) and then cubase ( fine too !!! ). What the hell is going on with the latest Asio driver in cubase ??? Any Ideas ?????? |
#2
|
|||
|
|||
![]()
Let me get this straight? Your Pro Tools is working fine, but your Cubase 6 is broken? You might want to the Cubase Forum and ask the same questions, You asked here on the Pro Tools Forum.
__________________
Producer/Engineer/Musician RIAA Platinum Sales Award: Lisa Stansfield "Affection" Main: Model: Dell 5750 Precision Workstation OS: Windows 11 Pro 64bit CPU:*Intel Core Processor i7-10750H (6 Core, 12MB Cache, 2.60 GHz to 5.00 GHz, Memory:64GB, 2X32GB,DDR4 2933Mhz Non-ECC OS M.2 512GB PCIe NVMe, Record Intel 1TB SSD, 2T SSD, 1TB SSD Focusrite Scarlett 18i20 3rd Gen AVID Pro Tools 2022.12 JBL LSR4328P 8" JBL LSR310S 10 inch Powered Studio Subwoofer* Yamaha HS50M Studio Monitors Alesis Elevate 3 Studio Monitors M-Audio Axiom 61 Midi Controller |
#3
|
|||
|
|||
![]() Quote:
|
#4
|
||||
|
||||
![]()
Did you by chance install the 002/003 controller driver instead of the rack driver? Now that you have the 8.0.4 beta driver, you should probably remove that and reinstall the correct driver(and cross your fingers). Mixing and matching is less likely to work
![]()
__________________
Gigabyte X79/intel i7 3930K, 32GB RAM, HD/Native, 192 IO 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 |
#5
|
|||
|
|||
![]()
O.K
Dear justus1900. I know this is the pro tools forum.Thats the reason why i post my question here! I use Avid / digidesign hardware and what to know if anybody got the same problems or got problems with Avid´s ASIO 002/003 rack driver 9.0. see the post from cherryrecording !!! Dear albee1952 i checked the driver twice times but it was the 002/003 rack driver. O.K removed the 8.04 driver and reinstall the latest driver and cross my fingers. !!! the same problem !!! the ASIO driver doesn´t worked right!!! the 8.04 driver worked right in any DAW thats supports ASIO but the new one did not !!! Dear Avid !The 002/003 console driver doesn´t worked correct ( in pro tools ) and the 002/003 rack asiodriver doesn´t worked correct too. What´s going on !!! |
#6
|
|||
|
|||
![]()
I agree, I have also updated to Pro Tools 9 and there is a lot of strange issues appearing. If you like to use in my case the 003r asio in Cubase it will crackle from hell, but if you switch to Generic Low Latency ASIO that its normal but then midi and stuff is out of order :-/
However, if you use Pro Tools 9, it sometimes still launches the app without the digi hardware and if you like to close it down it crashes. Here is another thing: on the digi003r the HOST LED flashes all the time ... why ? what does it mean ? Of course the avid support side does not have an answer. no matter what the name is changed to but the messega from the company is still: like it to work ? buy our expensive HD gear. any solutions are welcome |
#7
|
|||
|
|||
![]()
I have the same problem. See my post http://duc.avid.com/showthread.php?p...=1#post1753517
Really the problem is driver vs9. I think that we need to wait for new driver to solve this... |
#8
|
|||
|
|||
![]()
I'm having "fun" with the driver too.
1) ProTools would work fine, but when I try to close at the end of a session, the project would close, but PT would not. I have to use Ctrl-Alt-Delete. 2) I would switch the DIGI 002 on, but the FW light on the unit would flash, and there is no "Stand By" message. When this happens, PT would see it, but Sequoia won't (of course, this is after I close PT). 3) On XP, if I'm working with PT, the unit would say, "Stand By" before I open PT. Now, sometimes it says , "Stand By", and at other times the "Stand By" disappears after three seconds, but LED remains lit. Sometimes I "repair" the driver, sometimes I re-boot the computer and it works.
__________________
Derrkins GuyBarTola ******************** PT 2018; Nuendo 8.?; Studio One 3; former Sonar and Sequoia user .... GENELEC 1031A, AVANTONE MIX CUBES (Active); Sibelius 7.0; Dorico; Mac Mini 2.6 GHz Core i7, OS X 10.12.2 Sierra; 16GB RAM; 480 GB System SSD; 1 TB 7200 rpm Audio; 3 TB samples; Roland A-800 Pro controller; GOOD BYE PEE SEA!! |
#9
|
|||
|
|||
![]()
Which driver are you using? It seems to me that you should be using the driver that came with PT9 or the latest one from their site. I remember having some issues on an earlier PT install with ASIO driver on Mbox Mini. If I remember correctly, I went into Device mamager and unistalled the Mini. Then I went into the Program manager and deleted the software associated with the Mini (in my case, AVID Mbox 2 USB drivers). Rebooted system. Device manager reported unknown device (Mini). Reinstalled driver from PT9 driver disk. Worked fine. I believe that just reinstalling the driver may not be enough. There may be some software from a previous install that is giving problems but is not overwritten by the driver installer. I believe that unistalling the device coupled with unistalling the software flushes the system properly.
|
#10
|
|||
|
|||
![]()
Thanx for the response!
This was a clean install of Win 7, on a new hard drive, with the downloaded PT 9, and the new driver from the site. I might have even un-installed the driver, in the blur, but I'll try it again. Based on a comment in your post, I'll try re-booting with the DIGI 002 plugged in and turned on, when I re-install the driver. So many tries, in so many ways, I'm sure I forgot how many things I tried. Thanx again! ![]()
__________________
Derrkins GuyBarTola ******************** PT 2018; Nuendo 8.?; Studio One 3; former Sonar and Sequoia user .... GENELEC 1031A, AVANTONE MIX CUBES (Active); Sibelius 7.0; Dorico; Mac Mini 2.6 GHz Core i7, OS X 10.12.2 Sierra; 16GB RAM; 480 GB System SSD; 1 TB 7200 rpm Audio; 3 TB samples; Roland A-800 Pro controller; GOOD BYE PEE SEA!! |
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
DIGI ASIO DRIVER PROBLEM WITH FL 8 "Not Enough ASIO output channels available. | scottthafoo | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 14 | 04-19-2010 01:45 PM |
PRO TOOLS 7 ASIO DRIVER PROBLEM | instro001 | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 2 | 12-17-2005 07:57 AM |
ASIO / Wav Driver Problem (or maybe not) | jboaze | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 1 | 09-28-2004 10:44 PM |
002 ASIO Driver Problem | shipwrecked | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 1 | 01-15-2004 05:36 PM |
ASIO Driver Install Problem | splattstudio | Pro Tools TDM Systems (Win) | 9 | 11-05-2003 12:05 AM |