Sound stutters windows 7

The two changes in combination was required. Stuttering audio almost always indicates an insufficient performance of hardware, or memory. This also depends much on the audio source, and the software used. In case you have no sound issues on your host Ubuntu different Pulse Audio settings will not do much about sound issues arising from running a quite demanding guest OS like Windows 7.

To minimize effects coming from limitations of a virtual machine we therefore have to make sure to assign as much hardware ressources to the guest OS as possible, but make sure the host OS is still able to perform well including Pulse Audio in your case! From what we can see from your settings it seems that the requirements to get a smooth audio experience are met. There are few things only we may try to see whether there is an improvement:.

In case we then have a better sound output we may reduce the ressources step by step to find the optimum setting for the software we run on our guest. If we still cant get sound output smoothly we may have to try using a software with less demanding sound processing like e.

WinAmp or Foobar to further track the issue down. It may however be that your hardware capabilities - even though quite good - still are inssufficient for running Windows 7 and your additional software to play sound and video? No other changes to configuration VirtualBox Guest Additions 4. This happened to meet too, for some reason the CPUs were on 4 of 8. When I put the CPUs down to 1 it started working much better.

No audio device showed in guest. Some people had to switch to Alsa from Pulse Audio. Mine works fine WITH pulse audio. This probably has to do with how the HOST machine is set up. I got NO sound unless I used the realtek driver.

I have Linux Mint I didn't change default sound properties in VirtualBox:. Installing virtualbox guest additions didn't help to recover sound. Ubuntu Community Ask! I did read my manual that came with my motherboard. It doesn;t mention HPET. That manual you linked me is for a z77 motherboard. I have a z87 motherboard.

There is no HPET in a my z87 motherboard. I don't think these new z87 boards come with hpet in the bios. Hpet is old and bad timer anyway Like said the build in iTSC most cpu use these days are far Superior.

Hpet is hit or miss. That is probably why they disabled it. Well I have no idea what the issue still is lol. This is like finding a needle in the haystack. Than I tested my timer here are my results. QueryperformanceFrequency It works. Now the most important is that it improves something?

So far no stuttering. Ill keep you updated. Thanks alot :. Like said HPET is a hit or miss thing. Hpet is much slower and more latnecy for the sake of better latency IF you have latency issues pay attention to what you change and if you doing this you might as well use Latency Monitor to test your system latency with orignal settings vs forced hpet.

I do suggest you go to that topic as ask there though. Windows 8. So Windows 8. And disabling HPET is very stupid idea in general. For example on modern operating systems with so called tickless mode, OS will look at it's timer, job etc queues and will set HPET to fire exactly when it is needed for example 66ms later, when some of your app demands wakeup in some system call and not periodically every 10 or 15 ms needlessly burning CPU cycles on doing nothing.

Invariant TSC is cool feature, engineering marvel from Intel in its day. But having same "clock" tick value across all CPU cores in the system is good for time keeping and measurement and sadly can't magically bring back CPU from sleep. So it boils down to the following distinction between clock source and clock event devices.

The question is: Is that everything is properly managed, for hardware? I recently updated my motherboard to bios revision F9. To fix it, you can try different audio formats. Related article: Convert Video to Audio. If you use many input and output audio devices on your computer, they may cause conflicts. Because it's hard to tell which is causing the audio stuttering windows 10 problem, try disabling all of them.

Try uninstalling the conflict network driver might fix the audio stuttering windows 10 error. If you have a problem with your audio driver, the audio stuttering windows 10 issue may occur. You can reinstall the audio driver for repair. As soon as you are trying to save the state, the VM hangs of completely and only can be shut off by closing the window from taskbar or from the task manager in the host.

In case of no verbose logging and logging audio recording I can go further by pausing and starting the playback in the guest some times, as I already wrote. Thank you for your patience and effort in this case. Thanks for the logs -- I see that you're using some "portable version" of VirtualBox. Where did you get this build from, how is this intended to being used? Generally we don't support such custom builds.

However, I already have an idea what's going on now, the problem is related to the so-called multimedia endpoint detection. I'll have a look at that. I tried the release version VirtualBox The sound out works perfect in Win 7 and Win guests on Win host.

But the sound in microphone doesn't work at all. Should I file a new ticket or can it be handled as a part of this issue? Thanks pentagonik, In build "Version 5.

Actually sounds seems work even better than in 5. Replying to pentagonik :. The test build that 'pentagonik' was referring to must be 5. In VirtualBox VirtualBox Version 5. Audio is not in sync on Windows XP guest. There is always a 1 second delay. It is noticeable when start, pause or resume playing.

Disabling audio output sometimes causes crackles. It also slows down playback timer on Windows 7 guest and stops playback timer on Windows XP guest. As sound in Win10 like systems is broken i gave it a try on several versions of VirtualBox 5. Interesting enough in 6. I sorry to inform you, but the latest changes in the audio code put the distortion a little bit back.

There are some changes about the new Windows 10 default surround sound , , and follow-ups , , , , , , ; stream start optimization , , , ; random , , , Here are more details: In the current 5. It isn't so heavy as months ago and last for only 5 or 7 seconds.

It repeats after something like 50 seconds. And this happens on both of my Windows 10 host and guest system and Windows 8 host and Windows 7 system. So the audio of 5. There is another problem here: back in September I already wrote about the problem by switching the host audio from speaker to Bluetooth and back.

But back then one easily could simply stop or pause the playback and start it again. Then it went to the right audio device. In the current 5. At least till you switch back, stop the playback, switch the device once again and start the playback. Only after this you can get the sound on the other device. I think that some initialization optimizations or caching causing this kind of behavior. I created some logs and audio files for different version which I put here.

One can clearly see the synchronization troubles in the logs, which causes the distortion, and the device switching is also here. As at the last time, trying to record some audio during the device switch hangs the VM completely; I only could go further by killing it by window closing or through the host task manager. Without audio debugging there is still this issue, but at least no hanging of the VM. Upgrading from 5. I did notice audio was broken in the 5.

I am currently in a work environment and cannot allocate the time to look into it right now. Downgrading to 5.

Just want to give the current state. No changes since my last output about the 5. So playback in 6. Just a bit of it at the start of playback sometimes, but this is easily cured by stopping and starting the playback again. The 5. I put some audio files and logs from debug here. My other issue is still here and even got worse since my last message: switching the device.

Previously the playback just got stuck in the last second over and over again as one switched the host audio device during the playback. But it was solved by stopping and starting the playback once again.

In the last tested betas 5 weeks ago the device was cached somehow, so one have to do more, like turning VM audio output off and on in the VM settings or waiting sometime. No action could help here: stopping, pausing, starting once again, turning the audio output off and on, even saving the state of VM and start it again or switching back to the original host audio output device; the VM is just stuck in the old device and plays the last second forever.

The only solution right now is to shutdown the VM no restart and start it again with new device as the host current active audio output device.

I tried to test 4 scenarios: switch during playback and stopping the playback before the switch; I also tried to switch from speakers to the Bluetooth and in the either direction.

But there is no difference between them all, neither in normal nor in debug mode, it just doesn't work the way it was in 5. I'll have a look at all the provided files as soon as possible.

Hi pentagonik, Thank you or who else is taking care about all this audio issues very much for doing this job. Maybe this could be useful for your debugging activities. I give a report about the current situation of this issue. Good news first: since the early betas of 6. In the 6. All currently supported versions working fine on my Windows 10 guest and host system.

So in this corner of the audio system everything is fine. Now to my other issue — switching the sound device of the host. It looks a little bit better now, but still not as good as in 5. Current state: of course the complete shutdown and start helps as in 5. Restart of the VM or saving and restoring the state of the VM also helps now. Sometimes one have to repeat this couple of times to get the result.

Sometimes it helps to turn the audio output in the VM menu off and on, also couple of times. This worked in some early betas 6. What still not working beside the automatic switch: turning off and on the playback in the VM. It also always helped the version 5. I would try to make some log and audio files with extra audio debugging.

In the past the change of the devices with active audio debugging caused the VM to stuck; after that the VM has had to be killed in the task manager of the host. It probably caused by the audio files writing routine.

It would be probably better if we could suppress the writing of this files by some extra configuration. Then we would have at least more detailed logs itself. Of course if would be even better if this hanging in case of audio debugging and host device switching would completely disappear. I created the logs and the audio files in audio debug mode. Another question: this ticket was opened over the year ago for the different version of Virtual Box and for the general audio issues there.

Tested VirtualBox 5. Audio quality is good. However, delay is built up while playing sound. Audio is in sync at start but drifts gradually.

There is a 2 second delay after 2 hours of playing. Disabling and enabling audio output twice can get audio in sync again. Generally the problem with jerking or lost audio output after the change of audio output device on the host during the playback persists. In the 5. Even if one manages to get sound on the right device, it still jerks there, even after the playback in the guest was stopped.

It only happens if one forgets to stop the playback before the transition and do the transition during the playback. The transition succeeds if it doesn't happen during the playback. The only thing that helps right now is shutdown and start of the guest, not even the restart.

The jerking sound continues even if the playback or audio output is off in the guest. Finally, I managed to get the debug audio files without guest hanging during the transition in the debug mode. The trick is to do the first transition speakers to headphone or Bluetooth not during the playback, but stop the playback before. This way one has no immediate hangup of the guest and one can do as many transitions during the playback afterward as it wishes. So right now I got all the audio files and the logs from the audio debug session from all mentioned versions.

There just the skip of the sound happens. So it clearly not the problem in the guest, it is only the problem between the guest or VBox and the host audio system. I uploaded more fresh debug logs and sound files. Somebody added some additional sound logging into the source code; I saw nothing of it in the newly created logs but probably somebody could use this information anyway.

I tested with the currently available versions 5. Sadly, but as expected, the issue with lost sound after switching the output devices on the host is still here. Nothing changes in the last months, even the newly available version 6. I put some logs and a link to the recorded files. The files and the complete log are only from the version 6. In all other versions once again guest hangs completely if one switches the host audio output device in debug mode.