Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Creative Community Conversations the event browser

  • Posted by Aindreas Gallagher on July 3, 2011 at 12:37 pm

    getting past going completely nuts at apple, I’ve been wondering about the event browser.

    We can all agree that seeing all the events by default is a little crazy – I think the browser (i know, it’s called a browser) but i think it should be a blank slate that I then populate with the materials germaine to my current project – I don’t think it should be the repositry of all the events accesible to FCPX at that moment – I know you can move the events in the finder, but go with me. We can all have our suspicions about a chronologically dated event browser. The phrases “summer vacation” and Timmy’s first steps spring to mind – in fact you can argue that that is just the sort of thing a dated events architecture is there to support – not looking across at different projects ongoing – but rather, on a personal level – looking back in time. FCPXs default behavior is a chronologically dated event browser. But other stuff goes in there too – folders can go in there and smart collections, (the tag behaviour rethink of bins) goes in there. Then moving over to the right, we have the tag collections exposed – either as tiles, lists or filmstrips. This section is sort of doing the job of the source viewer and bin contents at once, in a pretty compacted way.
    that leaves room on the top half of the GUI for the viewer, and the inspector panel/colour corrector/wafeforms.

    Thats what we’ve got. And there is a problem with that in that I would argue that the source monitor has got to come back in some form, for certain essential tasks – and where does it go?

    Simon Ubsdell on issues relating to ganging –

    Curiously Gang is about the only thing that I quite literally can’t do without (and I’d seriously hate having to do without Replace) and that’s not being some kind of prima donna – it’s a hardcore fact of life. For almost everything else, even the major stuff, there is some kind of fudge or workaround or third party solution, but not this.

    To be honest – and no doubt it’s a failure of imagination on my part – I don’t see how I will be able to eye-match with FCPX now or in the future a) without these essential tools and b) without some kind of dual monitor arrangement that enables you to see your source clip and your timeline clip side by side. I know that sounds very antiquated in this brave new world …

    The same goes to Multiclip – which Apple have committed to, and well this stuff has to go somewhere – I guess it could be some kind of slide out operation like how projects are exposed (do not get me started an how stupid I think where and how they are exposing projects for browsing is.) but I guess something like that could happen, but I’d argue there could be something else – I want my blank slate back for starters. Jobs are jobs and each job is new.

    I want the blank browser, and the thing that is stopping that is FCPX chronologically exposing every event it can see. Why can’t we have an event browser of some description? cetain adobe products and MS products will open with a kind of custom boot, what do you want to open screen – in the case of FCPX it should be would you like to open a new event, would you like to open any or all of the events I can see here (box exposes events with nice little tick boxes beside them.
    That way I can at least begin to consider what professionally, an event means to me. Given that I am hugely unlikely to source my music from iTunes and my images from iPhoto – I might consider events as repositories for long term assets or something – in any event we are very likely to – if this programme survives professionally at all, which is open to real deadly doubt at an incredibly early stage, I.. actually think its toast to be honest and apple could care less, but if it survives, we are likely to begin thinking about events very differently than the consumer.
    We are going to need some kind of event staging area. You could argue that this can simply be done in the finder but if they sort of *remove* the event area, then maybe there is enough space freed up to invoke a source monitor? I don’t know, I dont actually think this will work thinking about it because the smart collections will still need to expose them selves over in the secnd panel that is eating up the home of source monitor.

    I’m noodling here – but I know I want, and this application pretty desperately needs, a rethink on the control and presentation of events (also I would argue the bifurcation of projects née sequnces into their own ten year old discreet *edit GUI below is needlessly confusing – for anyone – and needs to be completely reassessed.) And I think they are also going to need to reincorporate the source viewer – that could be as simple as collapsing the browser to list, sliding off the inspector to the right say – and then the full source monitor slides into view. They’d even get to animate all of that – which they love –

    (and seriously why, when I delete a clip – does it do a dissolve off? Its better to delete than to fade away apple. Give us a stripped chrome option too. that should be a priority – like graphite in OSX – this thing needs not to be quite so GUI sluggish on recent hardware and anyway The GUI is just too much. there are bloody animations everywhere I look for gods sake. Just turn off the glows, the dissolves, and the bevels, you can hide the option in a preference we need to use a shift key to access.)

    I myself don’t think anyone serious is going to touch this thing without some ability to invoke a source monitor – it has too many uses cases. Its also a perfectly valid expression of the editing thought process, our need to think and look at two things at once – the source monitor is in no way redundant. They have to figure out how to get it back – maybe not on by default, maybe invoking it means that the inspector or the full thumbnail browser are not available simultaneously – but they’ve got to get it back I think. And fix events.

    I still think this software is professional toast, because right this second – it is, and Apple will never.. my impressions of that company and their value systems is, shall we say, radically changed. No more heartfelt listen to their bollocks announcements for two hours for me. that level of engagement with the company is gone and it is not coming back.
    But if this weird thing they’ve birthed dies, if they don’t or choose not to fix it, if this is about where they want it, which lets face it, could well be true, well losing one out of three viable editing platforms is not a good thing. Actually – on an economic, industrial or cultural level – its not a good thing. well done Apple.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

    Aindreas Gallagher replied 15 years, 1 month ago 4 Members · 40 Replies
  • 40 Replies
  • Aindreas Gallagher

    July 3, 2011 at 4:06 pm

    replying away to myself – here’s a really rough projection of real estate –

    https://dl.dropbox.com/u/3421180/FCP%202%20monitor.jpg

    We can see the event area is in quite a bit of trouble – and not really a surprise here – the icons are back around FCP7 scale – so there was a reason for that.
    Also – are tabs completely unholy in the tabernacle of apple? because they would come in really handy in this application. the event area is the real problem. Having bins *kof* *kof* smart collections only expose horizontally into to fat big lozenges or lists with a fat big three part wide lozenges on top – is there no hope for opening things out into windows on this thing? to which the answer really is sadly no. I still want tabs tho.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Andrew Richards

    July 3, 2011 at 5:04 pm

    The current implementation of the Events and Projects Libraries is the most consumery aspect of FCPX, IMHO. I can’t see a busy editor not racking up a simply unmanageable clutter over a relatively short time, even with the folders.

    I think there needs to be a way to hide items in the Projects and Events Libraries, but I disagree on the blank slate. A blank slate suggests a 1:1 relationship of Projects to Events, and that just flies in the face of the whole point of separating the two. You want something just like we had in FCP7 with a Project encapsulating your the contents of your Browser, but that just isn’t the new model. However, if there were a way to selectively hide things in each Library, you could get pretty much the same effect by hiding everything but the one Project and one Event you are working on at a time.

    I just got done submitting a feedback asking for exactly that kind of hiding capability.

    As to the missing Viewer, it really isn’t totally gone if you are using the Inline Precision Editor. Yes, I know a lot of veteran editors bristle at the idea of editing in the timeline, but that is how FCPX was designed to be used, and you get your two-up displays when you use the IPE. They way they executed timeline editing in FCPX is very fast because you can tune your edits without having to manage the space in the timeline, yes, thanks to -DUN DUN DUN- the Magnetic Timeline.

    Taken in total, all the new-fangled stuff makes sense. If you try to apply your habits from FCP7 to any one feature at a time, it’ll enrage you (at least it did for me when I first tried it out). If you let go and use it the way it wants to be used, it is as fluid as the marketing claims.

    And before anyone says anything like “but I shouldn’t have to change the way I work to suit this new app!!!“, remember you had to do it for any other application you ever used, you just got so used to it that you didn’t think about it as working within the app’s natural limits and it just became The Way It Is Done™.

    I’m really curious how they will implement Multi-cam, but I doubt it will result in the return of a dedicated Viewer pane. You will probably get something that slide out like you get in the IPE, but you won’t have a dedicated two window setup.

    Best,
    Andy

  • Aindreas Gallagher

    July 3, 2011 at 5:08 pm

    [Andrew Richards] “but you won’t have a dedicated two window setup.”

    there really should be one. getting rid of it is a mistake. It’s not something to get your head around, or find alternate methodology for. it’s a mistake.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Andrew Richards

    July 3, 2011 at 5:19 pm

    Also, on the subject of GUI real estate, if you use a second monitor, you can send the Event Browser there. That seems like the ideal “pro” layout to me, at least once AJA/Blackmagic/Matrox deliver proper monitoring drivers so that you don’t have to waste the second display on that nonsensical “8-bit preview” (I think this will take Lion and it’s public AVFoundation to implement, but we’ll see).

    I also think fullscreen mode in Lion with two displays will be nice (hide that glaring white menu bar that spoils the otherwise low-light friendly presentation of the GUI), and it seems that’s what they are angling toward.

    Best,
    Andy

  • Aindreas Gallagher

    July 3, 2011 at 5:46 pm

    am I going mad or isn’t that a source and canvas on the main Imac display there?

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Andrew Richards

    July 3, 2011 at 5:51 pm

    [Aindreas Gallagher] “there really should be one. getting rid of it is a mistake. It’s not something to get your head around, or find alternate methodology for. it’s a mistake.”

    I respectfully disagree. And please note I didn’t use your least favorite phrase (wrapping one’s head), but you do need to approach FCPX without prejudice for its GUI design to make any sense. When I first approached it with my ten-years-of-editing-with-FCP-goggles on, I was baffled and didn’t like it at all. Only after I forced myself though a tutorial with an open mind did I start to see how things were intended to work. If you come at it with your FCP experience to guide you, you’ll be lost and it isn’t at all intuitive. It does need to be evaluated on its own merits and not from a perspective of how FCP7 works.

    Objectively speaking, a dedicated Viewer is wasted screen real estate when it isn’t being used (and that is quite often). This is especially troublesome when you are designing a UI that is more laptop-friendly (and let’s face it, a HUGE majority of FCP users work primarily on a MacBook Pro). You get a two-up view when you need one, and the UI morphs to show you other things when you don’t. Why do you need a two-up view all the time? What good is having a frame frozen there from your last selection if you are doing your editing in the timeline, the way FCPX was designed to work?

    A two-up view is only functionally necessary when you are comparing two abutting clips, the out frame of the first and the in frame of the second. You get exactly that with the Inline Precision Edit tool. It serves no other useful purpose, as the functionalities of Match Frame have been addressed elsewhere. The functions of all the other tabs that lived in FCP7’s Viewer window have also been moved elsewhere in FCPX.

    I get that you want your FCP7 GUI model back, but that ship has sailed. Your next best thing is Premiere Pro, but you knew that already.

    Best,
    Andy

  • David Lawrence

    July 3, 2011 at 5:58 pm

    [Aindreas Gallagher] “there really should be one. getting rid of it is a mistake. It’s not something to get your head around, or find alternate methodology for. it’s a mistake.”

    Absolutely correct. One of many!

  • Andrew Richards

    July 3, 2011 at 6:01 pm

    I thought the same thing at first, but note the unified playback controls underneath. It isn’t the inline precision editor either, judging by the timeline. Maybe a pre-release build that didn’t have a button on the bottom of the timeline to escape IPE mode?

    Best,
    Andy

  • Aindreas Gallagher

    July 3, 2011 at 6:05 pm

    [Andrew Richards] ” a dedicated Viewer is wasted screen real estate when it isn’t being used (and that is quite often).”

    with respect, not for me – or maybe we just edit a bit differently, but I really do use the source viewer all the time. I think its conceptually important that its there. Besides – ganging and multiclip are two acknowledged key features – an they both need to be hosted in something that can’t really diverge an awful lot from the logic and function of a source monitor. So you’re going to have to be able to invoke a source monitor? I don’t need the FCP7 GUI back, but they need to figure out the source monitor.

    [Andrew Richards] “Your next best thing is Premiere Pro, but you knew that already.”

    Oh indeed I do. I doth prepare for machine wipe and software installs. A 30 day trial of MC 5.5 even, God help me.

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    July 3, 2011 at 6:08 pm

    but look – there isn’t even any chrome between the windows – where did you get the pic?

    http://www.ogallchoir.net
    promo producer/editor.grading/motion graphics

Page 1 of 4

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