- Posts: 550
- Joined: Fri Aug 16, 2013 6:07 pm
This is specific to my hardware usage - I'm using a tascam 20X20 USB audio interface. its locked to external word clock at 96K to match other audio hardware here. everything gets done at 96K - field recording on SD 663 thru in house recording / mixing. The tascam is set as system sound IO and resolve is set to use system sound. FR : directly support external audio interfaces !
when R15 or R14 for that matter starts up, it sets the audio hardware sample rate to 48K. that makes sense IF your only audio hardware is a BMD device limited to 44.1 or 48K, or the computer built in sound which could run at multiple rates is now set to 48K.
the problem is when you do this, I no longer have sound output because of the sample rate mismatch. instead I have set Audio Midi Setup to launch at startup and always have it open because some apps like R are always messing with the audio sample rate. I then manually reset the hardware setting back to 96K and all works fine. if you feed 48K into the tascam at 96K, it does a sample rate conversion on the fly and all is good. if you change the sample rate to 48K I get nothing because the hardware is still clock locked at 96K. STOP !!!!! PLEASE STOP DOING THIS !!!! even switching from desktop and back to app often triggers R to set the audio sample rate again. I can't say how many times a day I have to change my hardware settings back to 96K, but R is probably the biggest offender in making life miserable.
I'm sure I'm not the only one using a dedicated audio I/O because I need more I/O than BMD video hardware has, I need to work at higher sample rates than 48K. I highly suspect that BMD will also have their own audio only I/O as part of Fairlight which will do more than 48K too at some point... so you can fix this bug early if you fix no other bugs I report ( outside of crashers ), please fix this one.
S
when R15 or R14 for that matter starts up, it sets the audio hardware sample rate to 48K. that makes sense IF your only audio hardware is a BMD device limited to 44.1 or 48K, or the computer built in sound which could run at multiple rates is now set to 48K.
the problem is when you do this, I no longer have sound output because of the sample rate mismatch. instead I have set Audio Midi Setup to launch at startup and always have it open because some apps like R are always messing with the audio sample rate. I then manually reset the hardware setting back to 96K and all works fine. if you feed 48K into the tascam at 96K, it does a sample rate conversion on the fly and all is good. if you change the sample rate to 48K I get nothing because the hardware is still clock locked at 96K. STOP !!!!! PLEASE STOP DOING THIS !!!! even switching from desktop and back to app often triggers R to set the audio sample rate again. I can't say how many times a day I have to change my hardware settings back to 96K, but R is probably the biggest offender in making life miserable.
I'm sure I'm not the only one using a dedicated audio I/O because I need more I/O than BMD video hardware has, I need to work at higher sample rates than 48K. I highly suspect that BMD will also have their own audio only I/O as part of Fairlight which will do more than 48K too at some point... so you can fix this bug early if you fix no other bugs I report ( outside of crashers ), please fix this one.
S
S
mac Studio Ultra 128gb OS 13.5+
TB3 ext 1TB SSD Cache, 1TB SSD Sys
4K 27Dell
Presonus Quantum 2626 TB3 Word clocked 96K
MiniPanel via enet
Behinger Xtouch USB via USB3 Hub->PCIe USB3X4 card
Wacom XL Pro
mac Studio Ultra 128gb OS 13.5+
TB3 ext 1TB SSD Cache, 1TB SSD Sys
4K 27Dell
Presonus Quantum 2626 TB3 Word clocked 96K
MiniPanel via enet
Behinger Xtouch USB via USB3 Hub->PCIe USB3X4 card
Wacom XL Pro