Details
Major Description
http://forum.team-mediaportal.com/development-mp-1-0-1-283/orphaned-recordings-problems-solutions-48238/
Looking at the recording table, we refer to the channe table by the idchannel field.
This has a few drawbacks which are;
If the enduser decides to delete all his channels in order to do a complete re-scan, maybe the reason was to get rid of a lot inactive channels etc- the reasons could be many.
The result is that the channels that the recordings point to now have different ID's.
The result in mp-tvplugin is that playback of the recording fail, no error msg. just no action happens when u click on the recording.
MP.log and error.log are riddled with lots of nasty exceptions though.
It took me a while to figure out what the problem was.
each time we reference recording.referencedChannel().somemethod(), then we have ourselves a null pointer exception.
We have rtv's nice recordedTV importer, which can be activated by using setupTV.
instead of entering setupTV, why not call it from the tvplugin instead?
proposal;
the user enters "MyRecorded TV".
He suddenly realizes that his recordings do not have channel logos no more, also those recordings will not start when u click on them.
ok, now he choose "repair/import" or whatever er choose to call in the left context menu ..the recording list is now refreshed, with logos and they playback fine now.
the DB has now been refreshed and all is dandy.
We could always use the existing skin button "clean up".
This would seem like a small task.
Then we have the next bigger proposal.
Instead of linking recording table to channel table with idchannel, why not use channel.name instead (if it is unique).
This would fix the problem where a recording would get orphaned.
Looking at the recording table, we refer to the channe table by the idchannel field.
This has a few drawbacks which are;
If the enduser decides to delete all his channels in order to do a complete re-scan, maybe the reason was to get rid of a lot inactive channels etc- the reasons could be many.
The result is that the channels that the recordings point to now have different ID's.
The result in mp-tvplugin is that playback of the recording fail, no error msg. just no action happens when u click on the recording.
MP.log and error.log are riddled with lots of nasty exceptions though.
It took me a while to figure out what the problem was.
each time we reference recording.referencedChannel().somemethod(), then we have ourselves a null pointer exception.
We have rtv's nice recordedTV importer, which can be activated by using setupTV.
instead of entering setupTV, why not call it from the tvplugin instead?
proposal;
the user enters "MyRecorded TV".
He suddenly realizes that his recordings do not have channel logos no more, also those recordings will not start when u click on them.
ok, now he choose "repair/import" or whatever er choose to call in the left context menu ..the recording list is now refreshed, with logos and they playback fine now.
the DB has now been refreshed and all is dandy.
We could always use the existing skin button "clean up".
This would seem like a small task.
Then we have the next bigger proposal.
Instead of linking recording table to channel table with idchannel, why not use channel.name instead (if it is unique).
This would fix the problem where a recording would get orphaned.