Side by Side issue after 1709 update with audacity (finally solved).

[William Gaatjes]

I just updated audacity to 2.2.0 to see if that hepled, and it did not.

It is in dutch unfortunately, do you think i can get replace my dutch windows for an english version with my current product key ?
I do noticed that when i want to downlaod the english version i have the bad luck that micrsoft always redirects me to the dutch version which i do not want.
I already given them feedback to add the option to choose for another language version on the website when wanting to download the windows iso.

Kan activeringscontext voor C:\Program Files (x86)\Audacity\audacity.exe niet maken. Fout in manifest of beleidsbestand op regel . Een onderdeelversie die nodig is voor de toepassing, conflicteert met een andere onderdeelversie die reeds actief is. Conflicterende onderdelen zijn: Onderdeel 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.19_none_cc92fab02215da61.manifest. Onderdeel 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.19_none_1440318736920367.manifest.

It says that these two conflict with each other :
C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.19_none_cc92fab02215da61.manifest.

C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.19_none_1440318736920367.manifest.

I assume this is a dll problem but i do not know why both of these dlls

Here are the details :
details:

- System
- Provider
[ Name] SideBySide
- EventID 78
[ Qualifiers] 49409
Level 2
Task 0
Keywords 0x80000000000000
- TimeCreated
[ SystemTime] 2017-11-12T14:32:06.862066100Z
EventRecordID 1162
Channel Application
Computer My PC.
Security
- EventData

C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.19_none_cc92fab02215da61.manifest

C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.19_none_1440318736920367.manifest



































C:\Program Files (x86)\Audacity\audacity.exe

 

[mikeymikec]

The event log entry is usually more helpful than that, oh well

http://www.audacityteam.org/download/legacy-windows/

It looks like you need the VisualC++ 2008 redistributable. I'd guess you need the 32-bit one considering where the app is installed, but nothing bad will happen if you install both versions.

- edit - I'm a bit surprised by that page talking about "Legacy Windows", because while I haven't yet seen a side-by-side issue on Win10, I've definitely seen it on Win8x.

 

[William Gaatjes]

But i have the latest audacity 2.2.0. That is not legacy.

 

[mikeymikec]

But i have the latest audacity 2.2.0. That is not legacy.

It appears to require the same support library.

- edit - scratch that, it may require visualc 2013 instead:

https://www.microsoft.com/en-gb/download/details.aspx?id=40784

 

[William Gaatjes]

Well, i installed the 32 bit redistributable and i have not seen the side by side error since.
I will keep checking the logs for a while.

Thank you.

 

[mikeymikec]

Np. The 2008 or 2013 one?

 

[William Gaatjes]

The 2008 32bit x86 version from the link via the audacity site.

 

[William Gaatjes]

Sigh, i do not know why, but the sidebyside error is back.
Oh well. A few more weeks and then i can install windows 10 fresh.
I have to create a list what needs to be changed after installation.

 

[William Gaatjes]

Now that i have an us english windows, the log entry is easier to digest because it is not a literal translation :

Activation context generation failed for "C:\Program Files (x86)\Audacity\audacity.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\WINDOWS\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.125_none_15cbcf8893620c09.manifest. Component 2: C:\WINDOWS\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.16299.125_none_5d79065fa7de350f.manifest.

The event id is 78.

I have been doing some reading because i am still curious and found an interesting explanation from microsoft support for someone with a similar eventid 78 sidebyside issue but for dreamweaver.exe from adobe.
This from another program from another user:

This error is caused by a wrong manifest embedded in the FormDesigner application. If you open the application in Visual Studio and extract the manifest you will see two references to the common controls dll - one processor-agnostic (*) version and one version requiring x86. On a 64-bit machine processor-agnostic references will appearantly resolve to the 64-bit version. The error in the event log is legitimate since imports are already defined from whatever version was process first. To test just try removing the processor-agnostic reference from the manifest and resave the app in Visual Studio. When you rerun the app the errors are gone.

This might be an audacity issue that has nothing to do with windows dll files. the event id 78 is key here.
This problem may have come to existence since update 1709 but since all the other programs do not have this issue on my pc, this might be audacity related.
To understand what is going on, i went to search for what an application manifest actually is.

https://msdn.microsoft.com/en-us/library/windows/desktop/aa374191(v=vs.85).aspx

An application manifest is an XML file that describes and identifies the shared and private side-by-side assemblies that an application should bind to at run time. These should be the same assembly versions that were used to test the application. Application manifests may also describe metadata for files that are private to the application.

With windows executables, one can add resources such bitmaps and other files. One of those resources is the manifest.

I went to the audacity forums and lo and behold, i am not the only one that notices these errors in the event viewer logs.
It seems something is different with windows since 1709 and perhaps the audacity developer needs to catch up.



As a sidenote :
Audacity works fine but has some issues when pressing play back right after the start it will not playback unless i do the following workaround:
1. set the samplerate at 48000 Hz
2. pres play and stop.
3. set the samplerate at 44100 Hz.
4. press play and profit.
I use 44100Hz because my mp3 codec does not support 48000Hz sample rate.
I have tried the lame codec but that codec sounds really awful when compared to my official fraunhofer codec.
It is as if the phase between the left and right channel is different after mp3 encoding with the lame codec.
That is why i still encode mp3 from 44100Khz by making use of the fraunhofer codec i have
.This strange sidebyside issue and the samplerate issue both has happened since windows update 1709.
I was still searching if windows 1709 is set to have a default sample rate of 48000Hz, i am still in the process of figuring that out.

As it turns out, dreamweaver from adobe had the same issue sidebyside eventid78.
And a very good support help called Arindam_G proposed this :

Workaround 2:

1. Open "Windows Explorer" and go to "<Installation drive>:\Program Files (x86)\Adobe\Adobe Dreamweaver CC"
2. Make a backup of "Dreamweaver.exe"
3. Download and install "Resource Tuner" from this link: http://www.restuner.com/download.htm
4. Launch "Resource Tuner"
5. Go to menu "File -> Open File..."
6. Browse to "<Installation drive>:\Program Files (x86)\Adobe\Adobe Dreamweaver CC" and select "Dreamweaver.exe"
7. Click "Open"
8. On the left-hand-side, expand "Manifest"
9. Select the file displayed under "Manifest"
10. Click the "Resource Editor" button
11. Locate the following section (please note that the value for "publicKeyToken" may vary) <dependency><dependentAssembly><assemblyIdentity type="win32" name="Microsoft.Windows.Common-Controls" version="6.0.0.0" processorArchitecture="*" publicKeyToken="6595b64144ccf1df" language="*"></assemblyIdentity></dependentAssembly></dependency>
12. Select and delete the entire section as in previous step
13. Click OK
14. Click Yes (for the confirmation dialog)
15. Go to menu "File -> Save File As..."
16. Keep the name as "Dreamweaver.exe" and click "Save"
17. Click Yes (for the confirmation dialog)
18. Close "Resource Tuner"
19. Launch Dreamweaver CC

I had nothing to lose, thus i installed the resource editor restuner.
I copied audacity.exe to a temp map where i have enough privileges.
I edited audacity.exe as described above with restuner, removing the assembly manifets text.
I then saved the program renamed my original audacity.exe as audacity_original.exe
copied from temp to programfiles (x86)/audacity folder auadacity.exe and ran audacity.
It works. No more error logs in the eventviewer. :^_^
I still have to some more testing if everything still functions with audacity.

the problem may be that the audacity developer may need an update to his visual studio version that is required to function for windows 1709.
I am not sure about that though...

edit:
edited the text because the samplerate issues are not all gone yet.
Can still be an audacity issue...

 

[William Gaatjes]

Well, this may help explain the error opening sound device message i get when pressing playback after a recording (since update 1709):

http://wiki.audacityteam.org/wiki/Windows_10_OS

If you have a machine upgraded from previous Windows, or older external sound devices, some or all of your devices may lack Windows 10 drivers that are properly matched to the device. In that case, Audacity 2.1.2 or versions before that might show Internal PortAudio error on launch and not see any devices at all, or might show error opening sound device when playing or recording on some devices.

http://wiki.audacityteam.org/wiki/Windows_10_OS#error_open

of course i checked for the latest drivers for the realtek ALC887 audio codec and i already have those and they are not updated since august 2015. On the realtek site there is no mention of the ALC887.

For now, i will just be using my workaround as described in the previous post .

 

[William Gaatjes]

Well, i have been testing some more and there one thing with audacity that i just do not get. The audiohost selection is so small and limited in available characters that it is impossible to read what is selected. I set it to an option that i think is windows WASAPI but no way to be sure. I just found out that there is also a windows directsound option. And strange thing is that MME did not work for me. But of course this is a newer version and now MME works. I will just leave it at MME. Selecting Windows wasapi causes the error opening sound device message when recording and immediately doing a playback.

To sum it up :

• Windows wasapi is the option that gives an error in playback device. That may be a driver issue that i cannot solve. That is solved by selecting MME which now allows me to select proper recording devices. I can remember that i had some issues before with older versions of audacity.

• The eventid 78 sidebyside issue is a manifest issue in audacity or because i have 2 audio devices and causes an error in the eventlog for audacity.One from realtek and one from AMD. I checked that in the device manager.

But this is now gone.
Another issue solved.