bugAdvene - Bugs: bug #16163, Shot validation GUI

 
 
Show feedback again

You are not allowed to post comments on this tracker with your current authentification level.

bug #16163: Shot validation GUI

Submitted by:  None
Submitted on:  Mon 14 Jun 2010 02:23:00 PM UTC  
 
Category: GUI (general)Severity: 3 - Normal
Priority: 5 - NormalStatus: None
Assigned to: NoneOriginator Email: -unavailable-
Open/Closed: OpenRelease: None
Operating System: None

Tue 22 Jun 2010 02:27:05 PM UTC, comment #5:

> > What is displayed is not the shot number, it is the
> > annotation content. It so happens that you always test with
> > shot numbers as contents, but any content is possible.
> > Automatic renumbering could be possible, but is not specific
> > to this view: it should be a generic behaviour for specific
> > types.

> Well, it happens that the name of the GUI is "Shot validation
> view", and its goal mainly is to validate shots. So I think
> that for the sake of simplicity we should stick to a GUI
> dedicated to shot validation (hence numbered).

> If we have to consider others types of annotations, then it
> should be annotations that cover the whole movie by
> definition. For the moment being, I have no other example of
> such coverage besides shots.

> If the GUI is to be used to validate/modify annotation
> boundaries, then it should present the two boundaries (begin
> ad end), and be annotation-centered (maybe a pretty much
> similar GUI, but not that one).

Ok, I guess I did not exactly respond to what you said, I reacted to the global GUI : the name to invoke the validation GUI should be "Validate shots" and not a general "validate annotations" and it should not be proposed for any annotation type.

It brings us back to the notion of constraints for annotation types (eg. pavement constraint), which is coherent with the Advene2 model if I am not mistaken.

Regarding renumbering of shots, I guess that as any cut validation instantly modifies the annotation boundaries (?), it should be possible also to modify annotations contents (or we should really define calculated attributes, accessible from calculation, such as /number in UML).

Y.

Yannick Prié <yprie>
Project Member
Tue 22 Jun 2010 02:06:26 PM UTC, comment #4:

> Implemented, except for the following.
>
> >- for each image, present the number of the shot it belongs > to (for instance
> > after the timecode : "00:00:37.290 (#13)"
> > - takes too much space for a very small benefit. WNI.
> > I disagree. You should give it a try, but on a second line).
> > 00:00:37.290
> > (#13)

> Too much work (specialisation of a generic component) given the necessity. Postponed.

ok.

> > Shots still do not appear sufficiently as such, individually.
> > The idea is to see shot 13 and to see shot 14.

> Note that the background color is already different.

Yes, but since there are numerous mentions of shots as #13 and #14 in the GUI, it seems necessary to give a direct visual cue about what is #13 and what is #14 (redundancy).

> > Shot number is not just another attribute that belongs to the
> > content of an annotation. Its very nature is to be a
> > calculated attribute.

> What is displayed is not the shot number, it is the
> annotation content. It so happens that you always test with
> shot numbers as contents, but any content is possible.
> Automatic renumbering could be possible, but is not specific
> to this view: it should be a generic behaviour for specific
> types.

Well, it happens that the name of the GUI is "Shot validation view", and its goal mainly is to validate shots. So I think that for the sake of simplicity we should stick to a GUI dedicated to shot validation (hence numbered).

If we have to consider others types of annotations, then it should be annotations that cover the whole movie by definition. For the moment being, I have no other example of such coverage besides shots.

If the GUI is to be used to validate/modify annotation boundaries, then it should present the two boundaries (begin ad end), and be annotation-centered (maybe a pretty much similar GUI, but not that one).

Y.

Yannick Prié <yprie>
Project Member
Tue 22 Jun 2010 01:49:37 PM UTC, comment #3:

Implemented, except for the following.

>- for each image, present the number of the shot it belongs to > (for instance
> after the timecode : "00:00:37.290 (#13)"
> -> takes too much space for a very small benefit. WNI.
> I disagree. You should give it a try, but on a second line).
> 00:00:37.290
> (#13)

Too much work (specialisation of a generic component) given the necessity. Postponed.

> Shots still do not appear sufficiently as such, individually. > The idea is to see shot 13 and to see shot 14.

Note that the background color is already different.

> Shot number is not just another attribute that belongs to the
> content of an annotation. Its very nature is to be a
> calculated attribute.

What is displayed is not the shot number, it is the annotation content. It so happens that you always test with shot numbers as contents, but any content is possible.
Automatic renumbering could be possible, but is not specific to this view: it should be a generic behaviour for specific types.

Olivier Aubert <oaubert>
Project Administrator
Sun 20 Jun 2010 08:49:03 AM UTC, comment #2:

Thanks for the modifications!

- for each image, present the number of the shot it belongs to (for instance
after the timecode : "00:00:37.290 (#13)"
-> takes too much space for a very small benefit. WNI.

I disagree. You should give it a try, but on a second line).

00:00:37.290
(#13)

Shots still do not appear sufficiently as such, individually. The idea is to see shot 13 and to see shot 14.

- add a red vertical line to highlight the cut
-> done

- rename arrows with "Next cut", "Previous cut".
-> done

- add buttons for either Validating or Merging (just clicking on an image is
a good shortcut, but is not very self-explainable)
-> not convenient. An instructional text has been added.

Rather add "click on a frame after the cut" or something like that : there are no timecodes in that GUI, just cuts, shots, frames).

- notify user of each action he has made, something like "Validated cut
#13-#14", "Merged shots #13-#14 to new shot #13"
-> done

rather use "Changed the cut #13-#14" if there is a change.

- allow undo and notify undo
-> done

Cool.

- the search form could be transformed to 2 forms, one for searching shot
ends, the other for searching shot beginnings.
-> not convenient: it adds another option with little or not benefit at all.
WNI.

+ automatically renumber shots, to avoid texts like "Beginning of #2 (title:
4).
-> risk of disorientation. It is good to keep some stable reference.

It is when I see #2 and 4 that disorientation begins. Best thing could be to just use the numbers.

Shot number is not just another attribute that belongs to the content of an annotation. Its very nature is to be a calculated attribute.

Also
- I tfound how to get the interface self-explainable: just add a vertical line before the frame under the mouse cursor : it will manifest the result of the action: "if I click, then the cut will be there"
- the huge "refresh" button is just not a good idea. A normal button will do the trick, with label "refresh frames"

Y.

Yannick Prié <yprie>
Project Member
Thu 17 Jun 2010 12:41:14 PM UTC, comment #1:

Mostly implemented:

- for each image, present the number of the shot it belongs to (for instance after the timecode : "00:00:37.290 (#13)"
-> takes too much space for a very small benefit. WNI.

- add a red vertical line to highlight the cut
-> done

- rename arrows with "Next cut", "Previous cut".
-> done

- add buttons for either Validating or Merging (just clicking on an image is a good shortcut, but is not very self-explainable)
-> not convenient. An instructional text has been added.

- notify user of each action he has made, something like "Validated cut #13-#14", "Merged shots #13-#14 to new shot #13"
-> done

- allow undo and notify undo
-> done

- the search form could be transformed to 2 forms, one for searching shot ends, the other for searching shot beginnings.
-> not convenient: it adds another option with little or not benefit at all. WNI.

+ automatically renumber shots, to avoid texts like "Beginning of #2 (title: 4).
-> risk of disorientation. It is good to keep some stable reference.

Olivier Aubert <oaubert>
Project Administrator
Mon 14 Jun 2010 02:23:00 PM UTC, original submission:

I definitely think that what is presented is not a shot, but a shot cut, that should be presented as such :
- for each image, present the number of the shot it belongs to (for instance after the timecode : "00:00:37.290 (#13)"
- add a red vertical line to highlight the cut
- rename arrows with "Next cut", "Previous cut".
- add buttons for either Validating or Merging (just clicking on an image is a good shortcut, but is not very self-explainable)
- notify user of each action he has made, something like "Validated cut #13-#14", "Merged shots #13-#14 to new shot #13"
- allow undo and notify undo
- the search form could be transformed to 2 forms, one for searching shot ends, the other for searching shot beginnings.

+ automatically renumber shots, to avoid texts like "Beginning of #2 (title: 4).

Anonymous

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by yprie (Posted a comment)
  • -unavailable- added by oaubert (Posted a comment)
  • -unavailable- added by None (Submitted the item)
  •  

    Please enter the title of George Orwell's famous dystopian book (it's a date):

     

     

    Follow 4 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Tue 22 Jun 2010 02:06:26 PM UTCyprieStatusFixed=>None
    Tue 22 Jun 2010 01:49:37 PM UTCoaubertStatusNone=>Fixed
    Sun 20 Jun 2010 08:49:03 AM UTCyprieOpen/ClosedClosed=>Open
    Thu 17 Jun 2010 12:41:14 PM UTCoaubertOpen/ClosedOpen=>Closed
    Show feedback again

    Back to the top


    Powered by Savane 3.1-cleanup