AndrewKirkland
Inspired
Hello I am currently using an AXE FX 2 via AES into my Metric Halo ULN-2 interface. I am a bit confused about the proper way to clock both systems.
This bit on the support wiki confused me.
However it also works when I use the metric halo's clock set to internal ( sample rate 48khz) and then the AXE world clock will work set on AES/SPDIF or AUTO. A brief message when I go to AES/SPDIF comes up and says "No Input Clock". When this message appears does this mean it is just setting the axe fx back to auto even if it stays selected on that area? Does it go away because it takes time to detect the new clock selection and I am on AES clock selection after it is detected? This is what mainly confused me.
The halo says for AES I should clock using dig in (44.1/48khz) however I would then need to set the axe fx to auto, as when I set it to AES and have the metric set to digital in there is an ungodly screeching noise. If someone could shed light on this issue, I would be extremely grateful. Thanks for your time and I hope every has a nice Thanksgiving.
So if axe is set to auto, and halo is set to dig in, does that mean the axe is the master clocking source?
And if the axe is set to aes/spdif or even auto, yet I have the metric halo set to internal, does this mean the axe fx is the slave?
This bit on the support wiki confused me.
- SPDIF/AES IN: uses the recovered clock for all input sources. A valid 48 kHz data stream must be present at the AES or SPDIF input. If a valid stream is not detected the unit will fall back to the internal clock and display "NO INPUT CLOCK!". The SPDIF/AES select must be set to the appropriate value, i.e. if the data stream is input to the XLR jack then SPDIF/AES SELECT must be set to AES.
However it also works when I use the metric halo's clock set to internal ( sample rate 48khz) and then the AXE world clock will work set on AES/SPDIF or AUTO. A brief message when I go to AES/SPDIF comes up and says "No Input Clock". When this message appears does this mean it is just setting the axe fx back to auto even if it stays selected on that area? Does it go away because it takes time to detect the new clock selection and I am on AES clock selection after it is detected? This is what mainly confused me.
The halo says for AES I should clock using dig in (44.1/48khz) however I would then need to set the axe fx to auto, as when I set it to AES and have the metric set to digital in there is an ungodly screeching noise. If someone could shed light on this issue, I would be extremely grateful. Thanks for your time and I hope every has a nice Thanksgiving.
So if axe is set to auto, and halo is set to dig in, does that mean the axe is the master clocking source?
And if the axe is set to aes/spdif or even auto, yet I have the metric halo set to internal, does this mean the axe fx is the slave?