[Thomas Macoy]

Ah, figured it was something like that. Thanks for the clarification.
-Tom

[Thomas Macoy]

I know, the use of Netscape is really weird, but for some reason that’s what Firefox and Chrome both report back under. Probably nothing to do but keep an eye on it. Thanks again for your help!

[Thomas Macoy]

Funny, that was one of the first pages I came across in my searching, and I thought I’d pretty much picked it dry. Buttt, some digging and retesting and I seem to have hit upon a solution; I had problems getting their browser detection to work, so I tried my own. Rather than writing a separate function, I just included it in the JS Callback I’m using, like so:
https://trmacoy.com/demo/callback.html
I also found some of the platforms (IE at least) react poorly if the Object ID and Embed Name are identical, which I assume is some error on my end because every other source I’ve viewed had them matching. But at this point, I’ve got a successful test on IE/FF/Chrome (PC) and FF/Chrome/Safari (OSX) and feel pretty strongly that if it’s not broke, don’t fix it. If you’re curious and want to glance at the updated code and post back if you see anything devastatingly wrong or out of compliance I’d welcome it, but otherwise, thanks very much for the pointer.

[Thomas Macoy]

Perfectly understandable, I’m not sure why Cow decided to zip up a single text file.
In the interest of focusing in I slapped up a simple test site at
https://trmacoy.com/demo/callback.html

I’ve copied all the relevant code from my project (mainly the SWF embed, the JS function, and the AS3 callback) and swapped out the original SWF for a dead simple one. Two buttons stop and start a simple animation. One Java scripted button will also stop the animation by sending a callback to AS3, but again, it only works in IE. Thanks for taking a look, apologies for what I’m sure is sort of sloppy HTML.

[Thomas Macoy]

That was one thing I checked actually- I know there’s a setting when you can pick if the audio gets cut along with the video, or if it uses only track 1 to output. (The Audio Follows Video option, under the Multicam Window options triangle; if I read you right, checking that on should let your edit read your audio tracks 3 and 4 without have to cut and copy them back into the final multicam track.)

I know it’s not that setting in my case cause I still get audio when I scrub in the multicam window, which I think would imply some kind of performance issue, but I can’t say for sure. Thanks though.

[Thomas Macoy]

Should’ve posted that too. The rig is:

Gigabyte MB (nForce4 SLI)
Athlon X2 3800+
2 Gigs RAM
eVGA 7800GT nVidia video card
WD Raptor 35 gig System drive
WD regular (7200rpm) Project Files drive
Windows XP SP2, fully updated

I think all my drivers are up to date, but I’ll check. I believe I tried Accelerated GPU effects both on and off and got the same result.

[Thomas Macoy]

As far as I can tell, PPro2 does actually maintain the timecode on the original tape; the thing is, when you drag it into the main timeline, the timecode of that timeline takes priority. However, if you look at the clip in the source monitor, you’ll find (I think, unless I’m looking at my last project wrong) that it displays the original time written to the tape. For example, I have a clip that I captured from timecode 00:00:15;00 to 00:54:57;24, and those are the first and last numbers the source monitor displays on that clip. When pulled into the main timeline though, it then displays whatever number your cursor’s under.

I’ve never tried capturing free run before, though if you timecode isn’t continous, because of starting and stopping in free run, you may run into an issue of PPro2 reading your tape as full of timecode breaks. Still not sure how to get around that one. However, if you can, and you can keep your cameras powered up, Free Run’s a great way to keep the cameras in sych, long as you can get the free run on both started up at the same time. I’m assuming you’re not shooting with a high end DSR or something that has a Timecode In/Out connector- barring that, I beleive the new DVX, the 100B, can take in Timecode from another camera through Firewire, which will give you perfect synch the whole way through. Good luck.

Hi, I have a similar problem. But this time is with the free run function. I want to capture a whole tape without losing the free run time code. When I try to capture with premiere pro 2 I lose the time code because premiere creates his own new tc, but I can see my own FR TC on the capture monitor…
Is there a way to shoot with free run tc and capture without losing that tc?
I know is probably not the best, but is that a good method to keep the sync between to cameras?

[Thomas Macoy]

Avid’s readme discusses drivers for nvidia workstation level Quardo cards, but not the desktop level cards; for those, I think it’s basically luck.
I think I did figure out the issue though, after digging around on some other forums: basically under a dual screen setup, Avid requires whichever monitor you have set as “1” to be your primary monitor. My usual setup has “2”, my larger screen, as the primary; changing primary over to 1 seems to fix the problem and the sub windows stay where they’re placed.
Thanks both for getting back to me so quickly.

[Thomas Macoy]

I’m currently on Forceware 91.31 (which I think means I’m actaully a little behind, will try updating). Clone view (same display image on each monitor) seems to solve the problem, obviously at the cost of one monitor.
I assume a program like Avid is designed with two monitor support in mind, so there must be some workaround. My monitors are running at different resolutions of 1280×1024 and 1680×1050, meaning I’m using Dual View mode rather than the more common Span mode (where the windows desktop is stretched out across both screens); is it possible that’s causing the conflict? (It also doesn’t make any difference if I just keep the main avid window on one screen, sub windows still jump around.)
Thanks very much for getting back to me.