Just an interest/request, probably not easy to implement.
Once a recording has been started (files created) can the plugin then change the file names with the corrected data from the now/next grab which is correctly parsed through your plugin.
There may be a problem with the way TvServer locks the files though.
It's not possible to change the file name while it is in use.
Could possibly alter the recording name in the database, but I don't think that's a best practice approach.
Is this in relation to the issues with Sky Grabber plugin?
Because there may be some light on the horizon in that regard. .....
hi, hurley,
I installed your plugin from the extension manager without problems. If I try to configure it, it takes really-really long to load (>2-3min... first I thought it crashed). Is this normal?
my setup: MP 1.14 final, MS SQL, 2x DVB-S2 Cards with several hundred channels found
That's no good at all!
I have noticed some sluggish config init before but not to that extent.
Though I only have some 20 channels, so that may be relevant.
Also I haven't had a chance to test it with 1.14 as yet.
Are there any errors in the plugin's/MP's log files? Particularly relating to database?
Will d/l 1.14 source and look into it and get back to you.
Thanks for the report.
which logs exactly should i check? tv-server or mp?
I tried the plugin and it works great otherwise. I have some problems with the character set of my provider with accented vowels (I see "Èu" insted "ú" and stuff) and I can simply replace them with the correct ones. I don´t need to configure it too often so I can wait every so often... no problem.
Sorry for the delay, Tv-Server logs (tv.log and error.log if exists) and EPG Cleaner error.log if it exists.
These can be found in the folders below:
C:\ProgramData\Team MediaPortal\MediaPortal TV Server\log\ C:\ProgramData\Team MediaPortal\MediaPortal TV Server\log\EpgCleaner\
Would be best to delete them first, then start the plugin config and exit straight out. Then zip/attach those files here.
I suspect this may be a database related issue so there may not be any reported errors.
In any case, I'll put together a special debug build with additional logging to help pin down the source of the issue.
I've identified some areas where efficiency could be improved and will implement these changes in the next release.
These are unlikely to cause such a delay, but I've seen unusual behavior with db activity before and it's possible that small delays don't scale linearly with many channels for example.
Unfortunately my time's severely limited at the moment so it may take a while to resolve this but I'll do the best I can.
...Had a quick look at MP 1.14 source and there doesn't appear to be any compatibility problems there.
Update @kszabo.
I set a up a 'pressure test' with 1000 channels, 50 groups and 200 filters and was able to reproduce load delays of around 20-25 seconds on my system.
The main cause turned out to be unexpected but was related to loading a large number of channels into the menu list associated with the filter test button.
I think there's room to optimize further so I'll just post a temporary fix manual install package for now and do a more thorough review over the coming weeks.
Thanks again for bringing this to my attention.
I hope this solves the bulk of the problem for now. Please let me know how successful the fix is for you.
Hi Hurley,
forgive me for my late response, I had a busy week.
I just tested the attached fix from the previous post and it worked like a charm. The plugin loads within seconds instead 2-3 minutes. Do you still need logs?