Skip to main content
New Participant
August 10, 2018
Answered

Encore error code 3 vas file

  • August 10, 2018
  • 17 replies
  • 24380 views

I have tried consistently importing and re-importing, changing file names, moving where files are located, or destined, I have re-encoded the film twice today and still getting the same error code, it would seem adobe no longer support this software fully, how do I go forward here? I have a client waiting on a Blu-ray disc of their wedding.

This topic has been closed for replies.
Correct answer neil wilkes

A great point Neil. I pointed out the ampersand in post 3, and I don't think we ever heard how that poster fared.

But in the many tests that followed, simple, legal filenames have a problem. I can find no difference (e.g. MediaInfo) between a 2017 file that works, and a 2018/19 file that does not.

And fascinating that Win 7 compatibility works.


https://forums.adobe.com/people/Stan+Jones  wrote

A great point Neil. I pointed out the ampersand in post 3, and I don't think we ever heard how that poster fared.

But in the many tests that followed, simple, legal filenames have a problem. I can find no difference (e.g. MediaInfo) between a 2017 file that works, and a 2018/19 file that does not.

And fascinating that Win 7 compatibility works.

Fascinating - and I suspect bloody infuriating for those affected.

There are 2 other solutions I can give though, both of which involve spending money unfortunately.

1 - x264 Pro plugin.

2 - TMPGEnc 264 encoder plugin

Whilst spending money to work round a bug in the AME is not ideal, it does have the serious advantages of

A - working, and

B - producing a far superior output compared to the AME Stock codec.

Both these plugins are built around the same encoder, and for the computer literate amongst us you can always try writing your own from the source files at the linked location.

I use both of the encoders above for all projects we do. Sometimes it is the x264 Pro that gives the superior result, sometimes it is the TMPGEnc version - strange huh? It just goes to show that encoding is a skill and an art all of it's own & in the heyday of DVD large authoring houses used to employ specialist encodists - that was all they did, all day long. Encode the final assets. Why? simply put because there is far more to getting the best looking final assets than simply clicking through presets - you really do need to understand how they work and more importantly how to tune the results and it takes time.

We seem to live in an age where everyone is always in such a hurry all the time, but some things cannot & should not be rushed and authoring is one of them.

Adobe really do need to fix their bugs, although sadly this no longer seems to be a priority for them as they seem to regard physical media - and the people who work in the field - as an embarrassing anachronism in a streaming age. Future generations will call this worse than short-sighted once the streamers hold the strings, content gets sanitized and anything that offends the progressive liberal ideals is immediately banned & removed from the platform. Physical media is important and Adobe should keep sight of this. It is all about the freedom to watch what I want, when I want to do it and not to be restricted to the stuff Netflix & Amazon think I should be allowed to see - and believe me that is where all this will end up.

17 replies

kobypics
New Participant
June 28, 2019

Finally I found the way to burn a blu-ray.

Right click on m4v file and choose Transcode settings.
Change H264 to MPEG-2.

Then right click again on m4v file and click Transcode Now.
Wait until the transcode is done.

I usually choose Build Image instead of Disc. (I couldn't make image file with H264.)
Then I build a Blu-Ray disc from iso data.

I hope this will help somebody's procedure.

JonesVid
Brainiac
June 30, 2019

You are correct that Mpeg2 will infact allow you to produce a disk. You can infact encode into BluRay Mpeg2  direct from the Premiere Pro timeline.

The downside is if you have a large set of video files H264 is much more efficient to help squeeze more on a disca dn maintain decent quality.

I have re-escalated this BluRay H264 build  issue again into Senior Adobe support and I really hope that we see a fix sometime.

Any fix has to be to address the issue with the latest H264 Blu Ray files - not in Encore as we know that is out of support.

Participating Frequently
June 3, 2019

I'm having the same problem with the latest Version 13.1.2 (Build 9). Adobe doesn't have a clue how angry their users are about their buggy software.

Jason Leaver
Known Participant
May 21, 2019

I've found success!

I'm running Encore as Administrator and with Windows 7 compatibility enabled. The very same files that presented the error built fine!

For future use, I've adjusted the properties of the Encore shortcut in my start menu. On the 'Compatibility' tab, I enabled "Run this program in compatibility mode for Windows 7", and turned on "Run this program as an administrator".

I hope this solution is successful for other users too.

Known Participant
March 10, 2019

I reported to the link at any rate because this is definitely a bug w\work around.

Just to be sure I did a fresh encode of a H264 file with some different parameters from prior files and 1 hour in length from CC 19' made a basic BR layout in Encore and it again had no issue in Encore building the final image.

So this appears to work at this time to some degree, I'm not sure if it will work for everyone or for every file I encounter though.

JonesVid
Brainiac
March 10, 2019

Thx for doing these tests. I’ll also be doing some tests as I am still running a 1703 version of Windows 10 and have quite a large H264 based blu ray project coming up soon.

I think right clicking on the Encore.exe file properties box allows you to permanently assign this to be launched in Windows 7 mode run as administrator, assuming you are the system owner/ manager.

Known Participant
March 10, 2019

Thank you!  I learned something today!

Known Participant
March 9, 2019

Just as a reply to this issue on my Windows 10 PC

I also encountered this error - I normally use CC 17' for importing\building in Encore but one of my filters seems to be faster on CC 19' (the very latest update) so I encoded 5 approx. 30 minute files using CC 19' and upon building in Encore I got the same error.

I noted the file it got the error on (1 of the 5) and transcoded in Encore, upon the next build it passed by that transcoded file fine but got the error on the next in line file (2 of 5). So instead of transcoding that one I re-started Encore in "Windows 7" compatibility and using Administer Rights (it was already set previously) I was bale to build the image no issue within Encore using those same files.

So I'm not sure if it will work again the next time for me on a different file or if it works for you, but in a pinch it may be able to be something to at least try first.

Stan Jones
Brainiac
March 9, 2019

Thanks for reporting.

Known Participant
March 6, 2019

I just got off tech support and they said it is a known issue and they are working on it and a future update will address it.   sigh... it's only been nearly two years now...

JonesVid
Brainiac
March 7, 2019

Thanks for the update and checking the latest updates.

Seems we could wait a long long time for this to be fixed......

Its very clear Adobe are more focused on developing new features that look good on the marketing brochure rather than fix problems that customers are using and paying for.

If anyone else has an update on this problem on H264 Blu Ray encoding failing on latest Premiere Pro releases then please update us

Thanks

Known Participant
March 6, 2019

Today's latest update does not fix the issue.

Participating Frequently
November 24, 2018

I'm seeing the same problem (on Mac). It appears to be caused when Encore decides that it must transcode the file.

I exported from Premiere using H.264 BluRay HD 29.97FPS Interlaced and told Encore not to transcode, but it did anyway and then barfed with the error. I'm currently re-exporting the asset at 23.97 Progressive (which will take another 6 hours); I already tried that with a shorter clip and it seemed to work.

JonesVid
Brainiac
November 25, 2018

Thanks for your observations

Can you go to this link below and vote for this bug to have higher priority

Just click on the 'vote button' and add a comment if you would like to

Link :

Fix errors in H264 Blu Ray encoded files - AME 2018 – Adobe video & audio apps

I added this item to this Forum which reports Bugs to Adobe and New requested features

The _ves bug  is a pain for all of us who create Blu Ray discs with H264 export - and wasting our time !

......  Maybe we can send a collective invoice (for all our wasted time) direct to Adobe Accounts

Thanks

New Participant
November 2, 2018

I was having the same issue recently. What I simply did "by accident" was not rename the image file. I just left it as "Untitled Project" and surprisingly it processed with no issues. Then after finishing processing I renamed my image file .

Stan Jones
Brainiac
November 2, 2018

I don't see how that could matter, but Audrey things have happened before! I'll test this later today.

Known Participant
November 4, 2018

Did you ever get Audrey's idea to work for you?

Known Participant
October 15, 2018

How do you Upvote the bug report in JonesVid post # 35?  I've never done that and searched and couldn't find.  Thanks

Stan Jones
Brainiac
October 15, 2018

The link takes me directly to that item and the vote button is on the page.

Known Participant
October 15, 2018

I am sorry, but what link?  (Clearly I'm new to this forum haha)