I don't want to abuse this thread for general MP2 questions, so only one comment:Because the DB handling is done by the server itself and a plugin has to use the functions the server is offering. Direct DB access is not fitting to the MP2 concept as all database actions have to be done by the MP2 server. And it is dangerous as we are using SQLite. SQLite is faster a lot compared to MySQL and it's way less complicated to set up and run. But SQLite did not like multiple accesses at the same time.what's the reason for you to go with the MP2 database instead of the TV database for recordings
Have done this a few times lately. No issues here and lightning fast. There is a problem on your setup/system then, no general MP2 issue.Import of existing recordings into the TV database is a pain! It takes ages, the configuration tool freezes and i had to do it more than one time to catch up all my recordings.
the configuration tool freezes
The configuration tool is part of TVE. As far as I know it has always had locks up during a large import, I assume the import is running on the event thread hence the GUI being unresponsive.There is a problem on your setup/system then, no general MP2 issue.
If you monitor the C:\ProgramData\Team MediaPortal\MP2-Server\Log\SetupTV log file, you will see the application is importing.I assume the import is running on the event thread hence the GUI being unresponsive.