[Bf-vfx] Bug when using va/b setting in edl file?

Tintwotin tintwotin tintwotin at gmail.com
Tue Nov 18 14:24:00 CET 2014


Oh sorry, 'AA/V' is handled correctly after your resent fix. :-)

2014-11-16 16:56 GMT+01:00 Tintwotin tintwotin <tintwotin at gmail.com>:

> Yet another thought on the EditModes. Apparently CMX 3600 is either 2 or 4
> audio channels. So most of the EditMode variations is caused by defining on
> what channels the audio should be placed.
>
> Since the Blender EDL importer script seems to fill up the clips from
> bellow and up/audio tracks from track 6 and up and do not distinguish
> between stereo/mono, maybe the main thing to parse is if video, audio or
> both should be added from an imported clip. In other words it might be
> simpler to just search for either 'v', 'a' or 'v'+'a' in the editmode
> string and add video, audio or both accordingly? The alternative is to add
> all the variations to the dict...
> (A python script to parse native Lightworks files ed5 to edl or mlt (for
> Shotcut): http://users.mur.at/ms/projects/lightworks_re/ed5decode.py -
> Some more audio editmodes can be seen here - but only for two channels).
>
> For me, right now, is the most crucial 'AA/V', because then I would only
> need to make one type of output from my script, if the resulting EDL should
> be parsed by both Blender and Lightworks (would like to research a bit at
> some point on the EDLs used by Resolve, but I hope they're similar to
> Lwks).
>
> Btw. I found out that Lightworks is very picky on the number of characters
> for each column ex. number (3 chr)+2 space+reel name (8 chr)+ 1 space+ etc.
> I guess that is a way to read reel names containing spaces. Odd thing is
> that if BL is used then there are 4 spaces between the number and the BL.
>
>
> 2014-11-16 0:48 GMT+01:00 Tintwotin tintwotin <tintwotin at gmail.com>:
>
>> Oh, great! Thanks for pushing the fix.
>>
>> The trouble with the EDL format is that it was invented for the analog
>> age. I mean for cutting negatives in the film lab or onlining tapes. And
>> ever since films where edited on computers the format has been altered to
>> fit that purpose instead making a mess of things...
>>
>> I found a bit more on the format (and the format differences) here (but
>> still old 1995!): http://www.edlmax.com/edlmaxhelp/edl/maxguide.html
>> And another EDL specification here: http://edl2aaf.sourceforge.net/
>> This one includes even more EditModes: {NONE, A, B, V, A2, A2\V, AA, AA\V}
>>
>> On a different note - using clip/file names specified in comments instead
>> of using reel name:
>> In order to solve the problems with file name vs. reel name and the
>> length limitation of the reel name a workaround has been added to the EDL
>> comments as described here (FCP7 manual):
>> https://documentation.apple.com/en/finalcutpro/usermanual/index.html#chapter=96%26section=3%26tasks=true
>>
>> "How Clips from an EDL Are Named:
>> Clips imported from an EDL are named in one of two ways. If the EDL was
>> exported from a nonlinear system, the name is exported like this:
>> * FROM CLIP NAME: CLIP NAME HERE
>> where CLIP NAME HERE is the name of your clip. Final Cut Pro can
>> recognize clip names exported from the following nonlinear editing systems:
>> Final Cut Pro, Media 100, and Avid. In all other cases, Final Cut Pro uses
>> the reel name as the clip name."
>>
>> Using comments to specify file names has become a standard, however I've
>> seen edl files where the clip name had a file extension and even some with
>> the full file path specified too. I've also seen some with the clip name
>> specified in a comment line but saying * COMMENT: instead of * FROM CLIP
>> NAME:
>>
>> Anyway, thanks for pushing that fix.
>>
>>
>>
>>
>> 2014-11-15 23:38 GMT+01:00 Campbell Barton <ideasman42 at gmail.com>:
>> >
>> > Your right, this was a bug in the importer,
>> > pushed fix
>> https://developer.blender.org/rBA0a853ec83c64764d3d14cc0bdface353420934aa
>> >
>> > The other changes you mention may be OK, but not sure which EDL spec
>> > they're from.
>> > the CMX spec doesn't seem to contain them (though its scanned images
>> > so I couldn't search)
>> > http://xmil.biz/EDL-X/CMX3600.pdf
>> >
>> > While writing the importer it became clear this format is very loosely
>> > defined, it maybe OK to extend support, but like to include a
>> > reference to the spec in the commit, and that its compatible with
>> > existing CMX EDL files.
>> >
>> > On Sat, Nov 15, 2014 at 11:32 PM, Tintwotin tintwotin
>> > <tintwotin at gmail.com> wrote:
>> > > Another thing, but still related, I found some missing <EditMode>
>> settings
>> > > in the Blender EDL import script used by ex. Lightworks, Sony Vegas
>> a. o.
>> > >
>> > > Ex. edl from Lightworks:
>> > > 001  IBM      AA/V C         00:00:05:02 00:00:12:17 00:00:05:01
>> 00:00:12:16
>> > >
>> > > It's the 'AA/V' setting which is currently not supported by the
>> Blender edl
>> > > import script. In this link a few more settings not used by the
>> Blender edl
>> > > import script can be found:
>> http://www.niwa.nu/2013/05/how-to-read-an-edl/
>> > >
>> > > Info from that page:
>> > > AA/V – Video and audio on channel 1 and 2
>> > > VA1A2 – Video and audio on channel 1 and 2
>> > > A12V – Video and audio on channel 1 and 2
>> > > AUD3 – Audio only on channel 3
>> > > A3 – Audio only on channel 3
>> > >
>> > > In line 225 of  io_sequencer_edl/parse_edl.py they can be easily be
>> added:
>> > > EDIT_DICT = {
>> > >     "none": 0,  # TODO, investigate this more.
>> > >     "v": EDIT_VIDEO,
>> > >     "a": EDIT_AUDIO,
>> > >     "aud3": EDIT_AUDIO,
>> > >     "a3": EDIT_AUDIO,
>> > >     "aa": EDIT_AUDIO_STEREO,
>> > >     "va": EDIT_VIDEO_AUDIO,
>> > >     "aa/v": EDIT_VIDEO_AUDIO,
>> > >     "va1a2": EDIT_VIDEO_AUDIO,
>> > >     "a12v": EDIT_VIDEO_AUDIO,
>> > >     "b": EDIT_VIDEO_AUDIO,
>> > >     }
>> > >
>> > > And just to clarify where the fix from previous post could be added:
>> > > When the VA/va/B/b settings are used, adding a video clip too can be
>> done
>> > > very simple with the stuff added in here in line 173 of
>> > > io_sequencer_edl/import_edl.py:
>> > > if edit.edit_type & (parse_edl.EDIT_VIDEO |
>> parse_edl.EDIT_VIDEO_AUDIO):
>> > >
>> > > BTW. the reason I've come across these things is because I'm working
>> on a
>> > > mlt to blender friendly edl script:
>> > > http://eyeframeconverter.wordpress.com/mlt2edl/
>> > >
>> > > 2014-11-14 19:46 GMT+01:00 Tintwotin tintwotin <tintwotin at gmail.com>:
>> > >>
>> > >> ideasman42 suggested that I posted here about this:
>> > >>
>> > >> Background:
>> > >> I'm using the EDL notes from the Blender import_edl.py script in
>> order to
>> > >> code a python script to convert ShotCut.org MLT files into Blender
>> friendly
>> > >> EDLs:
>> > >>
>> > >> The Blender EDL notes:
>> > >>>
>> > >>> * <EditMode>: 'V' | 'A' | 'VA' | 'B' | 'v' | 'a' | 'va' | 'b' which
>> > >>> equals Video, Audio, Video_Audio edits (note B or b can be used in
>> place of
>> > >>> VA or va).
>> > >>
>> > >>
>> > >> Bug?
>> > >> That's how I noticed that when VA/va/B/b settings (which equals
>> > >> Video+Audio) are used, only an audio clip is added to the time line,
>> and no
>> > >> video. With va I suppose that both a video and an audio clip should
>> be
>> > >> inserted?
>> > >>
>> > >> How to reproduce:
>> > >> Open this EDL example, and assign a video clip with audio. It must be
>> > >> longer than 30 sec.
>> > >>
>> > >>> * EDL example:
>> > >>> 1 test va C 00:00:00:00 00:00:30:00 00:00:00:00 00:00:30:00
>> > >>
>> > >>
>> > >> How to fix:
>> > >> When the VA/va/B/b settings are used, adding a video clip too, can
>> be done
>> > >> very simple with the stuff I added in bold here in line 173:
>> > >>
>> > >>> Code:
>> > >>> if edit.edit_type & (parse_edl.EDIT_VIDEO |
>> parse_edl.EDIT_VIDEO_AUDIO):
>> > >>
>> > >>
>> > >> This way a video clip is added too, when va/b setting is used.
>> > >>
>> > >> Is it a bug or expected behavior?
>> > >> So the question is if using the va/b setting should add both a video
>> clip
>> > >> and an audio clip, or is the current behavior what is to be expected?
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > Bf-vfx mailing list
>> > > Bf-vfx at blender.org
>> > > http://lists.blender.org/mailman/listinfo/bf-vfx
>> > >
>> >
>> >
>> >
>> > --
>> > - Campbell
>> > _______________________________________________
>> > Bf-vfx mailing list
>> > Bf-vfx at blender.org
>> > http://lists.blender.org/mailman/listinfo/bf-vfx
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-vfx/attachments/20141118/cae83db7/attachment.htm 


More information about the Bf-vfx mailing list