[Keith Picozzi]

Herb thanks for the reply, I did a bit of investigating…

The ones that had the issues were done when I added ‘Neat Video cleaner’ into the mix (it’s a plug-in that reduces ‘noise’ and clean-up the video)…

So Neat video running by itself and exporting no issues at all…

Neat video by itself exporting then later applying another effect and exporting no issues at all…

Neat video + any other effect running at the same time and exporting ‘MAY’ introduce a very small stutter\freeze at some point – did it to not every video but every 2 out of 3…

The videos all had the same frame-rate and resolution so perhaps it was the amount of ‘noise reduction\cleaning’ that was needed that made the error show-up?

At any rate I’ve done a few videos now with multiple effects without ‘Neat video’ plug-in and they all seem to be fine so it seems that was the common denominator.

[Keith Picozzi]

That’s good stuff! Thank you!

[Keith Picozzi]

In case anyone finds this in the future – Regarding MediaEncoder; installing Premiere Pro CC 2013 also installed the correct ME version so it is not a separate install for this version.

I was able to sign-in to my Adobe account but it took several tries and a PC restart for it to take effect for some reason. Premiere kept asking for a sign-in prompt so that took a while to get fixed. As of now this version (7.0) shows under the Cloud App and it’s working fine. Not sure why Adobe doesn’t keep these older versions on there for install, I assume it has to do something with the ‘Dolby’ export option they are no longer able to use?

[Keith Picozzi]

Thanks for the reply – Yes, that is the site I referred to but the CC 2013 Premiere links are dead now apparently. Luckily I was able to find a trial version I had on a backup of it so possibly I could install it and as long as Adobe lets me sign in using it I ‘think’? it should be ok?

I couldn’t find a backup of Media Encoder though, I know I had a separate CC version of ME – anyone know what version will work in conjunction with CC2013?

[Keith Picozzi]

Ok further update, I imported the VOB into Vegas and no issues what so ever.

I imported the seperate M2V & WAV file and this time Vegas shows the currect time on timeline for the WAV track but the M2V track is much shorter & it gives me an in-correct time of 1:07:55 (but the file is complete), so not sure why Premiere shows it as the right time and correct on timeline but it acts like this shorter time version of 1:07:55, I think something is wrong with it’s attributes\header(s).

[Keith Picozzi]

I tried MpegStreamclip a while ago and it couldn’t start, just to be sure I just tried again and upon running it I get a “mpeg streamclip could not initialize quicktime” error, I’m on a Windows 8.1 machine maybe it’s only for older operating systems? I have Quicktime installed (latest) and anything else that uses Quicktime works fine.

I don’t think it’s a demux issue anyway.

One of the first things I tried was importing just the VOB and I get the same result as importing the Mpeg.

But I have an update; I forgot I had Sony Vegas – I haven’t used it in years, the Mpeg that gives Premiere problems I imported into Vegas and it has no issues at all with the sync, so it’s specific to this video file and Premiere but not sure what it is? I can edit in Vegas but prefer Premiere that’s where all of my plugins are.