Speaking of DSLR files, Adobe has totally reinvented the way they are handled in CS5.  Most applications, including the CS3 and CS4 versions of both Premiere and After Effects, use QuickTime importers to access the content of Canon DSLR files.  This makes sense, since they are stored in an MOV wrapper, but leads to two issues.  One is that is specific to Adobe is that on a PC, QuickTime files go through a few extra steps before they are accessed by the application, so there is a performance hit, and with lots of files accessed at once, there are usually stability issues as well.  The other issue effects all applications that use QuickTime to access DSLR files, and that is that ever since QuickTime 7.6.2 was released, Canon DSLR files have been decoded in a much more flat and washed out color space than they were designed to be viewed in.  Prior to version 7.6.2, they were decoded in a way that clipped the highlights and shadows, which was even worse.  In CS5, Adobe worked with Mainconcept to create an importer that reads the DSLR source files without involving QuickTime at all.  This alleviates both the performance hit on PC systems, and the color space issues of QuickTime’s default decoding.  A lot of work was put into getting the decode matrix and color space exactly correct based on the processing that Canon’s hardware does to the file in the camera.  This should allow CS5 to decode the files more correctly than any other application that I am aware of, and give more options for color processing at later stages in the workflow pipeline, since more of the original color data is preserved.

The Mercury playback engine has a significant impact on the user experience, with most frequently used tools being available in real time.  Supposedly most of the decode and playback improvements are based on the new code written for native 64bit execution, with the GPU offload limited to effects processing.  While many editors don’t use very many discrete effects in their work, there are some intrinsic playback functions like scaling frame sizes and adapting frame rates that are considered effects and offloaded to the GPU.  This allows content of different frame rates and resolutions to be intercut seamlessly on the timeline, and it is truly seamless.

I have occasionally found myself editing in the wrong sequence frame rate without even noticing it, since the software makes the conversion on the fly.  Even more frequently I have found a clip shot in the wrong frame rate on a tapeless camera almost escaping detection because gone are the red render bars and playback glitches that used to stand out.  This allows editors to import media from many different sources without prerendering everything to a normalized format.  I used to spend about a quarter of my time at work converting strange source footage into 1080p24 intermediate files, because any footage not matching the timeline format would cause previous versions of Premiere to glitch during playback and occasionally crash.  Now I would recommend carefully converting any footage used in a final piece to the correct format for maximum control, but this step can now be put off until the online stage, since it is no longer required for playback and stability.  Since 90% of footage usually ends up on the cutting room floor, putting off these time consuming conversions until after the creative edit is finished, will drastically reduce the amount of footage you end up needing to process.

So this clear increase in performance leads to the question of: how far can you push it?  A few months back I processed an ISO noise test in After Effects CS4 for Shane Hurlbut.  We were comparing the image noise produced at twelve different ISO levels on the Canon 5D, and the project involved twelve streams of video with masks, levels, and position adjustments for a tiled view.  I was getting about two frames per second when rendering previews, which seemed reasonable considering the amount of processing involved.  When I saw the list of GPU accelerated effects in Premiere Pro CS5, and was asked to create torture test for Adobe to show off at NAB, this jumped to mind.  I recreated the entire project, using twelve layers of native DSLR footage, each layer having a motion effect and a 4-point garbage matte to create the tiling, and a color correction applied to exaggerate the noise to a clearly viewable level.  The same basic setup that was getting 2fps in AE CS4 played back in real-time in Premiere Pro CS5.  (Dual Xeon X5365 CPUs and 16GB RAM with a QuadroFX 4800) Needless to say I was quite impressed with the outcome, since it was deliberately beyond Adobe’s ten-layer playback claim, and using a complex format to decode and playback.  Clearly GPU acceleration can have a dramatic impact on application performance.

There has been much discussion and debate on tech forums and blogs about the specifics of Premiere Pro’s hardware support for CUDA acceleration.  Adobe has severely restricted the number of cards for which they officially support CUDA based GPU acceleration, to maintain control over the hardware environments upon which their accelerated code is tested, supposedly for stability reasons.  The official list is limited to QuadroFX 3800, 4800, and 5800, as well of the discontinued GeForce 285 GTX, with certain limitations, for those on a lower budget.  There are currently no officially supported mobile GPUs, even though notebook CPUs are usually more in need of a performance boost than desktop chips.  This may be due to the fact that even the newest mobile QuadroFX 3800M is still based on the G92 core from the GeForce 8000 series, but I don’t like seeing software artificially limited in regards to performance or hardware support, and this is an example of both.  Don’t confuse legitimate limitations and artificial limitations, since clearly a powerful GPU is necessary for optimal performance in CS5, but there are cards of equal capability that are specifically excluded from the list, supposedly for stability reasons.  Luckily Adobe has left an option for knowledgeable users to override some of those artificial limitations, and I anticipate seeing them being dropped completely in a future update.  I anticipate a more reasonable requirement of any NVidia card supporting CUDA 1.1 or 1.3, with at least 785MB of video memory, at some point in the future.

While Premiere Pro CS5 is not perfect, it is a complete reversal from the previous fiasco that was CS4.  It clearly demonstrates the possibilities provided by GPU acceleration, resting solidly on 64bit code with proper multithreaded programming, it scales to take advantage of whatever hardware is made available for it.  Since Adobe has made a practice of introducing significant improvements in incremental dot releases, I am looking forward to seeing how else they refine it in the coming months.

FTC Disclosure: I have been on Adobe’s beta team for many years, and Adobe has provided me a copy of CS5 for this review.  NVidia has provided me with graphics hardware in the past, which I utilized in this review.  My only admitted personal bias is my preference of Windows over OSX, because I like full control over every aspect of my computing experience.  If for some reason that bothers anyone, there are plenty of other sources of information on the internet, but I try to provide unique insight on how each of these tools fits into the larger post-production picture.  Any relevant critique or response is welcomed.

The other major new feature for this release of After Effects is the Rotobrush.  Based on Photoshop image processing functionality, extended to account for the information made available from multiple frames, this is the closest thing you are going to find to magic in a current generation compositing application.  It allows you to automatically separate foreground and background objects in a video image, otherwise known as rotoscoping.  Of course it is not perfect, but it is a huge advance, compared to previous tools.  Automated tools like this are usually much more impressive if you aren’t expecting a miracle going into the process, but as long as you have reasonable expectations, Rotobrush can give you usable results in a rush, or a good starting point when more precise work is required.  Much of the “magic” of the new tool is in the processing of the automatically defined edges, and this capability is available without using the Rotobrush, in the form of the “Refine Matte” effect.  This effect can be used to polish the edges of standard keys, or manually rotoscoped footage.  Most of the other major feature enhancements for this release come in the form of integrated third party plug-ins, including Color Finesse for grading, Mocha for tracking, and DigiEffects Freeform for 3D simulation.  Each of these are feature rich plug-ins that include functionality that is beyond the scope of this overview, but are well worth experimenting with if you spend a lot of time working in After Effects.

There are quite a few new features in Premiere Pro CS5 that don’t hinge on the new Mercury Playback Engine.  These relate primarily to metadata and content organization, as opposed to the media itself.  Speech detection tools were introduced in CS4, and now those can be used in conjunction with the features of Adobe Story, to link your actual footage to your original plans, including scripts, storyboards, and shot lists.  Much of this footage processing links to OnLocation CS5′s features, which besides monitoring the technical details of a captured media signal, allow ingest of metadata during the acquisition process.  Building up as much information as possible during production, on a per-shot and per-take basis, will further streamline the organization process during editorial.  All of this information is searchable, with the intent being that an editor will have a much easier time finding what they are looking for, as this metadata is passed down throughout the post production workflow, based on source timecode.  This content logging metadata is not the only way that CS5′s handling of non-media information has improved.

Adobe has also been working hard to streamline the process of exchanging existing projects with Premiere from Final Cut Pro and Avid Media Composer.  They have further refined the FCP XML import and export functionality that was first introduced in version 4.0.1, which offers some interesting options for Mac based workflows.  Working at a PC based facility, I have had more opportunity to take advantage of Premiere’s support for exchanging timelines with Avid.  My current workflow is to use EDLs to move my sequences from Avid to Premiere, but with CS5′s improved support for AAF import and export, hopefully I will soon be able to leverage the additional functionality offered by AAF exchange.  (One caveat with using EDLs to move sequences, is that occasionally Avid adds spaces to the end of every line, and CS5 will not relink to the source footage automatically, unless you manually remove those spaces)  I have yet to find the optimal settings to switch to AAF files, but I have talked with people who have it up and running.  Combining this sequences exchanging feature with CS5′s support for DNxHD in both MXF and MOV wrappers, offers some interesting possibilities, but the truly revolutionary workflow will finally arrive when Media Composer 5 is released next month, allowing Avid to link to external QuickTime files thru AMA.  Hopefully this will allow Premiere Pro CS5 and Media Composer 5 to exchange sequences that all reference the same source files, without any conversions or transcoding.  Since Canon DSLR files will be supported natively both applications, this should totally streamline my current workflow.

Now why would someone want to move their project between different NLE applications?  An editor’s familiarity with a specific toolset is usually important to them, so certain offline creative editors are not going to switch their primary editorial app no matter what.  To its credit, Avid has a solid reputation for handling extremely large projects with no decrease in performance.  While Premiere Pro has taken a huge step forward in that regard, it is going to take a long time for it to build a stable reputation, since trust usually develops very slowly.  On the other hand, Premiere makes a perfect interactive online conform tool, especially compared to Avid.  It can ingest most digital formats in their native form, supports SDI capture and playback over a number of different hardware solutions, and scales to 2K and 4K resolutions, in RGB color space if desired.  It is compatible with DPXs for color grading, and can playback surround sound for reviewing final mixes.  The fact that Premiere can use Dynamic Link to ingest your visual effects changes from After Effects, and to output to Encore for adding interaction becomes an added bonus for this conform solution.

Dynamic Link is now on its fourth iteration, and has matured into a functional tool, even at HD resolutions.  It is designed exchange media between apps, without having to waste time or disk space by rendering.  While it started as a method for importing AE comps into PPro, it became the backbone of PPro’s export capabilities thru Adobe Media Encoder as well.  While Media Encoder CS5 is a dramatic improvement from the previous version, Adobe also added back in the option to export files directly from within Premiere.  This is much quicker for rendering out small parts of large projects, avoiding the overhead of syncing the entire project with Media Encoder before rendering a couple of frames.  They also brought back the ability to easily export single frames from the timeline, a function that had been removed in CS4, an inexcusable oversight that has now been rectified.  Exporting a Premiere Pro sequence thru Media Encoder, while not transparent, is now a much faster and more stabile process than it was in CS4.  Media Encoder also now supports DPX sequences and AVC-Intra MXF files, for both input and output.  Still sequence support in both Premiere Pro and Media Encoder is still missing crucial options, for relinking footage in PPro and manually overriding the frame rate in AME.  Hopefully we will have more user control of these settings in future versions.

One thing that I would like to see handled differently in Media Encoder, as well as the Premiere exporter, is the default settings for each export plug-in.  Adobe is never going to be able to predict what settings every user is going to want, but it would be nice if it defaulted to whatever I selected last time I used that particular output option.  As it stands, Media Encoder defaults to the same output as the last file queued, but if I choose any other output (AVI, MOV, DPX) it returns all of the individual settings to the original default, which is usually DV based.  Now it is possible to save presets, but I hesitate to do so unless I anticipate using that exact configuration frequently, because sorting through too many presets can become harder than manually defining the individual settings.  On a relate note, be careful where you save your .prproj files, since selecting “Save As” does not default to the current project location as it should.  Instead it defaults to the folder containing the last piece of media that you imported.  I usually follow a strict project organizational pattern, but I have saved projects in the wrong folders daily since switching to CS5 thanks to this “feature.”  Hopefully this can be fixed in a minor update.

Now a subsidiary application to Premiere Pro, Encore CS5 is the next logical step in that application’s evolution as an interactive authoring tool.  The most significant new feature for larger productions would have to be support for DDP output, so that your Encore projects can now be replicated at a professional facility without any special hardware required on the authoring side.  Adobe has also continued to develop the Flash export options, allowing Encore users to output their interactive experiences directly to the web, now with most of the BluRay interactivity features, including the new multipage menus, supported as well.  Encore projects are now completely cross platform compatible, between the Mac and PC versions.  There is also better support for 23.976p and 24p source files, and an easier subtitling process.  AVCHD files can now be authored directly to BluRay discs without any transcoding, decreasing processing time, and increasing output quality.

Previous versions of Encore have used Dynamic Link to import Premiere Pro sequences as source clips, and more significantly in my opinion, to import After Effects compositions as motion menu backgrounds.  I was never really that impressed by Dynamic Link for Encore source clips, because your Premiere Pro sequence is usually finished by the time you make a DVD, and since you are going to have to transcode to MPEG2 at some point anyway, little time is saved.  Motion menu design on the other hand seems like a much better fit for the workflow benefits offered by Dynamic Link, since the menu needs to be edited in both Encore and AE during the authoring process.  Encore now also uses Dynamic Link to offload transcoding of those sequences, or any other incompatible source footage, to Adobe Media Encoder.  This will free up Encore to continue interactive authoring work, while asset transcoding proceeds in the background, and also allows third party accelerated encoding plug-ins that are compatible with Adobe Media Encoder, to be utilized for these internal transcodes.  While I am unaware of any CS5 compatible encoders, this was an issue with the Elemental Accelerator in CS4.  The files it generated at 24p were re-transcoded in Encore anyway, and Encore couldn’t utilize the accelerated plug-in directly.  Anyhow, while no CS5 version of Elemental Accelerator has been announced, Matrox’s CompressHD should be able to accelerate Encore’s BluRay H.264 encodes, once Matrox releases CS5 compatible drivers.

The one thing still missing from the Adobe package is a good intermediate format for exchanging files between other applications, systems, or facilities.  This capability is available from 3rd parties like Cineform or Matrox, but until Adobe integrates support for one directly into the suite, there will not be a single universal standard format, that can be counted on to be compatible everywhere.  It needs to be compatible with both Mac and PC, and store at least 10 bit HD footage with sufficient compression to playback smoothly on a laptop.  Apple and Avid have both recognized this need, and developed ProRes and DNxHD respectively.  AVC-Intra is Adobe’s current recommendation to meet those workflow needs, but that format has a complicated file structure, and is not a codec optimized for smooth playback.  This universal format would tie in well with OnLocation, if Adobe ever added support for HD-SDI capture capabilities.  That would allow ingest, either live or from tape playback, into a compressed format for editorial, with log notes entered in real-time similar to their current tapeless solution options.  And if a professional selection of scopes could be viewed of the SDI input signal, you would have an all-in-one onset workstation solution.  OnLocation CS5 currently offers most of these capabilities, but is limited to HDV, XDCam, and P2 acquisition for most of its features.  Oh, and if it supported my Canon DSLR, that would be pretty cool too; maybe next time.

As a whole the CS5 release is a major turning point for Adobe, especially with the problems their users experienced with CS4.  While I don’t yet fully utilize many of the new features, CS5 has already revolutionized the way I work.  Premiere Pro CS5 has replaced After Effects CS4 as central application from which I manage my projects.  I was lucky enough to be on the beta team, so most of the major issues I encountered with the software in my specific workflow, have already been resolved during the development process.  While CS5 is by no means perfect, it is a huge step forward that will begin to rebuild user confidence in Adobe products.  Once third party hardware and plug-ins have had time to be updated to be compatible with the new 64bit native applications, I see no other disadvantages or caveats to upgrading to CS5, which I highly recommend.

FTC Disclosure: I have been on Adobe’s beta team for many years, and Adobe has provided me a copy of CS5 for this review.  My only admitted personal bias is my preference of Windows over OSX, because I like full control over every aspect of my computing experience.  If for some reason that bothers anyone, there are plenty of other sources of information on the internet, but I try to provide unique insight on how each of these tools fits into the larger post-production picture.  Any relevant critique or response is welcomed.

Adobe announced all of the features of the new highly anticipated Creative Suite CS5, which will include native 64bit, CUDA GPU acceleration, and better support for formats like DPX and DSLR clips.  I will have many more CS5 details in future posts, delving into how that will change the landscape of many workflows.  There are lots more new developments in the post world, but those are the primary things that stick out to me right now.  We still have two more days, and I will be spending a good bit of time demonstration Cineform’s Neo3D features at their booth at the back of the Lower South Hall.  So if anyone wants to catch up with me, feel free to stop by.

Blackmagic Design has a lot of new products available, many utilizing SDI over fibre optic cable.  It is a pretty straightforward idea, but since fibre is even more expensive than BNC cables, I personally will have little use for it in the near future.  Their new UltraScope product is very exciting, and if it works as well as advertised, fills a big hole in the market.  Most other HD-SDI scope products are in the five figure range, so a $700 solution will be a very welcome option.  They also have two new variations to their Videohub line, the Enterprise version with 144/288 I/O channels, and the more reasonable Studio version with 16/32 channels.  I have filled our old 12/24 channel original model Videohub at Bandito Brothers to capacity with about 8 edit stations and the supporting equipment.  But between having 33% more connections, and 3Gb SDI support to avoid wasting two channels at a time, the new version would probably support facilities twice as large.

Thats all for now, as I have to prepare for another big day, but I will be checking in with my friends at AJA, Matrox, Sony, and maybe even Avid over the course of the week here.

Other new features in Photoshop CS4 that require OpenGL acceleration will benefit work on even regular sized images.  Images viewed at magnification levels that are not even multiples (1/2, 1/4, etc.) are now displayed at much higher quality, as well as being much faster and more fluid, since the preview is being scaled in the graphics card.  You can smoothly zoom to any level instead of the previous default 100%, 50%, 33%, etc. and the image will look perfectly clear.  You can also rotate the previewing plane without permanently effecting the image quality or dimensions, and continue to interact with the image at that angle.  Although it initially seems trivial, after a bit of thought I can conjure up a variety of important but obscure uses for this capability, most of which relate more to art and design than video post-production.  There is also a new pixel grid that is available to clearly dilineating the boundaries between individual pixels at extremely close zoom levels (>600%)  I am honestly not sure why this requires GPU acceleration, but it is unavailable unless you have a supported OpenGL graphics card.  My only complaint about the new functionality and acceleration found in Photoshop CS4 is that Adobe saw fit to specifically skip its implementation in the 64bit version of Windows XP.  Since this is the highest performing version of Windows available, Adobe’s failure to directly support it will cause its users continued frusteration for some time to come.

The only possible relief on the horizon in that regard is that Windows 7 seems to have been fast-tracked by Microsoft due to the Vista issues.  Speaking of future developments, hopefully we will soon be able to display 10bit color from Photoshop onto a Dreamcolor LCD via DisplayPort.  I suspect that this may not be available until CS5, but I am sure it is coming, based on the increasing level of hardware support on products that are now coming to market, with the Quadro CX leading the way.

Adobe has added many minor tweaks and improvements to all of their apps in CS4.  My favorite so far would be the new Adobe Media Encoder, which allows you to render and encode Premiere Pro and After Effects sequences  in the background, while you continue to work in the applications themselves.  This should help finally utilize all those extra CPU cores we all have buried in our systems.  There is also supposed to be more support for 64bit processing, especially in Photoshop.  The speech to text engine and enhanced dynamic link are the other features Adobe has been highlighting, but I don’t have as much use for those personally.  One thing that has been made clear by third parties, is that Premiere Pro is not finished, and that we should expect a major update soon.  I am not sure which details of that have been made public, but until that release, most third party extensions of Premiere will not be compatible with CS4.  Specifically I am awaiting support from Cineform for ProspectHD/4K, and from Matrox for the AXIO line of products.  Both companies have stated that their software will require support from the extended SDK in the update, so stay tuned for any news on that from Adobe in the near future.

The announcement of NVidia’s new high end GPU, the Quadro CX came as a bit of a surprise to me, since I had seen the specifications for what I believe will be the Quadro 5800, which should include 4GB of memory, and will be found in the new QuadroPlex.  The new Quadro CX card is very similar to the current Quadro 5600, with 1.5 GB of memory, and supports the same SDI daughter card, for broadcast preview and output.  This brings to mind the way that the GeForce9 series of consumer graphics cards were very similar to the previous line of GeForce8 cards.  The new Quadro CX seems most closely related to the Geforce 260 on the consumer side, but with a lower memory bandwidth for some reason.  One key new feature is the edition of DisplayPort output, which is made even more significant by the fact that is supports true 10bit color.  When combined with the new HP Dreamcolor LCD or similar display, this should allow true 10bit display of HD or 2K content without the need for expensive SDI interfaced components.  This is especially critical for desktop based color correction applications, many of which have been written specifically to be run on NVidia Quadro hardware.

Between better multithreading, and more use of the GPU, we should see significant performance increases.  The possibility of 10bit color out of CS4 is exciting as well, but I have not heard any details about that.  I have recently received one of the HP Dreamcolor displays, so I plan to post some info from my experience with that soon.

Apple recently released a free ProRes playback decoder for both OSX and Windows, which is pretty significant.  This with allow Final Cut Pro editors to share their footage using this efficient codec with Windows users and Mac users who don’t have Final Cut Pro.  Since there is still no way to encode to ProRes on PC, another format is still required to get footage back from the PC to the Mac.

Reading between the lines of some of NVidia’s Nvision, I believe I have acertained the specs on Nvidia’s next top end workstation graphics card.  The NVidia Quadro FX 5800 will have 4GB of memory, with a PCI-Express 2.0 interface, for 8GB/sec of bandwidth in both directions.  It should have two dual link DVI connectors and one DisplayPort connector, besides the usual Quadro stereo port.  It should support SLI Mosaic Mode, using four connections from two cards to support a four quadrant image, which will eventually allow full resolution display of 4K footage in realtime.

Speaking of 4K, Red has announced that Adobe will be releasing a plugin to edit R3D files natively in the CS3 suite of applications.  Coinciding with that due to the release of the first version of the Red SDK, Cineform has finally released an “official” version of their Red4K convertor.  They have also begun to advocate an offline/online workflow for the first time, under the brand name of Cineform Express.  My only comment is, once Adobe supports Red natively, shouldn’t the online be done straight from the R3D files?  In a perfect world, a Cineform offline with a relink to R3D files, exported as an EDL to SpeedGrade for color would be the ideal way to do post with Red footage.  If only life was that simple; maybe someday it will be.

Blackmagic has a number of new mini-convertors for analog component HD, HDMI, and HD-SDI, as well as an updated and expanded Video hub. The new “Broadcast” Video Hub is in a whole new category, increasing sixfold from 12×24 to 72×144 inputs/outputs, while adding support for 3Gb SDI.  They also released the BlackMagic Video Recorder, a micro sized H264-encoding HD capture device that offers component HD, and optionally SDI input, connected via USB.

Adobe has released another update for Premiere Pro CS3, so now we are at 3.2.0.  Among other smaller items, this update adds native support for XDCam-HD, and XDCam-EX, in all standard formats.  Adobe was much quicker to support Sony’s SxS solid state recording format than they were Panasonic’s P2 solid state format that had been out for two years.  On that note, I personally prefer the Sony varient for a number of reasons: modern ExpressCard interface, high transfer rate, 1080p cameras, etc.  Now we just need larger and much cheaper SxS cards.

Although I have yet to personally make it to that hall, I hear that Sony has a couple of cool new toys.  The PMW-EX3 extends their XDCam-EX line with a second model that adds support for interchangable lenses, capable of interfacing its 1/2″ imager with both 1/2″ and 2/3″ HD lenses.  There is also an XDCam-EX VTR, the EX30, which I anticipated was coming, but it seems that it is physically larger than I was hoping.  The EX format lends itself well to the creation of a small scale HD-SDI recording and playback device, which would pair well with a tiny HD-SDI camera.  They also seem to have finally finished their new XDCam-HD camera that records their new MPEG2-422 format to XD.   I expect that new 50Mb/s XDCam format will eventually be a broadcast HDCam replacement.  No 24p support there, so I won’t be using that format for a while, but we have seen that pattern before, and it will arrive eventually.

 Red also released details on their future products, but they aren’t due out until early 2009, so I will discuss those at a later date.

 AXIO 3.1 has few major improvements.  Besides overall stability improvements and bug fixes, Canon’s 25f HDV mode is now supported for you PAL folks, and AXIO systems are now compatible with Omneon media servers.  Nothing significant that effects the workflow of the other 95% of their users.

 Sony’s new HDV Cameras have a couple of interesting features.  The HVR-S270U is shoulder mount camcorder while the HVR-Z7U has the more usual ‘Handycam’ formfactor.  Both cameras use a similar imaging solution to the HVR-V1U, with three CMOS imagers at 1920×1080.  The larger HVR-S270U supports full sized DV cassettes, for over four hours of continuous recording, and has an HD-SDI output.  The smaller HVR-Z7U has a cheaper HDMI output instead of the SDI, and is limited to standard 1-hour MiniDV size cassettes.

The biggest feature that sets these two cameras apart is that they both use interchangable lenses.  Previously, the Canon XL-H1 was the only HDV camcorder to support this.  This is the primary feature that is missing from the new SxS flash media based XDCam camcorder, the Sony EX1.  Speaking of flash based recording, both of these cameras also support a new solid state recording accessory, the HVR-MRC1.  This little iPod sized device attaches to the side of the camera, and records the HDV stream directly to solid state CompactFlash memory cards, bypassing the tape entirely, but not the HDV compression.  CompactFlash cards are significantly cheaper than P2 or SxS cards, so I can see this becoming a very popular accessory.  Supposedly it interfaces directly with the new camcorders, but existing HDV camcorders can take advantage of it through the iLink or IEEE1394 firewire port, which transmits the HDV compressed stream live.  This would be similar to the disk based Firestore products, but with the added advantage of being a solid state solution.

The current Neo4K workflow is to use RedCine to export Cineform4K MOV files from the RedOne camera’s native R3D files.  These compressed files can be played in realtime, usually at 2K display resolution, in Premiere, AfterEffects, and a variety of other programs.  Filmout is the primary application for 4K finishing, and most filmout facilities are still going to require DPX files as the final step, but Cineform can be used for all of the steps prior to that point.  If they optimize their downsampled playback correctly, realtime CCR in Speedgrade should be possible in the near future, with 2K live playback and 4K renders.  Iridas needs to get Speedgrade working correctly in HD and 2K first though, before we get too far ahead of ourselves.

I Updated/Rewrote the following section Saturday morning after further testing and research:

I was able to download 2K and 4K R3D demo files directly from Red, and successfully imported them into RedCine.  I then was able to export them to Cineform2K and Cineform4K MOV files.  The 4K files took 4-6 seconds per frame to render, and the 2K took about 1 second per frame, on my dual 3.2Ghz Xeon workstation with my new 8800GTX GPU.  There is a known error in RedCine that prevents the encoding of files at exactly 4096 pixels wide, so testing is being done at 4088 pixels width instead.  I also converted the resulting MOV files to AVI, so I had four files to test, AVIs and MOVs at 2K and 4K.  After updating Quicktime at David Newman’s suggestion, all my files worked in both Premiere Pro (Prospect2K project) and in AfterEffects.  The 4K files do not really playback in Premiere, but you can scrub them.  In AE, I get 2fps at 4K in full quality.  At half quality (4K->2K) I get 6fps, which is the same as I get when playing back 2K footage at full.  All these AE tests were done at 8bpp, since I foresee doing work at 2K-8bit, and rendering at 4K-16bit.

Clearly there is still work to be done, but the software was all released in the last couple of days, in first public beta form.  Regardless, it is amazing that I am now able to edit 4K video footage in my bedroom on my Xeon workstation from 2005.  Once it is working correctly in AE, I will be all set, because that is where I like to do most of my online work.  It is much more precise than Premiere Pro, and the type of work I do rarely requires much realtime playback.  I am looking forward to getting a chance to do some “real” work with Red footage, but given the current performance, I am hoping that my first steps can be with a shorter project.  It also reassures me of my recent decision to invest in a new workstation, since 4K is a lot of data to be manipulating, no matter how you compress it.