Custom Query (16363 matches)
Results (1006 - 1008 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #16106 | duplicate | Audio capture for multiple VMs problem since 5.0 version -> duplicate of #16105. | ||
| Description |
I have 3 virtual machines, all with android x86 image, and using audio input device for capturing audio. On host machine I run linux and using pulseaudio. After booting up the VM, it's up with sink name same "Virtualbox: Pulseaudio", when I booting up second VM it also starts with sink name "Virtualbox: Pulseaudio"...(I see it in pavucontrol application on Inputs tab). No possibility to apply separate inputs for different VMs(because all of them has same name of sink in pavucontrol). Also no possibility to change sink name, because starting from version 5.0 all VMs starts with sink name "VirtualBox: Pulseaudio", in older versions(4.3.40 for examle) VM create the sink name same as virtual machine name.("VBox:<vmname>") No workaround for this problem, only rollback to version 4.* |
|||
| #9141 | obsolete | Audio cuts out after many hours of playback | ||
| Description |
I'm trying out running some broadcast automation software inside a VirtualBox Windows XP VM, on a Linux host (Ubuntu 10.04). Naturally this means a long-running audio playback task, which works nearly perfectly, but: After about 10-12 hours of playback, sound abruptly cuts out. When it does so, the playback software on the VM roughly doubles the rate at which it is "outputting" sound. I imagine this is because some component downstream is emptying the soundcard buffer faster than it would ordinarily, perhaps because it has experienced some failure and is emptying the buffer fast to keep the guest from freezing? To get sound working properly again I only need to restart the playback application, not the VM or host OS. The backend device is ALSA, sent through dmix. The VBox log file contains nothing particularly interesting except for a pair of PIT reconfigure messages when I stop and restart the playback app. ALSA sound capture is intentionally redirected to null. I haven't tried Pulse output as Pulse isn't installed on the box in question. OSS output selects the wrong sample rate (plays 44.1khz guest output at 48khz, leading to a slight chipmunk effect) so I haven't used it for any significant amount of time. So obviously this isn't a very useful bug report yet. How do I get more detailed information about what's going on in the audio backend? |
|||
| #11638 | obsolete | Audio device in eComStation crashes system. | ||
| Description |
Audio device in eComStation crashes system if you have enabled the device on Settings panel. Their device can be inappropriate or it swears with errors. The next release of VirtualBox should have this bug fixed. |
|||

