montster

Q: 10.0.3 DISASTEROUS

System -

Fastest MCP one can buy (with extra 2.5gz processor model 8gb ram 1.7core) Lacie THUNDERBOLT drives. 10.7.3 OS.

 

10.0.2 ran "relatively" fine. NOTHING changed except upgrading to 10.0.3

 

Re-renders everything everytime I restart the program - Even though it rendered to 100% on last shutdown.

And when it is rendering - it does it SLOWER than the last version 10.0.2!

 

Playback stutters. Beach ball is more present than 10.0.2 !

 

Titling of previous projects is messed up - baslines and tracking are changed!

 

To test - I reinstalled the previous version 10.0.2 and reloaded in those previous projects. All runs smoothly.

 

Reinstalled the 10.0.3 again - EVERYTHING THE SAME - and same issues!

 

WHO CARES ABOUT ALL THE NEW "FEATURES" WHEN IT DESTROYS MONTHS OF PREVIOUS WORK, AND EVERYTHING IS EVEN SLOWER THAN BEFORE??? Its so frustrating to read reviews by magazines etc who do not lay down feature length, complex movies and only talk about all the "great new features" and how performance is "improved" simply because they read that it SHOULD be improved!

 

Well it isnt - its WORSE! Doesnt Apple actually test things before releasing it ? Where has the trust gone???

 

And I have the most pimped out (portable) system one can get. Pity on those with less endowed systems!

 

EXTREMELY DISAPPOINTED AND ANGRY!

Final Cut Pro X

Posted on Feb 2, 2012 4:53 AM

Close

Q: 10.0.3 DISASTEROUS

  • All replies
  • Helpful answers

first Previous Page 13 of 19 last Next
  • by Photog01,

    Photog01 Photog01 Feb 14, 2012 8:31 AM in response to montster
    Level 1 (10 points)
    Feb 14, 2012 8:31 AM in response to montster

    Monster you are Right!! Its not a Plug-In Problem (which I never suggested), but indeed a CODE problem. CODE that was not fully tested on real-life projects. I like you have watched a bunch of demos and tutorials and the projects are as basic as they can be. And most never do some of the things I do, especially with still images.

    And anyone on this site who says that a minimum of 4GB of Ram will work with FCPx is misleading anyone who wants to tuse this editor with any kind of ease. I reccomend a minimum or 16GB and no less.

    The potential of this editor is coearly seen by everyone for sure. But its the recklessness and disrespect to those who make a living by Apple that has most people so upset. And to IAN, I think that most on this THREAD have used the FCPx feedback site more than onece!!! I know I have and will continue...a lot!!!

  • by Neil Whittey,

    Neil Whittey Neil Whittey Feb 14, 2012 8:40 AM in response to Neil Whittey
    Level 1 (130 points)
    Feb 14, 2012 8:40 AM in response to Neil Whittey

    Update on the titles issue: Trying to troubleshoot while still producing commercials. New commercial, added (copied/pasted) a stock leader and inserted an outro template from the Titles panel into the finished commercial. Both have Motion templates with titles. Those 2 items did not retain their rendering and require re-rendering every time FCPX is closed/opened.

     

    Took a few minutes and opened the outro template in the new/upgraded Motion (right-click in the Titles panel of FCPX), made a minor change, undid it and saved. Back in FCPX I reapplied the template to the outro. Now the rendering sticks.

     

    Seems more and more clear that Motion title templates all require upgrading to the new Motion, which will be a LOT of work. Therefore, best advice is do not bring in titles, templates, etc. that did not ship with 10.0.3 until you open them in the upgraded Motion first.

     

    For those of us with a ton of Motion titles and templates, that will be a huge task and, IMO, should not be needed.

  • by Penn-Ohio,

    Penn-Ohio Penn-Ohio Feb 14, 2012 8:40 AM in response to Photog01
    Level 1 (0 points)
    Feb 14, 2012 8:40 AM in response to Photog01

    "Photogog1" and "Montser" have you all called support on the phone and told them of the problem and had them help you through it or at least get to work on your problem?  If you read my post above, you will see that tech support cares, will do all they can to resolve your problem, and will make them aware of the issue so that engineering can do something about it.  if nothing else do it for the benefit of the entire NLE community.  ive actually called them about your posts and while they are sympathetic they can't take my referral of your information becasue 1) i don't own the software, 2) its not my complaint, and 3) referred forums is technically just hearsay from me a non user and non owner of the software

     

    so call them on the phone and let us know what they say?

  • by montster,

    montster montster Feb 14, 2012 9:50 AM in response to Penn-Ohio
    Level 1 (15 points)
    Feb 14, 2012 9:50 AM in response to Penn-Ohio

    @ PO,

     

    Have. They said they are aware and it is essentially a "work in progress."

     

    Hope you are not suggesting that by calling "tech support" that is going to "resolve your problem" as you put it when it is a problem in coding - not an individual with system pref, video card, and user error issues etc. I thought this was all clear now...

     

    It's not where it should be for pro heavy duty work YET. And too bad it went back in speed on an update promising the opposite. It was "ok" before but unusable now (depending on what you are doing).  But it did - and that is that. And talking to a guy on "tech support" will not fix an update.

     

    Only another UPDATE will fix an inherently faulty update.

     

    This thread has helped MANY - irritated a few (just because it hasnt affected them - or, any criticism is taken as a criticism against their best friend or something lol) and the problems are 110% known to Apple and they are at work on it 24-7 no doubt about that.

     

    Read this thread and be warned about what can be expected re 03. If it helps - fantastic. If not, continue to use and be happy OR revert back to '02 like I have (and others have written) and get some work done as I have with much better results.

     

    Only REAL solution is to wait for V. 12.0 or is it?????? lol

     

    DISCLAIMER: JOKE - not an attack on ANYONES best friend !!!

  • by Photog01,

    Photog01 Photog01 Feb 14, 2012 9:59 AM in response to Penn-Ohio
    Level 1 (10 points)
    Feb 14, 2012 9:59 AM in response to Penn-Ohio

    The one thing I have learned to be disciplined to do is once I involve myself on a thread in any forum, I go back and take the hour or so to at least read pretty much every post or reply. Not to be offensive at all to you, but if you go back and read some of the earlier posts you will see that I personally spoke about my experience on the phone with the Appe Tech. And it may be just too early for them to really understand that there is a real problem with the both the Re-Write of 10.00.03, (which really should be 10.10.00) and the way the Mine and Decipher information from their calls and on this Forum. Which several have stated...  is not the place to the place to complain. But this Forum, in my humble opinion, being more of a "Creative" editor, than a Technical one...is a very important and timesaving source for those who did "Write" this program to put thier finger on what the problem is. Technically I would think you have 4 areas of Concern to look at. First, its a "Downloaded Only" program. Is the problem in the download? 2: Is it an install problem? Meaning in updating with the old FCPX, having wrote its own permissions and such to a specific machine... things didn't mesh. 3: User error....you know people like me and you! 4: Something severely overlooked in the way this software was coded. Which is similar to No.2, but means that we can't really do anything to help it.

    Not just here, but in Forums on other sites, real professional editors are describing and explaining whats going on with the specs of thier machines and everything!! Why is it not protocol for Apple to Mine these sites and get more info in an hour than they would talking on the phone with one of us? I'm not saying don't call, but as you will read, my call with the Tech I spoke to reflected that as that moment it was ot an official problem with the software.

  • by montster,

    montster montster Feb 14, 2012 10:04 AM in response to Photog01
    Level 1 (15 points)
    Feb 14, 2012 10:04 AM in response to Photog01

    What one is NEVER going to hear admitted publicly on phone or print is...

     

    "We messed up and promise to fix it. Sorry about that."

     

    Always best to keep the focus on other issues than coding itself. Smoke screens can keep the people at bay for a considerable time haha

     

    And ya cant blame em either.

     

    They know. They are working on it. But dont expect it to be broadcast in public.

  • by Penn-Ohio,

    Penn-Ohio Penn-Ohio Feb 14, 2012 11:08 AM in response to montster
    Level 1 (0 points)
    Feb 14, 2012 11:08 AM in response to montster

    "montster" and "photogig01" and another others having this same slow down problem.  a word of encouragement....

    montster wrote:

     

    @ PO,

     

    Have. They said they are aware and it is essentially a "work in progress."

    ahhhh haaaa then there ya have it.  a result and now you know that they know and are working on it because from your call they now know what the problem is.

     

     

    montster wrote:

     

    .....Hope you are not suggesting that by calling "tech support" that is going to "resolve your problem" as you put it when it is a problem in coding - not an individual with system pref, video card, and user error issues etc. I thought this was all clear now...

    and now that they are aware of the problem they will work to resolve it.  it's obviously an engineering issue and tech support passes your convo and issue over to engineering and they fix it.  however, engineering usually takes 2 to 6 weeks for a coding issue.

     

    just read my iphone 4s issue above.  on the day the tech support team member called me she said, thank you for being patience and working with us for this resolve.  there is an update coming out today because of your call to us 4 weeks ago and just in the last 24 hours there has been 5 more people worldwide reporting the same prob you had and becasue you helped us and reported it by phone, we have an update that will resolve it . . and that it did.

     

    you never know just how awesome your helping tech support and engineering make things work better for the community.

     

     

    Only another UPDATE will fix an inherently faulty update.

    and in deed that will happen.  i have total confidence that apple will fix it.  they like the product and are putting their reputation on it, so give them a little time and be patient.  in the meantime, just use fcs3 that i think all of you have indicated that you migrated from and while i know that means a lot of work, hey i been there with 3 weddings and 5 tv shows that had to be recaptured, redited, and exported when things went sour as i have shared on other boards that i had to do once with avid when a major upgrade was totally unstable and caused more havoc than i care to even remember let alone live.

     

    if its any consolation . . i have about 9 jobs in house right now BUT i will take 1 or 2 small jobs and edit them on fcs3 and do them for you at below cost OR free . . so long as you pay shipping both ways via an external usb hdd or usb flash drive . .  just to help out.  u capture them with all the material into a single folder along with the project file in fcp7, then copy the folder to a usb flash or usb hdd and the 1 or 2 small projects to me, i will offload them onto my fw800 drives or internal drives in the macpro, then i will edit them according to instructions you provide in a text file, and when i am done, i will render and export a master full rez QT file into a folder labled OUTPUTS and with your return envenlope with shipping prepaid i will copy all the material back to your hdd or flash drive under a file folder named "COMPLETED" and send it back promptly.  i have a new girl that i hired to take some of my personal load off my back so she is doing all the other work and i will do yours.

     

    i have over 7 years of experience, 5 with avid, 2+ with final cut, producing 100-180 (150-180 for the last 4 years) videos every year including broadcast tv shows, events, weddings, film, and documentary which some say the volume is the equivilent of about 10-15 years of experience for the average full time editor.  so just let me know how i can help.

     

    BTW . . HAPPY VALENTINE'S DAY ALL !!!

  • by Penn-Ohio,

    Penn-Ohio Penn-Ohio Feb 14, 2012 2:20 PM in response to Neil Whittey
    Level 1 (0 points)
    Feb 14, 2012 2:20 PM in response to Neil Whittey

    Neil Whittey wrote:

     

    Update on the titles issue: .......

    Neil Whittey, off topic but how did you get your image to show?  i have one in my profile but it never shows.

  • by bill33,

    bill33 bill33 Feb 15, 2012 8:01 AM in response to Penn-Ohio
    Level 1 (40 points)
    Feb 15, 2012 8:01 AM in response to Penn-Ohio

    guys back to one of the topics with in this thread....that I read the solution for, but

     

    in 10.0.3 about the re-rendering: I made a dummy project and the first time it worked.

     

    This time however about 5 minutes in to my montage, with titles, motion graphics, sound overlaps, and color correction....I let this project render out to 100%, exited the project - saw the dummy project was still there - exited FCPX and when I went back in to my project (with the 5 min montage) it had to re-render, but not everything - selectively, but most of it.

     

    Do you have to actually enter the dummy project and exit?

     

    Or is there something else I'm missing.

     

    ...and pre-emptively - if I missed the full explanation of this solution should it already be with in this thread - just do me the favor and answer for me as I dont have time to re-read 13 pages....thanks to the brotherhood we have formed here....I feel like i've known you guyz for yearz

  • by montster,

    montster montster Feb 15, 2012 8:11 AM in response to bill33
    Level 1 (15 points)
    Feb 15, 2012 8:11 AM in response to bill33

    Brother Evil Complainer Bill, it's brother Evil Complainer Montster

     

    Shucks, I like the tone of your post  - how is that possible in such a satanic thread as this one? lol

     

    My finding is similar to yours. After "thinking" I had the solution on some page that I cant remember anymore, I discovered it cant be counted on because the render thing simply pops back with no apparent reason. And you know what? I DONT CARE ANYMORE if there is a "this workaround" or "that workaround" with this update - its enough of a "playing with fire" risk, I'm simply not willing to take with it anymore. In fear of what other "surprises" might rear their ugly head down the line on a job. With 1002 all the shortcomings are known, and havent had a hitch with anything I wasnt already aware of and prepared for.

     

    So I went BACKWARD to 1002, and stress levels have gone back to "normalcy" haha.

  • by bill33,

    bill33 bill33 Feb 15, 2012 8:22 AM in response to montster
    Level 1 (40 points)
    Feb 15, 2012 8:22 AM in response to montster

    lol

     

    Very cool dude! I respect your decisions. But I'm more of a renagade but more so I possibly have a bit more leeway than you do professionally, to take this risk.

     

    So, if any one else has a "this or that" work around please inform.

     

    (( C'mon bro! jump in to the fire! LOL ))

  • by montster,

    montster montster Feb 15, 2012 8:23 AM in response to bill33
    Level 1 (15 points)
    Feb 15, 2012 8:23 AM in response to bill33

    P.S Brother Evil Complainer Bill (BECB),

     

    Just in case it could work for you and YOUR type of projects....

     

    try the following...

     

    1. As opposed to manually deleting render files, I chose this option from the menu of the project(s) created in 10.0.2 that refused to stop re-rendering on reloads.

     

    2. Then quit.

     

    3. Then relaunched the app. Stopped all rendering. Made a duplicate of the projetc(s) affected.

     

    4. Then quit.

     

    5. Used Event Manager (although this can be done manually) to switch over the new dupe and switch off the old one.

     

    6. Relaunched FCPX 10.0.3

     

    7. Let the rendering rip away . This time first as PROXY files. Then as high res files (original or optimized option). Had a coffee. Looked to see if any more were posting angry posts about me

     

    8. Quit FCPX 10.0.3

     

    9. Relaunched. Voila. For the first time - everything was rendered as before.

     

    Of course this might not work for others as we all have our own situations in our projects, but after everything else this seemed to fix at least this particular productivity-breaking "bug". It has no affect on any of the other issues of course, as far as I can tell.

     

                           

          montster    Level 1 Level 1 (5 points)     

     

    Re: 10.0.3 DISASTEROUS

     

       Feb 4, 2012 9:51 AM    (in response to montster

    One thing I might add, it might take (depending on the complexity of the file - mine are VERY complex) a while when quitting. The tendency might be to ForceQUIT because we think its "frozen". Just wait and wait until it finally finishes before restarting again. Otherwise it might not "fix things" completely while collecting the shutdown data.

     

    Crossing fingers for anyone affected that this will help their particular situation.

     

     

    A PUBLIC SERVICE MESSAGE FOR BECB FROM BECM

  • by montster,

    montster montster Feb 15, 2012 8:24 AM in response to bill33
    Level 1 (15 points)
    Feb 15, 2012 8:24 AM in response to bill33

    psss

     

    Dont ever say I dint do nuttin' fer ya!

  • by Neil Whittey,

    Neil Whittey Neil Whittey Feb 15, 2012 8:44 AM in response to bill33
    Level 1 (130 points)
    Feb 15, 2012 8:44 AM in response to bill33

    I have tried deleting render files both manually and within FCPX, deleted prefs, tried editing existing titles, duplicating projects and allowing new renders to be created -- all to no avail. If the project has a pre 10.0.3 title within it, those titles/Motion templates always require re-rendering.

     

    I also found that any Motion templates created previous to .3 need to be reopened in the upgraded Motion then saved in order to avoid problems with new projects and titles.

     

    I have not tried the above mentioned twists and turns procedures. If I get time, might try if it appears there was a step that I have not tried yet.

     

    Bottom line: it appears all Motion templates and titles from the previous version will not hold rendering in 10.0.3. That appears to be the common thread on the re-rendering issue. Have not found any cases where this happens to plain footage, only titles/Motion templates.

  • by bill33,

    bill33 bill33 Feb 15, 2012 9:17 AM in response to Neil Whittey
    Level 1 (40 points)
    Feb 15, 2012 9:17 AM in response to Neil Whittey

    @Neil My issue has nothing to do with using .2 projects in .3. They are virgin .3 projects and events.

     

    @BECM ...rock on

first Previous Page 13 of 19 last Next