• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers

Encore error code 3 vas file

Community Beginner ,
Aug 10, 2018 Aug 10, 2018

Copy link to clipboard

Copied

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.

Views

15.8K

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Expert , Mar 13, 2019 Mar 13, 2019

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 t

...

Likes

Translate

Translate
Community Expert ,
Aug 10, 2018 Aug 10, 2018

Copy link to clipboard

Copied

What is the exact error message, including any "note" at the end.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Aug 10, 2018 Aug 10, 2018

Copy link to clipboard

Copied

Blu-ray Error: "device error", Code "3", Note: "File can not open. (A:\1unload

Files\Working media\Gillian & Mark\Project File\Post\Media Encoder\Bluray 1

\Mark & Gill\AuthorScriptHDMVSessions\Mark & Gill.m4v,_,ves)-

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 11, 2018 Aug 11, 2018

Copy link to clipboard

Copied

This error is not common.

Encore uses a lot of temporary space to create a Blu-ray, whether to burn or create an image.

Look at Encore preferences for the location of the cache files and check space on the drive for the Encore project location.

I do not see this as an error for filename, but Encore can have problems with filenames that include special characters (like the ampersand - &).

One user on Windows 10 reporting fixing this issue by running in windows 7 compatibilitay mode.

Always run Encore "as administrator."

Let us know how it goes.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 11, 2019 Mar 11, 2019

Copy link to clipboard

Copied

Gazman2013  wrote

Blu-ray Error: "device error", Code "3", Note: "File can not open. (A:\1unload

Files\Working media\Gillian & Mark\Project File\Post\Media Encoder\Bluray 1

\Mark & Gill\AuthorScriptHDMVSessions\Mark & Gill.m4v,_,ves)-

Do you still have this problem?

If so then I know what the solution is here - it's laughably simple really once you know.

The VES files are the actual assets used by the authorcore for Blu-ray (ScenaristBD also uses VES files as the asset, because the way it works is the authoring tool never actually touches your real asset until it gets multiplexed - it simply uses the VES reference to it) so if it cannot read this then there is usually a problem with the naming, and sure enough you have not only got spaces in your file name (generally a bad idea) but you have used a & which is a total no-no.

For all assets, it is absolutely far far better to only ever use Alphanumeric characters and underscores instead of spaces - if you do not then sooner or later it will bite you in the rear - hard.

Instead of the name being

Mark & Gill.m4v

you should rename it as Mark_and_Gill.M4V and re-import it.

Then replace the badly named footage with this one - do NOT try to simply point Encore at a different file as you will also have, hidden away, not only the M4V original but the VES, a MUI and an XUI file from the same name.

Hope this helps

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Mar 11, 2019 Mar 11, 2019

Copy link to clipboard

Copied

Thanks for this. A good reminder for following correct practice when naming files. However, I still dont get how a file following the correct naming convention works in the older Premiere Pro 2017 version but not in later versions - as reported by many people.

Anyway, I think having now understood how Encore uses the VES file, it suggests the whole issue is simple to fix.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 11, 2019 Mar 11, 2019

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Mar 11, 2019 Mar 11, 2019

Copy link to clipboard

Copied

Thankyou Neil, and to everyone for your help, I found yes it was exactly that, the naming and use of non Alphnumeric letters in the title.

As you said Neil and mentioned in Audrey's post and one or two others far earlier, such a simple and silly error caused so much headache. Lesson well and truly learned.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Mar 11, 2019 Mar 11, 2019

Copy link to clipboard

Copied

Agree that even correct simple names still have an issue under Windows 10 / in the later Adobe Premiere releases.

Not knowing how the code is structured at all, one can only assume there is some simple process within the later code that still works under Windows 7 environment and not in a Windows 10 environment.

I think still this (niggly) issue needs investigating/ clarifying and if necessary applying a simple fix as required.

8Raptor8 said Adobe support acknowedged it was a known problem in the post of 6th March ?.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Mar 13, 2019 Mar 13, 2019

Copy link to clipboard

Copied

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.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Mar 13, 2019 Mar 13, 2019

Copy link to clipboard

Copied

Very interesting info Neil. I remember playing with TMPG Eng encoder a number of years back but a quick look on the web now looks like it is worth trying out - with the 14 day free trial - then purchase if results are better.

I've always wondered how some of the very good quality H264 material I have seen on the web can have small files sizes versus getting a similar quality in AME with much larger file size?.

It would be a worthwhile exercise to try out the TMPG Eng encoder to compare quality and file sizes v AME.

You make some valid points about streaming,  and good quality 4K requires a very good Internet connection - and this is not always available to some people.

Some friends of mine in the UK are lucky if they get 2Mbs download - yes, they live in the countryside and rely on long old telephony cables back to the nearest distribution hub. Here you are stuffed without physical media.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
May 11, 2019 May 11, 2019

Copy link to clipboard

Copied

Take a look at my latest comment on this AME bug - in Adobe User - Feedback/Suggestions forum

https://adobe-video.uservoice.com/forums/media-encoder

The situation appears more involved with the recent Mail received from Adobe Support about Third Party Code infringement to carry on using AME 2017 (Version 11.1)

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 11, 2019 May 11, 2019

Copy link to clipboard

Copied

I don't see your comment in that uservoice item.

Yes, this will make it "unauthorized" to use that workaround.

I don't recall and did not look earlier in this thread: did you try the Win7 compatibility that works for some?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
May 12, 2019 May 12, 2019

Copy link to clipboard

Copied

Apologies - should be this page : https://adobe-video.uservoice.com/forums/911308-media-encoder/suggestions/35569942-fix-errors-in-h26...

Posted comment 11th May

Running Encore 6 in Windows 7 compatibility mode worked on a test file - but failed when I was building a project recently with Blu Ray H264 export

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Jun 02, 2019 Jun 02, 2019

Copy link to clipboard

Copied

No, this is not a solution. My filename is "Pearson_Meza Wedding_BluRay.m4v" and the H.264 uesage in Encore still fails with the error reported in this forum.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Jun 02, 2019 Jun 02, 2019

Copy link to clipboard

Copied

Did you try the Win7 compatibility that works for some?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 03, 2019 Jun 03, 2019

Copy link to clipboard

Copied

Apologies for this long post :

After 9 months of banging my head against a wall - I am giving up on this thread - however, there may be light at the end of the tunnel.

My conclusion after all this to and fro-ing with Adobe support is that (to quote Neil Wilkes ... "Adobe seem to regard physical media - and the people who work in the field - as an embarrassing anachronism in a streaming age...."

I have spent a great deal of time on this looking at differences between 2017 H264 Blu Ray Premiere exported files and 2019 exported files.

As per Adobe request last week I did two complete short test H264 Blu Ray projects and uploaded these to look at .... so far so good.

I also repeatedly (I mean repeatedly) told them I fully understood Encore was now out of support.

+++++++++++++++++++++++++++++++++++++++++++++++

This was Adobe Support response (after 9 months don't forget) >

This email is in reference to the open case regarding Script error on Encore when importing the file exported from Premiere Pro or Media Encoder latest version.

We have discussed this with our team wherein Premiere Pro and Media Encoder latest version are Exporting the project without any error.

The issue persists when importing the exporting file on Encore.

As the Encore is out support, we can not fix the errors on that Application and it is not compatible to recognize the Exported the file from the latest version of Premiere Pro and Media Encoder.

We request you to please click the below link and download the authorized DVD burning software.

You can refer to this list: https://www.toptenreviews.com/software/multimedia/best-dvd-authoring-software

+++++++++++++++++++++++++++++++++++++++++++++++

Very helpful - they point me at 10 other packages I can purchase .....on top of my Creative Cloud monthly fee, and use Encore yet again as an excuse. Zero help guys.

Self Help

No, I have not yet give up totally -but tried a few things

I looked back at old threads and found the AuthorScriptSessions error had been common back in 2010/2012.

I looked at the xmp text scripts with the 2017 and 2019 files and compared them. Only difference I could see was reference to version of Encoding engine. I also noticed 2019 produced an additional xmp file.

Test I ran - Encore Run as Administrator Only - not Win 7 compatibility

For 2019 test - ensures only .m4v and .wav file were in folder to import as timeline

Cleared Media Cache (Edit/Prefs/Media). Unticked Write XMP ids (but no idea if this made a difference)

Built file - but failed with same error. Ok'd it,  but then built again and it produced the ISO file no errors.

Conclusion - why 2017 files work first time is still a mystery, but I produced an iSO file 4 times with above method on 2019 files by OKing the error and rebuilding with out coming out of Encore.

Last question to the Forum - has anyone successfully used the 2019 exported Premiere H264 Blu Ray Files on other BluRay Disc Authoring Packages?. Not seen evidence of that anywhere yet.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 30, 2022 Apr 30, 2022

Copy link to clipboard

Copied

LATEST

Hello, not sure if there will be any response here as this is from 2019 but only today I have the same error. Mine is "File can not open.(E:\60th-birthday\disco1\AuthorScriptHDMVSessions\Bd-buffet-disco-p1.m4v.__.ves)-

Mind you the folder does not even exsist. I have compared this with other BluRay-folders I recently done without any troubles but that did not contain any of this either. So I really wonder, what this is. The File is done in the latest Adobe Premiere but Adobe Encore is of course still the same. Never ever had any problems.

The trouble trouble actually started when I wanted to do a double layer DL BluRay image. It did import the 35 GB file but when it was meant to write it it would say disc full. But this can not be as there is 807 GB left ....

But I have created a DVD image for now without any issues. But of course I would like to have HD quality as its going to be projected on a large wall. And the show is today in 14 days .... I wonder if I will have the same issue with part 2 ...But then why all of a sudden. And what does this .ves-file actually contain? I mean, it apparently is automatically generated by Encore ...

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Aug 27, 2018 Aug 27, 2018

Copy link to clipboard

Copied

こんにちは、Gazman2013さん

日本語で失礼します。

もし、Windows 10 April 2018 Update(v1803)+ Premiere Pro CC v12.1.2 をお使いの場合は、

Premiere Pro CC v12.1.1 にバージョンダウンしてみてください。

日本語コミュニティフォーラムで同投稿があります。

ブルーレイビルドでエラー3が出る

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Aug 29, 2018 Aug 29, 2018

Copy link to clipboard

Copied

Ummmm...what?

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 11, 2018 Sep 11, 2018

Copy link to clipboard

Copied

He said to try Premiere CC2017

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Sep 11, 2018 Sep 11, 2018

Copy link to clipboard

Copied

I have gone another route.  I want to be done with stupid Encore.  I still have to use it for now to put together a disc image/ISO file, but I am burning the disc image with another software.  There are a number of them out there, and I went with Ashampoo Burning Studio 19.  Very simple, intuitive, and effective.  I don't understand how Adobe makes professional software, but walks away from Encore with no replacement offered.  Ridiculous.  I would also like to find a good software to author discs from after the Adobe Media Encoder is finished rendering.  I wish I never had to deal with Encore again, and I will eventually get there.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 11, 2018 Sep 11, 2018

Copy link to clipboard

Copied

I'm on my phone and can't send you the link. Do a search in the encore forum for "alternatives."

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Sep 26, 2018 Sep 26, 2018

Copy link to clipboard

Copied

Just seen this thread about Encore 6. I have the exact same problem as Gazman2013 who posted the original issue.

Same file type fails on build .

I tried building a disc image but that failed too ! - so question is ....did you have to do this with older H264 media encoder files ?.

Quite frankly, now subscribed to Creative Suite and I too find it totally unacceptable that the production of BluRay discs is now forgotten by Adobe.

Yes - we would all like to give friends a Straeming Server address but we don't al have fact video streaming server pockets - so a BluRay disc for friends is still convenient.

Please Adobe - get this Encore problem  sorted out on Windows 10 - mmmhhh I bet that fell on deaf ears

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 26, 2018 Sep 26, 2018

Copy link to clipboard

Copied

The problem is not with Encore, but PR. So we're hoping for a fix.

Likes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines