Ben Rich
Forum Replies Created
-
I have been fighting this issue for years now. Still no proper fix yet but I have found a trick to help mitigate the issue a little:
Since the color shift is likely due to YouTube’s compression algorithm throwing away color data, as most compressions do, I took to de-saturating areas that were not vital color zones. Primarily it was desaturating the shadows and/or the highlights. This way YouTube’s process doesn’t have to throw away as much color data overall since there is less to throw away in the shadows. This is all speculation on my part but it seems to help some. And I will often oversaturate the mid-tones slightly in anticipation of losing some color.
Ben Rich
Videographer | Technologist
https://sites.google.com/site/benrichfilm/ -
Thank you so much for the help. A few follow up questions:
Before buying ClipWrap since its “not converting the footage” does that mean this will give me the closest to native files and furthermore should my files then be smaller than the ProRes versions (this is important to me because the ProRes are too huge to archive original media, even though I will be making ProRes copies just for editing purposes).
Secondly will ClipWrap encounter the same issue with very long clips 90+min?
Finally I may have convinced my office to invest in Adobe Premier. Will Premier on a Mac be able to import and work with the AVCHD footage any better?
Thank you again.
PS: Your trick of importing my long files in partial clips in FCP is working so far. The downside is the annoyance of having three clips instead of one and I am unhappy with my two audio tracks importing as left and right channels instead of two separate mono tracks.
Ben Rich
Videographer | Technologist
https://sites.google.com/site/benrichfilm/ -
Did you ever find a solution to this problem? I am having the same issue. We have been using the same 32gb cards on the same EX1s for three years and one of our cards just started giving us this same error message. Nothing in our work has changed except the error started after formatting the card in our camera in “PAL region” when we usually film in NTSC. But we did the same thing with four other cards that same shoot without a problem.
Ben Rich
Videographer | Technologist
https://sites.google.com/site/benrichfilm/ -
Thank You, I’ll give this a try. I don’t understand though why I would need to de-interlace my video if the project is progressive and the target video for DVD is interlaced?
Ben Rich
Videographer | Technologist
https://sites.google.com/site/benrichfilm/ -
I received a reply from Neat Video’s technical support on this issue. Quite informative. Will try their recommendations now:
It is a systemic issue related to the overall 32-bit software
system including FCP, its filters including Neat Video, codecs, etc.FCP 7 is a 32-bit application (not 64-bit one) and so it (together
with all used plug-ins and codecs) can use up to about 2.5-3 GB
only, irrespective of the available physical RAM. This is a
limitation of any 32-bit application on Mac.Apparently, the project – and that includes all the components
involved – FCP itself, filters you use (including Neat Video),
input codecs that read input clips, output codecs that encode
the output clip, and the like, – is hitting the limits of the
memory space available to FCP (2.5-3GB) and at some point Neat
Video (as one of the components residing in that limited memory
space) is not getting the requested memory block required for
regular processing and in that situation it cannot do anything
but report that problem using that error message that you have
shown. It cannot continue processing without the memory block.There are several measures that could be used to reduce the
memory load and prevent such a condition from occuring:1. Reduce the amount of system memory given to FCP:
Preferences > System Settings > Memory & Cache > Application
By default, it is usually set to 100%. Please try to reduce to
something like 50-60%
If more memory within those 2.5-3 GB remains free then OSX
may be able to provide it to Neat Video when it is needed
for processing.Remember to restart FCP after changing the above settings.
Only if the above doesn’t help, try the following options:
2. When you apply Neat Video, try to use a generally
simpler project, with fewer clips and fewer filters applied.
If possible, render them one at a time.Use smaller frame size if possible. Do not use large still
images directly in the timeline, instead resize them down
before including into the project.Restart FCP whenever possible. This makes memory resources recover.
3. When exporting, use a simpler output compression scheme, like 1-pass
instead of 2-pass. Or use a different output compression codec.
Different schemes and different codecs use different amount
of memory. Simpler ones usually are more economical in terms of memory use.4. Reduce the number of CPU cores used by Neat Video for
processing. Click the Options button to open the main window
of Neat Video. Then go to menu Tools > Preferences > Performance
and in that tab make sure the settings are set to use only CPU
and for example only one CPU core. This will reduce the
speed, but may also somewhat reduce the memory load.Please try these options above. Please let me know if the stability improves.
The best solution would be to switch to a 64-bit version of FCP.
Another possibility would be to pre-denoise each individual clip
before importing them into your main project. That would require
some additional manual work of course..I hope some of these ideas will help. Please let me know your
observations and findings. Perhaps we will then also come up with
some new ideas.Ben Rich
Videographer | Technologist
https://sites.google.com/site/benrichfilm/ -
True usually you can for most compression formats but for some reason the dimensions fields under geometry are greyed out and un-editable when H264 for Apple Devices is selected. And I haven’t found anything yet that makes those fields available.
Ben Rich
Videographer | Technologist
https://www.facebook.com/BenRichFilm