Amplitube 4 won't capture sound MacOS Mojave [Resolved]

[danilo9xm1]

Hi,

I have a Amplitube 4 which I use through an iRig HD since september 2015.

I has always worked fine until I upgraded to MacOs Mojave.

Apparently there is no input signal from the iRig anymore. Although the blue light turns green or orange on the iRig, which tells me the device itself is still capturing signal from the guitar, but no sound and the meters do no move, which tells me there is no signal at all being captured by the software.

It behave the same way when I try to use the built in microphone. No sound and the meters won't budge.

As is has been working fine until yesterday when I installed the new OS, I can't get around to think that there may be some incompatibility there with the new OS?

Are you guys having the same issue or are aware of the issue.

MacBook Pro (13-inch, 2017, Four Thunderbolt 3 Ports),
3.1 GHz Intel Core i5,
8 GB 2133 MHz LPDDR3
MacOS Mojave, v10.14

[garfy]

Still on Sierra here so haven't needed to try this, but a lot of people's audio woes on various forums have been due to a change in privacy rules for the microphone.

Go to SysPref>Security & Privacy>Privacy and check what apps need access to the microphone.

Counterintuitively, this has fixed all manner of input issues with the in-built mic and audio apps.

Hope that helps.

[danilo9xm1]

Problem solved!

Thanks!

Privacy settings :/

[garfy]

Glad to hear it.

Did that fix the iRig HD input as well?

[danilo9xm1]

yup!

[garfy]

Brilliant...

(and yet annoying and probably the last thing anyone would think of!)

[ian.ollerenshaw]

yes, just had the same here after upgrading to Mojave.
Annoying thing is i wasted so much time with IK tech support getting nowhere with this except to the point where the support op said i need to get the IRIG HD2 replaced. !!
then this morning after searching i was brought here and yes, as suggested earlier, it was the privacy settings.
Not very impressed with support for not picking up on this !!
Ahh well !

[DarkStar]

It would be worth replying to your Support Ticket with a link to this thread, and suggest that the solution is published as a FAQ.

[ian.ollerenshaw]

yes, had already replied to it but have now sent them the link as well .

Thanks