Hi @legnod
i think is better to split your MPEI in 2 files :
Atmolight Core.mpei (with version = MePo)
Atmolight + Atmowin (version of atmolight),
i think is better for update Core
@gemx
Can you explain what is the différence between patch files stored on repo plugin ?
V1_2_Framegrabber with OnNewFrameEvent.diff (seems to be used for all patched Core.dll)
V1_3_FrameGrabber with resize option take2.diff
Ok i found the problem! The plugin has enabled the AtmoWin Live View and not the MP Live view.
I also splitted the MPE files into two different plugins as azzuro suggested.
Atmolight process plugin
MP core changer
At the moment the MP core changer isn`t available in the plugin repository but i will add it as soon i am ready with it.
EDIT: What do you think...should i open up a new thread (maybe "Ambilight plugin suite") or something, because it contains now 3 different software tools (Atmolight process plugin, MP core changer and different AtmoWin versions)...the original threads are really confusing for everyone whos knew to Ambilight.
Yep, as we have discussed for open thread about AtmoWin Only !
I think we can create an Google code, with all Atmowin version & Atmolight (dédicated to MediaPortal) Software as Hardware (Teensy / Sedu / ...) ...
and add acces for Dev. ( as contributor or more)
Angie can post directly on Google code with an backup for her changes.
Hmm in my opinion a thread only for atmowin isn`t really necessary...i would include this in a new Thread about the whole Ambilight software you need. The existing threads are useless for people who want to get information about it.
To create a googlecode page is a good idea...have you already created one or should i do this?