Why users of the forum have to be censored or banned? I didn't sign any NDA with anyone.
Are you going to ban any link to 9to5mac or Mark Gurman's twitter account? With what standard, I'm confident that Apple didn't tell you exactly point by point every single update the new version will have. So how are you going to decide what is speculation and what is breaking an NDA (which you should first check with the user if he signed it)?
With this kind of actions you are policing more than Apple itself. How many videos are on youtube about the iPhone 7 before it was even presented in the keynote? Does are still there and many of the youtubers who made them are invited to the Apple Keynotes anyway.
As Sugarhill says, this is a forum and we need as many talented users as possible.
Tim Cooks brother sold a hamster to my sisters boyfriend and I can say with ABSOLUTE CERTAINTY that it's going to be renamed fcp XTREME. have a lime green spandex ui and the ability to shoot death rays from the webcam.
Seamusvfx wrote: Tim Cooks brother sold a hamster to my sisters boyfriend and I can say with ABSOLUTE CERTAINTY that it's going to be renamed fcp XTREME. have a lime green spandex ui and the ability to shoot death rays from the webcam.
I can't tell you that..NDA...but I'll tell you I have seen the hamster, and it's a BIG change from current hamsters... I realise that's not a helpful comment, but it's important for my ego you know I have access to beta hamsters and have seen things that would blow the minds of you non-beta plebs.
waternyc wrote: "Life is like a box of chocolates.....
You can enjoy them if you have the money?
AND... do NOT install the update ASAP unless you are willing to deal with potential bugs, pitfalls, etc. NEVER update mid-production. ALWAYS back up your system entirely before upgrading, including a copy of FCPX 10.2. Expect the best, be prepared for the worst. Life falls somewhere in-between.
I'd also like to share the gist of conversations I had with two different plugin developer recently. It isn't always in a plugin developers best interest to work with a beta copy of an app. Because the app developer is tweeking code to make it more efficient, fix bugs, add new features. The third party developer could potentially be knocked back and have wasted weeks of work with each turn. Thus, they usually wait for a final product to be released before updating their plugins. When the app is no longer going through daily metamorphosis and is static. Just FYI for those wondering why plugins aren't updated the same day as an app.
And to clarify something, my comment about banning someone, was specifically about someone who joined this forum with the singular intent to claim knowledge of the next FCPX release and claim to leak hearsay details. Not someone who joined this forum to help folks with their daily work.
The third party developer could potentially be knocked back and have wasted weeks of work with each turn. Thus, they usually wait for a final product to be released before updating their plugins. When the app is no longer going through daily metamorphosis and is static.
I always understood, the purpose of the beta process was to ‘test’ the new code for compatibility and usability … not re-write the code apps/plugins on the fly so as to offer reliable and accurate feedback to the parent developer so they knew where their code required adjustment and/or improvement.
I understand when third party developers wait until the GM version is released to actually update their products – I have no time for the folks who do nothing until that time. Although when developer beta programs are offered to third party developers, they should be participating in the process taking notes and offering valuable feedback with an experienced point of view so as to alleviate we end users from the process to ‘beta’ test for them after the official release.
As well as … plugin developers should openly inform their users when incompatibility issues exist before the final release of new apps or OS updates. If they participate in the process, they would be aware of such issues ahead of the release.
There is a developer version where third party can adjust there code so its will run on the new "engine" code.
It is smart to develop on this version to 1 get your plugin up to date on the release 2 for performance adjustments 3 new technology
Beta testing finds bugs, that means some code has to be rewritten, and sometimes it means it adversity effects other parts of code, and more has to be rewritten. Otherwise, how would bugs be fixed?
Third party developers, to my knowledge, are not all invited to beta testing of all apps. I've no idea how the process of choosing who is invited and who isn't works, but I know some developers are not invited. Very few have updates the day of a release.
I know of no "developer version" of FCPX. I've never seen or heard of one. For the OS, yes. But I've never seen one for individual apps.