What can we help you with?

Studiocode Tutorials | 5.17 Manual Creation of Movie Packages - Databasing

NOTE: Beginning December 31st, 2017, development of Studiocode and iCoda will stop and new licenses will not be available for purchase. Please consider Vosaic as a replacement. Read More.


In this video tutorial we're going to go over databasing.

Databasing is the process of extracting one or as many instances from any given timeline into another timeline or movie package. Typically this is for purposes of maybe extracting the exemplars is from a given timeline or multiple timelines and dumping them into their own movie package to create a video portfolio of sorts.

So you can see I have two movie packages open intersection one intersection two I'll just point out that back in the intersection one here there is one row that's called something interesting with one instance in it. That's the one row that intersection two does not have otherwise they've been coded very similarly with the same code window so I could use command a to select all the instances in this timeline if that's what I wanted to database but for sake of example I'm just going to choose this one bus row I'll hold the command key which lets me add to my selection choose a couple instances in the stroller row and I'll go ahead and create or a select this something interesting instance as well so today to base those instances I'll just click on the database icon on the timeline there and I don't have an actual database to dump those instances into yet so on the fly here I can just click new standalone database and I'll leave it name database for now and I'll choose the desktop and I'll hit safe.

So you can see that places the icon for the database over on the timeline and you get a little dialogue just letting you know that it's going to export those instances and use a little bit of space on your hard drive so yes and notice before I do that that there's a third movie package that opened here there's nothing in it yet so as soon as I click yes what it's doing is taking those handful instances from intersection one and dumping them into the database.

Now I get a message letting me know that it's updated so it okay now you can see the database here is just another movie package so everything you know about a movie package already holds true and in this timeline or database you can see that it's all of the instances that we just selected but none of the uncoated time so it's a nice way to tear down the number of instances to only the ones that matter the most if that's what you're trying to do.

So I'll close the database here close intersection one another thought is let's take some instances from intersection to and put them in that database as well so in this case I'll go ahead and choose the bus row again I will choose the I'll go ahead and choose the whole stroller row and I'll choose this view obstructed one instance. Remember there is no view obstructed instance of the first intersection one movie package that we database so again I'll go to the database icon here and in this case I don't need to create a new standalone database I can just dump into the one that's existing already and I'll click export so you can see that it opens the database that's already has some instances in there asks if I wish to append the instances from intersection to into the same database so yes and then it'll update that database package with the new information from intersection two.

So let me close intersection two and now you can see in the database here's all the instances and only the instance is none of the uncoated time from the initial movie packages in one place so because we had the same named rows in each of the initial movie packages the instances from those rows appended into the same single row in the database so it's a nice way to take a cumulative look at your coding over multiple packages.

Lastly just to be clear I want to reiterate the fact that a database is just in at the movie package it's not a special type of movie package so for example I could take instances from this database and database them into another new database if I wanted to as well so that process works the same way as what we just saw.

Also be aware that I've been demonstrating a standalone database so all the properties of the standalone concept that you should be familiar with already apply.

Thanks for watching.

Learn How Vosaic Products Can Help You Improve Performance.

Subscribe to our blog for tutorials, announcements, and updates.

We need your contact details to provide you with support, answer sales questions, and inform you about our product updates in a timely manner. We also provide many exclusive subscriber-only offers. Please check to subscribe. Check our privacy policy for the details on how we protect and manage your submitted data. You can unsubscribe anytime.