Film and 24p

Error message shows during play back of time line.

ritam_bhatta — Tue, 17 Nov 2009 12:40:00 GMT

i m doing a 35mm cinemascope film in avid xpress pro 4.6 sw with analog mojo . i have problem during play back of my time line error is :

EXCEPTION : PMM_ INSUFICIANT_MEDIA

wwt should i do to over come with this problem guide me plz.

Aaton Cantar "TRK" Info Missing After BWF Import

mschneider — Mon, 09 Nov 2009 16:59:01 GMT

Hi all:

A scripted episodic show here at PostWorks will be recording on an Aaton Cantar and post-sync'ing BWF audio in Media Composer 3.5.x. The Track ID/Track info metadata - boom, iso, etc - is key for smooth audio post when it comes time to turning over sound. That TRK information is now missing when importing BWF audio into Composer versions 3.5.x, 4.0, and a beta version of 4.0.x. I am trying 3.1.x now.

Three 3rd party softwares *do* however see this metadata: Wave Agent, BWF Widget Pro, AV Transfer, so the data is there. However I noticed that the Track ID is not written in its usually place (from the vantage point of BWF Widget Pro's metadata editor). If I manually key in the track ID where it is typically found within a metadata editor, Media Composer *does* see it.

So, could be Composer looking in the wrong place, could be issue with the firmware version of the Cantar. I have been in touch with some film assistants here who have had positive experiences with 2.20 firmware of the Cantar eliminating this problem (or simply not manifesting it).

Ring any bells for anyone (beyond those I have already spoken with)?

Matt Schneider, PostWorks

Updating clip's informations

Thad_b — Mon, 12 May 2008 17:31:48 GMT

Hello,

I've noticed that when you modify a clip's information (for example to change its color) you must open every bins where there are copies or sequences containing that clip and then save all bins, if you want this new information to be permanent.

Which seems to be quite simple for a few clips, tends to become a nightmare if you're in a middle of a project with thousands bins and sequences, and want to modify a large numbers of clips.

Michael : how (and where) are stored clip's informations (in bins and sequences) ? Is it possible to update a clip's information without opening all bins related to it ?

My understanding is that there is a save at bin level but not at an upper level (let's say at a project level) which could guaranteed that a modification on a clip goes back to copies and sequences located in other bins (when closed or when opened later).

Best regards,

Thaddée

Clip colour metadata will not hold, will not go away!

mark.burton — Mon, 16 Nov 2009 18:23:00 GMT

We are a long way into a project and have decided we want to colour all SFX orange. Previosly the SFX clips had no colour at all. However even if we colour all the SFX orange in their master (and only) bin location, we are finding that when a sequence is opened, the SFX in it will not always take this colour on and opening the SFX bin actually removes the colour from some of the master SFX clips in the bin.

So we gave up and tried to remove all the colouring as it was too sporadic. Now, of course we have some clips that simply will not remove their colour. I remove the colour in the master SFX bin, then someone openes a sequence with that SFX in and it still holds the colour. Opening the SFX bin does the oposite of above and makes the SFX orange again!

This is in a shared storage, 8 MC Nitris setup. In general it seems you just can't mess with clip colour after the SFX has been cut into sequences.

Is this to do with the media database on each drive for each user? Would we have to remove every single one and rebuild each users databases on the 8 machines?

What is the Avid metadata protocol for how this type of change is handled - any way to solve this and get on with either having the colour we want on the clips stay, or be able to permenatly remove a colour and not have to worry it comes back.

Just to be clear, we only have one set of SFX master bins, there are not multiple master copies of the same SFX in the project.

Many thanks
Mark

On the Issue of Sample Rates

olcerel — Sat, 07 Nov 2009 13:32:16 GMT

Project Specs :

PC - MCA ver 3.5.4

24p PAL

Method2, 48kHz Wave

MXF 3:1, PCM

Video is digitized from Digital Betacam, 48k wave files are imported using method 2 and with BOX 1 and BOX 2 set to "OFF" in import options. Video and audio is sunk and spot check throughout the 1 hr long sequence shows they are in sync. Sequence is played with 24 fps play rate and crash recorded on DVD as well as Digital Betacam for sync checking. Usually in the second half of the sequence sync is lost between audio and video. Audio is advanced by 2-3 and in some instances 12 frames. The difference is not gradual but fixed throughout the scenes. Spot check shows they are actually in sync. To analyze this issue, I imported the same wave files in FCP and MC and got the following results.( In MC I used method 2 with both boxes set to "OFF" in import options)

# of Samples Duration (FCP) Duration(MC 24p) Duration (MC 25p) Duration (MC 1080/24p)

Wave001 1455199 30:08 30:08 30:08 30:08

Wave002 7327679 2:32:16 2:32:17 2:32:17 2:32:16

Wave003 15229279 5:17:07 5:17:07 5:17:07 5:17:07

Wave004 7768319 2:41:20 2:41:22 2:41:21 2:41:21

Wave005 13284479 4:36:18 4:36:20 4:36:19 4:36:19

Wave006 13719679 4:45:20 4:45:21 4:45:21 4:45:20

Why is there a discrepancy in duration between MC projects with different frame rates ? Even between 24p PAL and 1080/24p projects ? Could this be a bug and be the cause of the above problem ? Or could the problem be caused by audio not being locked to video during the shoot ? ( I don't have the information on how audio was recorded in the field). If audio wasn't locked to video during the shoot and sample rate for some scenes were slightly less than 48kHz although they were meant to be 48kHz and Avid stamped them as 48k then would audio run slightly faster in the timeline compared to video and cause the delay during those scenes ?Has anyone experienced similar problems ? I'll appreciate any feedback.

Regards,

Oner Olcerel

DPX into Metafuze

nigelgourley — Wed, 11 Nov 2009 18:02:45 GMT

Normal 0 false false false EN-US X-NONE X-NONE MicrosoftInternetExplorer4  /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-qformat:yes; mso-style-parent:""; mso-padding-alt:0cm 5.4pt 0cm 5.4pt; mso-para-margin:0cm; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:"Times New Roman"; mso-fareast-theme-font:minor-fareast; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;}

We want to convert DPX's into MXF for use in symphony but nothing we do makes the process transparent. The Black and white levels are always wrong. We use the 709 LUT's for the source and the destination, but also we tried most other options and nothing makes it work correctly. If we import the DPX's into DS and select the 709 lut then it works correctly.

We have tried everything we can think of, does anyone have any experience of this workflow. Or think metafuze works correctly for this?

Thanks

AWOL audio levels

hellotansy — Tue, 10 Nov 2009 10:05:57 GMT

We're working on a project on two Avids with external mirrored hard drives, and manually transferring bins to consolidate sequences and stuff.

All the sequence settings seem to transfer seamlessly, except for some audio data - particularly audio levels. They appear to be the same on the timeline (ie the sample gain line is in the same place) but they do not play the same (all audio clips play at the same - earsplitting level).

Even more worryingly, some clips seem to be being slipped. The clip appears in the same position on the timeline, but its contents are slipped forwards (and this is reflected in the sample plot, too). Why would this be?

Thankyouuuuuuu

x Tansy

Filmscribe Error - Lengths don't match

steve62179 — Mon, 28 Jul 2008 20:31:10 GMT

Hi all,

A filmscribe question - I was doing a change list between two sequences using FilmScribe v23.8.3 and got an interesting error. It dumped me to the "Serious Program Error" and then said, "Error: Old and New sections should be of equal length, but are not:...this could be the result of incorrect KN values in one of the clips" I went ahead and isolated the shots in question in the 2 sequences. Firstly, it is the same shot, except 26 frames shorter in one of the sequences. Secondly, there are no KN values for either shot (the show is not film, but, HD tape native). And finally, the two shots were hand synced by me using 48fps material that I sped up and then synced with a .wav file from set.

Any thoughts?

match back to seperate production tracks from mixdown production track?

hellotansy — Mon, 09 Nov 2009 11:58:17 GMT

i have production sound tracks that were given to me as BWFs, which include one stereo mixdown track of multiple mono production tracks.

the film has been cut with the mixdown tracks, but i am now track laying the audio, and would like to use the original mic tracks.

is there an easy way to match back to the multiple tracks from the mixdown track?

or do i have to get back to the bin, find the track i need, note the timecode and splice it in manually?

help much appreciated

x x

Audio drifting in NTSC 23.98 project

lindor — Fri, 06 Nov 2009 15:45:21 GMT

Hi there,

I am currently working on Avid Adrenaline MC 3.1.3 on Mac.

Project is NTSC 23.98 35mm 3 perf

MXF picture files

OMF audio files (WAV)

The client want the audio recorded and imported as 48khz, 24 bit WAV files.

Today I discovered that on all my takes longer than a minute the audio is drifting out of sync, however it is drifting earlier NOT later which would be expected.

On a 2.39min clip at approx 2.22mins the audio is early by 4 frames.

I have tried restamping the audio in it's native state to 48.048 but it makes no difference, and I have also tried importing via later software (3.5.4) but still no difference.

If anyone has an inkling whatsoever as to why this is happening I would be very grateful for some advice.

Many thanks

FilmScribe v 25.0.4

popicutter — Thu, 05 Nov 2009 04:10:28 GMT

Working in FilmScribe v 25.0.4 and using sequences from MC 3.5.4.

System: MacPro 2 x 3 Ghz Quard-Core Intel Xeon, 4 GB ram, running OS 10.5.7

What do we do to fix this?

Change list won't preview. When I click preview button I get error message: "The Cut List template contains an error which was discovered while generating the Change List at event 1.
See the console for additional information.
The template variable vKeyNmbrEndB is not defined for the current event."

The console contents are:

SAsequencePoint_c::New(1184) : 0x1b02ed44
SAmobPoint_c::New(0x1ad84cd4, 1171) : 0x1b02ed84
SAmobPoint_c::New(0x1ad84cd4, 1250) : 0x1b02edd4
SAmobPoint_c::New(0x1ad84cd4, 0) : 0x1b02ee24
SAmobPoint_c::New(0x1ad84cd4, 3431) : 0x1b02ee74
SAsourceList_c::AddSource(“ 1B”)
SAmobSource_c::New(0x1ad84cd4, 1, 1) : “ 1B”
SAsequencePoint_c::New(1312) : 0x1b02eef4
SAsequencePoint_c::New(1264) : 0x1b02ef54
SAmobPoint_c::New(0x1ad84bc4, 1826) : 0x1b02ef94
SAmobPoint_c::New(0x1ad84bc4, 1874) : 0x1b02efe4
SAmobPoint_c::New(0x1ad84bc4, 0) : 0x1b02f034
SAmobPoint_c::New(0x1ad84bc4, 3377) : 0x1b02f084
SAsourceList_c::AddSource(“ 1D”)
SAmobSource_c::New(0x1ad84bc4, 1, 1) : “ 1D”
SAsequencePoint_c::New(1405) : 0x36d8d94
SAsequencePoint_c::New(1313) : 0x36d8df4
SAmobPoint_c::New(0x1ad78404, 5096) : 0x36d8e34
SAmobPoint_c::New(0x1ad78404, 5188) : 0x1b02f0d4
SAmobPoint_c::New(0x1ad78404, 0) : 0x1b02f124
SAmobPoint_c::New(0x1ad78404, 7055) : 0x1b02f174
SAsourceList_c::AddSource(“ 1F”)
SAmobSource_c::New(0x1ad78404, 1, 1) : “ 1F”
SAsequencePoint_c::New(1685) : 0x1b02f384
SAsequencePoint_c::New(1406) : 0x1b02f1c4
SAmobPoint_c::New(0x1ad84bc4, 2089) : 0x1b02f404
SAmobPoint_c::New(0x1ad84bc4, 2368) : 0x1b02f454
SAsequencePoint_c::New(1710) : 0x1b02f4d4
SAsequencePoint_c::New(1686) : 0x1b02f534
SAmobPoint_c::New(0x1ad7b1b4, 6710) : 0x1b02f574
SAmobPoint_c::New(0x1ad7b1b4, 6734) : 0x1b02f5c4
SAsequencePoint_c::New(1779) : 0x1b02f644
SAsequencePoint_c::New(1711) : 0x1b02f6a4
SAmobPoint_c::New(0x1ad85004, 2433) : 0x1b02f6e4
SAmobPoint_c::New(0x1ad85004, 2501) : 0x1b02f734
SAsequencePoint_c::New(1847) : 0x1b02f7b4
SAsequencePoint_c::New(1780) : 0x1b02f814
SAmobPoint_c::New(0x1ad85114, 2483) : 0x1b02f854
SAmobPoint_c::New(0x1ad85114, 2550) : 0x1b02f8a4
SAsequencePoint_c::New(1891) : 0x1b02f924
SAsequencePoint_c::New(1848) : 0x1b02f984
SAmobPoint_c::New(0x1ad7d3b4, 1089) : 0x1b02f9c4
SAmobPoint_c::New(0x1ad7d3b4, 1132) : 0x1b02fa14
SAsequencePoint_c::New(1969) : 0x1b02fa94
SAsequencePoint_c::New(1892) : 0x1b02faf4
SAmobPoint_c::New(0x1ad7c094, 5910) : 0x1b02fb34
SAmobPoint_c::New(0x1ad7c094, 5987) : 0x1b02fb84
SAmobPoint_c::New(0x1ad7c094, 0) : 0x1b02fbd4
SAmobPoint_c::New(0x1ad7c094, 7535) : 0x1b02fc24
SAsourceList_c::AddSource(“ 1M”)
SAmobSource_c::New(0x1ad7c094, 1, 1) : “ 1M”
SAsequencePoint_c::New(2529) : 0x1b02fca4
SAsequencePoint_c::New(1970) : 0x1b02fd04
SAmobPoint_c::New(0x1ad7b1b4, 2413) : 0x1b02fd44
SAmobPoint_c::New(0x1ad7b1b4, 2972) : 0x1b02fd94
SAsequencePoint_c::New(2581) : 0x1b02fe14
SAsequencePoint_c::New(2530) : 0x1b02fe74
SAmobPoint_c::New(0x1ad7d3b4, 1413) : 0x1b02feb4
SAmobPoint_c::New(0x1ad7d3b4, 1464) : 0x1b02ff04
SAsequencePoint_c::New(2626) : 0x1b02ff84
SAsequencePoint_c::New(2582) : 0x1b02ffe4
SAmobPoint_c::New(0x1ad78954, 1031) : 0x1b030024
SAmobPoint_c::New(0x1ad78954, 1075) : 0x1b030074
SAmobPoint_c::New(0x1ad78954, 0) : 0x1b0300c4
SAmobPoint_c::New(0x1ad78954, 3295) : 0x1b030114
SAsourceList_c::AddSource(“ 1Q”)
SAmobSource_c::New(0x1ad78954, 1, 1) : “ 1Q”
SAsequencePoint_c::New(2671) : 0x1b030194
SAsequencePoint_c::New(2627) : 0x1b0301f4
SAmobPoint_c::New(0x1ad79724, 1204) : 0x1b030234
SAmobPoint_c::New(0x1ad79724, 1248) : 0x1b030284
SAsequencePoint_c::New(2714) : 0x1b030304
SAsequencePoint_c::New(2672) : 0x1b030364
SAmobPoint_c::New(0x1ad8a0c4, 102) : 0x1b0303a4
SAmobPoint_c::New(0x1ad8a0c4, 144) : 0x1b0303f4
SAsequencePoint_c::New(2789) : 0x1b030474
SAsequencePoint_c::New(2715) : 0x1b0304d4
SAmobPoint_c::New(0x1ad7ae84, 1137) : 0x1b030514
SAmobPoint_c::New(0x1ad7ae84, 1211) : 0x1b030564
SAmobPoint_c::New(0x1ad7ae84, 0) : 0x1b0305b4
SAmobPoint_c::New(0x1ad7ae84, 1887) : 0x1b030604
SAsourceList_c::AddSource(“ 1U”)
SAmobSource_c::New(0x1ad7ae84, 1, 1) : “ 1U”
SAsequencePoint_c::New(2824) : 0x1b030684
SAsequencePoint_c::New(2790) : 0x1b0306e4
SAmobPoint_c::New(0x1ad84cd4, 3316) : 0x1b030724
SAmobPoint_c::New(0x1ad84cd4, 3350) : 0x1b030774
SAsequencePoint_c::New(2830) : 0x1b0307f4
SAsequencePoint_c::New(2825) : 0x1b030854
SAsequencePoint_c::New(0) : 0x1b0308d4
SAsequencePoint_c::New(2830) : 0x1b0309f4
SAsourceList_c::AddSource(“ 1Y”)
SAsequenceSource_c::New(0x1ad8a2e4) : “ 1Y”
SAsequencePoint_c::New(137) : 0x1b030a14
SAsequencePoint_c::New(0) : 0x1b030a34
SAsequencePoint_c::New(351) : 0x1b030ab4
SAsequencePoint_c::New(138) : 0x1b030b14
SAmobPoint_c::New(0x1ad8a1d4, 64) : 0x1b030b54
SAmobPoint_c::New(0x1ad8a1d4, 277) : 0x1b030ba4
SAsequencePoint_c::New(418) : 0x1b030c24
SAsequencePoint_c::New(352) : 0x1b030c84
SAmobPoint_c::New(0x1ad85664, 564) : 0x1b030cc4
SAmobPoint_c::New(0x1ad85664, 630) : 0x1b030d14
SAsequencePoint_c::New(513) : 0x1b030d94
SAsequencePoint_c::New(419) : 0x1b030df4
SAmobPoint_c::New(0x1ad7af94, 699) : 0x1b030e34
SAmobPoint_c::New(0x1ad7af94, 793) : 0x1b030e84
SAsequencePoint_c::New(567) : 0x1b030f04
SAsequencePoint_c::New(514) : 0x1b030f64
SAmobPoint_c::New(0x1ad85444, 171) : 0x1b030fa4
SAmobPoint_c::New(0x1ad85444, 224) : 0x1b030ff4
SAsequencePoint_c::New(644) : 0x1b031074
SAsequencePoint_c::New(568) : 0x1b0310d4
SAmobPoint_c::New(0x1ad7d3b4, 661) : 0x1b031114
SAmobPoint_c::New(0x1ad7d3b4, 737) : 0x1b031164
SAsequencePoint_c::New(703) : 0x1b0311e4
SAsequencePoint_c::New(645) : 0x1b031244
SAmobPoint_c::New(0x1ad79724, 3225) : 0x1b031284
SAmobPoint_c::New(0x1ad79724, 3283) : 0x1b0312d4
SAsequencePoint_c::New(801) : 0x1b031354
SAsequencePoint_c::New(704) : 0x1b0313b4
SAmobPoint_c::New(0x1ad8a0c4, 55) : 0x1b0313f4
SAmobPoint_c::New(0x1ad8a0c4, 152) : 0x1b031444
SAsequencePoint_c::New(836) : 0x1b0314c4
SAsequencePoint_c::New(802) : 0x1b031524
SAmobPoint_c::New(0x1ad849a4, 2465) : 0x1b031564
SAmobPoint_c::New(0x1ad849a4, 2499) : 0x1b0315b4
SAsequencePoint_c::New(921) : 0x1b031634
SAsequencePoint_c::New(837) : 0x1b031694
SAmobPoint_c::New(0x1ad79834, 263) : 0x1b0316d4
SAmobPoint_c::New(0x1ad79834, 347) : 0x1b031724
SAsequencePoint_c::New(988) : 0x1b0317a4
SAsequencePoint_c::New(922) : 0x1b031804
SAmobPoint_c::New(0x1ad85114, 1343) : 0x1b031844
SAmobPoint_c::New(0x1ad85114, 1409) : 0x1b031894
SAsequencePoint_c::New(1088) : 0x1b031914
SAsequencePoint_c::New(989) : 0x1b031974
SAmobPoint_c::New(0x1ad7b1b4, 525) : 0x1b0319b4
SAmobPoint_c::New(0x1ad7b1b4, 624) : 0x1b031a04
SAsequencePoint_c::New(1130) : 0x1b031a84
SAsequencePoint_c::New(1089) : 0x1b031ae4
SAmobPoint_c::New(0x1ad85004, 1598) : 0x1b031b24
SAmobPoint_c::New(0x1ad85004, 1639) : 0x1b031b74
SAsequencePoint_c::New(1183) : 0x1b031bf4
SAsequencePoint_c::New(1131) : 0x1b031c54
SAmobPoint_c::New(0x1ad7b1b4, 663) : 0x1b031c94
SAmobPoint_c::New(0x1ad7b1b4, 715) : 0x1b031ce4
SAsequencePoint_c::New(1263) : 0x1b031d64
SAsequencePoint_c::New(1184) : 0x1b031dc4
SAmobPoint_c::New(0x1ad84cd4, 1171) : 0x1b031e04
SAmobPoint_c::New(0x1ad84cd4, 1250) : 0x1b031e54
SAsequencePoint_c::New(1312) : 0x1b031ed4
SAsequencePoint_c::New(1264) : 0x1b031f34
SAmobPoint_c::New(0x1ad84bc4, 1826) : 0x1b031f74
SAmobPoint_c::New(0x1ad84bc4, 1874) : 0x1b031fc4
SAsequencePoint_c::New(1405) : 0x1b032044
SAsequencePoint_c::New(1313) : 0x1b0320a4
SAmobPoint_c::New(0x1ad78404, 5096) : 0x1b0320e4
SAmobPoint_c::New(0x1ad78404, 5188) : 0x1b032134
SAsequencePoint_c::New(1685) : 0x1b032374
SAsequencePoint_c::New(1406) : 0x1b0321b4
SAmobPoint_c::New(0x1ad84bc4, 2089) : 0x1b032404
SAmobPoint_c::New(0x1ad84bc4, 2368) : 0x1b032454
SAsequencePoint_c::New(1710) : 0x1b0324d4
SAsequencePoint_c::New(1686) : 0x1b032534
SAmobPoint_c::New(0x1ad7b1b4, 6710) : 0x1b032574
SAmobPoint_c::New(0x1ad7b1b4, 6734) : 0x1b0325c4
SAsequencePoint_c::New(1779) : 0x1b032644
SAsequencePoint_c::New(1711) : 0x1b0326a4
SAmobPoint_c::New(0x1ad85004, 2433) : 0x1b0326e4
SAmobPoint_c::New(0x1ad85004, 2501) : 0x1b032734
SAsequencePoint_c::New(1847) : 0x1b0327b4
SAsequencePoint_c::New(1780) : 0x1b032814
SAmobPoint_c::New(0x1ad85114, 2483) : 0x1b032854
SAmobPoint_c::New(0x1ad85114, 2550) : 0x1b0328a4
SAsequencePoint_c::New(1891) : 0x1b032924
SAsequencePoint_c::New(1848) : 0x1b032984
SAmobPoint_c::New(0x1ad7d3b4, 1089) : 0x1b0329c4
SAmobPoint_c::New(0x1ad7d3b4, 1132) : 0x1b032a14
SAsequencePoint_c::New(1969) : 0x1b032a94
SAsequencePoint_c::New(1892) : 0x1b032af4
SAmobPoint_c::New(0x1ad7c094, 5910) : 0x1b032b34
SAmobPoint_c::New(0x1ad7c094, 5987) : 0x1b032b84
SAsequencePoint_c::New(2529) : 0x1b032c04
SAsequencePoint_c::New(1970) : 0x1b032c64
SAmobPoint_c::New(0x1ad7b1b4, 2413) : 0x1b032ca4
SAmobPoint_c::New(0x1ad7b1b4, 2972) : 0x1b032cf4
SAsequencePoint_c::New(2581) : 0x1b032d74
SAsequencePoint_c::New(2530) : 0x1b032dd4
SAmobPoint_c::New(0x1ad7d3b4, 1413) : 0x1b032e14
SAmobPoint_c::New(0x1ad7d3b4, 1464) : 0x1b032e64
SAsequencePoint_c::New(2626) : 0x1b032ee4
SAsequencePoint_c::New(2582) : 0x1b032f44
SAmobPoint_c::New(0x1ad78954, 1031) : 0x1b032f84
SAmobPoint_c::New(0x1ad78954, 1075) : 0x1b032fd4
SAsequencePoint_c::New(2671) : 0x1b033054
SAsequencePoint_c::New(2627) : 0x1b0330b4
SAmobPoint_c::New(0x1ad79724, 1204) : 0x1b0330f4
SAmobPoint_c::New(0x1ad79724, 1248) : 0x1b033144
SAsequencePoint_c::New(2714) : 0x1b0331c4
SAsequencePoint_c::New(2672) : 0x1b033224
SAmobPoint_c::New(0x1ad8a0c4, 102) : 0x1b033264
SAmobPoint_c::New(0x1ad8a0c4, 144) : 0x1b0332b4
SAsequencePoint_c::New(2789) : 0x1b033334
SAsequencePoint_c::New(2715) : 0x1b033394
SAmobPoint_c::New(0x1ad7ae84, 1137) : 0x1b0333d4
SAmobPoint_c::New(0x1ad7ae84, 1211) : 0x1b033424
SAsequencePoint_c::New(2824) : 0x1b0334a4
SAsequencePoint_c::New(2790) : 0x1b033504
SAmobPoint_c::New(0x1ad84cd4, 3316) : 0x1b033544
SAmobPoint_c::New(0x1ad84cd4, 3350) : 0x1b033594
SAsequencePoint_c::New(2830) : 0x1b033614
SAsequencePoint_c::New(2825) : 0x1b033674
new CLopticalSource_c #1 : “ 2L”
SAsourceList_c::AddSource(“ 2L”)
SAsequencePoint_c::New(0) : 0x1b0367c4
SAsequencePoint_c::New(2830) : 0x1b0367e4
SAsourceList_c::AddSource(“ 2d”)
SAsequenceSource_c::New(0x1ad8a3f4) : “ 2d”
SAsequencePoint_c::New(137) : 0x1b0369b4
SAsequencePoint_c::New(0) : 0x1b0369d4
SAsequencePoint_c::New(341) : 0x1b036a54
SAsequencePoint_c::New(138) : 0x1b036ab4
SAmobPoint_c::New(0x1ad8a1d4, 64) : 0x1b036af4
SAmobPoint_c::New(0x1ad8a1d4, 267) : 0x1b036b44
SAsequencePoint_c::New(1701) : 0x1b036bc4
SAsequencePoint_c::New(342) : 0x1b036c24
SAsequencePoint_c::New(1710) : 0x1b036ca4
SAsequencePoint_c::New(1702) : 0x1b036d04
SAmobPoint_c::New(0x1ad7b1b4, 6726) : 0x1b036d44
SAmobPoint_c::New(0x1ad7b1b4, 6734) : 0x1b036d94
SAsequencePoint_c::New(1779) : 0x1b036e14
SAsequencePoint_c::New(1711) : 0x1b036e74
SAmobPoint_c::New(0x1ad85004, 2433) : 0x1b036eb4
SAmobPoint_c::New(0x1ad85004, 2501) : 0x1b036f04
SAsequencePoint_c::New(1847) : 0x1b036f84
SAsequencePoint_c::New(1780) : 0x1b036fe4
SAmobPoint_c::New(0x1ad85114, 2483) : 0x1b037024
SAmobPoint_c::New(0x1ad85114, 2550) : 0x1b037074
SAsequencePoint_c::New(1891) : 0x1b0370f4
SAsequencePoint_c::New(1848) : 0x1b037154
SAmobPoint_c::New(0x1ad7d3b4, 1089) : 0x1b037194
SAmobPoint_c::New(0x1ad7d3b4, 1132) : 0x1b0371e4
SAsequencePoint_c::New(1969) : 0x1b037264
SAsequencePoint_c::New(1892) : 0x1b0372c4
SAmobPoint_c::New(0x1ad7c094, 5910) : 0x1b037304
SAmobPoint_c::New(0x1ad7c094, 5987) : 0x1b037354
SAsequencePoint_c::New(2529) : 0x1b0373d4
SAsequencePoint_c::New(1970) : 0x1b037434
SAmobPoint_c::New(0x1ad7b1b4, 2413) : 0x1b037474
SAmobPoint_c::New(0x1ad7b1b4, 2972) : 0x1b0374c4
SAsequencePoint_c::New(2581) : 0x1b037544
SAsequencePoint_c::New(2530) : 0x1b0375a4
SAmobPoint_c::New(0x1ad7d3b4, 1413) : 0x1b0375e4
SAmobPoint_c::New(0x1ad7d3b4, 1464) : 0x1b037634
SAsequencePoint_c::New(2626) : 0x1b0376b4
SAsequencePoint_c::New(2582) : 0x1b037714
SAmobPoint_c::New(0x1ad78954, 1031) : 0x1b037754
SAmobPoint_c::New(0x1ad78954, 1075) : 0x1b0377a4
SAsequencePoint_c::New(2671) : 0x1b037824
SAsequencePoint_c::New(2627) : 0x1b037844
SAmobPoint_c::New(0x1ad79724, 1204) : 0x1b0378d4
SAmobPoint_c::New(0x1ad79724, 1248) : 0x1b037924
SAsequencePoint_c::New(2714) : 0x1b0379a4
SAsequencePoint_c::New(2672) : 0x1b0379c4
SAmobPoint_c::New(0x1ad8a0c4, 102) : 0x1b037a54
SAmobPoint_c::New(0x1ad8a0c4, 144) : 0x1b037aa4
SAsequencePoint_c::New(2789) : 0x1b037b24
SAsequencePoint_c::New(2715) : 0x1b037b44
SAmobPoint_c::New(0x1ad7ae84, 1137) : 0x1b037bd4
SAmobPoint_c::New(0x1ad7ae84, 1211) : 0x1b037c24
SAsequencePoint_c::New(2824) : 0x1b037ca4
SAsequencePoint_c::New(2790) : 0x1b037cc4
SAmobPoint_c::New(0x1ad84cd4, 3316) : 0x1b037d54
SAmobPoint_c::New(0x1ad84cd4, 3350) : 0x1b037da4
SAsequencePoint_c::New(2830) : 0x1b037e24
SAsequencePoint_c::New(2825) : 0x1b037e44

AvidCode Execution Stack:
    (level number: level description [object count] object description)
     9:      8:      7:      6:      5:      4:      3:      2:      1: AvidCode Parameter Stack:
    [ 1] FALSE
    [ 2] FALSE
Exception:
The Cut List template contains an error which was discovered while
generating the Change List at event 1.
See the console for additional information.
The template variable vKeyNmbrEndB is not defined for the current event.

updating sequences with modified master clip info

hellotansy — Thu, 22 Oct 2009 11:26:12 GMT

I'm working on a 35mm 3-perf PAL project, with film rate audio.

I have been capturing the entire TK tapes, and then subclipping by bringing in log files generated by telecine.

Now, with a couple of months of editing behind us, it appears that some of the keycodes in the metadata were incorrect.

I modified the offending files in Avid Log Exchange, then I imported them into the TK master clips using 'merge sources'.

However, when I look at my cut sequences, the metadata has not updated itself, nor has it in the subclips originally created by the first batch of log files.

Is it possible to reflect this new metadata in the cut sequences, without recreating every single subclip and replacing every shot manually?

thank youuu

sample rates in 24p pal

Laurie Hughes — Fri, 23 Oct 2009 02:20:01 GMT

I am working on a film shot on Genesis at 24 fps on a MC v3.05.

I imported my BWF files into the 24p project with the method 2 (video rate 100%+). My audio settings were 48k and bit depth 24 bit.

in the import options I selected

CONVERT SOURCE SAMPLE RATE TO PROJECT SAMPLE RATE

CONVERT SOURCE SAMPLE RATES WITH AUDIO PULLUP OR PULLDOWN TO PROJECT SAMPLE RATE ON IMPORT

CONVERT SOURCE SAMPLE RATE BIT DEPTH TO PROJECT SAMPLE BIT DEPTH ON IMPORT

I sent a test OMF off to the post sound and they complained the sample rate was 46k and they had to convert it to 48k.

This was confirmed in the avid bins.

so i turned off the setting

CONVERT SOURCE SAMPLE RATES WITH AUDIO PULLUP OR PULLDOWN TO PROJECT SAMPLE RATE ON IMPORT

and audio was imported at 48k and this satisfied the sound post.

I then went to playout to digibeta and it said

NOT ALL AUDIO SEGMENTS ARE AT THE PROJECT SAMPLE RATE. PLEASE CONVERT BEFORE PERFORMING A DIGITAL CUT

The only way to playout was to convert all the audio to 46k.

What would be the ideal workflow?

Thanks : )

Not shot in a format current MC or FCP can see!

Pixel Monkey — Sun, 01 Nov 2009 21:23:54 GMT

SONY HDV camera (Z5U) shot 1080i 24p. Using a SONY Z7U as a deck. Firewire. Having capture issues - same issues on MCA (HP8400) at work and Mac Pro (intel quad core) at home. Both systems up-to-spec.

Have newest versions of MS and FCP. Neither can see this format without burping timecode error messages every two seconds. In short, I've created EVERY project type in MC and tweaked every possible setting in FCP's video settings.

Totally able to capture 30i NTSC no problem... but obviously I'm going to have to online this thing in HD.

Clues? I'll even accept After Effects as an answer at this point!

making SD Pal copies from 1080p 24fps project

nigelad — Tue, 15 Sep 2009 21:40:14 GMT

I am planning to edit Red 24fps material on MC in a 1080p 24fps project, to master on blu-ray.

I will also need to make a Beta SP Pal master. How do I go about this conversion with Avid?

Will I get transcoding artifacts on the PAL version, or will it just be 4% faster and higher pitch sound?

Or would it be better to work with 25fps material and convert to 24fps for Blue Ray?

Any advice gratefully received.

3-perf 35mm Film Project and P2 1080 50i problems. Need Help!

Luis Rico — Fri, 23 Oct 2009 16:38:08 GMT

Hi,

I'm the assitant editor of a motion picture in Spain. The film is being shot in 35mm but the director also has shot two scenes with a P2 HVX200E camera for plot and aesthetic reasons.

The editor is cutting the film on a MacPro with Avid MC 3.5.2. I'm ingesting and dealing with daylies with an 2009 iMac and an Avid MC 4.0.2

Our problems started when we found out that all the footage shot by the second unit director with the P2 HVX200E was recorded in DVCPRO HD 1080 50i and NOT in 24p.

We need to put that footage into the editor's project so he can cut and mix both materials and, obviously, everything has to be in 24 fps.

We have tried several options:

-Create a 1080 25p project, export the DVCPRO HD 1080 50i footage as DNxHD 36 and import it in the 35mm 24p project, which alters the footage by repeating one frame (or is by erasing one frame?)...eh...not a solution.

-Create a 1080 25p project, export the DVCPRO HD 1080 50i footage as TIFF sequence and import it in the 35mm 24p project, which looks good and in glorious 24p BUT we lose the sound and the TC.

-Upgrade the editor's MC to version 4.0.2 which can 'mix' different framerates, but that doesn't solves the problem, does it? When need a final cut with a timeline with all footage in 24p in order to conform to a D.I.

Our deadline is approaching and we are a little concerned. I would really appreciate some tips or ideas.

Thanks in advance,

Luis Rico

Reference won't export

Steen Hansen — Mon, 26 Oct 2009 07:41:59 GMT

Hi. I'm trying to export a sequence to a standard Reference file. But get error on the audio on export. Never had this problem on 25fps. I'm in a film project. Sound came in seperately and sync'd in Avid. Error - CM_OFFSET_OUT_OF_RANGE. Help!

Perf slip problems in MC 3.5.1

Rvdhammen — Mon, 26 Oct 2009 17:41:42 GMT

Me and some fellow student editors have been experiencing some Perf slip problems using MC 3.5.1 with a 24p 35mm project and i was wondering if there's any solution to it.

First of all perf slip doesn't seem to work at all.

Strangest of all is that it seems we're only able to slip to the left.

When I slip 1 perf to the left my Slip heading correctly tells me it went from 0 to -1 etc. (appart from the fact that there has been no slipping).

When I slip 1 perf to the right thought the counter keeps on continuing to the left. So when the slip is at -1 and i slip to the right, the counter goes to -2 in stead of 0.

Timecode Help Please ...

vvp — Thu, 22 Oct 2009 17:49:35 GMT

I need some confirmation regarding the work-flow of a project I am about to output for local broadcast please ...

Deliveralbe is 1080i/59.94

- Source Footage / Avid Project Rate: 1080p/23.976

- I am using Avid's 30DF timeline timecode to bring the show to required time (22 mins.)

- Planning to use Avid's Crossconvert to achieve output to 1080i/59.94

- Closed Captioning is handled by an outside source. I am thinking that the TC burn DVD for transcription should have the 30DF display for timing and that should then correctly sync to the 1080i/59.94 master on the layback.

Thoughts are appreciated.

Thank you!

Film Project settings - AUDIO

Steen Hansen — Wed, 21 Oct 2009 06:58:12 GMT

Hi. I'm setting up a film project last minute. 35mm, 3 perf, shot at 24fps. Dailies being transferred at 25fps But just found out that sound is recording at 25fps. Should my project be as follows - 24p PAL (UK), Film, 35mm 3 Perf. Now - Audio Transfer Film rate OR Video rate?

Many thanks!

"unable to find key number for..." error

nigelad — Thu, 22 Oct 2009 11:04:07 GMT

Hello again!

I am trying out the Redcine workflow described in the Avid 'step by step' document.

Having used Redcine [v.20] and Test-XSLT to create QTs and an ALE, I then cut a simple sequence in MC [v3.05].

When I follow instructions in Filmscribe [v24.0.5] and hit preview I get the error message "unable to find key number" for each clip used.

Any ideas appreciated...

Nigel

Redcine to MC aspect ratios

nigelad — Thu, 22 Oct 2009 10:44:37 GMT

Probably being dumb here, but how do i get 2:1 AR footage to display correctly in a MC 1080 25p project?

I exported 2K 2:1 from Redcine , and MC knows the correct resolution in the bin headings column, but display it cropped.

Is there a way to resize the footage letterboxed for viewing?

Thanks for any help.

nigel

Has anyone used this camera?

chadg — Wed, 26 Aug 2009 20:04:16 GMT

The DP of a feature I'm cutting this fall is thinking of using the Canon EOS 5D Mark II. It's a still frame camera that also shoots full HD video at 1080p. Here's the link:

http://www.usa.canon.com/consumer/controller?act=ModelInfoAct&fcategoryid=139&modelid=17662

Workflow we have in mind is to shoot this camera (at 30p), offline on Media Composer and create an HD master, then do a film-out to introduce grain and additional contrast, then color the negative, mastering back to HD.

Wanted to see if anyone here has dealt with this camera for filmmaking before. And if so, what sorts of problems I might need to look out for, both with the media and the workflow?

Any feedback is greatly appreciated!

.wav and .bwf in the same project

hellotansy — Wed, 14 Oct 2009 11:32:57 GMT

I have a newbie audio question:

I'm in a 35mm 3 perf project, PAL (sped up 24 to 25 in telecine) synching in the Avid (Sound in at 100%).

Until now, I have been getting .bwf (m) from the shoot, with 25fps timecode, and bringing all the audio tracks into the avid, but synching only the mixed down stereo pair audio tracks. Does this sound sensible?

Now there is a new sound recordist. I have received single track .wav files (with 25fps timecode).

What shall I do with them? should I ask for a clone of the original sound files? or sync up with these ones and figure out how to conform it later?

Thanks

x x

Switch between 24P n’ 25i

rslpro — Fri, 16 Oct 2009 09:41:48 GMT

I was created a film project under 24P PAL. Project already 80% done. Some how I need to transfer this project to 25i PAL system. I know I need re-capture all my muster clips but I don’t want to lose my edited Sequence’s. How I’ll do this job without losing my last edit?