|
Subject:recording/playback issues
Posted by: paeaek
Date:5/1/2002 7:34:54 PM
I have used ACID 2.0 for years and have never ever had such a problem. Sometimes when I record, the existing loops and audio will play ahead of time. Forexample, I will initiate the recording and instead of the song playing where I expect it to start, it starts "ahead" of time (passing the marker I want to start recording at). Second, when it does record ontime, I will goback ro listen to my recording and the recording is not lined up with the rest of the song and is usually "ahead" of time. What the hell??? I want to go back to my Acid 2.0!!!! Same computer same setup.... Anyone have any ideas??? |
|
Subject:RE: recording/playback issues
Reply by: Ted_H
Date:5/2/2002 10:42:16 AM
Try updating your sound card drivers. Driver updates can be downloaded from the manufacturer's website. Ted |
|
Subject:RE: recording/playback issues
Reply by: paeaek
Date:5/7/2002 6:44:11 PM
Unfortunately, it didnt work... It is driving me crazy. As it is, I am on the phone with CREATIVE, right now... I cant get simple recordings to line up in time (after they are recorded, they end up out of time). Acid 2.0 NEVER did this.... |
|
Subject:RE: recording/playback issues
Reply by: xxFT13xx
Date:5/8/2002 5:53:11 AM
uh oh...another Creative Labs Sound Blaster victim.... its such a shame people dont know that SB cards suck for making music. i suggest selling it and getting a REAL card like a M-Audio or Terratec. Those bad boys are around the same price and are SOOOOO much better!! Believe me!! -Sin |
|
Subject:RE: recording/playback issues
Reply by: spesimen
Date:5/8/2002 4:19:53 PM
umm, actually i have the same problem with a gina24...i don't think the soundcard has much to do with it, but rather the drivers.. as near as i can tell my problem is related to the MME emulation windows2000 does and acid3 not really liking it so much. things work fine under 98, but since acid doesn't do asio or wdm natively under 2000 there isn't much workaround. it seems less likely to mess up if i use 16-bit only and don't use any plugins until after i'm done tracking.. anyway maybe you have win2k or maybe not, hope this helps. |
|
Subject:RE: recording/playback issues
Reply by: pwppch
Date:5/8/2002 4:30:46 PM
It is mostly a driver issue. Problem: How do you start playback and record at exactly the same point in time? Solution: With Native Wave drivers, most vendors adopted the approach that they only start streaming data (in either direction) after the final port is told to start. This implied behavior cause all streams to be in sync with each other. WDM breaks this behavior. What happens is that Kmixer gets involved and input and output cannot be assumed to be synchronous any longer. Some WDM drivers have figured out a means to the same thing that native wave drivers have been doing as described. SB cards NEVER did things like this, so the problem always existed. It was not as noticable with wave drivers since the over head of doing this was not where near what the overhead is with WDM KMIXER wave emulation. Note that this drift can occur with output and cards that have multiple output pairs, though for the most part the hardware vendors have found ways to sync their output ports together. WDM Kernel stream has the same issues for the most part. It is more directly solvable using WDM KS since you are very close the driver and can accurately calculate offsets between inputs and outputs. Depending the WDM driver implementation, a port can be n channel with WDM KS making it very much like ASIO. There is still the issue of input and output sync, but again, it is more doable. ASIO solves all of this directly for a single card (or multiple cards of the same type supported with a single driver.) ASIO uses a single callback mechanism for all inputs and outputs. This assures sync between all channels of input and output. These are the issues. I cannot address how SF plans to solve these problems, but I assure you that we will provide a solution to this problem. Peter |
|
Subject:RE: recording/playback issues
Reply by: paeaek
Date:5/27/2002 9:25:40 PM
OK, so unfortunately I dont understand everything that you wrote down. So are you saying that until SF writes a patch (if they write a patch), I must deal with it or go back to ACID 2.0? Thats poor. I would think that SF would test out these kind of things on sound cards that the average music creator would be using.I cant explain how disappointed I am with ACID 3.0. Is there a way to open open 3.0 projects into 2.0? |
|
Subject:RE: recording/playback issues
Reply by: Iacobus
Date:5/28/2002 1:35:20 PM
Welcome to the wonderful world of computer-based music making, bugs and all. :o) You cannot open version 3.0 projects in version 2.0. Sorry. Iacobus |
|
Subject:RE: recording/playback issues
Reply by: pwppch
Date:5/29/2002 4:56:10 PM
This is not an ACID 2 vs ACID 3 issue, but am audio driver issue. The only current solution is to use native WAVE drivers vs WDM drivers. We did test, but we dont write the audio drivers in use. There are altenatives and some drivers are better than others. It is beyond our control on how a particular vendor implements their drivers. We are addressing this issue for a future release of ACID. You didn't mention what audio hardware or OS you are using. Perhaps if you provide some more details I could suggest a course of action. Peter |
|
Subject:RE: recording/playback issues
Reply by: paeaek
Date:5/30/2002 3:00:37 PM
Hopefully you can shed some light and end my frustration... I am running a P4 1.8Ghz. I am using XP Pro as my OS. I have a Sound Blaster Audigy Patinum EX. 768 MB RAM. All my drivers have been updated. Sound card, video card, etc. I guess what is driving me crazy is that I am/was running Acid 2.0 on a P166 with Win 95 and 64 MB RAM and a Sound Blaster LIVE! With that set up I have NEVER EVER had a problem. Most of the projects I had, I just transferred into Acid 3.0. That is when I started having problems. NEVER before. I use Acid alot and I never saw a problem before I switched to Acid 3.0. Any suggestions would be greatly appreciated. |
|
Subject:RE: recording/playback issues
Reply by: pwppch
Date:5/30/2002 9:45:29 PM
ACID 2.0 on Win95 with an SBLive! is a big difference from ACID 3.0 on WinXP with an Audigy. The drivers that Win95 uses are true wave drivers, not WDM. The whole sync between record and playback basically doesn't occur. With the Audigy on WinXP you are using WDM drivers, and according to Creative, drivers with many bugs to work out. One thing to try is to switch all of your projects to 48 kHz, as this is the only sample rate that the Audigy (and SB Live) actually support. By doing this, you will eliminate the need for Windows to resample the audio. Peter |
|
Subject:RE: recording/playback issues
Reply by: paeaek
Date:6/5/2002 6:08:27 PM
All my projects are at 44.1khz. Is that suffient? Or should I change? Is there a difference in the way acid 3.0 interacts with acid 2.0? Is that why I never had problem with Acid 2.0 on my XP machine? |
|
Subject:RE: recording/playback issues
Reply by: pwppch
Date:6/6/2002 12:21:43 PM
I only suggested a course of action. The Audigy doesn't actually support 44.1 kHz. It resamples everything to 48 kHz. This can cause all kinds of synchronization issues. All I am suggesting is that you change the project from 44.1 kHz to 48 kHz and see if the problem is minimized. Peter |
|
Subject:RE: recording/playback issues
Reply by: DjXSoundz
Date:6/7/2002 3:24:45 PM
its a computer problem. not your sound card. u jus have to move it, if u restore your computer it may go away as it did to me. any questions mail me @ Djxsoundz@Hotmail.com |
|
Subject:RE: recording/playback issues
Reply by: paeaek
Date:6/10/2002 5:10:11 PM
Thanks for the help Peter, but I changed the sampling rate and it does not help. Why is it that when I used ACID 2 on my XP machine I never had these problems? Does it interact with XP drivers differently than 3.0? |
|
Subject:RE: recording/playback issues
Reply by: pwppch
Date:6/10/2002 6:57:01 PM
>>Why is it that when I used ACID 2 on my XP machine I never had these problems? Does it interact with XP drivers differently than 3.0? << If I knew, I would have answered the first time you asked. Peter |