Guitarjon
Fractal Fanatic
Good to have a solution. But this seems like a large gap. Useful to get to the bottom of it.
I agree!
Good to have a solution. But this seems like a large gap. Useful to get to the bottom of it.
If the driver isn't reporting the offset correctly, the recorded audio won't be in perfect time with previous (monitored) tracks.
Yes, while he has a workaround for now, it's not a true fix... any time another process takes priority (looking at you Windows Update), that delay could shift. Having to manually check the delay and adjust value all the time is something that should be done by the software itself.
Windows 10 introduces some big changes to the way it manages audio devices so I'd be curious to know if this same issue is apparent on Win7. Unfortunately, I don't have a win7 box to test on or I would tomorrow when my III shows up! Will definitely be trying to record into Reaper as soon as I get it.
Yes, the offset is based on hardware and software latency in your PC. You know the latency ms counters in your DAW? Those can change based on CPU and bus workloads. There are processes that could cause that latency to increase, and there's also situations where it could decrease. Less so with ASIO because it's designed to minimize these issues but not impossible. If you heavily loaded your USB bus, your USB-based ASIO devices (in this case Axe III) could get degraded CPU priority and thus increase latency.Wait, are you saying that offset I entered could shift?
Yes, while he has a workaround for now, it's not a true fix... any time another process takes priority (looking at you Windows Update), that delay could shift. Having to manually check the delay and adjust value all the time is something that should be done by the software itself.
Windows 10 introduces some big changes to the way it manages audio devices so I'd be curious to know if this same issue is apparent on Win7. Unfortunately, I don't have a win7 box to test on or I would tomorrow when my III shows up! Will definitely be trying to record into Reaper as soon as I get it.
Automatic Updates downloading in mid dense session could potentially cause performance issues (especially if using WiFi).
With Win10 Pro, you can shut all those things (including Automatic Updates) down.
Hmm maybe I should consider upgrading to pro.
I assume you mean that the CPU will have a harder time with handling the session so stuff like dropouts could potentially occur in such a case?
I've been building DAWs professionally for nearly 25 years... so I wanted to chime-in.
This has zero to do with Windows 7 vs. 8 vs. 10.
The value of the offset won't change.
ALL audio interfaces have an offset (latency). If reported properly by the driver, the DAW software manages it automatically... and all audio tracks will line up properly.
If the value isn't reported properly, you have to manually figure out the offset (in samples)… and enter that in your DAW software.
Once done, it's done.
If you're savvy and have Win10 Pro, you can disable all annoying components (OneDrive, Cortana, Automatic Updates, etc).
At that point, Win10 is a very solid DAW platform.
And to my original point, the value looks like it's not being reported properly so manually setting the delay is a workaround, not a solution.
Good to have a solution. But this seems like a large gap. Useful to get to the bottom of it.
I had to enter a value of 1325 samples to correct the offset and it works.
https://forum.fractalaudio.com/thre...-latency-issues-with-usb.137958/#post-1636630
https://forum.fractalaudio.com/thre...-latency-issues-with-usb.137958/#post-1637251
This is known. It's the USB Buffer Size IN the Axe-FX III itself (as explained in the above posts). That latency is not reported by the FAS driver.
That sounds about right for the default USB Buffer size of 256 in the Axe-Fx III itself - 256*2 for playback + 256*2 for recording + ASIO latency
I have this issue as well. There is something not quite right with the AxeFx 3 USB driver in my opinion.
This is the solution i found in the following thread;
https://forum.fractalaudio.com/thre...-latency-issues-with-usb.137958/#post-1637251
I stole this from AlberA
"record the loopback and measure the latency yourself.
You can easily do this with the Axe-Fx III by connecting a cable from say output 3 L to input 2 L and create a preset that routes IN USB->OUT 3 Block. Make sure to increase the OUT 3 knob in the front.
Then in your DAW, set a click track or something with clearly defined transients, and send it to track 7 (IN USB L).
In another track, set it to record Input 7 (INPUT 2 L).
In Cubase you should adjust "Record Shift" by the amount of delay between the tracks. Re-Record the track, check and adjust as necessary until both tracks are aligned."
What amount of samples did you type in that offset field?
Mine was 1149. Yours might need different though. Super easy test. Took about 10 minutes to find the right amount of offset. However, they should look into this more with the USB driver.