Welcome to our community

Be a part of something great, join today!

Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

how do i get rid of the orange render bar in FCP?

What is your computer give me more than you think i need to know

processor speed, quad? 8core?
ram
FCP version
not critical info but it helps and for the future.


Now look at your sequence under Sequence 1 on the left click the drop down box may say RT
Is that in unlimited or safe
and what is your playback quality.

Get familiar with these things also they will help you in the future.
 
Good call Joseph.
Force it
 
BigLu said:
What is your computer give me more than you think i need to know

processor speed, quad? 8core?
ram
FCP version
not critical info but it helps and for the future.


Now look at your sequence under Sequence 1 on the left click the drop down box may say RT
Is that in unlimited or safe
and what is your playback quality.

Get familiar with these things also they will help you in the future.
Click to expand...

MacBook Pro
2.4GHz Intel Core 2 Duo
4GB 667 MHz DDR2 SDRAM

Final Cut Pro 6.0.4

RT Unlimited
Playback Video Quality = Dynamic
Playback Frame Rate = Dynamic

(The whole point is to avoid rendering. Didn't have to before...)

Where do I select high precision YUV?
 
editor said he did that, no dice. still there. same with high precision YUV... anyone got any ideas? playback on the timeline is strobe-y now.
 
was there a 'don't upgrade' message i missed? i've been away shooting for quite awhile. now we upgraded everything bc it said we had to with build 16 and we are having this orange render bar and strobe-y playback. isn't this bothering anyone else?

bueller? bueller?
 
Hello,

Just tried out proxy editing last night for the first time and the only way to get stuff to play was by enabling the "Unlimited RT" under the "RT" button on the time line window.

The playback works, but everything is dropped into some low res mode and the orange bar appears over everything.

Are people really editing in this low res mode or are they transcoding and then editing?

Blah. It looked so simple to work with the footage at NAB. This is a pain in the ass (for those of us without the cash for the expensive software).

Anyhow, here are my specs:

Mac Pro Quad 3.0GHz (rev 1) w/ 8gigs memory
Cal Digit 8 terrabyte HD One
ATI 3870 512mb PCIe Video Card
Mac OS X 10.5.4
Final Cut Studio 2 / FCP v6.0.4
Quicktime v7.5
RED Quicktime Codec v3.1
RED Cine v3.12
RED Alert v3.48
Recent RED FCP Installer

Hope someone has some clues.

Thanks!

ATF
 
Hi,
I am using a similar system to ATFs and we ve been editing using the sd proxies with the orange line and its been good, playback is a little steppy and quality drops on the client monitor, but nothing to major.
I am testing the log and transfer plugin but i really dont wanna go that path since it uses my precious hard disk space !
 
Hopefully my comments here will be helpful. Unfortunately, until Final Cut supports the RedCode fully again FCP editors will have to deal with renderbars while using the proxies produced by the camera.

For me it dosen't really bother me that much, but for a lot of editors it really gets annoying, as it does for my boss who really hates having to render as he edits. So, I've been trying to come up with a workflow that doesn't eat up much time but would allow us to have smaller proxies to edit with while still allowing us to use the very helpful Crimson workflow model. After some thought and messing a very simple solution came to mind, I've tested it and it works really well.

So, basically (and I'm sure I'm not the first to come up with this) I bring in all the R3D files into RedRushes and set them up to render as DVCPro720. I choose that codec since it works so well in our system, looks good as a proxy and compresses pretty small. I set the size to 1440 x 720. Again, this could be whatever size works best, for us this larger size works well and is a good balance between pixel size and file size. If your tight for space, go smaller, it still should look pretty good.

Now, with these as proxies, we can edit and still take our XML into Crimson with minor tweaks for that workflow. It was a very simple and very smooth process and one we'll probably be using until either the RedCode works in the timeline, or R3D support is native.

Hope that helps some :)
 
This is awesome and I'm glad it works for you, but what about those with features and the MASSIVE amount of footage we're dealing with? Im at 7TB with (nearly) two backup copies of each 1TB drive (18 1TB drives total). I cant make QT wrappers of all that. I've already got a rough cut done...

And thank you ATF with the CalDigitHD1 who said you're having the same problem. I almost bought a CalDigit to see if that would remedy the problem. Phew! You saved me 8g!

Do I really have to export these scenes comprised of all "M" files on my timeline in chunks for the next round of editing? Gah! Come on FCP! Update!

Also: Is there any way to research EDLs online? Would that help?



ingramworks said:
Hopefully my comments here will be helpful. Unfortunately, until Final Cut supports the RedCode fully again FCP editors will have to deal with renderbars while using the proxies produced by the camera.

For me it dosen't really bother me that much, but for a lot of editors it really gets annoying, as it does for my boss who really hates having to render as he edits. So, I've been trying to come up with a workflow that doesn't eat up much time but would allow us to have smaller proxies to edit with while still allowing us to use the very helpful Crimson workflow model. After some thought and messing a very simple solution came to mind, I've tested it and it works really well.

So, basically (and I'm sure I'm not the first to come up with this) I bring in all the R3D files into RedRushes and set them up to render as DVCPro720. I choose that codec since it works so well in our system, looks good as a proxy and compresses pretty small. I set the size to 1440 x 720. Again, this could be whatever size works best, for us this larger size works well and is a good balance between pixel size and file size. If your tight for space, go smaller, it still should look pretty good.

Now, with these as proxies, we can edit and still take our XML into Crimson with minor tweaks for that workflow. It was a very simple and very smooth process and one we'll probably be using until either the RedCode works in the timeline, or R3D support is native.

Hope that helps some :)
Click to expand...
 
Yeah, unfortunately for very large projects like features using FCP, it's either deal with proxy renders or budget space and time for making wrappers. It's really too bad that Apple is silent on this and has made no beeps as to their plans. Honestly, I'm looking at what Adobe is doing with thier implementation and strongly considering that as an option until Apple gets its act together.

I'm sure, in time FCP, Avid, Adobe and most everyone else will have a much smoother workflow, but I did expect Apple to be in the forefront, to be honest.
 
ingramworks said:
Honestly, I'm looking at what Adobe is doing with thier implementation and strongly considering that as an option until Apple gets its act together.

I'm sure, in time FCP, Avid, Adobe and most everyone else will have a much smoother workflow, but I did expect Apple to be in the forefront, to be honest.
Click to expand...

I am seriously thinking of switching to Adobe too, I wonder if it will take my EDL.
 
Hey Guys, help needed here!!
While playing with the new tower we see this orange bar on top of the sequence timeline.
We have a Macpro 3.2Ghz, 16Gb in Ram, and I am playing the footage from the internal HDD. We have an AJA Io LD for SD conversion. Its pretty cool to see whats in your timeline on the CRT monitor!!! It looks incredibly awesome, even with no correction it looks great. The thing is that everytime I hit play it stops and this error comes up:
One or more frames were dropped during playback.
I imported the smallest proxy and the result keeps the same. I dont know what to do, but it would be very disappointing to know NOW that FCP cant run the smallest proxy in real time, because I can even play the highest res proxy in the Finder and it runs smoothly. I hope am the one doing something wrong. Any thoughts?? Your help is very much appreciated.
 
uncheck the "warn me Next Time" when that dropped Frame Dialog box comes up.

It will still drop frames but it won't stop playback this time.

make sure you are set to

Unlimited RT

Half or Low Quality

Full Frame Rate
 
You must log in or register to reply here.
Back
Top