The Beta for PP CS3 was released today and I'm wondering if I can load
cineform into it for proper HD editing??

Yes, I'm desperate to test PPRO CS3 with my film project and Aspect HD too...

- only thing with PPRO CS3 Beta is (according to their website):

Timemapping doesn't work properly
HDV editing isn't supported
Edit in Soundbooth (new name for Adobe Audition) disabled
Dynamic Link disabled

This is pretty weak, as these would be the first things I'd test!!

Oh, and OnLocation isn't included... this alone is reason enough to purchase the upgrade from PPRO 2 to CS3.

...I'm still going to download and test though, as I'm a sucker for a nice new funky application.

Somewhat off-topic, but Soundbooth is certainly not a new name for Audition. It's a different product with a (depending on how you look at it) more limited feature set and different focus on functionality. Unfortunately Audition will not be part of the new CS3.

I have Audition, so I assume I can still use that... mainly need to for 5.1 surround mix and noise-reduction, so I hope Soundbooth has at least that.

...I just wish Adobe were as good with sound as SonicFoundry/Sony are in Vegas.

I assume Cineform are keeping radio silence on this topic as they're probably trying to get it work themselves. And when they know more, we'll know more.

We are showing CS3 at NAB running Prospect 2K. Our tools with with it today with a few minor beta issues.

Had more time today to run another test. I did a direct comparison of a PPro2 720p desktop project, consisting of 10bit 1280x720 tiff image sequences that I rendered from Lightwave. The images are moving line graphs from a DAQ program. A thrity second clip, six layers deep, all with alpha channels, two layers have also have Color Correction, and a title layer.

This particular sequence, in PPro2, crashed on me about three times rendering out a 720p CFHD. Which required a reboot of the PC to recover the memory stuck in RAM. 1st image below is a screen grab of the performance monitor for PPro2):

As you can see only 50% of the quad-cores were being used, and just over 1.5mb ram. The render took about 17 minutes to process.

Opening the same project in PPro3 and rendering was a completely different animal. Image #2 indicates 100%, and get this, 1.71mb of ram! In fact more resources were utilized and not a single crash! The render took only 9 minutes to complete, that's almost twice as fast! (Image #3).

I'll post more results as I find them. This is very promissing!

Update. Cannot capure with cineform engine in PPro3 -locks up. I assume it's the HDV limitation. However, you can import, edit and export cineform files captured with PPro2.

Below is screen grab of an cineform quicktime export. The result file was HDV spec and played well. It used only 50% resources this time in the render. I'll have to test some more, otherwise, it's looking good.

After clearing my head and getting some quality time to test this out, I realized that I forgot to copy the cineform edit mode preset. Adding that, I was able to create a CFHD project, capture with cineform DV/HDV engine and edit as usual. Exporting CFHD, and both an avi and quicktime wrapped videos.

I could not export a cineform M2t, although the render dialog box did appear briefly before getting the "unable to create M2t" error. (PPro2 would just error). So my gut feeling is that cineform m2t exports will be possible in PPro3 once HDV is enabled.

Capture did utilize 100% processor, however, render was smooth and efficient with only 50% CPU usage.

Importing cineform projects created in PPro2 into PPro3, or just opening with PPro3 also works. There are a few new tools, etc. otherwise, it's pretty much the same environment, however the crashing seems to be absent!

Importing or opening HDV projects would work, except the actual .mpeg files would be offline and linking would yield a file compatibility error. So nice dice for HDV on both ends.

Peter, Am I understanding that you were able to load the Cineform presets?

I loaded Cineform on PP3 and tried a project but as you know the presets for
both Cineform and HD are locked out.. but the output sets look like they are
there and functional....

So how did you go about loading the cineform presets

If you want to try PPro3 (CS3) and cineform, do the following:

1. Download and Install the PPro3 preview.

2. Copy the following files/folders from you PPro2 folder to PPro3's:

Plugins (copy and paste the "cineform" folder):
C:\Program Files\Adobe\Adobe Premiere Pro 2.0\Plug-ins\en_US\CineForm

Presets (copy and paste the "cineform" folder):
C:\Program Files\Adobe\Adobe Premiere Pro 2.0\Settings\en_US\CineForm

Editing modes (copy and paste the "Cineform Editing Modes.xml"):
C:\Program Files\Adobe\Adobe Premiere Pro 2.0\Plug-ins\en_US\Editing Modes

Note: HDV Editing modes for the adobe edit modes xml file are listed and don't appear to be disabled in that file, most likely they are disabled in the main program.

Open PPro3, choose new project, and you'll see the cineform edit modes are now available.

The only issues so far is capture, as post encoding the CFHDs after ingest is very slow. Best done with PPro2, then import into PPro3. But you should give it a try anyways.

What's needed is for some you with rather large projects, who are having issues with crashing and app hanging, etc. to reopen these projects in PPro3 (save them to a new name) and see how they behave. Have fun!

Using identical and project and settings, in both PPro2 and 3:

Rendering time is about 1/3rd faster in PPro3. The rendered CFHD files are not identical, however. The audio is different. Not sure what, just says 16bit for the PPro3, while PPro2 is 16 bit 1536kbps PCM. Without audio clips (taking that out of the picture) The PPro3 render, a 16sec clip, is larger at 142megs, and the PPro2 is 133megs. Both files look and play identical. Only guess is slightly less compression with PPro3? But uses more resources. Shaving off a few minutes in render time vs. PPro2.

In light of this, I'm not sure is 100% processor usage is really buying much, as multitasking is impossible, even for a quad. If this is cineforms multithreaded code, it would be nice to have a feature to either turn this off or select the number of threads, (BTW, Newteks Lightwave has this feature in their render engine, and it's nice to control just how much resources the app is allowed).

Scrubbing and playback of the timeline is improved. Even for a heavy layered project, it manages ok in PPro3, where PPro2 just skips or doesn't even bother to redraw the screen.

FWIW, Cannot open a PPro3 project in PPro2, though it's mentioned in the Adobe forum. PPro2 just crashes.

We still have an issue with poor alpha handling, such as white title text against black. You will still have to place a black video clip underneath to fix.

I have one last test to do after lunch. A particular large project with the dreaded "render skip", Hung app, and don't wanna spit out CFHD, (likes only micorsoft avi with the wrapper).

Hope this help someone out there.

Opening my large and troublesome project, I noticed that the timelines were blank. However the sequences in the bins were intact. Double-clicking on them opened them up in new timelines. Obviously some changes has taken place in regards to timelines, any may indicate why they perform better?

Ok, now for the bad news....

Welcome back disappearing Premiere! No sooner do I scrub troubled areas on the timeline; a spot that would cause PPro2 to skip over or not render and 'poof'. Bye-bye application.

Attempting to render the timeline to CFHD generates "error compiling movie."

Mixed results when rendering a wrapped avi. The processor usage would peak at 100% for a few minutes, then drop to 50% for a bit. I thought it was timed to heavy areas on the timeline and the app was dynamically using extra threads as needed. Not the case. The program crashed and disappeared at the problem spot. At least in PPro2 I wouldn't lose the entire app, and the could work around it, (which in fact I able to render and microsoft avi and move on).

OK, to be fair, this may be an isolated problem and not a good overall picture. Which is why some of you need to test your troubled projects and see if there is a common issue. Answering this while the application is still being developed is important. Especially if we need to open old projects for updates, changes and/or recycling, (we need to help the folks at cineform to help us).

Therefore, if many of you are in need of a solution to fix current problems, here's your chance.

Man, I just love having a thread all to myself... (Sarcasm filter on).

I can confirm that the PPro3 is using more resources, and not due to cineform. I've tested several old PPro DV 480i projects, many heavy with effects and keys. In all PPro3 is utilizing 100% of all four-cores (and was using 100% of both processors in my old Dell). This equates to roughly 30% gain in speed for rendering. This is also apparent in scrubbing the timeline and timeline playback. Believe me, 30% is noticeable.

That said, my next cineform project, which starts today, is going to be cut in PPro3. Nuts? Yup!

David, when you get back from NAB, I'd like to try out that new 2K version. I have some green screen test to do, (something I've put off due to my workload and now have some time do it).

Oh, we're here. Just nothing to add, - yet.

Gonna download the Beta tomorrow. Would be cool if it didn't crash with Cineform.

Still smarting from not being able to use that $500.

Peter, I'll hope to add to the thread if I can get the HD parts to work tonight...

Thanks for the assistance.....

Thanks for all your work, Peter.

I've d/l'd CS3... I only copied the Cineform Presets folder over, and attempted to open one of my PPRO2 project. I'll try your suggestions tonight.

On my initial test, it started conforming all the audio files again! Got cold feet and cancelled it!

Will copy the folder with the conformed audio across from the PPRO2 project, see if that saves me a couple of hours of conforming (someone remind me why Premiere insists on doing this, and Vegas doesn't!).

I have 50 scenes (approx 30mins) from a 1/3 of a film I'm editing my on one timeline, approx 20hrs of footage (1080 50i), a few stills but nothing fancy.

Deinterlacing using Boris Continuum Complete 4 Deinterlace, colour-correcting with Magic Bullet Colorista and grading using Magic Bullet Suite. Project file size is around 60MB.

I kinda resent having to pay for either/both Premiere Pro upgrade and Aspect HD upgrade when the current workflow just ain't working for a reasonably simple project.

Hopefully our Beta testing of CS3 will prove that it's not just a PPRO2 bug-fix with a time re-mapping plug-in! But I'm not holding my breath.

Thanks guys, we need more examples other than mine.

Douglas, I think you'll need to ensure that the edit modes.xlm file is copied over, otherwise it'll default to a desktop project and use vfw, and it conforms.

I'm using prospect, which is 1920x1080i, and captures HDV and scales to 1920x1080i. I'm not sure about Aspect, and how it's addressed by PPro3 with HDV (ala 1440 rez) being disabled. That may simply not accept 1440 anything and just default back to desktop vfw anyway.

Uhm, put it anotherway, (If I remember this correctly). Whenever I capture to a prospect edit mode, it always scales up the media to 1920 and I don't get conforming and renderlines. If I import anything other than a 1920 or non-cineform, it conforms that file. So it would be interesting to know how PPro3 deals with Aspect 1440 even though it's not HDV.

Other than one very troublesome project, which I think is PPro issue, several other projects that I either imported, opened up with, or started in PPro3 have not exhibited any of past issues. There are things going on under the hood then. The only deal maker is that I'll have to use PPro3 for my next big project, which will gradually build and see what happens.

Otherwise, it's already useful in terms of cineform and short projects, even as a beta. It's just that you'll have to export a CFHD and use the usual third party tools to make a decent DVD. That's the other half of the problem (will an embedded encore engine save the day?). We won't find out until someone shells out the bucks, crosses their fingers and hits the render button.

I see the light...

Opened a Cineform project in PP3 and it didn't crash when color correcting!!

I have hope.

Another soul cured by cineform therapy!

Hello world. I've just finished my first full-blown cineform project in PPro3 preview. Not a critical or high value project, but an internal one. A 55 minute sales event for training purposes.

My project specs and requirements:

55 minute video of 10 parts or scenes
720p 8bit, high quality HD Prospect workflow (progressive capture and convert from HDV)
Publish to DVD (build within Encore 2)
Complete with motion menu's and transitions.

Cutting to the chase, the only issue I ran across was that after initial capture, cineform quit encoding about twenty minutes in to the media. Even HDLink failed, capturing only 2minutes of material. Funny enough, PPro2 captured and encoded flawlessly.

I was able to import the media into PPro3 Prospect 720p project and edit as usual. I added a timecode filter, two layers of titles and a graphic layer for logo. I also changed levels and did some basic CC. Then rendered the 55minute timeline. I am happy to say that for the first time since PPro 1.5.1, I've been able to render off the entire piece in one shot (over a two-hour period). I went to lunch, came back and was pleased to see it still working. For some of you, including me, rendering a four-layer sequence that's longer than ten-minutes without lockup, crash, or having to re-do the encoded media files was a blessing.

There are some little unknown changes (if I understand them correctly). One being that mpeg previews are run off the timeline and handled (in the background) by the encore engine. It's not a dynamic link as with AE, it's just using the encore engine.

Some old legacy plugins have been removed (i.e. the "greenscreen") and replaced by AE originated plugins.

Timelines are different somehow. If you open a PPro2 project with active timelines, they come up empty in PPro3. Double-clicking the sequences in the bin, reopens new timelines. I speculate much has been done to the core and how memory is handled.

The code now uses all processor cores/threads. Some users think it's a bug! (I can't play call of duty2 during renders anymore! Wah! :)

PPro3 is expected to handle AVCHD when released.

HDV indexing will be handled on the fly, during capture, rather than as a post process.

Since you can't test, edit, or mess with anything HDV (ala mpeg), the beta preview is useless for HD work, unless you have cineform :) Now, I'm being careful here, and I have to back this up with more projects. In light of my PPro2 issues, I may as well keeping working with PPro3 until it's release!

What remains to be seen is just how much better PPro3 will handle HDV in it's native format. Regardless, with cineform, it's no longer a concern for me.

Looking good Peter

Really hoping to simplify my workflow on PPCS3 release but so far this is working fine. (Fingers crossed again)

Xh-A1 -> HDVSplit (Low end laptop) -> MPEGStreamclip (fix timecodes only) -> HDlink (AspectHD) -> PPCS3 -> DebugMode frameserve -> Tmpgenc Express (resize & compress) -> Encore2 -> SD DVD Image File (ISO) -> Primera duplicator -> Very nice SD DVDs

Interesting, Peter.

I could well find myself finishing editing my film using the FREE PPROCS3 rather than the rather tedious and expensive journey called Prem 6,6.5,Pro1.5,Pro2 :(

I'll do me some testing tonight. I have 6 x 20 min projects which is actually just one movie (split out as it would constantly grind to a halt in PPRO2) - so I'll rejoin them back and see how PPROCS3 handles a movie-length project with Deinterlacing/Colour Correcting/MB Looks on every clip!

I did notice though that in my PPROCS3 timeline that some standard PAL DV clips in my 1080 50i CFHD project were marked as 'Offline' (it's CCTV footage) - I might have to re-import them I guess...

I DO like the look of DebugMode Frameserve - tried it the other day. Cuts down on HDD usage - does it have any other benefits? (Is Framserve equivalent of using lossless?).

So, it looks like Adobe have fixed their memory leak bugs, and are charging us $300 for the privilege.

I DO like the look of DebugMode Frameserve - tried it the other day. Cuts down on HDD usage - does it have any other benefits? (Is Framserve equivalent of using lossless?).

I haven't seen any loss, although on the Debugmode site there is a mention of slightly lower color sampling. I keep trying to notice.

They say use the YUV export from Premiere and I do.

Looking good Peter

Really hoping to simplify my workflow on PPCS3 release but so far this is working fine. (Fingers crossed again)

Xh-A1 -> HDVSplit (Low end laptop) -> MPEGStreamclip (fix timecodes only) -> HDlink (AspectHD) -> PPCS3 -> DebugMode frameserve -> Tmpgenc Express (resize & compress) -> Encore2 -> SD DVD Image File (ISO) -> Primera duplicator -> Very nice SD DVDs

Brad, I haven't gone quite that far, as this project is an internal review job, and so a 480 progressive encode from 720p source is good enough.

Let's hope that handing off the transcoding chore from PPro to encore reduces some of those steps. I wish the folks at Adobe are listening/reading and understand how beneficial it would be to just add custom filters to their encoder. Then we wouldn't have to resort to 'freeware'. DVinfo forum is riddled with cookbooks on using third party tools, (Vdub saved my bacon more than once).

Douglas, I know where you're coming from. It can't hurt to import your problem project into PPro3 and give it a shot. Let me know how it went.

OK - My first proper tests using PPROCS3 with my Aspect HD movie project.

Copied my MB and BCC plugins across to the CS3 directories, as well as:
Adobe Premiere Pro 2.0\Settings\en_US\CineForm
Adobe Premiere Pro 2.0\Plug-ins\en_US\CineForm
Adobe Premiere Pro 2.0\Plug-ins\en_US\Editing Modes\CineForm Editing Modes.xml

Opened PPRO2 project in PPROCS3 - saved to a new directory. Ensured all scratch disks were pointing to new (empty) directory.

On opening project it went ahead and conformed all the audio again (when you have thousands of clips it takes ages) - a pain in the proverbial, but at least it only does this once.

Project has one timeline, 1hr 11 mins long. Tried rendering out - this hung only a couple of mins in - couldn't handle the title sequence which is CFHD clip (slowed, Colorista and MB Looks) layered with 4 title clips, each with BCC burnt film. Not really a surprise as PPRO2 refused to render this unless I render each layered at a time.

So, ignoring that part of the timeline I attempted to render the rest - errored out "Error Compiling Movie" (nooooooo!) at a still in the timeline. Restarted PC and re-rendered just this part, and no complaints.

Don't bother running any other aps while PPROCS3 is open - the screen flickers badly... hmmm. I've not noticed this on PPRO2.

I guess the main reason rendering is a wee bit quicker is that it's able to hog more of the processor! It stays around the 80-98% mark while rendering. (most likely as I have dual core, and PPRO2 was only using one CPU? I'm guessing)

The useful Video and Audio Usage details for items in the Project Bins is not there - and you can't right-click on items in the Project view either - hmmm (Properties is still gettable from File->Properties->Selected).

My system is 4GB AMD X2 3800+ XP Pro SP2 NVidia 7900GS - so it's not a slouch... but it feels like one when editing with PPROCS3!

Have kicked off another, bigger render (not titles or stills) - so will report back once that's completed.

PS - Another gripe from PPRO2 hasn't been touched... the fact that you can't find the original location of an Offline file - so say you've mistakenly deleted or renamed a folder and now your 01 Track 01.wav is offline, and you have several 01 Track 01.wav in your foley database (as you do if you rip your sound libraries from audio CDs) - you're stuffed.

This is probably silly to mention, but since I knew better and still didn't do it...

A lot of my problems with Premiere (especially title sequences) disappeared with regular defrags.

I know you have to do it, every board reminds you, but I was annoyed at the inconvenience and kept putting it off. Now it's an overnight thing.

Undoubtedly not a factor here, but thought I'd bring it up anyway

Hmmm - just trying once more to render out that title sequence (first disabled the titles and rendered the video clip) - then Enabled the 4 layered titles and it's hung half way through rendering - I'm unable to Cancel the Render, showing as Not Responding in Task Manager and 0% CPU.

Have recently defragged HDD, and I recognise this behaviour from PPRO2. Maybe I should actually post these findings on the Adobe board instead of complaining about them here!

Defrag, yes. PPro3 will use all of the resources, so go for lunch or do something else.

You're PPro2 project maybe corrupt. You may have to rebuild the problem spots in PPro3 if you can't work around it.

Going avi wrapper (with cineform encode) vs. direct CFHD may fix. Lower the rez from High quality to medium quality may help also.

Originally created projects in PPro3 are not showing the same issues. Importing PPro2 is a mixed bag, some work, others don't.

BTW, FWIW, Adobe techs mentioned that PPro3 projects are backwards compatible, and can be opened in PPro2 (minus PPro3 special features).

Another user on the adobe forum has reported that you can regain Mpeg usage in PPro3 if you copy the "mainconcept" plugins/files like we did with cinforms.

You can no-longer render directly to a DVD from the timeline. You have to pre-encode the sequence and hand that off to encore. Lost functionality. In light of all this 'dynamic linking', why?

In the final analysis, I'm not entirely happy nor relieved with having to use unfinished beta software on mission critical projects.

I also had the "error compiling movie" on an imported 1080i clip, which I wanted to render to 480p widescreen. Choosing the avi wrapper with Cineform encoder; Medium quality, RBG color and progessive, worked.

If you can't go directly to CFHD, then try the wrapper.

FYI, Prospect 2K trail is in. Time to give that a go. I'll install tonight.

Peter - I'm getting these errors when rendering the timeline (haven't even tried a long export yet).

Kicked off a big render overnight and it failed 4 hrs in (although I'm coming to the conclusion that adding FX and rendering to preview is a bad idea for the whole project... and I should just leave the rendering to the export stage - where perhaps Frameserver or avi w/cf wrapper might do the trick!).

I'll try adding the other 3 projects to this one - to make it the whole movie... that'll tell me whether standard scrubbing is still buggy and memory leaks etc have been fixed.

So, have combined my 4 split smaller projects into one large PPROCS3 project. Size of prproj file is now 71MB.

Basically thousands of clips (about 800GB of CFHD avis indexed) - waited ages for the audio to conform - editing during this process is possible, but unreliable and slow.

So far, so good though. Will report back.

Right-clicking on an item in the Project window only works when you click on the same line to the right of the item (ie. not under the Name column).

So far the only downside I can find is the inability to edit audio in Audition/Soundbooth from right-clicking on the audio - disabled in this Beta :(

Douglas, I have a project file that is repeatedly getting the "error compliling movie". The only fix for that, and for an earlier, more intense project was to use the "microsoft avi" choosing the cineform encoder, and in settings, selecting "medium", and "automatic".

This has worked consistently so, that when I can export CFHD, I just go the other route. Nothing else short of uncompressed worked. I could not even push an adobe M2t. It's not a cineform issue. My best guess that however PPro2 writes the project file, some specific code is readable in PPro3 (not changed) and what causes PPro2 to crash does so with PPro3.

I have an employee two-day soccer tournament that is waiting for edits. About 8-hours of HDV material. It's not mission critical, (unless you ask the players whom keep knocking at my door, or droping me hints). This weekend my wife is going out of town... the new Prospect 2K is in... The beer (edit juice) is getting cold...

It's time to see if I can crash this application, (not that I'm tired of hearing "...I fixed my PPro woes by switching to Vegas, and my world is now a complete utopia... ahhh."). But I have yet to real test this application.

Prospect 2k installed without issue. Though I get a dialog box for v2.3 when PPro3 starts, I'm sure it's 2k v3, checking registry and dll's confirms this.

Hmmm. Upconvert 4:2:2 to 4:4:4 RGB? I smell an HD-SDI test during tommorrows lunch break. Time to test that greenscreen I've been putting off.

My troublesome projects are on the BOXX in the studio. My Dell 650 w/Dual Xeon 3Ghz is running fine. Not too bad for Min. spec. No playback or render issues so far. In fact, I'm seeing a few more layers in RT. Before I swore only the video showed in RT, now I'm getting two more layers of titles in RT.

So if PPro3 is using more threads, it looks like Prospect 2K is also doing the same and thus it's a 30% gain in performance? I haven't loading this up on the other machine. I'm gonna pay close attention and do a comparison.

It's late, as my two year old says: nigh-nigh.

Peter, where are you seeing the "v2.3" text? I need to update that.

As for the "Upconvert 4:2:2 to 4:4:4 RGB", also experiment with the 4:4:4 rendering options in the compiler options. Put some red titles on a blue background to really see the benefits.

David

1. Yes, it's the "2.3" text on splash screen. (HDlink's splash shows it correctly with the new graphic and version). Can we get that fixed so I can proceed with the render? (Kidding :)

2. Ok, you asked for it.

Peter you may not be running PHD v3.0 within CS3. The splash should say 3.0 as it does on my home PC (and show the film reel.) This is like an install issue with CS3 and PPro2.0 installed, new components only go into one Premiere installation. See if the new files went into the 2.0 plugins fonder, if so copy them into CS3.

Yes, that was the case, sorry. I just installed on my BOXX, and it went into PPro3. I then copied to PPro2.

I am happy to report that my particularly troublesome PPro2 project managed to render a High quality CFHD right over the troubled areas, and within PPro2! I did not have use the wrapper, nor export to PPro3.

I imported the PPro2 file into PPro3 for testing, and the app crashed (processors spiked, PPro3 disappeared) right at particular spot with three layers of high-rez tiffs. Even scrubbing over that spot in PPro3 crashed.

However, in defense of PPro3, a particular PPro3 originated project, where I had a similiar sequence that refused export directly to CFHD, I was able to so with Prospect 2X 3.0.

It's a little early, however, it looks like I can now render troublesome PPro2 projects without having to export them to PPro3, or an elaborate workaround.

Douglas, it might be worth a shot to use the P2K trial and see if you can put an end to your rendering woes. I can put this particular project to bed and move on!

BTW, when I fired up HDlink PK2, I was surprised to see a capture window pop up for my Xena card. I've gotta try some 444 capture next.

Handling large TIFFs (or images in general) is a bug in CS3, it will crash in the non-CineForm edit mode. To increase the importance of adobe fixing this, please submit a bug report. Note: turning off 32-bit processing will help, but that is only a poor workaround.

4:4:4 is not offered as a capture format yet. When it is it will be in the Wafian HR-2, Prospect 2K Ingest and NEO 2K Ingest only. 4:4:4 support is currently geared toward file based workflow (DPX, TGA, TIFF, etc) and for the highest quality effects rendering.

1. Verified and Bug'd. Even if it doesn't crash, just place some moderately size tiffs on four or more layers deep, add a few cross disolves, and preview render the timeline and playback in the monitor is erractic. (Bug'd that one too).

2. I meant to capture 4:2:2 SDI and upconvert to 4:4:4 (forgot to bring my viper in... must have left it in on the dresser at home :)

Dave, I couldn't get PPro2 or 3 to capture live from the XHG1 via Xena HS. I can see the output image, via monitor from the Xena card. Xena, adobe project and cineform settings are 1080i 60Hz (SDI port is also enabled on the Canon and set to HD, auto). Adobes' HD-SDI edit mode did not work either. Nor would HDLink. It recognizes the card, but there was no image.

I ran out of time, and will reinstall/update the Xena drivers tommorrow.

How are you connecting your Canon via SDI?

Make sure you are using the Xena drivers shipped with Prospect. These are located in C:\Program Files\CineForm\AJAIO.

Cineform specific Xena drivers? Maybe I should have read the instructions first :)

Will do.

Installing the cineform version of Xena drivers did the trick. We're in business. I'm now keying 10bit 4:2:2 HD-SDI material in PPro3.

I'm having some fun with PPro3 and the new Prospect 2k.

I have about eight-hours of soccer video to cut, but decided to do something a little more interesting. A VFX project to put this software through it's paces. (It's been a long while since I've working on something this heavy without one single incident).

I've provided some media here, and I know it does little justice for the original content, which is simply beautiful. Capturing 4:2:2 HD-SDI that keys at uncompressed quality, yet acts and plays at the speed of compressed? A quality that is imperceivable from the original, exported to AE and back again for final edit... amazing.

If you want something higher rez (or different from divX), I'll have to find another means to upload an m2t file.

http://stage6.divx.com/user/peferling/video/1207535/Transporter-FX;-testing-cineform-plugin

The forum was having issues, and I was not able to load these screen captures in the last post:

(Any recommendations as to where I can load some higher rez m2t clips?)

Dave, is there anything you'd like me to test?

I haven't attempted a "PK2" sized project. I'm assuming it's the upconvering of the 444 from HDSDI 422 that matters, as I'm limited to 1080i. My concerns about stability in my own work have been answered thus far.

For straight capture, cut and render (minus the mpeg stuff), I'm pleased with this 'beta', and it's easy to forget that it's still a 'beta'.

I use YouSendIt.com for large files.

Peter, you been doing so many excellent tests it is hard to think what to add.

Have you tried the 4:4:4 export option with red titles on blue backward or any other difficult color combination. When do the same using 4:2:2, and compare with the source timeline. You can try the 4:2:2 -> 4:4:4 filter option to see it impact on the 4:2:2 material.

Steve, I'll check out yousendit.com thanks.

David, I'll give that a shot.

BTW, I ran into two issues:

In P2k (1080i HDSDI) with PPro3 project. Imported a 979x979 jpeg image, went to apply a title and noticed that the title tool is wayyyy slow in opening vs. an Adobe HD-SDI project (desktop). About a ten-seconds longer.

Also, toggling the safe margins button in the preview monitor more than three times caused the app to crash. I also had to reboot as the safe margin would not go away via the AJA on the external monitor. It was stuck in perpetual memory. The video would redraw correctly, and yet the margins remained on the monitor.

PPro3 reflects the wrong data for image pixel depth (that's already been reported). I have not heard anything about the large tiff issues from Adobe either.