MMDeviceAPILib questions

[kdschlosser]

I have a couple of questions for ya jonib.

why is it that you package a tlb file with AudioEndPointCtrl?
I was looking at the generated MMDeviceAPILib.py and couldn't this be simply packaged with AudioEndpoint?

there is only a few lines in the file that has to be changed. would be the import of stdole to the code below and then you can have comtypes generate the stdole file and you package that also. and change the import stdole back

try:
    import stdole
except:
    from comtypes.client import GetModule

    GetModule("stdole2.tlb")
    import comtypes.gen.stdole as stdole

you would also need to remove the lines below from both the MMDeviceAPILib as well as stdole.

from comtypes import _check_version; _check_version('501')

I have not tested this with anything other then Windows 7 But i do not think that Microsoft has changed the API on anything like the GUID's/UUID's they may have changed some of the parameters but these can be dealt with at the code level. then you would have a pure python implementation

[jonisb]

I include the generated code when used with EventGhost 0.4 as the comtypes in Python 2.6 don't generate correct code for the .tlb, so there shouldn't be a problem including it when using newer Pythons.

But the idea as for now is to use the .tlb to generate the API interfaces and get any improvements in case the comtypes has been updated, without me having to make a new release just for that.

Edit: Also comtypes handles Python 2/3 related issues. as my library is intended to work with both.

But honestly I have not thought too much about it as I was focusing on more important stuff like making the library API as usable as possible.

As the library is not finished yet, I might change my mind how I want it, and that's part of the reason I haven't finished it yet as I'm having some problems deciding on some stuff.

[kdschlosser]

fully understandable. But if you took the correctly generated file from a python 2.7 installation and use it in a 2.6 installation would it work? I bet it would. and that could alleviate some support issues. I know there was something about the thing making files that it didn't remove.. But also I have another question and I do not know if you have had an issue with this as well. but in Windows 10 say with eventghost. if for some reason the AudioEndpointControl plugin ends up in the EG installation folder is comtypes able to generate the file? because it appears as tho this file gets written to the plugin directory. and I know that there is are issues with windows 10 and an application not being able to write anything to the ProgramFiles directory. And if this lib was to get added to EG then it would be in the core directory in the ProgramFiles folder which could potentially cause an issue.

also... is the problem with comtypes generating the file in python 2.6 have to deal with stdole? because if it does then you can simply do an import of stdole before you create the MMDeviceAPILib and if there is an error in this then you can have it generate the stdole and then import MMDeviceAPILib.

It's just that I was reading the PR on the EventGhost Github page. and sifting through the forum thread on AudioEndpointControl trying to separate any support questions/problems between the plugin and the actual back end. and the biggest one that concerns me thus far is the one where a file was created and there was something wrong with it. other then that i do not have any real concerns with it.

There are a couple of ideas that I have if you wouldn't mind can i submit a PR for them. and then you can go through it and see what ya think. you might get a few ideas that you want to use, But it could also get a spark in ya to want to work on it again. I know how that goes with getting burnt out on a specific project.

Just trying to toss out some ideas to ya to remove any possible issues. Lord knows with my code I am having to do cleanup all to often. LOL I am trying to be more careful now because of the catastrophe when i added the named pipe to EG. I want to avoid having that happen again. and also because of the complexities of comtypes and ctypes trying to fix issues are a nightmare. as well as if there is an issue I know you do not want us editing the library. which would make it so that the responsibility would fall on you to solve the issues.

there is one other thing. I do want to make sure that you are still ok with it getting used in EventGhost. And if you are still ok with that then you will need to put some kind of a license in place on it. and have it as a header in the files.

sorry for the long winded response. and I am sure it will not be the last one if you are ok with us using it. Trying to get a better understanding of how it works and why things are done the way you have done it. and also trying to make sure that things like generated files get written where they should be.

[jonisb]

But if you took the correctly generated file from a python 2.7 installation and use it in a 2.6 installation would it work?

I haven't tested/checked how specific the code is between 2.6/2.7 but I'm fairy certain Python 2/3 produces non compatible code.

But also I have another question and I do not know if you have had an issue with this as well. but in Windows 10 say with eventghost. if for some reason the AudioEndpointControl plugin ends up in the EG installation folder is comtypes able to generate the file?

I haven't done any checking in Windows 10, but I believe comtypes has several fallbacks where it puts the generated files, but again haven't looked into that specifically yet.

also... is the problem with comtypes generating the file in python 2.6 have to deal with stdole?

I believe it was "MMDeviceAPILib.py" and some variable type wasn't properly generated, don't remember exactly anymore.

biggest one that concerns me thus far is the one where a file was created and there was something wrong with it.

Yeah that is something I intend to handle, I haven't looked into it more but it should be easy to handle by re generating the API files if the previously generated files can't be imported.
But I need to look into it further.

There are a couple of ideas that I have if you wouldn't mind can i submit a PR for them.

Sure, but I'm (trying) to focus on other projects right now (XBMC2 plugin remastered HD remake), So I can't put too much effort into in right now.

as well as if there is an issue I know you do not want us editing the library. which would make it so that the responsibility would fall on you to solve the issues.

I just think that any changes should be done to the source repository unless it's intended to be a fork that is different than the original version.

I do want to make sure that you are still ok with it getting used in EventGhost.

Of course, that's why I made it a separate library so it could be used by other projects and not just the project I needed the functionality for in the first place.

And if you are still ok with that then you will need to put some kind of a license in place on it. and have it as a header in the files.

So I hate doing documentation, and I care even less for license stuff, I just wanna code. I want it to be some kind of open source license compatible with EventGhost but I just haven't had the interest to look into it properly yet.

Trying to get a better understanding of how it works and why things are done the way you have done it.

This library is my first attempt at making a library that is not just for my personal projects, so I had to do stuff much differently to how I'm used to. So I am definitely interested in feedback, suggestions and code.

Unfortunately I'm very unflexible and can basically work on one bigger project at a time, and then it takes awhile for me to get going on a different project, but I'm working on trying to be more flexible but I probably need a brain transplant for that.

[kdschlosser]

well it could be worse ya know. you could be like me.. all over the place with what seems like no direction. put the 2 of us into one person and imagine what ya would end up with... LOL

[kdschlosser]

Simply select one of the licenses that GitHub provides. They are pretty much all the same.

Just make sure that you add a couple of additional requirements to it.

1: If this software is to be distributed along with another piece of software. That software has to fall within the guidelines of your license. Meaning it has to be Open Source.

2: In the Printed/Electronic/Imaginary Documentation a little thank you or blurb about you the author and the name of the library.

3: Any place that the parent software displays it's license and copyright information, The library's license and copyright should also be show.

4: Because this library is open source not the author or any person(s) that have contributed code are held liable for any losses including but not limited to lost revenue, damages, labor, time, arms, legs.....

5: In no way am I to be required to provide support, consulting, bug fixes, or even have to speak with you.

6: If it is found that you have had monetary/tangible gains from the use of this software other then a pay for support system. You will be required to donate a whole heap amount of time volunteering with early teens. Showing them what life is like away from the computer, cell phones and video games. and why it is wrong to use someones work without their permission for personal gain (stealing).

You are using this software of your own free will and no one is forcing you. If you don't like the terms of the license.. then don't use it!.

HEH I kinda like that.... #6 is is a good punishment I think.

[jonisb]

I'll check what GitHub provides.

Your number 6 is something I don't agree with, but that is something I need to figure out.