Hey guys,
hope someone out there can help me!
Setup:
ABIT AS8
2,8GHz pentium
1GB DDR
2 x Pulsar + syncplate
Sonar 4
SFP 4
Problem:
After noticing audio and midi was seriously out of sync with my old Sonar 2.2, I went ahead and bought Sonar 4, ignorantly hoping this would fix the problem (which, partially, it actually did...) but the problem still remains. After installing Sonar 4 i tried the asio2-drivers, and eventually all asio-drivers, but the sync problem was still there. Lowering ULLI from 25ms to 13ms helped a little. Switched over to WDM, and got sluggish response and crackling. MME I never got to work at all. And, oh yes, all in 24-bit. Asio works fine except for the slight delay in audio.
And another thing: I can´t open the asio-panel in Sonar... never could.
Anybody have a cure?
If there is someone out there with a working Sonar4/scope4-setup similar to mine, could you please post a copy of your aud.ini file?
On a deadline..... HHEEEEEEEELP!!!
Help! Sonar4 / Scope4 sync problem!
no reason it shouldn't work...it also shouldn't be hard. maybe your os is messed up or you have lots running in the backround(what IS running?)...you should not be able to open the control panel, asio is not administered from within sonar with a scope card, it's done in scope.
do you have a separate hd for your audio files or are you using only one drive? where are you monitoring the audio from? DON'T monitor through sonar! monitor sonar and all other audio through a scope mixer instead and you will eliminate latency as a problem on everything but vstis. lowering ulli down below 13ms to 5 or 7ms will help to eliminate latency on vstis and punchins
...
have you done the basic xp tweeks yet? you need to at least turn of system restore, auto updates and all that damn xp eyecandy(sliding 3d window buttons, etc). make the screen look like 98 and turn off the screen saver. also you should disable write behind caching on your hds.
it goes without saying that you need to turn off antivirus programs(all that internet stuff as a matter of fact) when using your computer for music production(for best results)....
check system information. is the cwa card sharing an irq with anything else? if so, you must change that by disabling unused ports or devices and/or moving the card to anither slot.
do you have a separate hd for your audio files or are you using only one drive? where are you monitoring the audio from? DON'T monitor through sonar! monitor sonar and all other audio through a scope mixer instead and you will eliminate latency as a problem on everything but vstis. lowering ulli down below 13ms to 5 or 7ms will help to eliminate latency on vstis and punchins
...have you done the basic xp tweeks yet? you need to at least turn of system restore, auto updates and all that damn xp eyecandy(sliding 3d window buttons, etc). make the screen look like 98 and turn off the screen saver. also you should disable write behind caching on your hds.
it goes without saying that you need to turn off antivirus programs(all that internet stuff as a matter of fact) when using your computer for music production(for best results)....
check system information. is the cwa card sharing an irq with anything else? if so, you must change that by disabling unused ports or devices and/or moving the card to anither slot.
I've done all of the above:
OS is XP Home SP2 tweaked, running on Standard PC driver.
Audio is running on a separate SATA-drive.
ULLI is 13ms (Sonar reports 11ms).
Monitoring only through Scope.
Write behid cacheing is off.
No antivirus, all redundant programs and services are off.
No hardware conflicts, and all reundant ports disabled.
Pulsar cards in PCI-slots 2&4
The delay isn't too big, about 25ms, but it still makes recording audio on a midi-background go enough out of sync to be unusable as it is, at least without manual timing of individual tracks/clips.
When trying different drivers in Scope (asio/wdm/mme) I ended up with blue screens of death quite a few times - each time a different file was reorted to be the cause of the crash.
Maybe I'll just have to reinstall OS? I'm starting to think that it's gotten screwed up somehow. Come to think of it, after building the PC and installing Sonar 2.2, everything seemed to work fine (never had a project with this much midi before starting to do audio, though...). Then, at some point, things just got out of sync...
OS is XP Home SP2 tweaked, running on Standard PC driver.
Audio is running on a separate SATA-drive.
ULLI is 13ms (Sonar reports 11ms).
Monitoring only through Scope.
Write behid cacheing is off.
No antivirus, all redundant programs and services are off.
No hardware conflicts, and all reundant ports disabled.
Pulsar cards in PCI-slots 2&4
The delay isn't too big, about 25ms, but it still makes recording audio on a midi-background go enough out of sync to be unusable as it is, at least without manual timing of individual tracks/clips.
When trying different drivers in Scope (asio/wdm/mme) I ended up with blue screens of death quite a few times - each time a different file was reorted to be the cause of the crash.
Maybe I'll just have to reinstall OS? I'm starting to think that it's gotten screwed up somehow. Come to think of it, after building the PC and installing Sonar 2.2, everything seemed to work fine (never had a project with this much midi before starting to do audio, though...). Then, at some point, things just got out of sync...
Not using any VST:s yet....
Midi in current project is comprised of soundfonts from STS-3000, 2 Scope synths, and offboard synths. All of these are in sync with each other, but the audio is delayed.
Before installing Sonar 4, something seemed to be wrong with the timing in general also, things just weren't sounding as they should.
Installing v4 and using asio2 drivers with syncplate clock seemed to correct that problem.
Maybe I'll just have to suck it up and do a clean OS install... again...
Midi in current project is comprised of soundfonts from STS-3000, 2 Scope synths, and offboard synths. All of these are in sync with each other, but the audio is delayed.
Before installing Sonar 4, something seemed to be wrong with the timing in general also, things just weren't sounding as they should.
Installing v4 and using asio2 drivers with syncplate clock seemed to correct that problem.
Maybe I'll just have to suck it up and do a clean OS install... again...
OK - did some more thorough checking. Here's what seems to be happening. Sonar is storing audio to the tracks about 13ms EARLIER than it should...
Tried recording the metronome ta an audio track, and it was recorded 13ms earlier to the new track. Then I also tried recording that track to yet another track with the same result.
What the *!/#?"&% is going on!?
Tried recording the metronome ta an audio track, and it was recorded 13ms earlier to the new track. Then I also tried recording that track to yet another track with the same result.
What the *!/#?"&% is going on!?
hey
i use sonar 3.1.1 and dont have any of the problems you describe
but regarding that aud.ini file, normaly if u have a problem with your audio driver in sonar u should be able to just delete the ini file and start sonar again. Normaly sonar will create a new file and reconfigure itself, could be that u have to select asio and other settings again but this way your sure that u have a new *clean* aud.ini file tailored for your specific system
i use sonar 3.1.1 and dont have any of the problems you describe
but regarding that aud.ini file, normaly if u have a problem with your audio driver in sonar u should be able to just delete the ini file and start sonar again. Normaly sonar will create a new file and reconfigure itself, could be that u have to select asio and other settings again but this way your sure that u have a new *clean* aud.ini file tailored for your specific system