Vidyo Desktop 3.3 on Linux no longer sees any audio devices

NEW
Assigned to

Status

4 years ago
3 years ago

People

(Reporter: jld, Assigned: freshness)

Tracking

Details

(Whiteboard: [Vidyo CAS-39817])

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
After the upgrade to 3.3, Vidyo Desktop is now convinced that I have no microphone or speaker devices.  I can use `pacmd` to see that Vidyo is connected to the PulseAudio server (list-clients) and that the devices exist (list-sinks, list-sources), but they don't appear in the Vidyo GUI, and there is no sound in or out.

This effectively caused me to miss a meeting this morning, because I hadn't prepared a contingency plan ahead of time.

There does not appear to be any useful information in the log file.

Comment 1

4 years ago
Hello Jed,

I wanted to close the loop with you, since I realized I replied to the Yammer thread but not the bug. As mentioned earlier, I have submitted a case on your behalf to Vidyo.

Comment 2

4 years ago
Hello Jed,

Just got back a reply from Vidyo Tech Support:

"Hi Mark,

Thank you for the detailed report, can you just provide the log file for tracking?

Also, for temporary testing, can you have them add:

'VIDYO_AUDIO_FRAMEWORK=ALSA' to /etc/environment file and then reboot the system for changes to take effect.

Let us know if this makes any difference.

Thank you,

Frank"

Can you crank a diagnostic report and attach it to the bug?

Also, Vidyo Desktop 3.3.2 is coming in another week - they think that they have quashed most of these bugs in that release, and want to get your logs to confirm that they have not missed anything.
(Reporter)

Comment 3

4 years ago
Created attachment 8514397 [details]
2014100900-redacted.log

I thought I'd already attached the log, but I see not.  I've removed other people's names from this file, but everything else is intact.
(Reporter)

Comment 4

4 years ago
If I do `pulseaudio --kill`, then start Vidyo with VIDYO_AUDIO_FRAMEWORK=ALSA, I can connect it directly to the audio device.  (At least it opens the device; I'd need to do a test call with someone else to see if it works.)  This, of course, will break everything else on the system that wants to use audio.

I haven't been able to convince Vidyo to use the ALSA device that backends to PulseAudio.
(Assignee)

Updated

4 years ago
Whiteboard: [Vidyo CAS-39817]
(Assignee)

Updated

4 years ago
Assignee: nobody → mrichards
Product: Audio/Visual Infrastructure → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.