Value: -2004287484 | 0x88890004 | 2290679812
What does it mean ?
-
AUDCLNT_E_DEVICE_INVALIDATED
-
- The audio endpoint device has been unplugged, or the audio hardware or associated hardware resources have been reconfigured, disabled, removed, or otherwise made unavailable for use.
- Value: 4 | 0x0004 | 0b0000000000000100
- The audio endpoint device has been unplugged, or the audio hardware or associated hardware resources have been reconfigured, disabled, removed, or otherwise made unavailable for use.
Where does it come from ?
-
FACILITY_AUDCLNT
-
- Audio Client (Audio stream between an audio application and the audio engine (for a shared-mode stream) or the hardware buffer of an audio endpoint device (for an exclusive-mode stream))
- Value: 2185 | 0x889 | 0b100010001001
Loading
Getting Error Code 0x88890004 After Updating to New Version of Foobar
I recently got a new computer and transferred my Foobar settings from my old Foobar installation (running v1.3.10) to the new one using a backup created by the Autosave & Autobackup component (foo_Jesus). This worked fine except for now on the new installation running Foobar version v1.4.4, I am getting «Unrecoverable playback error: Unknown error code (0x88890004)» at least once per day (usually in the afternoon and when I wake up in the morning). Usually I pause playback in foobar, do something else for a few hours, and when I come back to the computer, playback has fully stopped and I get the error code. I don’t think I get the error at the usual time unless a song is paused or being played; if playback is stopped, I don’t think I get the error, but I’m not positive about this…
I have updated all the components I use via the Help>Check for Updated Components menu. I am using the following components: Autosave & Autobackup, Facets, Lyric Show Panel 3, Masstagger, No Display Standby, Playback Statistics, Playlist Organizer, Scheduler, and Skip Track.
Does anyone have an idea as to what might be causing this error message? Thank you!
- Remove From My Forums
-
Вопрос
-
I am using Expression Encoder 4 API for a screen capture program and occasionally I get either of the following error messages in DebugView. When this happens, the video file captured will not have audio.
[ERROR] SOURCE : Failed to mix audio samples from source 0. Hr = 0x80600007
[ERROR] SOURCE : Failed to get next packet size from audio capture client 0. Hr = 0x88890004.
Is there anyway to trap error codes Hr = 0x80600007 and Hr = 0x88890004? The expression API does not seem to throw any exceptions when the errors happen.
The relevant function is as following. The function may be called multiple times.
public void Start()
{
EncoderDevice audio = null;
_AudioDevices = EncoderDevices.FindDevices(EncoderDeviceType.Audio);
foreach (EncoderDevice ed in _AudioDevices)
{
if (ed.Name == _ConfigSettings._AudioDeviceName && ed.Category == EncoderDeviceCategory.Capture)
{
audio = ed;
break;
}
}Microsoft.Expression.Encoder.Profiles.ConstantBitrate _videoBitrate = new Microsoft.Expression.Encoder.Profiles.ConstantBitrate(10000);
ConstantBitrate _AudioBitrate = new ConstantBitrate(48);_CaptureJob = new ScreenCaptureJob();
_CaptureJob.CaptureRectangle = new Rectangle(left, top, width, height);
_CaptureJob.ScreenCaptureVideoProfile.Quality = 95;
_CaptureJob.ScreenCaptureVideoProfile.FrameRate = 15;
_CaptureJob.ScreenCaptureVideoProfile.Bitrate = _videoBitrate;if (audio != null)
{
_CaptureJob.AddAudioDeviceSource(audio);
}
m_AudioProfile.Codec = AudioCodec.Wma;
m_AudioProfile.SamplesPerSecond = 44100;
m_AudioProfile.Bitrate = _AudioBitrate;
m_AudioProfile.BitsPerSample = 16;
m_AudioProfile.Channels = 1;
_CaptureJob.ScreenCaptureAudioProfile = m_AudioProfile;_CaptureJob.Start();
}
Topic: BASSWASAPI error message in log (Read 1568 times)
Hello,
With the latest versions of Windows10 1903 (Version 10.0.18362.476) and 1909 (Version 10.0.18363.476), I am getting an error in logs every time I am calling BASS_WASAPI_GetDeviceInfo().
It is easy to reproduce by running the «list» sample program, that comes with BASSWASAPI.
The error looks like this but repeated many times:
avcoreaudiocoreclientaudioclientmmdeviceactivator.cpp(303)AUDIOSES.DLL!7AC1EC4A: (caller: 7AB70436) ReturnHr(1) tid(2f20) 88890004
Running the same code on older versions of Windows10 1809 (Version 10.0.17763.864) seems to be free of error messages.
However BASS_WASAPI_GetDeviceInfo seems to be working correctly. The only problem is those messages get printed on every BASS_WASAPI_GetDeviceInfo call.
This may be Microsoft issue since I see there are other instances when they left OutputDebugString on Release versions, see https://social.msdn.microsoft.com/Forums/vstudio/en-US/3a5a145a-c13d-4898-bb61-a5baadc9332f/why-am-i-getting-hundreds-of-weird-messages-in-debug-output-window?forum=vcgeneral
Is there anything you can do on your side so we don’t get a lot of those messages? The log message seems to be displayed when MMDevAPI.dll!CEndpointDevice::Activate() is called.
Best regards,
Cristian
Logged
I don’t seem to be able to reproduce that here (on 1909), using the DebugView app to capture debug text. Perhaps it’s device-dependent. Can you reproduce it on other systems? Does the number of debug entries match the number of devices listed by the LIST.EXE example?
Logged
I am so sorry for the late reply.
I modified the LIST code to use OutputDebugString() instead of printf() so we know when the error occurs.
List enumerates 56 devices and returns 48 errors, I saw this happening on at least another system.
I attached the debug log.
Every time the error is printed, the call stack looks like this:
KernelBase.dll!_OutputDebugStringW@4() Unknown
AudioSes.dll!wil::details::LogFailure() Unknown
AudioSes.dll!wil::details::ReportFailure() Unknown
> MMDevAPI.dll!CEndpointDevice::Activate() Unknown
89f84d8b() Unknown
In each error message I see «88890004» which means AUDCLNT_E_DEVICE_INVALIDATED … which means:
«The audio endpoint device has been unplugged, or the audio hardware or associated hardware resources have been reconfigured, disabled, removed, or otherwise made unavailable for use.»
Maybe the devices that show the error are unplugged?
PS: Devices with BASS_DEVICE_ENABLED flag set do not show an error when using BASS_WASAPI_GetDeviceInfo on them.
Best regards,
Cristian
« Last Edit: 12 Dec ’19 — 08:17 by Cristian1980 »
Logged
The «Activate» call in BASS_WASAPI_GetDeviceInfo is used to get the defperiod/minperiod/mixfreq/mixchans info. Here’s an update that will skip that call (the info will be 0s) when the device doesn’t have the BASS_DEVICE_ENABLED flag set.
www.un4seen.com/stuff/basswasapi.zip
Logged
The error message is gone and I can’t find any other issues.
Thank you,
Cristian
Logged