2015-06-25, 13:41
Hmm.
The log seems to be from the debug version? I'm not sure what is crashing - as there is no exception thrown by Yatse2 in the log. When you say crashing what do you mean?
Make sure no other version is running - sometimes a thread left over if doesn't close probably. Check Task Manager and force close everything.
Start with a new fresh directory and use the latest 3.1 version. Delete the Log directory and delete the Yatse2.db and the Yatse2.xml file. eg. start a fresh.
Run the Yatse2.exe
Should go straight to settings screen - (as there is no xml) on the 2nd screen
If it crashes at this point - something is up with your 2nd screen.
If crashes -
Copy the following xml file - using this one in the directory:
https://github.com/Ghawken/Yatse2-1/rele...Yatse2.xml
This is the default settings - just not using the 2nd screen.
Hopefully this then runs as it should and we can then work on the 2nd screen issues.
The remote is the connection between Yatse2 and Kodi - this needs to be setup. By clicking on the Yatse2 wifi like button and connecting to a running kodi instance - ideally on the same machine.
Kodi needs to be running and the web control needs to be enabled and the ports need to be the same. Pays to set that up first. Should connect to the kodi instance.
Lets see if that goes okay - presume something is crashing when it tries to run it on your 2nd screen. Would suggest focus on getting it running on single/first screen and then trouble shoot the rest.
Edit:
I've just re-read your post and sorry didn't follow you before - when you say "second screen" - you mean enabled second screen in the options dialog? And then it crashes. It works okay on first screen with no crashes?
Probably do need that log data as that's why it's there - try to zip it and out on mediafire or something similar.
The unusual thing is your secondscreen is called framebuf - and seems to want a refreshrate of 1. Something is obviously up with the automatic detection of your screen, What motherboard and video driver is it?
Thanks
The log seems to be from the debug version? I'm not sure what is crashing - as there is no exception thrown by Yatse2 in the log. When you say crashing what do you mean?
Make sure no other version is running - sometimes a thread left over if doesn't close probably. Check Task Manager and force close everything.
Start with a new fresh directory and use the latest 3.1 version. Delete the Log directory and delete the Yatse2.db and the Yatse2.xml file. eg. start a fresh.
Run the Yatse2.exe
Should go straight to settings screen - (as there is no xml) on the 2nd screen
If it crashes at this point - something is up with your 2nd screen.
If crashes -
Copy the following xml file - using this one in the directory:
https://github.com/Ghawken/Yatse2-1/rele...Yatse2.xml
This is the default settings - just not using the 2nd screen.
Hopefully this then runs as it should and we can then work on the 2nd screen issues.
The remote is the connection between Yatse2 and Kodi - this needs to be setup. By clicking on the Yatse2 wifi like button and connecting to a running kodi instance - ideally on the same machine.
Kodi needs to be running and the web control needs to be enabled and the ports need to be the same. Pays to set that up first. Should connect to the kodi instance.
Lets see if that goes okay - presume something is crashing when it tries to run it on your 2nd screen. Would suggest focus on getting it running on single/first screen and then trouble shoot the rest.
Edit:
I've just re-read your post and sorry didn't follow you before - when you say "second screen" - you mean enabled second screen in the options dialog? And then it crashes. It works okay on first screen with no crashes?
Probably do need that log data as that's why it's there - try to zip it and out on mediafire or something similar.
The unusual thing is your secondscreen is called framebuf - and seems to want a refreshrate of 1. Something is obviously up with the automatic detection of your screen, What motherboard and video driver is it?
Thanks