AtmoWin - improvement discussion (9 Viewers)

[HomeY]

Gentleman ... could you please provide the versions you want to use for testing in the first post - I'm following this thread now since start and I have meanwhile NO clue what combination should work.

The 2 versions in first post should work. I don't have connection issues when i let Atmolight start/exit Atmowin together with MediaPortal. Haven't tested if Atmolight also connects nicely to an already running Atmowin.

@BassFan
I've just rolled back to Atmolight 1.0.19017.1 since i also have the freeze with 1.0.19019.0

 

[BassFan]

Gentleman ... could you please provide the versions you want to use for testing in the first post - I'm following this thread now since start and I have meanwhile NO clue what combination should work.

Fact is that using the last ones provided in the Plugin Installer atmowin works - as it always did - but atmolight doesn't (connect?).

Markus

Yes that is a bad..
i think all files here should be deleted.
then a new MPEI installer should be created with the last used file by me,
i will then Change the Revision to both AtmoWin = Atmolight.

We can only fix the incompatibility, if both files have the same version. (The pure mess)
@azzuro what your think?

@HomeY I've just rolled back to Atmolight 1.0.19017.1 since i also have the freeze with 1.0.19019.0

My suspicion is that the problems slow in MP arise.
Until I can change what because I have to wait next final on that.

See FrameGrabber.cs that is the class which send the next Frame to AmbiLight Plugin
is any wrong then here ..

greets

 

[pur_berger]

Yeah - would be a good thing to do. Also - it's only a feeling - but you push out releases to fast.

What also would be a good thing to have is to automate the registration during installation.

 

[azzuro]

We can only fix the incompatibility, if both files have the same version. (The pure mess)

i dislike to have same version for Atmowin & Atmolight.
why ? - > because the Atmolight can bump with change, Atmowin not, vice versa.
i must release a new Atmowin package based on your file.
what is the version ? 16x9 ou 4/3 ???

But Sure, is better to add in fist post all binary files. for have lot of help from user.

 

[azzuro]

First Post edited, with test binary.

 

[BassFan]

i dislike to have same version for Atmowin & Atmolight.
why ? - > because the Atmolight can bump with change, Atmowin not, vice versa.

No problem your decision.

Ich habe ein spezielles Build für @HomeY erstellt
Damit kann er testen ob MP immer noch einfriert.
Diese Version Rendert nichts gibt aber alle 1000 MS eine Message aus.
Friert MP weiterhin ein dann liegt es nicht an Atmolight sondern an MP(FrameGrabber) selbst
bzw. am TsReader.
-----------------------------
I have created a special build for @HomeY
So he can test whether MP still freezes.
This version renders nothing there but every 1000 MS off a message.
MP still freezes then it is not Atmolight but MP(FrameGrabber) itself
or the TsReader.

I can't do on this time more

greets

 

[pur_berger]

OK - so - what I have found ...

I tried now tons of combinations to find what is working and what isn't - and - believe it or not - in my case the problem is the Path in Program Data ...

No idea why - but - if I copy all the content from Atmowin (only the Content!) to a folder in c:\atmo - it works. Copying the whole Folder - fail ...

I checked permission and everything - no difference.

Found somthing even more strange ... when I give teh Folder in ProgramData the same name as the one in C:\ - so both are called "atmo" the plugin is able to start atmowin - but can't connect. When I change teh Name in ProgramData back to Atmowin it works again (Plugin pointing to c:\atmo)

 

[BassFan]

OK - so - what I have found ...
I tried now tons of combinations to find what is working and what isn't - and - believe it or not - in my case the problem is the Path in Program Data ...
No idea why - but - if I copy all the content from Atmowin (only the Content!) to a folder in c:\atmo - it works. Copying the whole Folder - fail ...

You can not simply move the data to a folder of your choice.
AtmoWin and AtmoLight use a folder with read and write access.
This is the folder "C:\ProgramData\Team MediaPortal\MediaPortal"
Without it, you will find no functioning language file.
I don't understand why you experimenting around.

please do not Change any which is not compatible to the install order of MPEI.

greets

 

[pur_berger]

OK - so - what I have found ...
I tried now tons of combinations to find what is working and what isn't - and - believe it or not - in my case the problem is the Path in Program Data ...
No idea why - but - if I copy all the content from Atmowin (only the Content!) to a folder in c:\atmo - it works. Copying the whole Folder - fail ...

You can not simply move the data to a folder of your choice.
AtmoWin and AtmoLight use a folder with read and write access.
This is the folder "C:\ProgramData\Team MediaPortal\MediaPortal"
Without it, you will find no functioning language file.
I don't understand why you experimenting around.

please do not Change any which is not compatible to the install order of MPEI.

greets

Sorry - but only to claryfy this - I know what I'm doing ...

Atmowin is not an Installation at all and the point here is that when going from scratch with the provided installation files It simply does not work (at least with 8.1). With the original installation (and atmowin always was inteneded to bo in a root Folder - you have changed this to the Team-Media Directory in ProgramData) - so hopefully you didn't put hardcoded paths somewhere?

Anyway - bottomline is - using the installer it won't work. Moving the Filelocation back to a rootfolder it does. Removing / Renaming your Folder it fails again. Did you give any thought in the fact that "Team Mediaportal" could cause issus because of the space?

 

[azzuro]

@pur_berger : try to register Atmowin
comand line : AtmowinA.exe /register maybe the registry is broken, and look the rights on this folder.