Hello David,

many thanks for your mail.

David Coe schrieb:

>> - The content of the video window is not constantly refreshed. Only if
>>    redrawing the window area is necessary for some other reason (i.e.
>>    moving another programs window overlapping to DVBcut), the related
>>    part of the video window is correctly redrawn.
>>    I assume that Windows 7 doesn't get the information that the content
>>    of the DVBcut window needs to be refreshed due to new content of the
>>    Mplayer window within it.
> 
>>    If Aero is activated, screen refresh seems to work significantly
>>    better. Obviously, Aero forces some kind of "continuous screen
>>    refresh" (wasting ressources...).
> 
> Don't see the above.

Interesting - this effect is persistent here.

Maybe you could do a quick check? In the extended system settings, at
visual effects, select "for optimum performance" (that effectively
disables all "advanced" display features). Will the video be shown
correctly and smooth from within DVBcut?

Remark: as soon as I grab the DVBcut window at its title bar (for
example, for moving it on the screen), the video content is correctly
updated during playback (even if I don't move the mouse, just keep the
left mouse button pressed on the DVBcut title bar). Obviously, this is
really something related to refreshing parts of the screen that the OS
is not aware of changed content.

>> - After playback has been started, it cannot be stopped anymore. The
>>    only way to stop it is by closing DVBcut. As above, I assume that the
>>    mouse click on the stop button is not properly transferred to the
>>    MPlayer thread that runs "inside" the DBVcut window.
>>    (Activating Aero doesn't change anything here.)
> 
> However, I have noticed the above non-responsive button behaviour on 
> 64bit Windows 7, coming back recently to a new installation of 
> DVBcut-0.6.0-166 along with Tiesi's current build of 
> Mplayer-rtm-svn-34401. This was only corrected by rolling back to an old 
> copy of Mplayer-rtm-svn-28311.
> 
> I'm not sure quite what this means - perhaps different implementations 
> of the qt3 or qt3-under-qt4 libraries under mingw / mingw64? Ralph has 
> not updated DVBcut for a while so the 166 / 28311 builds come from 
> around the same date.

Well, that was a really good hint. After moving back to 28311,
start/stop works fine again. Many thanks!
Before that, I normally tried newer versions if some functions were
broken - only rarely older versions work better. :-)

Thanks & regards,
Tilmann


------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
DVBCUT-user mailing list
DVBCUT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dvbcut-user

Reply via email to