Better because of price. I had a RED and sold it to someone across the ocean for $.75 on the dollar since it was just too much $ for my clients to pay. Not much tops the RED MX in image/options tho except maybe the Alexa or Epic.
Yes, I've seen the benefit of rendering to a good intermediate (Cineform, ProRes, DNxHD, etc...) at 4:2:2 with post work where you're pushing levels. If you're just cutting in post, of course Brian202020 is correct. You can't get something from nothing.
Oh I agree, there is a benefit, just technically it's still an 8bit 420 file wrapped in a 10bit 422 shell edited in an RGB environment. That workflow will obviously make any footage better. Does it make 10bit 422 footage into 12bit 444 footage? No, but it helps. No matter which way you look at it, it is still 8bit 420. That's all I'm saying.
I disagree on with the fact that epic is better, I have yet to see EPIC footage that looks better than MX R1 footage, except from major hollywood films of course, but they can make anything look amazing...
@starstuff I'm on a PC using Sony Vegas. I line up all of my clips and frameserve out of Vegas into Virtual Dub (using Debug Frameserver), clean it there with Neat Video and transcode it into a 4:2:2 YbCr (UYVY) file using Lagarith Lossless codec. I take that finished file back into Vegas and color correct. when I compare the original footage to the transcoded footage (as good as the original looks) it's like night and day. To test them I crank up the saturation and lower the gamma all the way on both the original and new file. No comparison. You can see the noise in the original footage but the new version has no artifacts....at all. I can now go where I want to go with color correcting/unsharp mask etc..
The thing about Neat Video is when done right you lose no detail....just noise. I don't know how it does it...but it works like a miracle. I've used several noise reduction methods in the past and they all seemed to go too far in either direction.
I'm willing to bet one good reason you frameserve out to use Neat video is that Sony Vegas and Neat Video don't really "get along". As you know Neat incorporated a workaround with the "No Lag" check box.
Damn, I overlooked frameserving to Virtual Dub and using Neat Video there.
>>I'm on a PC using Sony Vegas. I line up all of my clips and frameserve out of Vegas into Virtual Dub (using Debug Frameserver), clean it there with Neat Video and transcode it into a 4:2:2 YbCr (UYVY) file using Lagarith Lossless codec. I take that finished file back into Vegas and color correct. >>
No doubt, that´s a good way to hold a good quality through the whole process. But for huge projects it´s too time consuming and inconvenient imo...
@nic2011 I have not done a huge project with that workflow but it shouldn't be too bad. I don't think you'll have a "same day" turnover with this method when it comes to large projects but if you give yourself at least a couple of days (or slightly more) then depending on how well you CC you can have a large project done over the weekend.
For example....when I suggested lining up all of my clips .....that's already one step of editing. What I mean is...all of my scenes are in order and exactly where I want them on the timeline. If your PC can work with AVCHD (or these modified versions of it) then you either trim them or line them up where they need to be. That to me is the hardest part.
Then I just highlight all the clips, right click and "disable resample." From there I frameserve over to VD by selecting "File/Render As" and choosing "Debug Frameserver." You basically spend almost no time in VD because all you do there is choose "Neat Video" and configure the noise profile. Set it to the absolute minimum which is:
Click configure -- Choose "Auto Profile" - Click on "Noise Filter Settings" -- check the "Very low freq" radio button -- Under "Noise Reduction Amounts" slide the "Luminance channel" slider to 0% and leave the "Chrominance channels" at 100% -- and click "Apply." In the Neat Video Configuration box make sure the threshold is at 0% (I find you don't need any more than this" -- I keep the "Radius" at either 1 or 3 frames -- and leave the "Adaptive Filtration" unchecked -- Hit "Ok" and your almost finished -- At this point I just set the color depth (to what I mentioned before) and compression and just render the new lossless file.
The render here will take a long time. A five minute clip can take up to an hour to render on a 32 bit machine. So yeah...it can take half a day to do an hour long movie. But it's a necessary step and well worth it. I used to do what @Driftwood suggested and make the "noise clean up" the last process... but that kind of defeats the purpose of wanting to push your colors during the edit process. Besides..whether up front or after the fact...the render will still take the same amount of time. Also, if you chose to clean up afterwards that forces you to work with AVCHD on the timeline....and we all know, with AVCHD, when you add even just one plugin on the timeline....everything starts to slow down considerably (I'm still on a 32 bit PC by the way so YMMV).
@proaudio4 "I'm willing to bet one good reason you frameserve out to use Neat video is that Sony Vegas and Neat Video don't really "get along"."
Exactly!! I have Neat Video for Vegas also and I found it does not work quite as well (or maybe I should say "Quite the same"). I have no idea why. But the plus with Virtual Dub is that you have two different views (an "Input Video Pane" and an "Output Video Pane"). I love the fact that I can see the original video while watching the processed video in realtime (well...not exactly realtime....but you get the point) because I can see exactly what's going on with the clip and make any necessary quick changes. Helps me to determine if I have too much or too little. I can't afford to run through an entire looooonngggg denoise process only to come back and say..."Oops...I have to redo it over." I'd want to choke someone at that point. :-)
Neat Video also renders faster in VirtualDub than it does in Premiere and After Effects. (don't know about Vegas). Apparently these "bigger" apps add more overhead to the rendering process.
@driftwood "I use it on FCP - 8 core Hackintosh, its not so bad!"
Out of curiousity, how many frames per second does it render (with temporal smoothing turned on)? Also, are these 8 real cores or a quad core with hyper-threading? And what's the speed of the processor?