[Nick Meyers]

[raju bhai] “when i dropped the video in it says there are no matching sequence settings so it creates the sequence with the matching setting for me.”

exactly, so FCP is working outside of it;s comfort zone.

chose a sequence preset that matches your clips quite close.
same frame rate of course,
and try 1280×720 as that’s sure pixels e your video is.

nevertheless i doubt this will change things, and i suggest that the files from Ableton are at fault for whatever reason.
to test, make a new sequence of ANY flavour, and drop the audio in.
re-procesing the files thru FCP or compressor should be tried, just see if it works/

[raju bhai] ” red line and 1 that is either purple or blue or grey”

either the default great line meaning no rendering requited
or the steely blue-grey line which means there is some slight mis-match, but FCP can deal with it, and play back a “full quality” image.

nick

[Nick Meyers]

[raju bhai] “the video i am using is small 640×360 frame size … But my sequence settings are fully setup to match the new video”

ok , i sont think this is a standard FCP sequence setting,
so that *could* affect RT [performance, but i would guess only for the video.

try changing your sequence settings to oe of the offered ones, see what happens.
my guess is it will remain the same.

[raju bhai] “Larry Jordan video where he said only trash them if it really is an issue.”

a little alarmist perhaps.
you just have to re-set your preferences.
make sure you have things like keyboard layout saved if you have modified it.

[raju bhai] “the sequence only needs rendering when i drop the ableton audio file in. When i import it into the timeline, 2 red render lines appear at top.”

why 2 lines i wonder?
that would imply video and audio renders required
are you getting the audio beeps that Michael asked about?

nick

[Nick Meyers]

it’s all very strange.

FCP can play AIFF and WAV quite happily
simple mis-matches, like a 16bit audio file in a 24 bit sequence would NOT require rendering.

you could trash your FCP preferences and see if that helps.

otherwise, i’d say there;s something wrong with the files from Ableton.
I have no experience with Ableton, so can’t help there.

one more thing to check: what is your sequence preset?
does is have the same frame-rate as the material you are working with?
it helps if it does, especially with audio sync.
however, again this would not cause your audio to need rendering.

as i can’t help too much getting to the bottom of the problem, as an alternative i would suggest:

set the appropriate sequence preset.
delete all audio or start a new project.
re-import the 24bit files
batch export them from FCP to AIFF or WAV
then bring those new files into FCP.

nick

[Nick Meyers]

what sort of problems are you having?
it’s pretty simple, so can only work in a simple way.
it can help cover up a small, straight hair that is not moving,
or a small spot.

there are two position markers, P1 and P2, you use them to define the start and end of the hair.
if it’s a spot, the start and end are basically in the same place.

the filter then substitutes that area from the next or previous frame,
and there’s a other control where you can create an off-set, so you wind up replacing the hair or spot with another part of the image.

it’s limited for actual hairs, and pretty good for single frame spots.
for a single frame spot, you have to blade the problem frame, then apply the filter.

i hope that helps,
nick

[Nick Meyers]

[Johnny Smith] “I’ve edited that interlaced footage before and it looked great on Vimeo”

you were probably combining it with progressive footage, and the time line had been set to progressive, or Field Dominance = None in your sequence settings,

you could do that yourself, it’s a quick and dirty approach to de-interlacing.
does it blend the fields? i can’t remember.

you could de-interlace in compressor, yes.
i think that would be better than fields = none in FCP, which is sort of the least sophisticated approach.
doing it in compressor means you can’t really preview it though, so i don’t tend to do that.

Natress Smart De-Interlaceis the best within-FCP de-interlace, but it costs so maybe not worth it for your one-off.
FCP does have a de-interlace, so give that a go.
also try the de-flicker filet set to max. that actually BLENDS the fields, which gives you maximum resolution, BUT keeps both fields, so you’d have to trim the offending frame.
at least you’d be able to see it directly in FCP

[Johnny Smith] “I’ve edited that interlaced footage before and it looked great on Vimeo”

well if you think it looked great, then you could probably just set field order to none, and be done with it
but test it first, see if it looks ok.
maybe your footage is1920x1080 and on Vimeo it was 1280×720, so the drop in resolution was less noticeable?

your other solution of course is to trim that frame.

cheers,
nick

[Nick Meyers]

[Johnny Smith] “That frame was edited out, it’s not in FCP’s timeline but it’s showing up on H264”

i wonder if your footage is interlaced.

FCP’s canvas won’t show the fields,
but it could appear “combed” with the frame you thought was your in-point once you get to quicktime.
it’s happened to me.

go back into FCP, find those cut points,
set your canvas to 100%.
that will show you fields as combed images.

nick

[Nick Meyers]

well i think there are other apps to achieve the same end.

QT change from VideoToolshed,
and QTedit from Digital Rebellion (30 day free demo from memory)

nick

[Nick Meyers]

live sometimes gotten weird frame rates after a transcode.
running the clips through Cinema Tools and conforming has fixed it for me.

nick

[Nick Meyers]

thought 1:
is this FCP 7.0 perhaps?
maybe a re-install without the update?

thought 2:
try trashing preferences

nick

[Nick Meyers]

[Randall Johannes] ” I’m not sure how this was changed to alpha.”

you had the viewer selected, and you hit Shift W.
just one of those things…

nick