Bug: dMCScripting.Converter COM interface broken in R17.0

[Gwennie]

Just a heads-up - the dMCScripting.Converter COM object can't be instantiated in version R17.0.

Tested on a couple of machines running Windows 10, including a freshly-installed virtual machine. Worked fine on previous versions of dBpoweramp.

Retrieving the COM class factory for component with CLSID {1C2E0932-61B5-4EAB-A832-06EE6564047D} failed due to the following error: 800700b6 The operating system cannot run . (Exception from HRESULT: 0x800700B6).

[Spoon]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

If you open a command prompt and change into the folder where dBpoweramp is installed then type:

regsvr32 dmcscripting.dll

What message is shown?

[Gwennie]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

Hi Spoon -

regsvr32 dmcscripting.dll

It (re-)registers successfully, but the class was already registered in the first place - that's not the problem.

Can you reproduce? (Quick test in PowerShell - New-Object -ComObject dMCScripting.Converter)

I should have mentioned in my first post - .NET ultimately throws System.BadImageFormatException. I followed a hunch and tested on both x64 and x86, but the problem's present on both.

Cheers

[Michael Sargent]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

I ran into the same problem. When I run it under the debugger, I get a message box that says:



(In case the image doesn't come through...)

WmpWia.exe - Ordinal Not Found

The ordinal 381 could not be located in the dynamic link library
C:\Program Files\dBpoweramp\dMCScripting.dll

OK

I tried removing and re-adding the reference a couple of different ways. Same result in all cases.

Hope this helps,
Mike

[Spoon]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

Download, unzip and replace the dMCScripting.dll:

http://www.dbpoweramp.com/beta/dMCScripting.zip

Note this is the 64 bit version of the DLL.

[Gwennie]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

Download, unzip and replace the dMCScripting.dll

Confirmed fixed!

Nice job - thanks mate.

[Michael Sargent]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

That fixed it.

Thanks for the incredibly fast fix.

Mike

[hvaleton]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

Hi, Spoon,

I'm having a slightly different problem.
Running a standalone script containing a reference to the dMCScripting.Converter object runs without problems.
I created a .VBS script named dMC_Test.vbs containing the following code:

' create shell object
Set WshShell = CreateObject("WScript.Shell")

' Create dMC Object
Set dMC = CreateObject("dMCScripting.Converter")

' Read All IDTags
For i = 0 To 10000
 Dim ElementValue
 ElementValue = dMC.ReadIDTagElementValue("M:\1_KLAS\ZZ_Verzamel\Pianotrio\Gál, Shostakovich - Piano Trios (Briggs Piano Trio 2018)\01 Piano Trio in E major, Op. 18_ I. Tranquillo ma con moto.flac", i)
 If ElementValue = "" Then Exit For
 Call WshShell.Popup(ElementValue, , "Read Tag", 0)
Next

And then I ran the following command from the command box:

Program Files\dBpoweramp>cscript C:\users\hans\dmc_test.vbs

This resulted in a number of pop-ups showing the name and content of all tags in the flac file.
So far so good.

But when I call the following piece of code from a VBS script that I start from within MediaMonkey

' create shell object
Set WshShell = CreateObject("WScript.Shell")
' Create dMC Object
Set dMC = CreateObject("dMCScripting.Converter")

' Read All IDTags
For i = 0 To 10000
 Dim ElementValue
 ElementValue = dMC.ReadIDTagElementValue("M:\1_KLAS\ZZ_Verzamel\Pianotrio\Gál, Shostakovich - Piano Trios (Briggs Piano Trio 2018)\01 Piano Trio in E major, Op. 18_ I. Tranquillo ma con moto.flac", i)
 If ElementValue = "" Then Exit For
 MsgBox ElementValue
Next

I consistently get the error

Sorry for the Dutch language error message, but translated roughly it says:

ActiveX component can't create the object 'dMCScripting.Converter'

What am I doing wrong, here? Is this maybe a case of 32 vs. 64 bit? Or something completely different?

[Spoon]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

It is likely Media Monkey does not have permissions to create activeX objects, or run the script.

Media Monkey is 64 bit?

[hvaleton]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

Hi Spoon, thanks for your reaction

10 years ago at least one person used this method successfully in a MediaMonkey script, see here, so I know it must be possible.

I'm a little bit surprised to find that my MediaMonkey runs in 32bit mode, if I can believe the task manager:

My Windows 10 installation works in 64bit architecture, so I always thought MediaMonkey would also run as 64bit. Maybe I should investigate this further...

Question: is it absolutely impossible for a 32bit applicationto call the dMCScripting.Converter object? Are there workarounds? Or should I simply try and get a 64bit version of MM?

Thanks in advance!
Regards, Hans Valeton

[hvaleton]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

Thanks for your reply, Spoon,

There has been at least one other person who tried to do this from within MediaMonkey and succeeded, as can be read here Seeing this was 10 years ago, he probably ran a 32 bit version of dBpoweramp?

My Mediamonkey runs in 32bit mode. It appears there never was and never will be a 64bit version.


Is it possible to download a 32bit version of the dmCScripting.Converter object? And would that solve my problem?

Thanks in advance!
Regards,Hans Valeton

[Spoon]

Re: Bug: dMCScripting.Converter COM interface broken in R17.0

We have never tested 32 bit calling 64 bit. It is not possible to have a 32 bit scripting in 64 bit Windows.