[Jeron Coolman]

Heh heh, like I said, I wasn’t sure if I understood your problem.

It sounded like your “sparkles not aligning to the ball” problem might be square-pixel/non-square pixel aspect ratio mismatch issues between your premiere pro project footage and the animation you rendered from PI.

All of my projects are widescreen video footage. On my widescreen DV and HDV projects, I usually end up with square pixel renderings from animation programs like PI. In that case, I have to tell PPro to Interpret the footage to non-square pixels, 1.2 for DV wide or 1.3 for HDV.

You mentioned “studdering” then you mentioned “flickering”. I thought the “studdering” might be just un-rendered timeline playback. I didn’t realize you saw this after rendering.

[Jeron Coolman]

I’m not sure I fully understand the problem, but if your CS3 project is non-square pixels and the output of PI is square pixels (or vice-versa), did you try right clicking on the PI clip in PPro and use the Interpret Footage function to tell it to treat the square pixels as non-square (or vice-versa)?

[Jeron Coolman]

For a Windows user, it doesn’t really help 😉 An application like ProAnimator, for me, isn’t really reason to spend alot of money and time buying a new computer and switching to a different platform. Now if it were my NLE application we were talking about that might be a different issue…

I’m sure that those of us that can’t get it to work are a minority. Tech support has been great trying to help me solve the problem. I’m sure we will eventually be able to figure it out, but I wasted too much time and finally had to stop trying. I was getting too far behind in my projects.

I run Lightwave on my machine, so I bought the 3D Arsenal plug-in for it that makes it easy to set up logos and 3D titles. It has been running flawlessly. I’ll try ProAnimator again after another point release or when I have some extra-time…

[Jeron Coolman]

Oh yeah, I remember you were having RS422 deck control issues too when trying to capture through HD-SDI.

If I remember right, you could “crash-record” just fine through the HD-SDI not using the RS422 deck control, but of course that is pretty useless when you need to batch capture.

In your research, did you find anyone complaining about RS422 deck control issues with your deck like you did with the firewire; e.g. are the RS422 problems Aja or Deck problems?

For what it is worth, I have no RS422 deck control problems using my Sony M10U deck -> firewire -> HD-Connect-LE -> Aja Xena LH with HD-HDI and RS422 deck control. The Xena controls the M10U deck just fine with the RS422 through the HD-Connect-LE.

[Jeron Coolman]

I remember your other thread, but not the specifics.

I think the only support you are going to currently get is HD-SDI ingestion into uncompressed media with the Aja. I’ve used my Aja card with HDV captured through firewire and HDV captured through an HD-Connect-LE through the HD-SDI as uncompressed HD. It works great with the uncompressed HD.

You are only going to capture compressed footage via firewire and I’ve found that using the Xena when working with compressed footage is pretty much a step backwards with my workflows due to it having to dedicate resources to convert everything to uncompressed HD. With compressed footage, Premiere Pro is far more stable and responsive when working with the Adobe presets.

The Xena shines when you need to deal with uncompressed footage through SDI or component I/O (depending on what card).

If you are working with DVCPro and Premiere Pro, then I recommend looking at the new MOTU V3HD device, https://www.v3hd.com/

[Jeron Coolman]

I have an HDTV that I used to use as a monitor connected to the Xena card to monitor my HDV timeline through the Xena’s component outputs. The HDTV has two sets of component inputs, one labelled YPbPr and the other labelled YCbCr. Maybe someone smarter than me can explain the difference between the two.

If I remember right, one set of connections worked and the other didn’t. It has been a while. I quit using my Xena card to monitor my HDV, DV and uncompressed SD timelines, because the presets were too laggy and slow compared to the Adobe ones (they really need an Aja Dissolve Transition). I use the new CS3 feature to monitor the timeline through a second DVI monitor. Now if I had to output uncompressed HD, then I’d have no choice to use the Xena…

[Jeron Coolman]

Every once in a while, I can get a GOOD targa sequence rendered, other than that this program will not render anything without crashing with this error.

Rendering to a targa sequence will not crash, but 80% of them will have mostly black frames with only a few of the frames with any graphics.

Oh well, I guess I should have downloaded a trial before wasting my money…

[Jeron Coolman]

I’m having the same problem with HDV resolution. I created an animation, rendered it just fine, changed the color of the letters and now it won’t render at all.

Did this ever get resolved?

[Jeron Coolman]

You can output a native HDV file from Adobe Media Encoder. There is a setting (I can’t remember the exact one) that you should have to tweak with.

You won’t get the same exact quality, because Premiere Pro doesn’t have any type of “smart rendering” like most of the other NLEs. It will re-render every frame on your timeline no matter what.

[Jeron Coolman]

I bought an HP 8400 and at the same time built one. The HP is a GREAT machine. I use Dells at work and prefer HP over Dell.

I normally build my machines and only bought the HP because of how finicky Avid is and it was a certified machine. It was only a single quad-core. The machine I built at the same time is basically the same machine with twice the memory and two quad-core chips and 33% more hard drives for the RAID controller. It was still $2,000 less than the HP 😉