Oh, 1-track is much better now that I know the difference. Thank you for the explanation!
On Mon, Feb 22, 2010 at 3:10 PM, Artur Jaroschek <[email protected]> wrote: > This is realy simple. > > 2-track-design: see opensource project "openshot" > > 1-track-design: most professional solutions like "sony vegas" - free > demo version at sony media. > > Here the difference in ACSII: > > 2-tracks: > > track1: XXXXXXXXX---------XXXXXXXXXXXX----- > trans.: --------T---------T'---------T----- > track2: --------YYYYYYYYYYY----------YYYYYY > > where X is a video on track1 and Y is a video-clip on track2 and > T is a transition from track1 to track2 and > T' is a transition from track2 to track1 > -> you have to decide transition direction manually > > > 1-track: > > track: 11111111(12)2222222(23)3333333(34)44444 > > where (N,N+1) is a transition from video-clip N to video clip N+1 > > as you see - less pain - no decision to make on transition-direction as > its implicit > > Artur > > > > > > Am Montag, den 22.02.2010, 11:28 -0500 schrieb Brett Alton: >> For someone who doesn't know single-track versus >> two-track/double-track, can someone please provide screenshots? I >> didn't understand the description... >> >> 2010/2/22 Titcomb, Andrew <[email protected]>: >> > Count this as another vote for the single-track transition design. It makes >> > for a cleaner UI. >> > >> > As well, when multiple video tracks are made available, we can use them for >> > organizational purposes: storing alternate versions of the edit in >> > different >> > tracks. >> > >> > >> > >> > >> > >> > - andrewt >> > >> > ________________________________ >> > >> > From: Dries Desmet [mailto:[email protected]] >> > Sent: Monday, February 22, 2010 7:14 AM >> > To: Artur Jaroschek >> > Cc: [email protected] >> > Subject: Re: [PiTiVi] Transition Thoughts >> > >> > >> > >> > As an editing professional lurking on this list, this 1 track/2 track >> > transition is one part of the design that interests me. My vote goes to >> > single track design for much the same reason that artur is pointing out >> > here. >> > Both avid and fcp have adopted it and the Premiere used to have 2 track >> > transitions but I believe has moved away from that. >> > On avid, it's even possible to collapse 2 layers in a single layer and ad a >> > transition to the newly formed layer. By double clicking the collapsed >> > piece, the orignal 2 get revealed. But this is probably a next stage thing. >> > >> > Regards, >> > >> > Dries Desmet. >> > >> > On 22 February 2010 15:23, Artur Jaroschek <[email protected]> wrote: >> > >> > Hello, >> > >> > are there any blueprints describing the workflow of transitions between >> > different video clips and also between audio clips? >> > >> > I would like to know if you plan to implement transitions using a >> > two-track-design (transistions work between track-A and track-B and the >> > other way round) like many projects do or using a sigle-track design >> > (like SONY Vegas). I'd like to note (working with sony vegas for many >> > years now, since version 4) that a single-track design is much more >> > convenient because: >> > >> > 1. it allows a clean work-flow, i.e. video-tracks are rendered (and >> > overlay each other) from top to bottom. A track-A-B-design breaks this >> > because it must allow to transit from track-B (bottom) to track-A >> > (top). >> > >> > 2. it allows a "build-in" default transition just by overlapping the >> > ending of clip-1 with the beginning of clip-2 (sound and video of >> > course) (see sony vegas). >> > >> > 3. it allows to preconfigure a default transitions overlapping time >> > which is applied when multiple clips are dragged from the import area >> > into the timeline. All dragged clips are then automatically overlapped >> > by this time. Great for dragging a bunch of photos into the timeline to >> > render them as a video with background music. (Of course one then needs >> > the default photo-length-time also in the preferences). >> > >> > I would realy like to see pitivi to support this mode. Sony Vegas has >> > this design since the beginning (at least version 4 which is 5 years >> > old) and has never changed anything about it - because its perfect. >> > >> > Artur >> > >> > >> > ------------------------------------------------------------------------------ >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > Pitivi-pitivi mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi >> > >> > >> > -- >> > Urga >> > Wollestraat 5 >> > 8790 Waregem >> > www.urga.be >> > >> > ------------------------------------------------------------------------------ >> > Download Intel® Parallel Studio Eval >> > Try the new software tools for yourself. Speed compiling, find bugs >> > proactively, and fine-tune applications for parallel performance. >> > See why Intel Parallel Studio got high marks during beta. >> > http://p.sf.net/sfu/intel-sw-dev >> > _______________________________________________ >> > Pitivi-pitivi mailing list >> > [email protected] >> > https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi >> > >> > > > > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Pitivi-pitivi mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pitivi-pitivi
