1.0.8 available

[sub]

Okay, just testing it now and yes that does cure the tearing issue nicely. Does this mean if I start it on the secondary display and then force it over to the primary it will similarly revert back to software playback only?

Yes, unless you leave the window on the monitor it was created on, acceleration will not work. Behind the scenes when you move the app to another monitor Directshow starts using off-screen buffers to hold temporary image of the screen and does slow bitblt operations to show the screen.

[joecru]

Thanks Sub

New Software version working fine for me and with the PVR 350

[sixeyes]

Yes, unless you leave the window on the monitor it was created on, acceleration will not work. Behind the scenes when you move the app to another monitor Directshow starts using off-screen buffers to hold temporary image of the screen and does slow bitblt operations to show the screen.

Would it be possible to have a command line option controlling which monitor is used?

[HtV]

I don't think this was mentioned before:
I watched livetv through the mvp (pvrx2), when the program was finished I just turned the mvp off (on/off button), I did not quit the livetv, 6 hrs later I saw it was still recording to the temp-rec-dir. Is this supposed to be like this?
This was using the mvpmc dongle however I doubt that that has anything to do with it.

Cya Hans

[mvallevand]

I don't think this was mentioned before:
I watched livetv through the mvp (pvrx2), when the program was finished I just turned the mvp off (on/off button), I did not quit the livetv, 6 hrs later I saw it was still recording to the temp-rec-dir. Is this supposed to be like this?
This was using the mvpmc dongle however I doubt that that has anything to do with it.

Hans, see my replay to jksmurf on this thread.

http://forums.nextpvr.com/showthread.php?t=27701

I don't know if it's related to mvpmc, after all all the sockets are dropped and the GBPVR logs says that the client is gone, and a new server is started.

Martin

[HtV]

Ok Martin, thanks a lot, as I understand it it's a pvrx2 bug and not a mvpmc dongle bug?

[HtV]

............ as I understand it it's a pvrx2 bug and not a mvpmc dongle bug?

Sorry didn't read your post well enough.:o

[HtV]

Thought I'd try it out with the dongle that comes with 1.08, afaIct it does exactly the same. I also tried with gbpvr.exe there the recording does nicely stop ~ 1 min after the mvp is closed down, the moment when the gbpvr.exe is restarted. So that would mean it really is a pvrx2 problem.
One other thing I found out is that pvrx2 doesn't take the ~minute for restarting after the mvp is shutdown. It reacts right away. I now have one server running again and it always reconnects right away even if I reconnect within secs.

cya Hans

[mvallevand]

Thought I'd try it out with the dongle that comes with 1.08, afaIct it does exactly the same. I also tried with gbpvr.exe there the recording does nicely stop ~ 1 min after the mvp is closed down, the moment when the gbpvr.exe is restarted. So that would mean it really is a pvrx2 problem.
One other thing I found out is that pvrx2 doesn't take the ~minute for restarting after the mvp is shutdown. It reacts right away. I now have one server running again and it always reconnects right away even if I reconnect within secs.

cya Hans

Thanks for confirming this and also for the tip on the server. I like to have server side logs and have always been restrarting the service. This will be so much easier.

Martin

[sub]

I don't think this was mentioned before:
I watched livetv through the mvp (pvrx2), when the program was finished I just turned the mvp off (on/off button), I did not quit the livetv, 6 hrs later I saw it was still recording to the temp-rec-dir. Is this supposed to be like this?
This was using the mvpmc dongle however I doubt that that has anything to do with it.

Cya Hans

I've fixed this bug for the next release.