[William Meese]

Yes, I’m excited, and waving my hands — especially since this TV station is about to replace two systems — maybe pulling the trigger this week.
Now, my Avid experience is with the dedicated hardware: Symphony Nitris DX, MC Adrenaline, MC Meridien (still chugging along beautifully, thank you). I assume this is essentially an MC software system with no performance boost from the Aja box.

So I’m doing homework in a hurry:
MC 5.5 is 32-bit. Any problem running it on an Adobe CS5-friendly 64-bit box?

What’s the MC software realtime performance like? Specifically, performance on a z400 box, compared to Premiere Pro CS5 using Matrox LE hardware (the current plan).
On a z800 box?
Using SD 2:1 media?
Using XDCAM EX via AMA?

I’m working on getting a demo, but what’s the real world experience out there using MC software for SD online?

[William Meese]

At least John knows he’s clueless here — that’s like a breath of fresh air.

John, if you haven’t gotten Bob Zelin advice before, don’t take it personally.
Just take it.

Different broadcast venues have different requirements; some are very stringent. If you have an imminent need for broadcast quality, don’t pay for gear; pay for a pro to help you get your material to spec–and talk to him/her early in the process.

[William Meese]

When I RTFM I find that “speed” always returns a 1D, positive value, but”velocity” returns a result w/ the same dimension as the property.
So thanks, Dan; a more elegant solution.

When I plug it in, the results are similar but not identical–perhaps a matter of which chunk of the timeline is being sampled; my original math samples the frame before, “velocity” is probably the value at the instant of the frame start.

At least now the expression functions. Onward–and thanks again, guys.

[William Meese]

I thought “speed” would give the actual distance moved, whatever the direction, while I need just the horizontal component.

Your “try valueAtTime(…)[0] instead” tip confused me for a while, but it clicked: valueAtTime is a property, so it needs to come before specifying the dimension.

“transform.anchorPoint[0]-transform.anchorPoint.valueAtTime(time(1-24))[0]”

is working. Thanks!

[William Meese]

That’s good to hear. Thanks!

[William Meese]

Thanks for the tip, Brian.
Alan: 1394 max length is officially 15 ft, and I have a 30 ft run here. Add a repeater and the cost is the same as HDMI. Also, others with experience have warned me that long runs of firewire just aren’t that reliable.
With HDMI I should be getting the camera signal without the HDV compression, so a better image for the same price, better results for any greenscreen work, and much cheaper than HDSDI. That’s my thinking, anyway.
Hmm; wonder if OnLocation will work w/ an HDMI card…

[William Meese]

And my cross-post on the Premiere Pro forum gave me another possible source for good cables. Thanks, Joshua.

[William Meese]

You’re right; that’ll do the job and that’ll fit the budget. Thanks.

[William Meese]

Thanks, Brian. It looks like it’s a matter of buy some good cable and if it works, don’t buy the repeaters. It’s also good to hear that Intensity’s working well w/ CS4.2.
I like Cineform, but first I’d try transcoding to something already available.
Any cable recommendations?

[William Meese]

75 feet — I’m happy for you. According to the BJC website, the Series 1 cable is certified for “45 feet for Category 1, 25 feet for Category 2” so it may work for my client’s studio. I certainly like the wide range of lengths they carry, and the Tartan series is cheap, too. Thanks.