Exchange of work messages with peer review

[a] In this video we will see an example of how work messages are exchanged [b] between a project manager and a task assignee in Cerebro [c]and how the built-in Mirada utility is used [d]as a tool to create an audiovisual peer review.[e]

By default, tasks in Cerebro are created [f] with a “No Status” setting, which should be changed [g] to “Ready to Start” before getting started, [h] something that can be done manually, [i] for example, by the project manager. [j]

Once this happens, Cerebro sends a message notifying [k] the task assignee that he can get started and clearly [l] signals to him that the task status has changed.[m]

The assignee accesses the task, for example, through his personal [n] task list in the “To Do List” window. [o] He sees the forum, learns about the assigned task, and [p] having understood what needs to be done, closes Cerebro and [q] gets started on the assignment.[r]

Next time he will need Cerebro is to create [s] a report after he completes the assignment.[t]

~

To do this, the assignee launches Cerebro, finds his task, [u] and writes a new message, such as “Report,” in its forum.[v]

Like any message, the report includes text and [w] one or more attached files. [x] In addition, it has to include the number of hours worked, [y] which will make it possible to collect statistics [z] on projects/tasks and assignees. [a] Before sending the message, the task’s status should be [b] switched to “Pending Review.” This will signal to the project manager [c] that the assignment has been completed and is awaiting peer review.[d]

Then, the project manager receives a notification about the new message, [e] sees the task’s new status, [f] logs into the forum, and reads the assignee’s report.[g]

~

Of course, a peer review about the completed assignment [h] can be written as a text message in the Cerebro forum [i] (the message type is “Review”).[j] However, a more convenient way when annotating media files [k] in supported formats is to use the Mirada utility [l] as an annotation tool.[m]

First, Mirada is used as a media file player.[n] A file can be opened either by double-clicking on it [o] or by clicking on the Mirada pop-up button.[p]

A Mirada program window appears, [q] where we can see video playing tools [r] on the control panel at the bottom.[s] A timeline with the downloaded file is displayed here as well.[t] The mouse can be used to zoom in and out of the timeline [u] and to move it with the middle button.[v]

The project manager clicks on the play button [w] and evaluates the completed assignment.[x]

When a specific shot needs to be viewed, the timeline should be zoomed [y] in to the level where separate shots can be seen.[z] Then, the mouse or the control buttons for moving between shots [a] can be used to get to the desired part of the video.[b]

~

Once the desired shot is reached, [c] the view can be zoomed in with the mouse scroll wheel.[d] Clicking and holding the middle button will switch to the panoramic view.[e]

First, the project manager creates just a text comment, [f] where he uses words to describe the shot’s overall problems.[g] He does this by writing his comments in the “New Comment” field [h] and clicking on the publish button.[i]

This is the simplest way of annotation.[j] Such text can be included in all other [k] types of comments, which will be discussed later.[l]

The newly created comment appears on the list of the panel [m] on the right hand side, and a label with its number is reflected in the [n] view window in the upper right corner. Clicking on the label [o] makes the text of the comment visible.[p] Labels in the shots that contain comments [q] are also displayed on the timeline.[r]

~

Next, a “sketch”-type comment will be created, which makes it possible [s] to make visual labels in a shot by using drawing tools.[t] The project manager selects the appropriate tool on the upper [u] Mirada panel and labels the problematic parts of the shot.[v]

~

When drawing a sketch, comment labels can be moved [w] to any part of the view window.[x] A sketch can be assigned a life span, [y] i.e. the number of shots on the timeline, [z] during which the drawings will be displayed.[a]

~

And if the project manager wants to make not a single picture [b] but wants to show the movement of a certain object, [c] for example, flying water drops in the shot, [d] then an onion-skin mode should be used.[e] First, the project manager should move to the first shot [f] of the animation and launch the onion-skin mode via the playback bar.[g]

~

The timeline will reflect a range for the number of shots [h] before and after, where the added drawings will be displayed.[i] The project manager draws the original layout of the objects in the initial shot, [j] then draws the second layout in the second shot, and so forth.[k] He creates a series of drawings.[l] If the onion-skin mode is turned off, an animated depiction [m] of objects in drawings in one comment is created.[n]

~

Video annotation makes it possible to include comments [o] not only about a separate shot, but also about [p] the image dynamics when the video is played.[q] The project manager selects a looping range [r] within the video, which he has comments about.[s]

~

Here the project manager comments on the dynamics [t] and records the video comment.[u] He uses the mouse to zoom in on the desired area.[v]

~

As he makes his comments into the mike, [w] he uses the mouse for pointing.[x] A video can be paused during the recording [y] and a marker can be used to add notes to the shot.[z]

~

A fourth comment has been added, it has its own [a] timeline and its recording can be played – [b] all the performed actions will be repeated [c] in synchronization with the recorded voice.[d]

As a result, a completed peer review includes four comments of different types:[e]

  • Text; [f]
  • Sketch – one picture and animation with several frames; [g]
  • Видеокомментарий.[h]

Please note that a task’s status is changed within [i] the Mirada utility itself before a peer review is published.[j]

~

When the project manager logs out of the program, [k] his comments are sent to Cerebro.[l] The task’s status is lowered as the task [m] is sent to the assignee for rework.[n]

~

Then the task assignee logs into Cerebro again because he has received [o] an email notifying him that a peer review had been published in the forum.[p]

The unread task is highlighted in bold in the “To Do List”.[q] The assignee can either click on the light bulb [r] on the tool panel to be redirected automatically [s] or click on the highlighted task in the list.[t] The project manager’s message with a peer review [u] is displayed in the task’s forum.[v] The assignee double-clicks on it [w] to open and reads the comment inside.[x]

~

The next comment can be accessed by clicking on the button [y] above the timeline or by selecting the comment from the list.[z]

~

~

In this case, two comments are displayed in one shot [a] but the drawings are visible only [b] for the comment that is active.[c] The other comment can be activated by selecting it from the list on [d] the right hand side or right from the view window by clicking on the label [e] for the desired comment. In the latter case, [f] the comment’s text along with the answers will appear next to the label.[g]

Next comment in the list is the comment with animation in drawings, [h] demonstrating the correct trajectory of the objects in the scene.[i]

Next in line is the video comment. The assignee plays it [j] and watches the comments on the dynamics.[k]

Having read all the comments, the assignee [l] is ready to get started on the revision.[m]

Before logging out of Mirada, he switches the status to “In Progress”. [n] As a result, Cerebro doesn’t create a new message [o] with a file and just changes the task’s status.[p]

Having worked on the project manager’s comments, [q] the assignee is ready to publish a new version of the file.[r] He logs into Cerebro and replies to the previous message [s] with a report, attaching the new file.[t] He again specifies the time spent on the assignment [u] and switches the task’s status to “Pending review”.[v]

~

Then, the project manager receives a notification about [w] a new report and sees the task’s status in the “Inbox” list.[x]

Now he wants not just to open the new file [y] but to compare it to the previous version.[z] This can be done by displaying the list of the task’s file attachments, [a] selecting the two versions from the list for comparison, [b] and clicking on the “Compare the Selected Files” button.[c]

This launches the Mirada utility, which now has a timeline [d] with two versions of the video at the same time.[e] By default, when the comparison button is off, [f] the view window displays only a shot from the “A” version – [g] this is the main play mode.[h]

In addition, the option to compare two images can be turned on.[i] Comparison is available for two versions, “A” and “B,” [j] of a media file and for shots within the same version. [k] In the latter case, the marker on the timeline is used.[l]

In both cases, there are three ways to compare images:[m]

  • horizontal layout of shots;[n]
  • vertical layout of shots;[o]
  • comparison in the “wipe” mode where shots are superimposed [p] on each other and a vertical “wipe” appears in the view window. [q] Moving the “wipe” with the mouse, a pixel level [r] comparison of images can be performed.[s]

Having compared the new version of the video with the previous one, [t] the project manager decides that the task is executed well [u] and therefore just closes Mirada without sending [v] new comments to Cerebro.[w]

To finish the assignment, he just writes a text message, [x] such as “Review”, where he moves the task [y] to the final status by marking it as “Completed”.[z]