Neo Scene

I've been trying to give Cineform's Neo Scene a shot this morning. I had originally downloaded the trial a few months ago but got incredibly busy. I fired up the app anyway and attempted to do a test for the speed and it crawled to render one frame. I was then reminded that Cineform only provides a 7 (7 days, really??) trial of the software. So, okay, the performance had to be the results of an expired trial, right? I deleted the files and downloaded a new version and I still see the same speed results.

I want to assume there's some little file somewhere that tells Neo Scene to not function properly because I'm trying to get use out of it beyond it's trial. I'm hoping this is not a clue as to the speed of the app. I guess I screwed up and should have fully tested it when I initially downloaded it, but it's hard for me to want to take a risk on buying the app if I can't gauge the speed.

A commenter on here said he's found that NeoHD is a lot faster than Final Cut, but what about Neo Scene? It's quite a bit cheaper, but I was hoping that was from the source file limitations and not because of speed. If anybody has an opinion on what I might be experiencing (i.e. - the software is crippled OR that's just how slow it is) please let me know.

The next Final Cut Pro

A number of people have been posting/tweeting rumors about when the next version of Apple's Final Cut Studio will come out, but there's been little talk about what will actually be in it. Will it be a major upgrade or just enough of a change to warrant a whole new version number?

Scott Simmons wrote up some of the things he'd like to see addressed, and a couple of them are my major hopes. Simply FCP should NOT open the previous project, at least not in a multi-user, multi-edit suite environment like a post house. If Apple truly thinks its product is making major penetration in to post houses across this country, and is NOT simply being used by one editor/producer on one long project, then they need to get serious about the way its software handles projects and users settings.

A Project and User Prompt

Yeah, like Avid, but who cares? There should be two modes you could put FCP in to and this can be asked when you install the product for the first time. You could edit in the traditional FCP way which would be to always load the previously opened project and the previously used user settings. However, we should have the option of a "post house" style with a window prompt asking us which project we want to open and which user settings. I have clients where one machine might have two editors working on it on the same day. And three different projects might be worked on. It would be nice to know from the start which project you're opening and who's settings are going to be loaded. And about the user settings - they should be consolidated under one global user setting name. Give us more things to tweak and all of those things that are listed under the User Preferences menu item? That's absolutely silly to call it that if one user can change something deep down inside that menu structure and it affects EVERY user who comes after him. Make those settings customizable to a particular user's name. So when I select my project and my name at the beginning, then I'll record EVERY keyframe when I ride the audio mixers. You might not want to do that, so you change that under your user setting name and you'll know from the start what FCP's behavior will be.

Capture/Render Scratch Settings

Another pet peeve of mine that FCP does is how it treats capture scratch settings (where you digitize and render to) as a global setting and not something that's a project-level setting. I think it should be the latter. Apple gives us editors a lot of rope to hang ourselves, especially in multi-user and/or multi-project environments. For example: have you ever worked on multiple projects in one day? Do each of those projects live on separate drives? So do you remember to change the capture scratch EVERY time you open a different project? Or when you take a seat for the first time in a few days at a busy edit suite, do you always remember to check the capture scratch settings before you proceed? If you do, you're awesome. I bet most of us forget every now and then and sometimes this can be a critical mistake. Like what if the producer wants to view a project you've been working on in another room. They load that partition, open the project and there's media and/or render files missing. D'oh!

Apple could cure us of some of these ills by simply making the capture scratch a setting for that project. So when you open that project, FCP will automatically make the appropriate partition set as the capture scratch. If for some reason that partition is not mounted on the desktop, you'll get a warning prompt to do so. Easy right? Maybe there's an obvious reason why Apple shouldn't do this, but it seems to make sense to me.

I can think of further things that would help with media management, like having the ability to import music/graphic files/photos from within FCP, and FCP knowing what to do with the files. For example: you load a music CD, import some tracks and FCP automatically saves it to a MUSIC folder on the appropriate scratch disk, imports the music to the drive as 48K AIFF AND imports those tracks in to your project.

We'll see what the next version holds, but I'm hoping it's something like the above.

NOISE!

So there have been a few posts on boards about potential noise issues with the HMC150. I honestly hadn't seen it myself, and I wrote off most of those reports as user error. Indeed many of those threads ended with a resolution that saw some combination of resetting the camera and using different scene files.

I also never had a way to monitor my footage outside of my computer until recently. So when I finally sat down to look at the footage I shot from a wedding this past weekend, I was shocked. There was noise, everywhere... in shadows, which wouldn't be all too surprising, but also in highlights and in perfectly lit scenes. I went back and checked some of my previous footage. I saw a little bit of noise, especially in the shadows, but the footage looked good otherwise. So something happened to my camera just before this wedding shoot.

Here's a sample still from this shoot: noisy mess

So the last couple of days whenever I had some downtime I've been tweaking and testing. I reset the camera, which I'm not 100% sure actually truly reset the camera as much as at least rest the scene files and menu (see this thread for more information) and then searched through the HMC150 board at DVX User and found Barry Green's scene file recommendations. The results were noticeably better and returned my level of satisfaction with this camera.

I noted that the camera looked the best shooting 720p 60, even though the "native" shooting rate of this camera is suppose to be 24p. I noticed just a tiny bit more noise in 24 vs. the 60p footage. Here's a 60p still post-camera reset and using new Scene File settings: much better. There is still some noise present here, but (at least to me) it's much softer and not the hideous distortion you see in the other still.

Ultimately I'm not really sure what happened to my camera. And if you find yourself shooting with yours and you have noise, everywhere, it's not suppose to be this way. I think we have to accept the fact that we're going to have some noise/compression, seeing as how this is not full blown uncompressed HD we're shooting here, but the footage should look relatively clean and beautiful. I'm going to continue to do more testing but I'm definitely going to be much more on guard with what is happening with my camera and you better believe I'll do some last minute testing prior to a big shoot to make sure the camera hasn't gone wonky again.

Note: The Scene File setting tweaks were as follows:

Detail: +2

VDetail: +2

Detail Coring: +1

Chroma +2 (I think this should probably be returned to 0 as the resulting image becomes just a little too saturated, but you might prefer this)

Master Ped: -20

Cine-Like V

More Conversion Time Data

I just shot a wedding with the HMC150 this past weekend. As far as I can tell the camera performed beautifully and as it had to put up with its operator's weaknesses. I'll obviously know a lot more as I get in to the editing process and see how the footage looks, especially in the extremely bright, overly lit-by-the-sun scenes and in the evening, when the light was starting to wain. I also used a Litepanels LP-Micro, so I'm looking forward to seeing how that looks.

One note, which actually surpassed my expectations, was how long it took to convert one of the AVCHD clips to ProRes. I assumed with my Mac Pro 3.0 DP it was about a 50% realtime process. I just processed my longest clip to date - 15 minutes - and it took 5:18 to convert this, thus greater than 50% realtime (or even faster). It's good to know that maybe there's a bump in speed the longer your clip is.