carlosagm79
Max Output Level: -84 dBFS
- Total Posts : 301
- Joined: 2011/02/07 00:35:29
- Status: offline
ASIO Latency & Monitoring
I don't know about you guys, but this is one the weakest point in my recording experience with Sonar, since ASIO drivers things are worst, Sonar does not support ADM , but ridiculously close my input channel when have the focus!!.I mean, I open the input channel in the software mixer of my hardware interface,I'm monitoring trough it(like the normal windows way) but when back to Sonar it close it!, forcing my to use the ¨Sonar input monitoring¨ which I hate, because most of softsynths and effects are CPU hungry and with complex projects, multiple tracks its not reliable(clips, pops, drops, stops etc)
Tested my DIGI 001, Cretaive X-Fi ExtremeMusic, TACAM US-224, M-Audio Micro, Yamaha Waveforce, always the same history in ASIO mode, any ideas, any trick or advice please??
|
mudgel
Max Output Level: 0 dBFS
- Total Posts : 12010
- Joined: 2004/08/13 00:56:05
- Location: Linton Victoria (Near Ballarat)
- Status: offline
Re:ASIO Latency & Monitoring
2011/09/25 01:56:11
(permalink)
I'm not aware that any of the audio cards you've listed there have drivers written to support ADM either. DIGI 001 from memory don;t play nice with other DAW software esp SONAR.
GO to SONAR Preferences->Audio->Recording and Playback
Check the box = Share Drivers with other Programs.
This will allow which ever program has focus to access the selected driver.
make sure that Windows is not set to use any of the devices that yu are using an ASIO driver with. Windows can't use ASIO drivers and if it grabs hold of an audio device during startup then you won't be able to select ASIO in the first place.
Mike V. (MUDGEL) STUDIO: Win 10 Pro x64, SPlat & CbB x64, PC: ASUS Z370-A, INTEL i7 8700k, 32GIG DDR4 2400, OC 4.7Ghz. Storage: 7 TB SATA III, 750GiG SSD & Samsung 500 Gig 960 EVO NVMe M.2. Monitors: Adam A7X, JBL 10” Sub. Audio I/O & DSP Server: DIGIGRID IOS & IOX. Screen: Raven MTi + 43" HD 4K TV Monitor. Keyboard Controller: Native Instruments Komplete Kontrol S88.
|
thomasabarnes
Max Output Level: -43 dBFS
- Total Posts : 3234
- Joined: 2003/11/11 03:19:17
- Location: Milwaukee, WI USA
- Status: offline
Re:ASIO Latency & Monitoring
2011/09/25 02:22:46
(permalink)
"I open the input channel in the software mixer of my hardware interface,I'm monitoring trough it(like the normal windows way) but when back to Sonar it close it!,... any ideas, any trick or advice please??" Maybe try this from the X1 reference manual: Minimize driver state changes SONAR has an option to not reset audio devices each time playback or recording starts. This option minimizes device state transitions in response to transport operations. When enabled, SONAR attempts to keep the device in a running state as far as possible.
To configure the MinimizeDriverStateChanges option
1. Go to Edit > Preferences > Audio - Configuration File. 2. Under Configuration Settings, click Edit Config File.
The Aud.ini file opens in the default Windows text editor. 3. In Aud.ini, locate the entry called MinimizeDriverStateChanges and set it to the desired
value. For example: MinimizeDriverStateChanges=1 Valid values are as follows: • 0 = off. • 1 = On for ASIO only (default). • 2 = On for WDM only. • 3 = On for both ASIO and WDM.
4. Save Aud.ini and close the Windows text editor.
5. Click Reload Config Settings to reload the current audio configuration settings from Aud.ini.
Note: The MinimizeDriverStateChanges variable only applies when using ASIO or WDM driver modes, not when using the MME driver mode.
 "It's not a song till it touches your heart. It's not a song till it tears you apart!" Lyrics of Amy Grant. SONAR Platinum X64 (jBridge), Windows 10 Pro 64-Bit, Core i7 990X Extreme Edition Processor 3.46 GHz 6 Cores, Gigabyte EX58-UD5, Crucial Ballistix 24GB 1333MHz DDR3 @1333 MHz, TASCAM UH-7000, Behringer X-Touch, EVGA GTX 980TI Superclocked 6GB, 1TB Samsung EVO 850 SSD, 150GB, 320GB, 1TB 7200rpm HDDs
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:ASIO Latency & Monitoring
2011/09/25 13:07:32
(permalink)
I open the input channel in the software mixer of my hardware interface,I'm monitoring trough it(like the normal windows way) but when back to Sonar it close it!
I don't think SONAR is doing anything; I think this is a Windows program focus issue, possible exacerbated by bad firmware/driver design choices. I can turn on direct monitoring in my 1820m and Input monitoring in SONAR, and hear both signals (phasing if the latency is low, and slapback if the latency is high). If I turn off Input monitoring in SONAR, I continue to hear the direct-monitored signal through the 1820m. but if I turn off direct-monitoring, and leave Input monitoring on in SONAR, I will lose the signal from SONAR when I change focus to the mixer app. However, I recently discovered that if I minimize SONAR by clicking its icon in the Taskbar, it retains control of the driver/port when I change focus to the mixer app. So Win7 is not consistent in how it handles this. the main resaon I don;t think this is a sONAr issue is that that the hardware shouldn't be using the driver to perform direct monitoring. That should all be happening in firmware, beyond the control of SONAR, or even Windows. SONAR shouldn't be able to close a port that the firmware is using no matter what it does. As an example, I have an issue where SONAR stops echoing audio when I rewind after recording a take. I have to cycle the audio engine to get input monitoring back. This is a problem with the 1820m's x64 drivers. But this does not affect direct-monitoring via the 1820m's mixer, because that's controlled by firmware. P.S. The status of the MinimizeDriverStateChanges and Share Drivers has no bearing on either of these behaviors in my environment.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|
carlosagm79
Max Output Level: -84 dBFS
- Total Posts : 301
- Joined: 2011/02/07 00:35:29
- Status: offline
Re:ASIO Latency & Monitoring
2011/09/25 19:47:46
(permalink)
Well, after read bundlefly I re-check the behavior with Sonar X1c, my fault because since last month I been using just the DIGI 001 and it have not an independent software or hardware mixer(except for Pro Tools TDM internal).
But then I switch to the Extremusic and US-224 and amazing!, Sonar its not closing the input, no matters if I turn of or on record,or echo button, but I tell you what, this was not the usual behavior in previous version of Sonar.
|
thomasabarnes
Max Output Level: -43 dBFS
- Total Posts : 3234
- Joined: 2003/11/11 03:19:17
- Location: Milwaukee, WI USA
- Status: offline
Re:ASIO Latency & Monitoring
2011/09/25 20:55:38
(permalink)
Brundlefly always makes excellent contributions to the forums here. Glad to hear you're OK, now.
post edited by thomasabarnes - 2011/09/25 23:36:51
"It's not a song till it touches your heart. It's not a song till it tears you apart!" Lyrics of Amy Grant. SONAR Platinum X64 (jBridge), Windows 10 Pro 64-Bit, Core i7 990X Extreme Edition Processor 3.46 GHz 6 Cores, Gigabyte EX58-UD5, Crucial Ballistix 24GB 1333MHz DDR3 @1333 MHz, TASCAM UH-7000, Behringer X-Touch, EVGA GTX 980TI Superclocked 6GB, 1TB Samsung EVO 850 SSD, 150GB, 320GB, 1TB 7200rpm HDDs
|
brundlefly
Max Output Level: 0 dBFS
- Total Posts : 14250
- Joined: 2007/09/14 14:57:59
- Location: Manitou Spgs, Colorado
- Status: offline
Re:ASIO Latency & Monitoring
2011/09/25 22:56:50
(permalink)
Thanks, Thomas. I was probably a little windier than necessary on this one, but glad it inspired the OP to take another look and work it out.
SONAR Platinum x64, 2x MOTU 2408/PCIe-424 (24-bit, 48kHz) Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
|