Writing XML files for later use

[solecize]

This would probably be a feature request, but I thought I would start here to see what people think.

1. I would like to use VIDBlaster to edit live footage for a TV show style vidcast (It seems this is well covered by VIDBlaster)
2. The cameras we are shooting on will be shooting in a much higher resolution and we'll be down sampling for the vidcast. (Not sure if my computer has the horse power to keep up with multiple live HD sources)
3. I was wondering if it is possible to store the VIDBlaster transitions (ins and outs) in an XML standard that could later be imported into an NLE like final cut pro, or Vegas. (I don't know if VIDBlaster has a "macro record" function or anything like this built in). There are various conform data structures already out there, I'd just like a way to remember what transitions I pushed and when I pushed them.

This would allow me to take the raw camera footage and apply the same transitions in the editor for export to some other format. This would also require VIDBlaster to keep up with timecodes etc. which may be asking too much, but I'd definitely pay more for the pro version if it had those capabilities.

So you may ask why I would want this functionality. Basically I'd like to shoot a video and stream it live to the web, but I'd also like to take the transitions from the live version and use them to produce a high definition version of the video for publishing at a later date without having to re-edit all the footage.

The cameras we'll be using are a RED One and an HVX

J.D.

[Mike]

See http://vidblaster.com/forum/index.php?topic=123.msg514#msg514.

[solecize]

I'm less interested in the actual transitions themselves than I am interested in where the transitions happen. What I would like is some kind of XML log that would tell me where all the cuts are. Then after the live show I can go back and re-cut the footage at a higher resolution in an NLE like final cut etc.

There is some software called crimson that does a good job conforming XML and various video sources for the cinema industry specifically for footage generated by the RED One. If you could generate XML usable by this software for post production that would be awesome.

http://www.crimsonworkflow.com/home.htm

Otherwise the workflow for the show I'm producing would be:

1. Acquire and broadcast footage live
2. Capture all footage from live and camera source
3. Compare captured footage to live
4. Re-cut footage based on live in NLE
5. Export high resolution footage NLE

What I'm really looking for is:

1. Broadcast footage live
2. Capture all footage from camera source and XML data for transitions
3. Apply XML from live to camera footage in NLE
4. Export high resolution footage from NLE

[Mike]

Took some effort but I managed to move your post to the right thread. I referred to the other thread not for the transitions, but for the description of the transitions. I understand now that you do not need these.

Frankly I do not quite see your problem. Why won't you record in highres in VidBlaster, and skip the whole NLE step? Wouldn't that be what you're really looking for?

[solecize]

I don't have a computer that is fast enough to mix two ultra-high def sources for a final output of 4096x2160 in real time, but if I had the in/out data for the clips then i could take the sources into any NLE and remaster in ultra high def for blu-ray or cinema distribution.

There are probably very few systems in the world that can live edit a 4k source- I might venture to say they don't exist. Plus I don't need high resolution for the web feed, only for the re-master.

Here is a schematic of the setup

RedOne Cam A RedOne Cam B
| |
| ======> 1080p output
===================> 1080p output Computer/ Vidblaster ====> Live feed
| |
4k acquire 4k acquire
| |
| ======> 4k footage
===================> 4k footage NLE/ Vidblaster data ====> 4k master for cinema/disc distribution

[solecize]

FYI- i'm going to buy vidblaster anyway for the live distro of our show. It's a much better value and the hardware mixers will never offer what i'm asking for, so Props for creating a great product.

If you want i could help do some testing or send you footage of the program pilot. Or if you figure out a way to squeeze a 4k image out of a computer in real-time I'll be the first one to sign up.

FYI- here is a link to a single frame of a 4k image for reference (http://images.digitalmedianet.com/2007/Week_8/eh78xw8b/story/4kstill.jpg). Our camera generates 30 of these a second.

[Mike]

Thanks.

Ah, well there's highdef and then there's highdef :) That res no doubt will be supported by VidBlaster one day, but we will have to wait for a suitable PC to come along.

So "all" you need is file stating which transition was done when, right? What protocols does your software support, and can you give me a link to where it's explained? As basic as possible please, as I only need a few relevant commands.

Great still, reminds me of a scene of Coach Carter. Wish I had this resolution in my home cinema :P

[solecize]

I'll take a look and see what I can find. I'm sure there are a few standards. I'll try to find the one that is well covered and fairly basic.

I understand that this is not a trivial request and really appreciate you looking into it. It speaks highly of your product and level of support for a budding vidcast industry.

[solecize]

here is the apple xml interchange format spec from their dev website. The clips section specifies elements for ins/outs.

http://beta.devworld.apple.com/documentation/AppleApplications/Reference/FinalCutPro_XML/Elements/chapter_5_section_1.html#//apple_ref/doc/uid/TP30001156-TPXREF101

Here is an example clip:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE xmeml>
<xmeml version="4">
<clip id ="Jeremy Solo">
<name>Jeremy Solo</name>
<duration>188</duration>
<rate>
<ntsc>TRUE</ntsc>
<timebase>30</timebase>
</rate>
<file id="Jeremy Solo1">
<name>Jeremy Solo1</name>
<pathurl>file://localhost/Jeremy%20Solo</pathurl>
<duration>188</duration>
</file>
</clip>
</xmeml>

[Mike]

Does this mean you will be editing in FCP, or is it such a standard that whatever you will be using supports this (proprietary) protocol? I can add this, but as you are currently the only one asking for it I won't invest my time until you show your commitment. Hope you understand.

[solecize]

I thought there was an XML standard across editors, however it looks like each one has their own method of import export. Yes Final Cut would be my primary method of editing. I understand that you can't work on it until I invest in your product. Thanks for taking me seriously.

J.D.

[Mike]

Figures :)
Ok, I'll use this one then. FCP seems like a safe bet anyway. Let me know when you've ordered and I'll get to it.