Participant

Answered

Encore error code 3 vas file

Forum|Forum|7 years ago
August 10, 2018
17 replies
24451 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.

Show previous replies

Jason Leaver

Known Participant

Ditto.

I have a project that gets updated every year. Each year, the client needs me to add one more video to their show reel. I created the 2018 video in PremPro, encoded as H264bluray with AME, import into Encore, build ISO - and when it gets to the very end - I get the same message. I removed the 2018 video from the project and presto, the ISO burns without a hitch.

I managed to re-encode the video using MPEG-2 bluray, and it worked fine. I guess you could say it's not a big compromise for me. No one is going to notice the difference. Still, I hope it gets resolved.

B

bend69307138

Participating Frequently

Hi,

This issue is a AME issue, not a Encore issue. As we all pay for AME, this issue has to be fixed.

Thank You.

BD

Stan Jones

Community Expert

I agree it should be fixed. In my tests, exports from PR and AME cause the issue, not just AME.

Contrary to my post 61 above, my test yesterday showed that Win7 compatibility was a workaround. More testing needed, but it makes me wonder if there is an interaction between version of Windows and the latest PR/AME?

Re: "device not ready", Code; "3" Note; "File can not open" I'm considering giving up on encore and life itself.

H

HeDrie

Known Participant

is the Issue fixed with new release today?!

Stan Jones

Community Expert

I do not see it on the list of bug fixes and the known issues has not been updated yet. I'm in the process of a reinstall, and loading PR CS6/Encore now. I'll test when I can.

JonesVid

Community Expert

So after reading your post and all the thread from 11th August I just wanted to post that last night I tried re-encoding using Mpeg2 Blu Ray and tweaking the bit rates.

Result - it worked. I Created an iso file and just then right clicked on it in Windows 10 and burned a disc.

Using Mpeg 2 was not such an issue on this occasion as I had plenty of room on the Blu Ray disc - but for projects where you are nearing your limit on capacity, then H264 is best as it is a more efficient compression codec of course.

Obviously if the client wants H264 blu ray format then are stuck for now until Adobe issue a fix.

So this should be classified as a 'work-around' for now I think and we still need the correct H264 Blu Ray fix from Media Encoder 2018 V2 !!!!!, now probably 2019 ?.

Picture quality from my test disc was very good as I was able to use max bit rates.

I will escalate this issue directly with Adobe as well.

Maybe this is of some help to others.....

Stan Jones

Community Expert

Yes, thanks for reporting.

T

tonyn26504140

Participant

Just ran into this problem. Created a BD image last Friday no problem. The next day, having upgraded PremPro and Media Encoder to the latest verions, I got the above error on a new BD project, so obviously the h.264 Blu-ray files from Media Encoder no longer work with dear old Encore.

But I got around the problem by importing non-standard h.264 files (non-standard for Blu-ray) into Encore and letting it transcode them itself. I imported one small 720p file and a large 4k (2160p) file.

I expected Encore to spit them out but it dutifully transcoded them both (took a couple of hours) and created an image file from which I successfully burnt a Blu-ray disk. And the quality was unexpectedly very good.

So it turns out that if you work in 4K and routinely export 4K files from your edit, then you can just throw them at Encore without having to bother with the h.264 Blu-ray export - bonus!

Stan Jones

Community Expert

Thanks for reporting. I think the problem most users have gotten with the h.264 files in PR 2018.1.2 is not being able to import. Yours imported, but then on build you get this error?

T

tonyn26504140

Participant

Correct. The files imported OK but the image build failed. I can build a new Blu-ray image using h.264 Blu-ray files generated before updating Media Encoder, but not after.

150kw

Community Expert

こんにちは、Gazman2013さん

日本語で失礼します。

もし、Windows 10 April 2018 Update（v1803）＋ Premiere Pro CC v12.1.2 をお使いの場合は、

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

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

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

jefjaeger

Participating Frequently

Ummmm...what?

8

8raptor8

Known Participant

He said to try Premiere CC2017

G

Gazman2013Author

Participant

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)-

neil wilkes

Legend

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

neil wilkesCorrect answer

Legend

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.

Stan Jones

Community Expert

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

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded