Forum Replies Created

Page 2 of 4
  • Erik Davis

    January 9, 2018 at 3:13 am in reply to: Vegas pro vs Adobe Premiere

    My experience is that the uplifted 708 captions are gobbleygook in Vegas. If you look at them in a third party app you will see that the 708 captions are garbled garbage. If the uplift worked I really wouldn’t be complaining.

  • Erik Davis

    January 8, 2018 at 4:21 pm in reply to: Vegas pro vs Adobe Premiere

    John,

    What a good and patient reply. I agree with everything you said except one little difference between PPro and Vegas. Ends up being a fairly big difference for me.

    In PPro you can add 708 or 608 captions. In Vegas you can add only 608.

    All of my broadcast spot deliveries must have 708 captions so I have to send everything through PPro after outputting from Vegas.

    Erik

  • Erik Davis

    January 8, 2018 at 6:44 am in reply to: Kicking the tires of Resolve

    Cool. Thanks again. Will do.

  • Erik Davis

    January 8, 2018 at 6:09 am in reply to: Kicking the tires of Resolve

    Marc thanks for the helpful reply and shot of hope that this might work. I will test.

    In the manual on page 579, where it discusses automatically conforming “missing” clips, it doesn’t explicitly reference importing clips with a different extension as being recognized. Right?

    Erik

  • Erik Davis

    January 8, 2018 at 5:53 am in reply to: Kicking the tires of Resolve

    Thank you Tero, but that’s kind of my point. I don’t see anyway in the manual to replace existing proxy files with the source original files with the exact same names but different extensions.

    Erik

  • Erik Davis

    March 27, 2017 at 2:53 pm in reply to: Sony Vegas Project File Not Working

    Can you copy only the veg file to another computer with Vegas and open it? If you can get it to open on another computer you can export the edl and then reimport the edl into a new veg on your main computer.

    Erik

  • In the end, the only workable solution was to export an edl and then import it again into Vegas Pro 13. This worked pretty well as it relinked all my media. It did not bring in any of the keyframing or fx options. A pain that this info isn’t included in the edl but better than starting over for sure.

    Unfortunately, I don’t know what the problem was though!

    Thanks to everyone for the input!

    Erik

  • Paul you are on the job! Thanks.

    Your idea about emailing a veg got me thinking, Why not just try and open the veg on another computer. I did that and everything worked as expected! It couldn’t find the media, etc. But it opened just fine. So the question now is what to do?

    Not clear, but if I set all FX to bypass and save the veg will that eliminate possible fx problems?

    Should I export an EDL or such and then try to build again?

    Just try to resave it under a different name and try to open again on the offending computer?

    Will let you know how it goes.
    Erik

  • Also, to your question of have I replaced any drives recently. I would say within the last year I have replaced my main media drive. I did this to get a larger drive going from 1TB to 2TB. I copied all the data over and didn’t have any hiccups.

    Erik

  • OK, try re-scanning your VST Folders.

    ****ACTUALLY I DON’T HAVE A CLUE HOW TO DO THIS.

    Have you tried to bring in ONE of those stubborn Veggies as a NESTED Veg? – I’m not holding out any hope here.

    *****YES I HAVE AND VEGAS WILL CRASH WITHIN SECONDS OF MERELY TRYING TO BRING IT IN TO VEGAS. IT DOESN’T EVER BEGIN TO LOAD REALLY.

    Can you see/remember any of the “missing” Media? Have you replaced any Drives recently?

    *****YES I CAN SEE ALL OF THE MEDIA BUT KEEP IN MIND WHEN I TRY TO OPEN THE PROBLEM VEG FILES, I DON’T MAKE IT TO THE MISSING MEDIA DIALOGUE BOX. I CRASH BEFORE I GET TO THAT.

    THANKS, I’M NOT YELLING WITH ALL CAPS, JUST TRYING TO MAKE IT EASIER TO SEE MY RESPONSE.

Page 2 of 4

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy