Hi all,
Just thought I revisit this age-old question (well.. maybe not age-old
):
Should MP recording engine be a service?
I have been trialing GBPVR for the past week (*ducks for cover*) and have found that when you do get TV recording working.. it simply *works*.. all the time.. even when you are surfing the net, watching videos, watching TV that is also being recorded, listening to music, whatever...
(1) The recording service is a lean mean recording machine.
(2) When the frontend crashes/has a problem (as you do) the recording service is not affected.
Whereas with MP, I find that my recordings tend to stutter due to: listening to music (with Visualization on), checking TV guide.
Sometimes my MP dies while watching video (it happens) - and I have to frantically try and restart it - hoping that i don't miss out too much of my recording
So I can't help but wonder if the service approach provides a more robust solution (?).
Oops.. sorry for the long post.. thanks for your patience
Just thought I revisit this age-old question (well.. maybe not age-old
Should MP recording engine be a service?
I have been trialing GBPVR for the past week (*ducks for cover*) and have found that when you do get TV recording working.. it simply *works*.. all the time.. even when you are surfing the net, watching videos, watching TV that is also being recorded, listening to music, whatever...
(1) The recording service is a lean mean recording machine.
(2) When the frontend crashes/has a problem (as you do) the recording service is not affected.
Whereas with MP, I find that my recordings tend to stutter due to: listening to music (with Visualization on), checking TV guide.
Sometimes my MP dies while watching video (it happens) - and I have to frantically try and restart it - hoping that i don't miss out too much of my recording
So I can't help but wonder if the service approach provides a more robust solution (?).
Oops.. sorry for the long post.. thanks for your patience
Canada