Resolved OSX version does not recognise any input device for Vivox speech

EdisonRex

New member
Hi, this anomaly has existed in the last version I had which was from July, but I downloaded the latest version and it still exists.

OSX version is Mojave, but verified the same problem exists on Catalina. I'm logging the issue against Dayturn 2.6.5.146558736 although it apparently existed in previous versions.

Problem: No mic input when speaking voice (i.e. nobody can hear you) - Vivox white dot appears but no mic.

More details: when I go into preferences, sound and media, input/output devices, and try to select any input device, the little mic icon stays greyed out, in the log the only activity noted is:

2020-10-29T17:22:45Z INFO: #Voice; LLVivoxVoiceClient::stateMachine: : setting tuning speaker level to 50
2020-10-29T17:22:48Z INFO: #Voice; LLVivoxVoiceClient::stateMachine: : setting tuning speaker level to 50

Any input device selected behaves the same.

In Firestorm, vivox voice behaves as expected, and I know my core audio interface(s) are fine in Audio/Midi setup.

Any suggestions or if you need more info, it would be appreciated

Thanks
 
Also, go to your System Preferences -> Security & Privacy Select Microphone and check if Dayturn actually has the permission to use it. If not, unlock, and enable Dayturn (it should be listed there)
 
Dayturn 2.6.5 (146558736) Oct 1 2020 21:59:56 ("Release")
Release Notes

CPU: Intel(R) Core(TM) i5-4670 CPU @ 3.40GHz (3400 MHz)
Memory: 32768 MB
OS Version: macOS 10.14.6 Darwin 18.7.0 Darwin Kernel Version 18.7.0: Mon Aug 31 20:53:32 PDT 2020; root:xnu-4903.278.44~1/RELEASE_X86_64 x86_64
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce GTX 775M OpenGL Engine

OpenGL Version: 2.1 NVIDIA-12.0.24 355.11.10.50.10.103

Window size: 2240x1335
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 1024m
Bandwidth: 928kbit/s
LOD factor: 6.5
Render quality: 4
Advanced Lighting Model: Enabled
Texture memory: 512MB
VFS (cache) creation time: January 03 2018 04:31:28
Retina display: OFF

J2C Decoder Version: OpenJPEG: 1.5.0, Runtime: 1.5.0
Audio Driver Version: FMOD Studio 2.00.11
CEF-Version: Dullahan: 1.1.1080 - CEF: 3.3325.1750.gaabe4c4 / Chrome: 65
LibVLC Version: 2.2.8
Voice Server Version: Not Connected
Built with Clang version 4.2.1 Compatible Apple LLVM 10.0.1 (clang-1001.0.46.4)
October 30 2020 09:30:51
 
Also it does not appear in the apps list under security and privacy -> microphone, and I don't have any option to add it.
 
Also it does not appear in the apps list under security and privacy -> microphone, and I don't have any option to add it.
When it is not there, it is not allowed to use the microphone and that is the reason why it don't work.

You can try and remove the viewer completely from the Applications folder, in addition to temporarily move the Dayturn folder out from the ~Library/Applications Support folder and then add the viewer back again from the DMG. I would restart the Mac before adding the viewer back. Let it recreate the Dayturn folder and move you setting and such back after it has been started once and asked for permission to use the microphone. Note it will only ask for that permission when in a voice enabled region. You also have to activate voice from Sound & Media prefs while in a voice activated region.

If macOS has registered it will not accept use of a system resource by an Application, it can be notoriously difficult to get it to get it to re-accept the use. I had a similar problem with a raid driver that the system flat out refused to use no matter.

If you cannot get it working you might even call Apple support and ask them how yo resolve it.
 
There is also a new viewer version 2.6.6 in Resources today, so if you download it, it might trigger the question to use the microphone again once in a voice angled region.
 

I ended up resetting - I dont think Dayturn ever did ask the question about mic, but the use of tccutil reset Microphone did reset all of my apps, I have been wrestling with Firestorm first, and it's been a bit of a wrestle to get things working again across all of the apps.

I will download the new 2.6.6 and see now, if it asks the question. You apparently get one chance at that question, the decision is permanent.
 
Right, so I just loaded that new 2.6.6 and... no, it didn't ask to use the microphone so I can't permission it to, although I did the exact same procedure I used for firestorm (which did pop up and ask as soon as I selected an input device). It does see the various input (and output) devices and lets me swap them around, but nothing is allowed on input and the app does not appear in the privacy window (because it hasn't asked for permission to use the mic, I assume)
 
It is exactly the same issue I had with a RAID device driver which never could get approved after the first approval request failed because remote access did not allow it (you had to have a direct keyboard connection to the server).

The only option I have found if it happens is to reinstall the system completely - which is crazy. Apple is NOT making things easy for users any more.
 
There is one thing I am pretty positive will clear it if you are on Mojave, and that is to upgrade the system to Catalina, but that might of course not be an option for you.
 
oh this one can go to Catalina, but not all my Macs can. I am more worried about other people running Macs.

Okay, so what I am hearing is, the application is behaving according to you? This is probably a big deal for a lot of my opensim customers, a surprising number are on Macs, maybe I shouldn't be so surprised, and they use voice far more than I do (I don't use voice a lot, but I think it should work)......

I dont see a workaround for this.
 
oh this one can go to Catalina, but not all my Macs can. I am more worried about other people running Macs.

Okay, so what I am hearing is, the application is behaving according to you? This is probably a big deal for a lot of my opensim customers, a surprising number are on Macs, maybe I shouldn't be so surprised, and they use voice far more than I do (I don't use voice a lot, but I think it should work)......

I dont see a workaround for this.
It works as long as you don't dismiss the question to use the microphone - which some people probably will do, and then have a use for it later.
It also works on Big Sur beta if you allow it to use the microphone when initially asked.
 
but it hasn't asked to use the microphone, Geir. I don't know how to get it to do that, and I did reboot, etc, all the other apps have asked since.
 
I also noticed on the About info you sent me it says Voice Server Version: Not Connected
What version of OpenSim do you try this on?
 
my own region is voice enabled, and I am using that region to test this.
I'm on a maybe one month old build of core.
 
Did you try go to a voice region and toggle voice enabled off and on from Preferences -> Sound & Media?
yes. My region is voice enabled Vivox. and went to preferences -> sound & Media
it does not ask me to approve the app for microphone. I cleared (as I said) the whole app list and one by one have added them back.
 
Teleport to
Code:
grid.xmir.org:8002:Dayturn
where I know there is working voice.

From Preferences -> Sound & media toggle voice chat off, then on, then click OK and see if the white dot appears over you. It should at this stage ask you for permission to use the microphone.
 

Members online

No members online now.
Back
Top