[Andy Neil]

Well, certainly that’s the answer to the workflow. Although it’s poor solace for those of us who aren’t experienced or fluent in Illustrator. But it doesn’t really answer the question of why these problems exist in programs that come in a suite, presumably because they’re supposed to work well with each other.

I’m not naive. I get that there are things that are handled differently between programs, or don’t translate well. But if you were Adobe, would you have 3 different ways of handling vector shapes, one for each program? Or would you try to consolidate the feature so that they are essentially transferable between programs? It seems a no brainer to me. If there’s a good reason it’s this way, I’d love to hear it.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

[Andrew Kimery] “PPro will automatically create 8 audio tracks in my timeline (assuming it has less than 8 to start with). even though I only have 3 activated.”

I’m not sure we’re talking about the same thing, but I’ve noticed that when Premiere loads a source with more tracks than the sequence, there’ll be a little plus sign on the last visible track. you have to click on that to expose all the source tracks and from there you can deselect to prevent Premiere from making new tracks in your sequence.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Wow, Herb, that was fascinating. Thank you so much for clearing some of that up (as clear as it can be anyway). I’ve always been annoyed with how Premiere handles audio, and this has certainly not made my opinion any kinder.

The last few days have been an interesting flight into the dark recesses of Premiere audio and Premiere multiclips. I’m sad to say it hasn’t been much fun. The fact that they give you the opportunity to edit multiclips, but if you do, you can screw up your multiclip is an interesting feature.

I ended up rebuilding the multiclips as Camera 1 clips. It works fine if you open the multiclip in the timeline and make adjustments provided you do so before ever loading it into the source monitor. The second you double click the multiclip, you lose the ability to make changes without screwing it up. But as long as you don’t, I was able to delete tracks and move tracks around until I had the sources I wanted.

When I’m done with this project, I’ll try the Switch Audio version although I’m not really clear about the implementation. Is it like Avid where you can right click and change the audio source in the timeline?

I hope Adobe does some work on their multiclip implementation in the future. It seems like they got the bones of a good feature, but it’s not well executed as of yet.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Thanks Herb. The multiclips were definitely made using Camera 1 setting. Can you elaborate on how the three types are different and why you can add sources after the fact to Switch Audio and All Cameras but not Camera 1?

BTW, I remade all the multiclips with Camera 1 (not really knowing the difference), and was able to get the right number of tracks and audio sources. It only “freezes” the configuration after the first time I load the multiclip into the source monitor. After that point, I can’t change anything.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Copy/Paste doesn’t work into secondary storylines (sadly), even if you select the storyline container first. If the copy/paste is in the same sequence, you can select the clip you want to copy and then hold OPT and drag a copy into the new storyline.

This, of course, doesn’t work when you’re copying from other projects. For that, usually I just paste to the end of my sequence and then drag the pasted clip/clips into the secondary. Not ideal, but…

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

[Mark Smith] “I’m no web master dude, so hence the question.”

You’re directing your question to the wrong place. You should be asking webmasters and HTML gurus. That’s where any parcing of meta-data is going to have to happen.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

When posting crash threads, please do not post the ENTIRE crash thread. It’s not necessary and it janks up the website formatting. At the top of the crash report, it’ll tell you which thread crashed:

[Robert Rinkewich] “Crashed Thread: 0 Dispatch queue: com.apple.main-thread”

And then you just need to post the actual thread that crashed:

[Robert Rinkewich] “Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff8cc654dd objc_msgSend + 29
1 com.apple.QuartzCore 0x00007fff8d353fe0 CAAnimation_setter(CAAnimation*, unsigned int, _CAValueType, void const*) + 117
2 com.apple.QuartzCore 0x00007fff8d35501d -[CAPropertyAnimation setKeyPath:] + 31
3 com.apple.QuartzCore 0x00007fff8d358ccd +[CAPropertyAnimation animationWithKeyPath:] + 62
4 com.apple.FinalCut 0x000000010a59a27a -[PEMeterLayer layoutSublayers] + 3082
5 com.apple.QuartzCore 0x00007fff8d33f904 CA::Layer::layout_if_needed(CA::Transaction*) + 366
6 com.apple.QuartzCore 0x00007fff8d33f782 CA::Layer::layout_and_display_if_needed(CA::Transaction*) + 24
7 com.apple.QuartzCore 0x00007fff8d33ecf1 CA::Context::commit_transaction(CA::Transaction*) + 277
8 com.apple.QuartzCore 0x00007fff8d33ea24 CA::Transaction::commit() + 508
9 com.apple.QuartzCore 0x00007fff8d34d917 CA::Transaction::observer_callback(__CFRunLoopObserver*, unsigned long, void*) + 71
10 com.apple.CoreFoundation 0x00007fff999ebe37 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
11 com.apple.CoreFoundation 0x00007fff999ebda7 __CFRunLoopDoObservers + 391
12 com.apple.CoreFoundation 0x00007fff999dd358 CFRunLoopRunSpecific + 328
13 com.apple.HIToolbox 0x00007fff98068935 RunCurrentEventLoopInMode + 235
14 com.apple.HIToolbox 0x00007fff9806876f ReceiveNextEventCommon + 432
15 com.apple.HIToolbox 0x00007fff980685af _BlockUntilNextEventMatchingListInModeWithFilter + 71
16 com.apple.AppKit 0x00007fff8be4f0ee _DPSNextEvent + 1067
17 com.apple.AppKit 0x00007fff8c21b943 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
18 com.apple.AppKit 0x00007fff8be44fc8 -[NSApplication run] + 682
19 com.apple.prokit 0x000000010a98842f NSProApplicationMain + 329
20 com.apple.FinalCut 0x000000010a533bf0 main + 1344
21 libdyld.dylib 0x00007fff995315ad start + 1”

It’s much cleaner. But in reality, very few of us understand crash threads at all. Maybe you’ll get lucky but I can’t tell what’s happening with your computer. On the surface it sounds like some kind of memory issue. But again, I don’t read crash threads or understand them.

I would try creating an identical compressor setting for 720p (which codec are you using: pro res or H264?) and share via that to see if the crashes go away.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Ok. You likely have two things going on here. First, your proxy media was showing as offline because you never asked FCPX to make proxy media from your original files. This can be confusing, but basically this boils down to a display issue. One that you’ve solved, based on your post. As long as you keep the display showing original media, you should be fine with your media. If you desire to work with proxies, you can always select all the clips in your library/event, right click and choose Transcode to have it create proxies. It’ll do this in the background but you have to wait to use the proxy view until it’s finished.

The second issue is one that I see with people new to FCPX. Every clip in your browser can be opened in it’s own timeline. This is a convenient way to make changes to the master clip before it ever makes its way into a sequence or “project”. What I’ve seen often is that sometimes new FCPX editors will open a clip in Timeline and proceed to edit their project inside that clip (which FCPX allows you to do). The downside to this, aside from ruining one of your master clips, is that if you crash, FCPX won’t know where you left off and it’ll look to you as if your project went missing, when in reality, you never had a project to begin with.

The short answer (hopefully) is that no, you don’t have to start over. However, the long answer is, you’re going to have to right click and choose Open in Timeline for every one of your clips until you find the sequence you’d been working on. Once you do. you need to create an actual project (CMD+N) and copy/paste the contents of that clip into the project. Then, it’ll probably be a good idea to reimport the master clip you mangled my editing an entire project into it.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

You can embed QT movies with meta-data inside FCPX. The real question is whether or not that meta-data can be read by another app, script, or browser plugin. That I don’t know.

In FCPX, though, if you select a clip and open the inspector, under the info tab you’ll see all the meta-data associated with that clip up to that point. You can also add custom fields. You can try running tests where you add meta-data and then try to read it with your site search.

Of course, and easier route might be to use a hosting site like you tube or vimeo for your videos. Those sits allow for “tagging” of the video which can then be searched for.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

When you say you’re sharing a couple at a time, what exactly do you mean? There’s no batch export in FCPX so are you just exporting one, then exporting the next while it’s working on the first? Also, did you create a special share setting or are you using a default FCPX share? Do you have Compressor? If so, are you using a compressor setting or can you try with a compressor setting?

Andy

https://plus.google.com/u/0/107277729326633563425/videos