No.
The Vegas project is the veg file and premiere would have no clue what to do with it. Vegas is non-destructive and never touches the original media.

I have no idea what level of experience the OP of this thread actually has but the question he poses begs a lot of answers in different directions.

It is not necessarily a question of .veg file project opening in another app - but more of a considered workflow matter.
Indeed SCS has worked to some degree on the transfer of an .xml file export to other apps but there is a really serious concern of whether they are taking the best approach.

This forum has been strewn with really sad and heart-wrenching case studies of vegas editors who wanted to collaborate with someone else's environs. And only to discover it is super tough going.

You might be able to do what you want with this translation program:

http://www.aatranslator.com.au/

Steve Mann, videoITguy and Laurence are all correct.
Premiere can't open a veg file and yes it is all about the workflow.

The latest version of AATranslator (v5.8) can open a veg file and convert it to something that Premiere can read eg an FCP xml and vice versa.

This is great for either one off one way conversions or two way conversions PRIOR to the application of effects as fx are not converted.

So while AAT goes further than any other application as far as conversion of detail goes there always comes a time when a project needs to be finished on one computer.

Runaway, your singular post is most interesting - any personal experience with AATrans/? This program has not been discussed here before to my knowledge.
You are suggesting that it does exactly what VegasPro already does to export a cuts only version - only you make a point of two-way exchanges? is that true with what versions of each program I ask.

This still does not deal with what I feel is the fundamental flaw of VegasPro development for workflows which is to export/import timecode properly or to work with better video codec transfers. This is something SCS really needs to get it right.

videoITguy,
BTW I'm one of the developers of AATranslator and I write the documentation.
http://www.aatranslator.com.au/

Re your "...fundamental flaw of VegasPro development for workflows which is to export/import timecode"
I have to agree (well my take - paraphrase) lovely as VegPro is in many ways it's import/export file options tend to trash BWF timecode metadata.

Eg, re the Vegas formats we support:--
1) AAF export all media converted to AIFC (.aiff) mono files, so timecode gone.
2) to Final Cut Pro - xml (what we call F-xml); a quote from my doco.
To Export as F-xml
File > Export > Final Cut Pro 7/DaVinci Resolve (*.xml)
You will be given the option to choose the location for your new F-xml & and also modify it's name. Suggest you add -F- to the original name.
Important; Having clicked 'Save' you'll see a message 'Export media pool?' – Click NO
Though 'Yes' has an obvious advantage that media is copied it has distinct disadvantages.
Each clip becomes a 'consolidated' file with no handles.
BWF info (meta data) like timecode is removed.
Some media (Eg MXF) maybe split into mono files, with new randomly named files. This can make finding extra 'streams' that maybe required in Audio post a laborious job.
If you had chosen NO to 'Export media pool ?' Ie the recommended option.
The F-xml will refer to exactly the same media as used in the Vegas original Edit.
So, if Vegas default option ignored it is possible to interchange (well export from) FCP to Vegas Pro using AATranslator.

3) Sony Vegas Script Xml (we call this V-xml) is fine with regard to timecode.
IMO this format has merit (the fact the scripts have not been included since Vegas v9 leads me to think Sony is backing away from this format {we include slightly enhanced scripts with AATranslator}

The 'deal-breaker' for us, which motivated us to read native .VEG files is that both V-XML and Vegas EDL (txt) have 'Issues' with 'channel mapping'.

Vegas -XML does not preserve audio channel mapping if using audio files with greater than 2 channels (Eg poly Wav). A mono channel is always mapped as though it came from channel 1.
The Vegas-edl (v-txt) format is fine with poly files though not stereo media. Mono mapped from a Stereo file is always returned as going to chan 1&2.

AATranslator can read audio channel mapping from the Native VEG format, which has no such issues.

videoITguy, "are suggesting that it does exactly what VegasPro already does to export a cuts only version"
Hmm, not sure what u mean.
But we are 'audio' focused, can convert near all 'detail' contained in a source format to a destination format; this can go way beyond simple 'cuts'.

As to video;- we don't attempt to understand / convert Codecs Required or dissolves / overlays / stretch /sub-titles /etc. But we do-can pass on single or multi clip vid info to DAW's / NLE's that have the potential to understand this stuff.

To get a good ideal of what I've found as to DAW/NLE capabilities & what 'detail' AATranslator supports, please have a look at my MS Excel XLS, http://www.aatranslator.com.au/ccount/click.php?id=7

John Lundsten
AATranslator, London

Thank you John Lundsten, for a very informative post. It is always nice to hear from the development people as insiders. I keep my ear close to the BlackMagic Design team as they and now I can see from you as well have a very keen ear about what is goin' down.

This is good inside dope and I would think that we are pretty much on the same ball field. SCS has been fumbling a bit in recent years and is really letting down the NLE user as well as letting third-party support go astray.

John - did Sony ever publish a codex or map of the veg file, or did you figure it out on your own?

Thanks for your post/update John.

Hi John

Now that you are reading directly from .veg files (if I understand you correctly) I wonder if you might consider a slight diversion from your main line of business.

A problem that has occasionally occurred to people hereabouts is that a .veg file becomes corrupted in some way, and will no longer load. (Vegas can provide pretty good autosave and backup facilities via scripting so there will often be an alternative .veg file available that will allow you to continue without having lost very much, but sometimes all you have is the now damaged .veg file.)

What would be very helpful in these circumstances would be a utility that could parse the .veg file and recover as much as possible of the information that can still be understood into a new working .veg file. I don't suppose you'd be interested in making such a utility available (assuming you have indeed worked out the secrets of the .veg file format)? Obviously, the market for such a utility would be pretty tiny so I don't suppose it could really be justified on financial grounds, but it would be an absolute lifesaver on those (admittedly very rare) occasions when it would be needed.

Or perhaps an option to attempt to recover data from a corrupt .veg could be added to the capabilities of AATranslator. In fact, thinking about it, the ability to rescue partial information from corrupted files of any of the formats you are able to deal with would probably be an attractive feature to customers. (I don't know how often other DAW/NLE's files get corrupted but I expect it happens occasionally. I should think their users would be just as glad to be able to recover at least something from the corrupted files as we Vegas users would be.)

Many thanks for making AATranslator available - I know it has saved my brother's bacon a number of times (he's a professional sound man, I'm just an amateur).

Mark

Steve M

John - did Sony ever publish a codex or map of the veg file, or did you figure it out on your own?

Steve, I don't write the AATranslater code, so can't say for sure.
But Sony are for sure 'helpful' and appreciate what we can add to their app.

My informed guess is in this case my programming partner worked out .VEG on his own.
John

thanx rraud.
Though we sell AATranslator licences, or we think the $$ we ask is more than reasonable, our main motivation is to free fellow creative people to use / interchange between whatever DAW's / NLE's they want to use.

And for me no problem, the 3rd share I get from AATranslator sales is approx $3/hr, the reason this rate is so low is what we do is stupidly massively complex, so requires hours to get get right/usable.
John L

Mark
yes we do now read .VEG files and also xxx.veg.BAK if they are renamed to the form xxx.veg.

Now as to veg file becoming 'corrupt':--
1) from what I've found VEG is far more 'robust' than most formats.
2) but Vegas Pro has a 'death wish aspect' if u choose to export to FCP-xml, aaf & others. A new VEG will be written, if it's written to same location as the original VEG, then the original VEG will get overwritten with a 'lame' dilute less well featured VEG .

I don't want to steal my partner's thunder but......

First let me say that some pretty well placed guys in Sony have been nothing but supportive of our efforts. However, Sony is a big company and no one person has total control so the VEG file schema, for their own reasons, was not forthcoming from Sony and we respect that but as John has pointed out we also respect the need for Vegas users to interact with other DAWS . So with a bit of jiggery and a bit of pokery we pretty much have the format nailed purely by working it out for ourselves.

If John is getting $3ph I think we may need to review his payments LOL
But seriously the reason is that John goes to unbelievable lengths to test each source format and then test it against each destination format - I'm talking thousands and thousands of man hours without which AATranslator would not be as it is today.

As to corrupt session files it really is not possible to anticipate 'corruption' and then be able to recover from said corruption when reading session files so a blanket function to do that is not really possible. However, we have been known to try and manually assist users with corrupt session files. Now as you would expect this can be pretty intense sort of work but feel free to ask, however, don't be offended if we are unable to help

"This program has not been discussed here before to my knowledge.
You are suggesting that it does exactly what VegasPro already does to export a cuts only version - only you make a point of two-way exchanges? is that true with what versions of each program I ask."
No not really - AATranslator does far more than 'cuts only' and as John has pointed out a quick look at his 'conversion guide' which is available from our website will detail exactly what we convert from one format to another and back again. However, we are the only session convertor that is able to convert the maximum amount of detail possible.

There are limitations not only as to what we can read but also what we can write that makes sense to another format. Add to that we don't do midi, fx/plugins or any more than basic video (depending on the destination format).

Forgetting ProTools, OMF & AAF for the moment you get all that functionality for the $59 'Standard' version of AATranslator ($199 if you want to interchange with PT, OMF or AAF).

I'll finish by reinforcing our support of our users and our product in that not only have we never charged for updates but we continually and regularly improve and enhance our product.

Feel free to or suggest improvements or ask questions of either John or myself.

Wow...another thread where a question I've been wondering about (as a complete newb) immediately balloons into esoterica many levels beyond my understanding.

Is there a workflow where vegas and premier can be used together in a project, or is it a matter of feeding the results of one program into the other?

3d87c4 - there is no pat answer to your question. This thread started with what we believe was a request by a professional - in which a workflow would have to be developed between two editing entities- think of it as like a housing builder asking for a third party contract to negotiate with the home owner how to have electrical conduit installed. NO easy task my friend.

If you are a hobbyist - then you have different options - check the feature set of VegasPro12 build 770 and definitely search Premiere in this forum. You head will burst pretty soon.

Thanks...fortunately my eyes glaze over long before cranial pressure reaches dangerous levels.

I get it that most of these threads are between folks working at a whole 'nuther level. I pop open a lot of them hoping some info will sink in. A few crumbs for us mere mortals would be appreciated. <G>

Cheers.

It never hurts to ask questions ;-)

On a very simple level I think it is fair to say that even if you are working with another person at some other location who is also using Vegas there comes a time when the project has to be finalised on a single machine and once you reach that point there can be no more to-ing and fro-ing.

The same applies with 2 people using 2 different daws - it just happens to occur earlier in the project.

Using AATranslator means that you can convert from one daw to another and back again which means that you don't have to bounce down to stems and move large amounts of audio back and forth all the time. You could for example just record a small solo section to a session and return just that audio clip and the session file rather than bouncing down say 30mb of mostly silence and sending that back.

A simple example I know but like wise you could send your session and audio to another person and maybe all they are doing is applying fades & automation and then all that has to be sent back is the session file and it goes on from there.

But you could ignore all this and just keep bouncing and sending each track over and over - doesn't cost any money but of course you lose all your separate clips/regions, fades, volume/pan/mute track automation, track names, etc, etc.

I think you get the picture

Its really all about choices and what works best for you and your circumstances

As an aside, you would be very surprised to learn how many of our users receive PT sessions where the client assumes it is going to be mixed by a REAL daw (PT) and our AAT user converts it to Vegas, Nuendo, Reaper, what ever and delivers the finished product back to the happy client who is none the wiser ;-)

Edit:
"Is there a workflow where vegas and premier can be used together in a project, or is it a matter of feeding the results of one program into the other?"
I think I answered that but if not the answer is both. You convert one session to another and the other person opens it up and pretty much sees what you see.
They can make changes and just send back a converted session and any additional or altered audio.

I go back to my earlier observation, SCS has kind of put their eggs in a basket where they are trying to satisfy this to and fro outline that Runaway alludes to. With VegasPro 12 build 770 they want the user of one NLE to suggest the cuts session to another edit suite.

I maintain this is a seldom if ever real world situation that one would encounter between two edit houses. RATHER for large scale projects you employ entities that can do certain things - say I want titling from one house and complex compositing from another. Then the to and fro exchanges are more about format of digital intermediates and such workflow - not composing full composition cuts to another editor.

FWIW,
using the new import and export functions,
I've been able to go perfectly from Vegas 12 into After Effects (cuts only)

and back and forth to FC7 (cut only also) (31 tracks worth!) (I had to fix the frame rates in the XML using cut and paste)

I've also sent it into Resolve which incorporated crossfades and reverses. I only had to re-create reframing.

I would think if it works for AE you should at least be able to get the raw cut into Premiere.

hope this helps.
Keith

K-Decisive - your comments and experience are not only very valuable to forum members but to the SCS Quality control programming engineers monitoring this thread as we speak>
Would you care to answer the following?

1) Were you the editor in all software manipulations and did not have to communicate your issues with someone else?

2) What do you mean by reframing in Resolve - you mean the aspect ratio of the video did not hold? >MOV containers or ?

3) After Effects version number that you used?