Somehow, you're using a old version of ECP2Assembly. Can you delete ECP2Assembly.dll from your MediaPortal folder then reinstall the latest version of MPW. That should fix it.
Sam
Sam
Webinterface plugin (1 Viewer)
- Thread starter Maschine
- Start date
Any way to manual recording via WAP ???
Is there any way to add a manual recording, on the same way as web interface do, via WAP. I can see how to do it throw EPG, but some channels doen not have EPG guide. How can i make a recording of them.
Thanks.
Is there any way to add a manual recording, on the same way as web interface do, via WAP. I can see how to do it throw EPG, but some channels doen not have EPG guide. How can i make a recording of them.
Thanks.
Denmark
Re: Any way to manual recording via WAP ???
No - not yet that is.
We might be integrating this in the future.
laura25 said:
No - not yet that is.
We might be integrating this in the future.
computer said:
Perhaps look at the amount of memory being used by Apache - and what's available in the machine.
I've never experienced it at my own HTPC....
CPU penatly isn't so bad here; TV does not suffer at all, but you can see when you first access the web interface because there is a lot of disk activity for a few seconds. Having a hardware TV tuner helps here. But I agree that the load seems a bit on the high side.
computer said:
Mine is ~10MB and ~36MB
- Thread starter
- #370
Hi!
This surely depends on the size of your TV database. I have very detailed data here on my HTPC which is for the next 14 days with ~35 channels. At the moment the algorithms dealing with the data are not very optimised. For example right now the hover data (when you go with your mouse pointer over a show) is loaded for all (!) shows in the guide view.
If we changed this to load it just when hovering over the one show you want to see it for it will decrease the database activity a lot. Same is for checking if a show is part of a series recording. There is also a lot of scanning in the database done.
Next thing is that using SQLite is slower than using a "real" MySQL-Server for example. This also explains the disc activity as SQLite is only a file on your hdd...
The only thing I can say at the moment is that you need to live with this. Sorry. We're all in all still in an early status of our projects and sometimes a quick'n dirty implementation is done to get it working, optimisation will be done later...
Maschine
This surely depends on the size of your TV database. I have very detailed data here on my HTPC which is for the next 14 days with ~35 channels. At the moment the algorithms dealing with the data are not very optimised. For example right now the hover data (when you go with your mouse pointer over a show) is loaded for all (!) shows in the guide view.
If we changed this to load it just when hovering over the one show you want to see it for it will decrease the database activity a lot. Same is for checking if a show is part of a series recording. There is also a lot of scanning in the database done.
Next thing is that using SQLite is slower than using a "real" MySQL-Server for example. This also explains the disc activity as SQLite is only a file on your hdd...
The only thing I can say at the moment is that you need to live with this. Sorry. We're all in all still in an early status of our projects and sometimes a quick'n dirty implementation is done to get it working, optimisation will be done later...
Maschine