[Cin] My current hack on batchrender I/O points .....

[Andrew Randrianasulu]

В сообщении от Wednesday 20 January 2021 11:21:42 Rafa Mar Multimedia en Gnu\Linux via Cin написал(а):
> Yes, I knew about this part of the manual, but I see it as a bug or an
> error that the render takes into account the insertion point (position of
> the playhead).

My point was about setting SELECTION in those projects (possibly by creating
10-20 copies of them with dangerous "Save to EDL path" function).

So, you basically will have 20 little sub-project still around as a batchjob list.
After you load this list you render those fragments ..
Not as neat as your montage (idea) but I wonder if it works currently at all ?

I mean I'm not very sure what selection will be if you say put THREE 
labels without any other indication of desired region ....

But I think testing In-Out points or visual selection now is fastest route ...




> 
> What I mean is an improvement that on the one hand solves the playhead.
> That we do not have to make sure that this is at the beginning to make a
> render, this is really a mistake (bug).
> 
> And in a project to be able to define several non-consecutive sections in
> the same batch render.
> 
> The process would be.
> 1 New
> 2 Use current EDL
> 3 (New button) (Set in out points) or (in out reference)
> The fourth point would be to indicate the name and output format.
> 
> This collects the time code information of the current position of the
> entry exit points.
> If we move these points to another section and repeat the three previous
> steps, new, will always create a new line with ALL (project), this will
> render the whole project, but if we have moved the marks in out, and press
> the "in out reference" button again, ALL will be replaced by the stretch of
> timecode marked by in out points and export only the fragment. When
> executing it, Batch will export all the defined sections while we can be
> having a snack.
> 
> [image: Idea_2.png]
> 
> 
> I am aware that giving ideas is the easy part of the job... if I had the
> knowledge that you have in C programming it would help you, but in this
> sense I am stupid and useless... I can only try, sorry. Don't feel
> obligated to do this either. The only thing I see as an error is that the
> render takes into account the the position of the play head (the Insert
> Point position as the manual calls it)
> 
> Imagine that you have to do a batch render of 20 projects... and you have
> to open one by one to ensure that the playhead is at the beginning... it is
> not very logical... a batch is made with the editor without any project
> loaded, most of the time, and this detail of the play head wastes a lot of
> time without any logic that justifies it, being able to use the entry and
> exit points (in out points) for it
> 
> My sincere thanks.
> 
> El mié, 20 ene 2021 a las 7:46, Andrew Randrianasulu via Cin (<
> cin at lists.cinelerra-gg.org>) escribió:
> 
> > В сообщении от Wednesday 20 January 2021 09:38:26 Rafa Mar Multimedia en
> > Gnu\Linux via Cin написал(а):
> > > Thank you very much Andrew.
> > > I think that initially it would be sufficient that the render will ignore
> > > the position of the playhead.
> >
> >
> > Currently, Batchrender operation described in pdf as such
> >
> > =====
> >
> > You do not have to render an entire projects. We can limit ourselves to an
> > active
> > region that we can set through a selection in Cut and Paste mode, with
> > labels or
> > In/Out Points. Or the rendering will start from the Insert Point position
> > until the
> > end of the project. Remember: if we want to render the entire project (and
> > not
> > just one active region) it is important to bring the Insertion Point to
> > the beginning
> > of the timeline. This is the only way we are sure to include the whole
> > project.
> >
> > =====
> >
> > try to set 'i/o points' in those batches (before rendering) and see if it
> > works for you already?
> >
> >
> > > The rest ... I'm very sorry to give you so much work with this assistant.
> > > But I'm going to see these changes and I'll tell you.
> > >
> > > El mié, 20 ene 2021 a las 6:49, Andrew Randrianasulu via Cin (<
> > > cin at lists.cinelerra-gg.org>) escribió:
> > >
> > > > It still doesn't work, resize event missing, and probably I must do i/o
> > > > points
> > > > just like labels - per job?
> > > >
> > > >
> > > > Also, interested parties can change BatchRenderJob::get_strategy
> > > >
> > > > for returning RANGE_PROJECT and not RANGE_SELECTION ...
> > > >
> > > > Not sure if we should make this GUI-configurable .....
> > > >
> > > > --
> > > > Cin mailing list
> > > > Cin at lists.cinelerra-gg.org
> > > > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> > > >
> > >
> >
> >
> > --
> > Cin mailing list
> > Cin at lists.cinelerra-gg.org
> > https://lists.cinelerra-gg.org/mailman/listinfo/cin
> >
>