View Issue Details

IDProjectCategoryView StatusLast Update
0000134Cinelerra-GG[All Projects] Bugpublic2019-03-01 03:18
ReporterPierre Assigned Togoodguy  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platformi7-3770k, 32GB(ram), GTX-750TiOSLinux Mint MateOS Version18.3
Product Version 
Target VersionFixed in Version 
Summary0000134: The image (frame) of the "Out point" ( ] ) is not transferred to the Timeline
DescriptionThe image (frame) of the "Out point" ( ] ) is not transferred to the Timeline, this final frame selected in Viewer is always lost in each of the clips transferred to the timeline.
TagsNo tags attached.

Activities

PhyllisSmith

PhyllisSmith

2019-03-01 03:18

manager   ~0001050

I have updated the preliminary manual documentation to incorporate some wording to help avoid future confusion.
PhyllisSmith

PhyllisSmith

2019-02-21 23:14

manager   ~0000963

Editing documentation in an attempt to explain different interpretations.
PhyllisSmith

PhyllisSmith

2019-02-21 00:12

manager   ~0000962

I think we will have to just remember what the brackets / timeline positions represent to each of us. I will notify of potential confusion in Ethe diting section of combined manual based on the above notes.
Pierre

Pierre

2019-02-20 13:32

updater   ~0000959

Unless the system of "in" and "out" markers can become smart enough to know that the "in" mark is always placed before the displayed frame and the "out" mark is always placed after the displayed frame. While taking into account in its calculations whether the "Always show next frame" option is used or not.
Pierre

Pierre

2019-02-20 13:05

updater   ~0000958

That's true,

All the confusion comes from the fact that the Viewer shows frames, while the markers determine spaces (or rather times) that are not visible between frames.

Each frame is delimited by two spaces (one preceding and one following it).

In the same way 10 frames are delimited by eleven spaces, which includes the space before the first frame and the one (the 11th) after the 10th frame.

Simply place the markers after or before the sequences as you watch, depending on whether the "Always show next frame" option is used or not, will always cause it to miss a frames (at the beginning or end of the sequence) once the clip has been transferred to the timeline.

To obtain a clip on the timeline exactly as you saw in the Viewer, you must necessarily move the "in" mark back from the beginning before the first desired frame or move the "out" mark forward after the last desired frame, depending on whether the "Always show next frame" option is used or not.
IgorBeg

IgorBeg

2019-02-20 12:23

reporter   ~0000957

The reference of the markers is in the middle of the icon, as you know.
Please GG don't move from the middle otherwise my markers will no longer work.
Added screenshots of the markers SUV original and Suv-sub1 (mine).

PhyllisSmith

PhyllisSmith

2019-02-19 17:18

manager   ~0000955

That is what confused me too. Especially when the [ and ] markers turn from the color green to the color red. It needs to have better documentation and I am hoping to get back to working on that. But I will inquire to GG about the somewhat misleading markers and the insertion line.
Pierre

Pierre

2019-02-19 17:06

updater   ~0000954

What misleads is the shape of the markers"[" and"]"; they give the false impression of being inclusive, that is, that everything placed in between would be included in the clip transferred to the timeline.

 But that's not true, one of the two markers will not include the frame that was visible at the time the marker was affixed.

Depending on whether the "Always show next frame" option is used or not, it is the "in" or "out" marker that will not be inclusive.
Pierre

Pierre

2019-02-19 16:44

updater   ~0000953

Forget my last message, it's a mistake... Yes, there is a displacement of the "in" marker, but there is no loss of frames. 10 frames are on the timeline.
Pierre

Pierre

2019-02-19 16:32

updater   ~0000952

It is important to add that in my explanation there is really a loss of a frame too.

The "in" mark that I place when I see frame 0 will actually indicate 1 and it is from frame 1 that the clip will be transferred to the time line. There is a loss of 1 frame.

A segment that I identify in the Viewer between frames 00 and 10 (which should represent 10 frames), will give once transferred to the timeline a clip of 9 frames.
PhyllisSmith

PhyllisSmith

2019-02-19 15:49

manager   ~0000951

OK, good. I will close this later today.
I am looking at the other problem of "jog takes 1frame too much to reverse the frame" to see if anything can be done about that.
Pierre

Pierre

2019-02-19 15:08

updater   ~0000950

Okay,

I understand the problem now. I have done tests again, like you, with scrolling timecode segments. I have always made sure to place my "in" and "out" marks without moving the cursor back. I don't check "Always show next frame", but I don't think it changes the result.

The problem I discovered:

If I put "in" and "out" marks on frames 1 and 10, the clip transferred on the timeline will go from frame 1 to frame 10, but in the Viewer, if I click on the "out" mark, it will show me frame 11.

Hence my impression that I was losing a frame when I checked the source of my clips.
Pierre

Pierre

2019-02-19 15:06

updater   ~0000949

Okay,

I understand the problem now. I have done tests again, like you, with scrolling timecode segments. I have always made sure to place my "in" and "out" marks without moving the cursor back. I don't check "Always show next frame", but I don't think it changes the result.

The problem I discovered:

If I put "in" and "out" markers on frames 0000001 and frame 0000010, the clip transferred on the timeline will go from frame 0000001 to frame 0000010, but in the Viewer, if I click on the "out" mark, it will indicate frame 0000011 !!

Hence my impression that I was losing a frame when I checked the source of my clips.
PhyllisSmith

PhyllisSmith

2019-02-19 00:54

manager   ~0000948

It turns after that it is not losing the last frame but is somewhat confusing. In more thorough testing to better show GG that there might be a problem, I think that the fact that it is showing the next frame led to my initial confusion. I use "Always show next frame" set in Settings->Preferences, Appearance tab.

In the demo as referenced next, the frames are numbered 0 to 98. I cut out frames 10-19, 40-49, and 70-79. So the "white" bars in the Inter-View mode are numbered 0-9, 20-39, 50-69, and 80-98.

The demo to show it really is correct is at:
https://streamable.com/ijx3i

The final outcome from the demo is at:
https://streamable.com/ye6wd

The input to create the scenario is at:
https://streamable.com/16puz
PhyllisSmith

PhyllisSmith

2019-02-18 18:04

manager   ~0000941

I demonstrated this to GG as described. He will look at the code in the next couple of days to see what is happening.

Issue History

Date Modified Username Field Change
2019-02-13 16:35 Pierre New Issue
2019-02-18 18:03 PhyllisSmith Assigned To => goodguy
2019-02-18 18:03 PhyllisSmith Status new => assigned
2019-02-18 18:04 PhyllisSmith Status assigned => confirmed
2019-02-18 18:04 PhyllisSmith Note Added: 0000941
2019-02-19 00:54 PhyllisSmith Note Added: 0000948
2019-02-19 15:06 Pierre Note Added: 0000949
2019-02-19 15:08 Pierre Note Added: 0000950
2019-02-19 15:49 PhyllisSmith Note Added: 0000951
2019-02-19 16:32 Pierre Note Added: 0000952
2019-02-19 16:44 Pierre Note Added: 0000953
2019-02-19 17:06 Pierre Note Added: 0000954
2019-02-19 17:18 PhyllisSmith Note Added: 0000955
2019-02-20 12:23 IgorBeg File Added: In-Out-points_SUV-original.png
2019-02-20 12:23 IgorBeg File Added: In-Out-points_SUV-sub1.png
2019-02-20 12:23 IgorBeg Note Added: 0000957
2019-02-20 13:05 Pierre Note Added: 0000958
2019-02-20 13:32 Pierre Note Added: 0000959
2019-02-21 00:12 PhyllisSmith Note Added: 0000962
2019-02-21 23:14 PhyllisSmith Status confirmed => resolved
2019-02-21 23:14 PhyllisSmith Resolution open => no change required
2019-02-21 23:14 PhyllisSmith Note Added: 0000963
2019-03-01 03:18 PhyllisSmith Status resolved => closed
2019-03-01 03:18 PhyllisSmith Note Added: 0001050