Rafael Amador
Forum Replies Created
-
Are you able to play the original clips in the camera you shot with?
It smell a bit to corrupted media, but if the camera clips were corrupted you probably would have had on the Log&Transfer.
First I would try to L&T again.
rafael -
That might be one of the many glitches that can happens when you try to edit an unsupported format (H264/MP4) in FC.
[Aron Zana] “My scratch disk is set to the computer HD..which has 1 GB free disk space. “
1GB?
You should be happy that you are able to open your computer and even open FC.
Just to open the system and the applications needs a certain amount of HD free space for what is called “Virtual memory”. That’s a kind of temporal memory where applications write data, and is necessary even if applications are in ‘”stand by”. Have a look to the Activity Monitor.
Free HD space is what you need.
rafael -
[Ben Hooton] “Now, I can zoom in 1% to hide the line, which isn’t ideal but it’s a workaround. However, will I have lost quality somewhere if for example the online person has exported as interlaced and I’ve put it into a progressive sequence and carried on as normal?”
At this stage would be difficult to find out if there has been any mistake, but don’t do what you intend to do. Don’t zoom the picture, that will degrade it a lot.
Just crop a little bit (0.5% or even less), to get rid of those purple lines.
rafael -
[Craig Seeman] “Not a genius, one just needs to understand Apple’s NLE equivalent of Esperanto.
In many respects it’s a language unto itself. I think it’s a very good language. It draws from many sources but the some total of the experience can be very different.”
You are right Craig. FCPX implies the need to learn a language and a bunch of concepts, and without understanding of those, you are off the game.
Somebody (just to rant) compared FCP with Tetris. Ok lets accept that. You don’t need to learn no language to play Tetris.[Craig Seeman] “I believe FCPX is much more intuitive to the new Editor…I suspect those rooted in “convention” have a harder time unlearning which is why we see comments claiming FCPX is hard to grok by some.”
You are right. When you are used to a few old simple logic and solid convention to accept a bunch of uncertain, unproved lab designed conventions is not that easy. When you are new and experienceless and you have no arguments to compare one with the other, you take whatever they give you.
I can accept whatever adjective in favor of FCPX, except “intuitive”.[cem yildirim] “I have to disagree with that. My students learn much faster to edit on FCP X now.”
Did the ever tried to learn FCP?rafael
-
The main difference is that you need to be a kind of genius to understand FCPX.
FCP is for more limited and short minded people. Like my self.
rafael -
Depends of what you mean by “treated”.
Progressive footage will work without problem on any progressive or Interlaced sequence. Will keep looking progressive.
However Progressive footage shouldn’t be “interpreted” (Browser) as Interlaced , because (except with Uncompressed footage), the chroma is codified different in Interlaced than in progressive stuff. That could lead to color issues.
rafael -
And then what happens if ( as I do) you just want to put some things (media: captured stuff and renders) on an external HD and leave the rest on the System HD?
rafael -
-
Unless your audio guy has exported with a wrong time-base, I think this is the well known bug that has been documented by Matt Lyon.
When you import audio to FC, the application manage it as it had the same time base than your default sequence (Easy setup). So if your default sequence is 29,97fps and you import any audio and lie it on a 23,98 fps sequence, the audio will go out of sync.That’s why happens this:
[Alan Langdon] “The worst and strangest is that when I start a new sequence and try without the nesting, just pasting the oringinal clip cuttings and the imported audio AIFs, the files do NO”i guess your default sequence is 29,97, so when you import your audio FC treat it as 29,97 and so drifts on your 23,98 sequence.
Try this:
– Delete the audio from FC.
– In “Easy setups”, select any 23,98 fps option (so when you open a new sequence will be 23,98)
– reimport the audio and lie it on his place.
That should workIf you want to know more about the bug and how to fix more complicated scenes:
https://library.creativecow.net/articles/lyon_matt/
But if you are working with just one mix from your audio guy, you don’t need to resource to XMLs. Just do as i wrote above.
Rafael -
[Magnus Monfeldt] “400x225px”
Horrible number for compression.
You can’t use numbers that are not divisible by 4.[Magnus Monfeldt] “max 100mb/appr “
I guess you mean 100MB.100MB for 23 minutes film, means that you can allow a bit more than 4MB per minute of film.
That means 4 x 8.000.000 bits per minute, 32.000 bits per 60 seconds, which is the same than 533.333’333 bits per second, or 533Kbps.
If you discount the audio data rate, lets say 96Kbps, you can set 437Kbps for the picture without reaching the 100MB file limit.
That that data rate for such a small video size will yield a very, very good picture.But:
– Make the size 320×180, because that’s real 16×9. You can go to 400×224 (no x225) and the picture still will look very good.
– leave the original time-base: 25fps or 30fps. No need to reduce to 15fps.
– Make Multi-pass, and set KEY-FRAMES AUTO.
If you need better audio, increase the audio data rate and reduce the video data rate by the same amount.
rafael