Erik Lundberg
Forum Replies Created
-
Agreed. And nerely every piece of software that we use that thrives on XML has their markup base. Yes, they’ve had to change things around inbetween 7 and X, but that’s far from inventing a new and improved secret way of writing XML (remeber, “XML was stoneage, and we now have found the holy grail of markup languages!” according to apple just a while back). Of course it couldn’t be the same XML. X does things that 7 didn’t (and in some ways didn’t need to). Now it’s more of the wait and see-game to find out who makes the feature usable (apart from exporting and importing back into X)…
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
Ok. Admittedly, some of the published parameters came through. In my text templates (lower thirds, subtitles) text were exported/imported. Rigs, drop boxes, colour settings, build in/out-settings did not. Which surely is a bummer if your work heavily relies on Motion Templates and riggings of those.
So far we are at our facility still in wait and see-modus. And we will surely not make any decisions just yet. More likely late 2011/early 2012. And FCPX is as we see it not yet the thing we need. Yet. I would very much like it to get there though. There are some fun rides.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
My answers are a bit slow here (still in moderation mode, might be for a while still). It does work at my end. I have no idea what David is trying, or why it isn’t working. If you would like me to walk you through, I’d happily do that.
I did export an XML-file from FCPX 10.1. Imported it back in. Everything came through nicely. Apart from the settings on published parameters on my Motion templates. They were reset to the default values (=not included in the export). This is an issue, yes, but shouldn’t be too damn icky for the apples to toss a fix together on that. Feels more like (again) something overlooked.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
The XML from 10.1 seems to be very much the old familiar xml version 1.0 we (or at least some of us) has been staring at for (in my case) at least 8 years now (including the ?xml version=”1.0″ encoding=”UTF-8″? -tag…). They might have had to make up a bunch of new markers and tags and stuff to get this working, but it’s not that alien as what they threatened us with in the FAQ. The things the exporter (for now) misses are settings on published parameters on Motion templates. Which surely must be something they (=apple) can address. Either way this reassures me that there now are means to get things (with a little translational help) into this island to and from other vessels.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
Just did. Worked for me.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
Just because there is an XML-import/export option doesn’t mean there is an XML-translator (=import any kind of XML and make sense of the tagging system of that particular XML). To try to import an XML that isn’t encoded in a way the program in question can relate to (directly and tag for tag) will result in gibberish at best. Someone (or something) needs to actually translate the tags of the source-XML into strings that the destination program can handle. Trying to import an Digital Rapids Stream 1.5 XML into FCPS didn’t work that well either. Anyone that tried, should try something different to do with their time.
At the same time, would be nice if apple in their next effort made (at least a half assed) effort at giving us FCP7 XML translational capabilities to FCPX. As for now, the XML in/out features is just goodness waiting to happen. It merely means there are ways of getting stuff in and out of the X into/from other software, if anyone cared to teach the other end to speak/translate the markups.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
But now at least, since FCPX is now using the same basic way of communicating , there should be a viable way to get someone to make a translation from a FCP7 flavoured XML to a FCPX flavoured XML.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
My take is that FCPX as of now has some issues with render files. I’m seeing this kind of artefacts too, mostly related to transparency when rendered. Re-rendering sometimes fixes, and sometimes not. Hopefully ironed out sooner than later.
Erik Lundberg
Technical Director, Media Technology, University of Gothenburg, Sweden
-
” with the Panasonics machines you can set them to play DV out instead of pro can’t you?”
Not really. Not in my world. Which, I should’ve mentioned, is PAL. PAL-DV and DVCPRO25 uses different sampling resolutions. And apparently the DL-card uses field-reversal to work with virtually every other codec there is. Just not DVCPRO25, which is the reason why this problem occurs for this specific codec. This happens not at playback, but at capture. So the material is captured with the wrong field order. Which can be dealt with. By methods that craves a) a lot of rendering b) lowering quality. Something we don’t want. This is just something that should work, I say. I would like to have a neat way to capture PAL-standard DVCPRO25 material via SDI, edit it, and then print it to DVCPRO25 via SDI. So far BM hasn’t been able (or should I say bothered enough) to provide us with the means to do just that.
The only decks we have that uses FW are DV and DVCAM-decks. And sure, but again that requires rendering to match the standards.
-
This happens to me as well, with the same setup. I’ve found that going into the preferences and switching inputs from/to analogue/digital back and forth “awakens” the card. Don’t know why, but it does. Restarting does work to, but takes a wee bit longer.