Forum Replies Created

Page 12 of 25
  • Roger Poole

    November 4, 2015 at 8:08 pm in reply to: The Disappearing Wave Form Nightmare Returns

    Yes, Quicktime 7.6.4. It’s on the Snow Leopard installer disk. Any problems, we’re here.

  • Roger Poole

    November 4, 2015 at 7:33 pm in reply to: The Disappearing Wave Form Nightmare Returns

    Hi Mike, I would suggest you buy another hard disk and install it alongside your present disk. Install Snow Leopard and FCP6 and see how it goes. That way you can choose which disk you want to boot from and later make the final decision on which version you would like to work on in future projects. FCP6 requires Rosetta because it’s not fully coco. It’s quite a while since I did an FCP6 install but as I recall Rosetta is in “optional installers” on the Snow Leopard installer DVD. You seem to have put a lot of work into your new system. I little more and it will be a great improvement over the G5.

  • Roger Poole

    November 4, 2015 at 6:57 pm in reply to: Music Won’t Playback

    Myreille, this forum is for the old version of FCP. It’s not that you are not welcome here but you would probably find a solution to your problems in the FCPX forum here on the cow, where the folks there will be better able to advise you. At the top of this page FCPX or FCPX techniques. Good luck.

  • Roger Poole

    November 4, 2015 at 6:30 pm in reply to: The Disappearing Wave Form Nightmare Returns

    The RAM issues apply to both FCP6 and 7 because they are 32bit applications and even though they might now be running in a 64bit environment they can only address a theoretical 4gigs of ram regardless of how much more is physically present in the computer. However, due to the faster speed of the Mac Pro you will see a huge difference compared to running on your G5. Like I said before, FCP6 seems to cope well with that RAM limitation but FCP7 is prone to out of memory errors. They put various new features into FCP7 such as labels, search and variable speed, etc, so maybe they are responsible for the out of memory issue. But if you can live without those features you wont see a great deal of difference between 6 and 7. As to the future well, FCP7 was discontinued 5 years ago so is definitely becoming a bit of an old horse, but lots of us like the workflow even though FCP7 is living on borrowed time. The main problem being that newer computers can’t run the older operating system which is needed to run the Final Cut Studio suite dependably – or at all.

  • Roger Poole

    November 4, 2015 at 4:02 pm in reply to: The Disappearing Wave Form Nightmare Returns

    Mike, I’m a great fan of FCP6. I have 6 – 7 and X on my Mac Pro, each on it’s own boot volume. FCP6 runs sweet and never lets me down. However, there do seem to be some issues with FCP7. As both apps are 32bit they are severely limited regarding RAM. They can only access 4gigs of ram in theory, but 2.5gigs in practice. FCP6 seems fine with that, I have Boris and all the FX Factory plug ins installed, not a problem.
    I get the feeling that when they wrote FCP7 they put just that bit too much into it and as a result makes it unstable due to running into the RAM buffers and causing “out of memory” errors. That’s just my theory though.

    Moving your ESATA externals to internal is unlikely to show an improvement. You are editing SD which has a very low data rate. You could download Blackmagic speed test or AJA system test to check what speeds you are getting from your drives. What ESATA card do you have and are you running the appropriate drivers. I use the Highpoint Rocket Raid and G-Raid externals, no problem.

    If you have FCP6 why not install that. You will need to install Rosetta though. This is on your Snow Leopard installer disk. I can assure you that it runs great on a Mac Pro running 10.6.8 and hopefully you will get your waveforms back.

  • Roger Poole

    November 3, 2015 at 9:04 pm in reply to: FC7 – Blurred Text

    Text in video has always been a problem because of interlacing. With the advent of progressive workflow this has largely gone away. If you working in an interlaced SD sequence then titles are never going to look great. Fine font’s wont display well so try using something more heavy. You can try applying a directional blur, (1 pixel vertical) to the text layer, which will help. Also, as a test, try setting up a progressive HD sequence and see how your titling looks on that. It should look great if everything is set up correctly and will rule out hardware issues. The 7300 GT is not a well spec’d card for video really.

    Afterthought. Try viewing at 100%

  • Roger Poole

    October 30, 2015 at 11:37 pm in reply to: burning a DVD without strech or in a box

    Nick, you are doing a great job here.
    Nefin, in item properties it lists the creator as Blu ray player. Is this an hd Blu ray rip? If so, how did it end up dv pal.

  • Roger Poole

    October 29, 2015 at 4:09 pm in reply to: burning a DVD without strech or in a box

    In sequence settings, is anamorphic checked or unchecked.

  • Roger Poole

    October 29, 2015 at 3:42 pm in reply to: burning a DVD without strech or in a box

    Ok, in the FCP browser select one of your clips, right click, then from the drop down menu choose “Format”. You will see all the info about the raw clip. My guess is that it’s a non standard frame size and you didn’t set up your sequence manually. Instead dropped a clip into the timeline and said yes when you were asked if you wish to set the sequence to match your footage. Take a look at your sequence settings and see if they agree with the settings displayed in the browser and what you assumed the frame size of the imported clips were.

  • Roger Poole

    October 29, 2015 at 2:23 pm in reply to: burning a DVD without strech or in a box

    Why export to H264. Export QT movie without conversion, DV PAL in this instance, then make your DVD from that. If your footage is anamorphic don’t forget to set that when building the DVD.

Page 12 of 25

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy