Nikolas Bäurle
Forum Replies Created
-
[james Lackleter] “You nailed it, I work for Adobe, Autodesk, and Avid… They pay me to mar Apple brands.”
I apologise if you thought I was accusing you of propaganda. I should have been clearer, even though I didn’t mention you…I was speaking in general terms. This isn’t the first time someone has been warning people about X. I was just throwing around ideas, and its very possible that something like that could be going on in any forum. That comment was not directed at you, I should have made that clear, sorry about that.
But still, it would be interesting to know why you think its necessary to spend time warning young editors about X? Especially when most of your facts don’t seem to be a problem for anyone else in this debate?
-
[Oliver Peters] “I guess the puzzling part is why someone feels the urge to warn everyone else away from the software. Clearly a bad experience, but what else? “
For the same reason FCPX editors like spreading the word, people who don’t like it have the need to spread their opinions, especially since many still feel deeply hurt by Apple for killing Legacy, even though it still works. But many still want a better version of Legacy.
I find it interesting when people spend time making a software look bad, but don’t really know how to use it, and don’t need to use it. Wouldn’t it be better spending time telling other people what software you recommend and like using without trying to make others look bad? I think its the fear of something different, and the uncertainty that perhaps you might at some point not be taken seriously anymore.
Or there really is an agenda behind some of it. Gettin payed to spread the word.
“Always look on the bright side of life” – Monty Python
-
[Andre van Berlo] “If I would be an editor using a program that has been bashed for 2+ years by an entire industry, would I put my credibility on the line by telling people I use it?”
This is probably true for young editors starting out, but it also depends what part of the media industry they want to work in. I don’t see why this would be an issue for any experienced editor.
In my experience most editors in the industry in Germany don’t like FCPX, especially since they haven’t really used it, and most larger companies don’t take it seriously yet.
However, I haven’t lost any credibility by telling people I like it. Why? Because producers see what I can do.
As a freelance editor I can use the software I like when I edit at my home studio, but need to be proficient in other NLEs to get jobs, that’s always been the case and will never change.[Andre van Berlo] ” Some are apparently more open and yes I believe that perhaps no serious in La editor is using it.”
But what constitutes a “serious editor.” Anybody making a living editing is a serious editor. And there are plenty of people not involved in film working and living in LA. Film and Large Broadcast Editors aren’t better, they might be considered better by many, since we are judged on the quality of the content we edit which has less to do with skills, but the connections one has.
“Always look on the bright side of life” – Monty Python
-
excuse me, it only handles red code well? Simply not true.
“Always look on the bright side of life” – Monty Python
-
[james Lackleter] “Just another note, if you use X you will not get hired in NY, LA, or London.”
That doesn’t make sense. If you ONLY knew how to use X then that would be the case. And in that case you probably haven’t been an editor for very long.
James, are you aware that most people posting here have been editors for quite some time and actually know how to use other NLEs as well? I still make most of my money (90%) on Avid and Legacy, that doesn’t mean X is a bad software, because funny enough I actually prefer using X, sorry about that.
[james Lackleter] “I’ve poked this programs with more holes than swiss chess”
Based on what you have been posting I still feel that you don’t know or haven’t started understanding X…or simply refuse to like it.
Mastering a software takes time, not just looking at it once in a while and only trying to find bugs. Most editors at the places I work for have never really dealt with X, but alway have big opinions. And most of them have never actually finished a single project on it…Your advice to young editors is very biased, and you won’t be helping anybody that way. Most young editors won’t be getting jobs in LA, NY or London… and most won’t be getting those High End Broadcasting jobs either.
You keep on using the word “fact” but I have a feeling you’re ignoring the post disagreeing with you from people who are making a very good living with X. Oh, sorry, according to you, people using X don’t have a clue what their doing… The only fact of your’s that I would agree with is that X isn’t an established software yet, but that has absolutely nothing to do with its quality.
“Always look on the bright side of life” – Monty Python
-
Patrice, thanks for reminding me! FCPX editors (especially those European ones) are amateurs, of course, we love earning money just for fun! So we really are unemployed after all, it’s just a hobby…:-))
[Patrice Freymond] “and imagine that: I thought I’d been an editor for 33 years…but since I use FCPX daily, it must be a figment of my imagination…”
Are you sure you are using FCPX?… Did you take the blue pill or the red pill?
“Always look on the bright side of life” – Monty Python
-
Hey Tangier, I just did a quick test, and in this case I did open the package contents:-) while it was still in copying process.
If both libraries are on the same drive, in my case a USB-3 WD Elements, X doesn’t take any time at all to copy. I opened the package contents immediately and the files were inside the new event. X was simply generating waveforms for a couple of minutes, while I was checking out the package contents.
Then I created a new library in my system SSD Drive. When I moved the event to that library X created aliases, then the program started generating audio waveforms, then it started copying files. The aliases turned into blank files with .fcpcopy added to the end of the name, while each was copying. It seemed to take the same amount of time to copy than it usually would dragging files from one drive to the other.
X really does seem to mask the copying of files inside the same drive. The interesting thing is when I duplicated the Transcoded Media folder it took 15 minutes for 42 GB… copying the 42 GB event to a library on the same drive takes no time at all, except for the few minutes of waveform generating.
“Always look on the bright side of life” – Monty Python
-
What exactly doesn’t work for you? Audio levels? Works like any other NLE. XML works very well… and whats wrong with color correction, other that you can’t keyframe it yet. With the color board you can do the same correctios as with a 3-way color corrector
“Always look on the bright side of life” – Monty Python
-
I’m sorry, but using that Conan youtube video (sooo old) shows you don’t really know how to use X yet.
There are plenty of things Apple needs to improve, but most of the ones you mention work very well.
“Always look on the bright side of life” – Monty Python
-
[Tangier Clarke] “After the update to 10.1 I had a library that was essentially the name of my drive with all of the events and projects I had from the previous version of FCP X. “
That’s normal. You can hide 10.0.9 events and projects and only keep the ones online you need at the moment. You don’t have to update everything at once.
Even if you do its not really a problem, since you can create new Libraries and drag the events from the “Drive Library” into your new ones, making one for each project.
Personally I prefer to make one library per project, and create a folder for each client to put the project libraries in. The nice thing about the libraries is that you can put them anywhere. And I don’t see any reason for moving or hiding things on finder lever anymore. The only reason to do that was that “FCPX Legacy”:-) wasn’t able to on/offline events
[Tangier Clarke] “How: Quit FCP 10.1 then use “show package contents” to remove the appropriate event folders from current library and copy to package contents of the new Finder-level project library I created in FCP X. Next I deleted the original event.
Result: Restarting FCP 10.1 the new project library had nothing in it. The original had the name of the event, but no content. No Go! “
I’m sorry but if you fiddle in the package contents you set yourself up for those kinds of problems. There’s absolutely no reason for doing that. Make a new Library in X and drag events from one library to the other, it does it pretty quickly as far as I can tell, and it doesn’t screw up anything 🙂
“Always look on the bright side of life” – Monty Python