[Baz Leffler]

I recently did a 9 camera edit. It was done using leo’s technique and applying a PiP effect to each clip using ‘motion’ thus creating a 9 way split screen.

The computer I was using could play it in real time.

Then I played the timeline using ‘voiceover record’ to record my voice as direction to which camera to use and the asterisk key to provide the cut point; all on the run.

After that I went back and cut (^K) at the asterisks, deleted the unwanted portions and finally disabled the ‘motion’ to bring each portion up to full screen.

Then I went thru it all again and did sone fine adjusting.

An advantage with each camera on a different layer was that I could then colour match each camera and then apply that setting to the whole layer/layers. But only do this AFTER you have completed your edit as it will slow down your realtime performance! (you can also do it prior to the cut but disable the colourgrade until after the edit)

Incidently this was a digibetacam job where I injested everything as ‘off line’ in DV mode (to keep file sizes down and realtime performace high). After that I did a project trim and batch captured the trimmed project as uncompressed from the digibetacam.

I also recently completed a 5 camera workout video using the same technique. In fact I have never used the multicam mode in premiere because it requires rendering but my technique doesn’t.

Baz

[Baz Leffler]

Just an update on the ProVTR export to tape plug in with Multibridge Extreme; it appears to be consistantly frame accurate again when inserting into a Digibetacam using the 5.8 drivers. FYI my offet is 50.
I will check it soon using a Decklink Extreme.

Baz

[Baz Leffler]

Hey Dean. Yes I still use ProVTR although recently I had some accuracy issues with it. I was having extremely good success with it about 12 months ago and the BMD deck control was sadly inaccurate. But now the BMD deck control is 100% accurate and ProVTR is not. Go figure that! the only thing that changed was the BMD drivers and having spoken to both BMD and Pipeline (ProVTR) we can’t seem to get any logical conclusion. BTW you may need to upgrade your ProVTR to the latest if you need it to work with PPRO 2.0. It DOES require the use of a com port as it uses port sensors to detect their special 232>422 cable.

As for the ‘PPro capture GUI’, that is part of Premiere’s software; ‘export to tape’ is a third party plug in. There is quite an amount of functionality available thru the plugin as evidenced by ProVTR’s interface which BMD don’t seemed to have tapped into; and maybe its a cross-platfom issue but nevertheless many years ago (Prem 5.1) I actually wrote a plugin for deck control using the then available SDK from Adobe. Maybe I better do a refresher course on Visual C….

Also it should be noted that PPro 2.0 has its own built in ‘9 pin deck control’ based on ProVTR where a special cable is not required other than a 232>422 standard converter cable. I use a USB>422 adaptor but the PPro interface is so unpredictably inaccurate that I don’t even go there!.

Baz

Baz

[Baz Leffler]

Hey Dean … I always have an outboard monitor across the timecode display output of the digi or HDcam deck. Thats how I check on the ‘export to tape’ progress.

Also as a tip, if you need to abort ‘export to tape’ when using Decklink deck control just disconnect the 9 pin cable. In my case I have a switch box that connects the 9 pin devices and I just switch control away. The downside is that you have to manually stop the deck.

Yes there are some fundamental basics missing with the Decklink deck control and maybe oneday it will have all the functionality of ProVTR which I also have.

Baz

[Baz Leffler]

I have this problem sometimes too. Its caused by playing something close to the end. My workaround is to place BLACK way down the end of the timeline. Then the last clip you are playing is NOT the end and all plays fine.

[Baz Leffler]

What I have done in the past with the ‘broken timecode’ problem was to create a sequence for each part of the tape where the break had occured and set the sequence start timecode to reflect the true timecode of that portion. Then its just a matter of cut and paste from the individual sequences into the main. Does that make sense?
Baz

[Baz Leffler]

I tried this with my HDCAM JH3 in 5.1 (6 channels) and it work ok (5.8 drivers). If you open the clip in a stereo project it will only play tracks 1+2. But if you expand the track out you should see 6 channels. If you open a new 5.1 sequence it will play all 6 channels.
If you open in Audition it will show you the 6 discrete tracks and you can save them as individual tracks as needed.
But what I did notice as a BUG is that if you try AUDIO ONLY 5.1 capture it appears it is capturing but it doen’t actually save it; but as I said earlier it works OK as video+audio. Incidently it captures and saves a 2 channel AUDIO ONLY just fine.

Baz

[Baz Leffler]

I use this function on a very regular basis. As I never read manuals I assumed it was normal as with most ‘cut and paste’ features within windows programming.
Isn’t the concept of video editing based on text editing ala MS Word etc?

Baz

[Baz Leffler]

Phil said:
“I went into my audio codecs and selected the emulator codec once again. Now the program continues to boot up without any problem”

Yes Phil… thats what I found as mentioned in my previous post…

“What I did was open the control panel and disable the audio codecs, confirm PPro would open all the way and the while PPro was running go and re-enable the codecs. After that PPro would open normally everytime. Didn’t make sense then, still doesn’t make sense now; but nevertheless I blamed it on Bill Gates.”

See you have confirmed it wasn’t something I did stupidly!

Baz

[Baz Leffler]

Tim said “The last thing you see on the screen may not be the problem”

This is in fact the case. It is displaying the last ‘successful’ load.

Look for “Plugin Loading.log” in a Premiere 2.0 folder on your system drive and open it in notepad. You will see from the ‘Write_on.AEX’ onwards …
————————————————————————–
Loading C:\Program Files\Adobe\Adobe Premiere Pro 2.0\Plug-ins\Common\AEFilters\Write_on.AEX
Loading from the registry…
The plugin has a PiPL.
The plugin was successfully loaded from the registry.

Loading VST plugins…

Scanning for the following file types: *.dll

Scanning C:\Program Files\Steinberg\VstPlugins and sub-directories
————————————————————————–

It may not be the same as mine but it indicates that after ‘Write_on.AEX’ it looks to load VST but what it doesn’t say as part of the .dll is the codecs (dynamic link libraries are what contain the codec drivers). Thats where I had my problem.
If you search these forums and the Adobe forums you will find it is covered in detail.

What I did was open the control panel and disable the audio codecs, confirm PPro would open all the way and the while PPro was running go and re-enable the codecs. After that PPro would open normally everytime. Didn’t make sense then, still doesn’t make sense now; but nevertheless I blamed it on Bill Gates.

Baz