Michael Riepe wrote:
> You can use the mouse wheel (inside the linear slider) to do that. Or
> the scrolling zone on your touchpad, in case you use a notebook. Works
> perfectly on my Thinkpad T60, for example. Since that also has a nice
> hi-resolution display, I actually prefer it for cutting.
>
> Depending on the Shift/Ctrl/Alt keys, a single click of my wheel moves
> by approximately 1 minute (normal), 1 second (+shift), 1 frame (+ctrl)
> or 10 minutes (+alt). You can use other values, however; just change
> them in the configuration file. All values are in units of frames; e.g.
> 1 second corresponds to 25 or 30 frames, depending on whether you use
> PAL or NTSC.
Nice. although I still reckon some kb only jumps would be faster in how
I use it.
> BTW: I guess we need to update the documentation :-(
I think you just did ;)
>> While broadcasters like to not stick to their timing, I do find some
>> amount of shows with a 8|3.5|8|3.5|8 etc. minute structure, at least in .au
>>
>> I would propose some buttons to do direct skip of certain time amounts.
>
> I think that might be too many buttons. Plus, you need to navigate the
> cursor too much when you use buttons. Using the scrolling wheel is much
> more practical.
when you have one. I hadn't thought to put the mouse over the slider
bars - could scrolling wheel also work when hovering over the video
frame and/or the most of the rest of the UI ?
and frame by frame when over the frame indicator, minutes while hovering
over the :mm: part of the time etc ?
>> Even if there was no clickables, it could be a good use of the keyboard,
>> perhaps borrowing key bindings similar to mplayer:
>> right/left arrow = +/- 30 seconds
>> ctrl-right/left arrow = +/- 3.5 minutes
>> [/] = frame step fwd/back
>> {/} = back to I frame / forward to next B frame after an I or P {ie so
>> no frame recoding necessary.
>
> Maybe I can add keyboard shortcuts that work as replacements for the
> mouse wheel (in case there is none). I'm not sure if left/right arrow
> isn't already taken by the GUI, however.
up and down move through the marked frames, but let/rght don't seem to
do anything at the moment.
>> Additionally, I have been unable to work out the difference or use of
>> the pair of frame indication |go|time, although I notice the frame type
>> and * {which is visible until the last frame} - is that still work in
>> progress ?
>
> "*" indicates that the frame will be exported, according to the current
> cut list. The time and frame number on the right refer to the exported
> file, the ones on the left refer to the original file.
Maybe some text labels of original position, exported position - I get
it now - I just needed to add multipe start|stop pairs - now it makes sense.
DaveT.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
DVBCUT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dvbcut-user
