[Thomas Newman]

I fixed the issue!!
OK,
SO here goes.

Please dont take my words as god but I believe I have managed to get rid of the crappy font issues in FC Studio 2. It had nothing to do with which monitor or viewing it at 100 percent or not. This is what I did and it worked.

First in Live Type:

I created my floating TEXT then exported it from Live type and selected
– Compression ( NONE )
– SIZE – Current

In Final Cut Pro I decide to right click and select
– NEW SEQUENCE
– Import new FILE

I brought in my new titles that I just created in LIVE TYPE.
I grabbed the titles and placed them in my new sequence. FC asked me if I would like my new sequence to match the settings of my new clip. I said YES!

Now no more crappy text and the animation is 99.9999999 % perfect. It no longer looks like someone took a dump on my text then ran it over with a truck!

Once again, Im not sure why this made a difference but perhaps by letting FC chose its own settings based on the imported clip is best. Now no matter where you get your happy little font animations from, they work!

Try it!

Thomas

[Thomas Newman]

Yeah I think this is a total FCP studio 2 BS problem. There is no way TEXT should look this bad. I have never had this problem with older versions of FCP but now since I bought the newest version this problem has occurred. When I set the canvas to 100 percent it just looks like a larger version of the same crappy fonts. No matter what program they are created in when they come into FCP they turn to crap! The only time they look great is when you are stationed on a single frame with no render. Once its render, its hello crap! If you were to start a fresh new sequence in FCP what would you set the presets to if working with DV footage at 720 X 480??

Thanks
THomas

[Thomas Newman]

Hi,

Its a simple DV NTSC 720 X 480 timeline sequence preset. The monitors are the same two monitors I have used for years with HD footage and no problems. This is suddenly happening with the new sequence I created. They are ACER 19 inch monitors.

Thanks
Thomas

[Thomas Newman]

Hi,

I have an ATI Radeon HD 2600, which I am thinking is just not powerful enough for some of the things I want to do. I often get error messages in FC when trying to use Noise industries filters on certain footage. It tells me that my graphics hardware cannot handle the following filter. Its odd, so I guess Im going to buy a much better graphics card and see if that helps.

Thanks

Thomas

[Thomas Newman]

Thanks to all you wonderful people on this forum for all your suggestions and responses. Its devastating when your partner in crime is acting strangely and with no apparent reasons that you know of. Sometimes I wish programmers would simply make the errors be as specific as “Hey dummy dont use back slashes!” instead of some random string of code that only they know how to decipher. Today is a new day since I have had 5 hours sleep in the past 3 or 4 days , not sure. In any case it seems the dark cloud has been lifted and I can get on with editing my movie “Bong Of The Dead”!

PS

I wish I knew how to use automator so I could have saved my wrists from breaking. I guess there’s another tutorial to place in the stack of things to learn and do.

Once again Thank you!!!

I dont mean this in a bad way but I hope I dont have to wonder through any more forums searching for the holy grail any time soon. I have a lot of catching up to do now that my MAC is back! hope to be of assistance to others here though in any way I can.

Thomas

[Thomas Newman]

Well I spent three solid days around the clock with minimal 2 hours of a sleep just to try and find why I was getting this stupid “out of disc space” error on my new MAC Quad 2.8 GHz intel with 4 gigs of RAM. Below is the issues I had and what I did to finally fix it.

PROBLEM 1:
When trying to render in FCP 5.1.4 I would get an “Out of disc space ” Error after about 15 seconds or so even though I have tree terabytes of space.

PROBLEM 2: When trying to export to quicktime as an MOV file I would get the same error as above, then FCP would crash.

I did a lot of research on as many forums as I could as well as the apple site and found a few possible reasons that this could happen. I also knew that I had installed some new filters that were problematic to begin with. Those filters were “Magic Bullet Looks” and” FX factory”. Sometimes I could get access to the LOOKS viewer through FC and sometimes I could not. I found out that other people had this issue due to the new piece of crap intel chip that we are stuck with now in our MAC pros. I dont care how fast they make the computers, if they make PC’s crash all the time then the MAC is at risk also (What the hell was Steve Jobs thinking?) Anyway before I go onto a why I hate PC’s rant I will explain the solution.

SOLUTION to problems 1 and 2:

It seems that some people reported that the new OS system has an issue with placing a ( / ) in your clip titles as well. I never had this problem before but I guess with the new systems it is an issue. So when you log and capture and are naming your clips as I did with ALL 765 shots that I had captured with an average of 4 ( / ) inside each title, then you should do what I did. Spend about 8 hours going through your clips one by one and removing those nasty little buggers and replacing them with a ( – ) instead. Do this on the original source clips and not in FCP because it makes no difference what you call your shots there. Its the source files that matter. Yes this totally sucks because it will move all your clips in your FC project to off line, then you have to go through therm one at a time AGAIN inside FCP just to reconnect them because now the names have changed and FC needs to know where they are.

For example:

ThenewMACIntelSUCKS/CU/Take/3

WOULD HAVE TO BE CHANGED TO

ThenewMACIntelSUCKS-CU-Take-3

Now do that for all your clips in the folder where they are stored. Yes its loads of fun, make sure you have a bucket of ice handy and wrist braces because your hands will feel like they were smashed with a sledge hammer by the time you’re done.

After doing all that, I then deleted the Preference files for FCP. I went to the apple site and downloaded a free AP called “Preference manager”. Its a nifty easy one click program that SAVES YOUR PREFS OR DELETS THEM FOR YOU.

I also got rid of the problematic filters in my FCP application support/ Plug ins folder and made sure there was no traces of them in the Applications folder either.

The best part of it all is this. I read somewhere that If you have a drive allocated to TIME MACHINE that it could cause issues with FCP. Well it so happens that the Western Digital external drive that I am using for storing all my MOV clips is also the TIME MACHINE drive which I had set to on. Well I turned this off and only after doing so did my results improve 100 %!!

So did I need to do all that other crap or was it a simple turn off the Time machine on the active drive issue? I dont know. Im trying to edit my feature film “Bong Of The Dead” and I bought this new MAC Pro in order to give my feature film the best it could have, and instead I have had nothing but headaches since I did so. In the end though I did all of the above just to be on the safe side and it SEEMS I can now edit like the wind and export with NO ISSUES! I think I won for today.

If you are having those same issues I suggest starting with the simplest and that is either switch TIME MACHINE off or make another disk your time machine disc. Then if that does not work go ahead and do all the other stuff and see what happens. DON T FORGET TO REPAIR DISC PERMISSIONS after you do all that deleting files and crap.

Best of luck people!

PS

Check out my movie site I would love some feed back: http://www.bongofthedead.com

Thomas

[Thomas Newman]

Yeah I tried everything under the sun with those filters. It seems that “Looks” either works sometimes or not at all. I did some research on other sites and forums and found the same issues by others. I did complete re installs on them and still nothing. I managed to get the FX factory one to work and be stable but have not tried an export yet to see if it would cause the same errors yet. More testing under way.

Thomas

[Thomas Newman]

Sorry I thought it was including all the previous information I had posted or that people could click on my name and see my past posts. In any case I had a horrible glitch in my new Power MAC Pro- Quad core with 2.8 GHz Xeon. Every time I tried to do a render I would get a “out of disc space ERROR” even though I have 3 Terabits. When ever I tried to export anything it would crash my FCP 5.1.4 after that error.

I cleared the preference files from FCP and nothing
I re installed my OSX leopard latest version and nothing
I ended up getting rid of all the filters I had placed on my shots in the timeline and it worked! So this lead me to believe that it was one of the filters or the combination of them. I had about four filters on each clip. Once I had tried that test and was successful decided to reinstall my FCP to be on the safe side and now everything WORKS!!

The filters to be aware of that may have caused the issues are:

Magic Bullet – LOOKS builder
Nattres: FX Factory

Outside of that Im not sure if there was anything else that could have caused this.

Good luck to all the others that had the same problem.

Thomas

[Thomas Newman]

Hi Ben,

Well after akk my efforts I still get the same out of disc space error whioch makes no sense. I have 3 TB of space so that is out of the equation. I reinstalled the OS and FC and deleted the preference files and still I get this stupid error then it crashes too. Here is the top half of the report, I’m not sure what the heck it means maybe you do. Please let me know as I am about to take this new machine back and go back to my old G4 Silver.

Thanks
Thomas

Process: Final Cut Pro [297]
Path: /Applications/Final Cut Pro.app/Contents/MacOS/Final Cut Pro
Identifier: com.apple.FinalCutPro
Version: 5.1.4 (5.1.4)
Build Info: FCPApp-702211411~2
Code Type: X86 (Native)
Parent Process: launchd [111]

Date/Time: 2008-11-07 18:48:03.204 -0800
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x000000000000003c
Crashed Thread: 0

Thread 0 Crashed:
0 com.apple.FinalCutPro 0x0040f490 NewCanvasAndGWorld(KGRect*, unsigned long, KGQTCanvasFormat, KGCanvasRec**, unsigned char) + 264

[Thomas Newman]

Hi Ben,

Thank you so much for the tips in trying to fix this most horrible experience. I bought my MAC from the Apple store so they installed the extra 2 Gigs of RAM for me before I received it. Im sure it should all be in spec. I have re installed my OS and FCP, now I am trying to render again. I will post as soon as I have the results. I hope this is a simple fix. If its the machine itself then I guess I can still take it in since I have only had it for less than one month.
Thanks again

Thomas