[Ben Mullins]

I totally agree that Apple is way too secretive in just about everything they do – but can’t argue with success…

I think this creates an atmosphere where no-one at Apple will want to (or be brave enough to) change their strategy in relation to marketing or customer relations, despite what many customers would prefer (less secrecy).

…I get the feeling that they know it’s not done yet and are playing it extra close to the vest until the last of the missing features are back in.

Personally I wish they wouldn’t play it so close, it has a direct effect on the financial decisions I have to make and puts me in a position where planning the future of my career becomes more guess work than strategy, both in terms of purchasing new hardware and learning new software. This is how I pay the bills. If I am your customer I would like at least some support. Just saying…

[Ben Mullins]

Does the playhead now snap to the cut point after doing a Ripple?

I hope so, it would be a big time saver. Overall very happy with the new features though, and I know it’s been said before but the fact that people from Adobe actually interact with this forum certainly helps with confidence and trust in the product.

[Ben Mullins]

[Michael Sanders] “one can only speculate what’s coming in the next few days.

An actual apple with a thunderbolt connection that streams juice out over a giant magnet.

[Ben Mullins]

I’m based in London too and have switched from Legacy to PPro. I can’t speak for the rest of London but the other editors I do know have either stayed with Legacy or moved to PPro as well (with 1 moving to MC). None have taken up X. This is all for corporate work with the exception of the chap who went with MC (makes the most sense for broadcast at the moment I think). Again this is just my experience and I’m sure there are others who can say different. Just what does it all mean?!

[Ben Mullins]

Hi,

Thank you all for your responses. My main reason for shooting at 50fps is as Shane says for slow motion. I use a Panasonic GH3 which allows 1080p 50 fps but reduces the data rate from 72Mbps to 50Mbps. Previously I had shot on a RED One and noticed that 50fps would reduce the frame size to 720 and I was just curious as to why some cameras might do this (a colleague uses a 5D and mentioned the same thing).

Thanks,

Ben.

[Ben Mullins]

Excellent, thank you this fixed the issue for me. In case you can’t open the link or it expires –

Open System Settings and under the Scratch Disks tab make sure that at the bottom Limit Capture/Exports and Limit Capture Now are both DE-SELECTED.

Thanks again.

[Ben Mullins]

Craig –
The timeline index and not having to target tracks I understand, but the main thing I find to be more work in X is adding the keywords. I find it quicker just to name clips and organize in bins. With X I’m renaming the clip, then adding the same text as a keyword so that I can organize in a folder in the event browser. Is this correct or I am missing the point of keywords? I understand their use when searching for media but are they supposed to be used instead of organizing clips in a folder or in conjunction with?

Jason –
I get the exact same speed boost in CS6 from not needing to render the timeline and the dynamic link with After Effects. I think this is just a development in non-linear editing across the board.

[Ben Mullins]

Philip talks a lot about X being the fastest NLE on offer. I keep hearing this over and over, that it’s 2-4 times faster to use X. How? I already work quickly using the keyboard as much as I can, and surely most of the speed in editing is gained from knowing what to cut and where to put it without needing to try out multiple scenarios before finding the right one. That comes from experience and practice, not a new interface.

So, how is X faster? What specifically does it do differently that will speed up my workflow? I’d really like to know because if it does (which I haven’t found to be the case yet) I will certainly use it more often.

Ben.

[Ben Mullins]

I’m not doubting what happened to you. But I find it hard to reconcile stories like this. I’ve been using FCPX every day since February on non-inconsequential work, and I’ve never had data suddenly disappear.

I finished a project in X (10.0.1), then returned to it a couple of weeks later and every single clip was offline. Since this was the first version of the software I couldn’t reconnect anything so I lost the entire project. I hadn’t made any changes to my folder/file structure or moved anything around in my Finder, it just refused to see the clips. Granted this was on the 0.1 release, but just because it hasn’t happened to you doesn’t mean it hasn’t happened. Luckily it was a personal project and not critical in any way but still, rather annoying.

On another note, one of the things that X is usually credited for is speeding up people’s workflows, however I find it takes longer to log clips in X than in other NLE’s. Maybe I’m not approaching this correctly but once imported I’ll rename the clips, then have to assign that same name as a keyword so that I can organize the clips into folders in the Event Browser. It seems like adding more work rather than speeding it up.

Not that I dislike X but I agree with Oliver, I enjoy CS6 and MC a lot more.

Ben.

[Ben Mullins]

Hi Carlo,

I have the same message pop up when I first load X, however I just click ‘OK’ and the software works fine. It’s just a warning that as the graphics card is not supported it might not run as smoothly. Does your version do this or does it shut down and not allow you to edit at all?

Ben.