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

For me the Windows 7 Compability Mode fixed the problem as well. Thank you guys

thanks for taking the time to reply Neil.

Sadly I do only use alphanumeric titles and I use 1920 25p (although its exported as 25i through the bluray preset) so I don't think either of those were causing the issue.

Since switching to TMPGEnc Plugin I have been pretty successful other than a recent hiccup which sorted itself with a few restarts (this always scares the hell out of me..)

davidpayne1981  wrote So, where do I start. The error I get in all instances (Unless I import an mpeg instead of h264 bluray file, in which case I get a different error about the video properties not being the same as the timeline) is this: Blu-ray Error; "device not ready", Code; "3" "File can not open. and then the file path and it points to \AuthorScriptHDMVSessions\Filename.m4v.21_35_15 etc etc (more numbers) UTC+01_00DST.ves)- I have spent no less than 12 hours trying to solve this today. It started occuring since upgrading premiere CC to the latest version (12.2). I had various issues with this before I'd even noticed the encore issue so I rolled it back to 12.1. Now the files from my h,264 bluray preset (5.1 sound using surcode, level 4.1, 21mbps bitrate, 1080p25) throw up this error. I have tried: - restarting -reinstalling encore - exporting new files with varying different paramaters changed. For example I exported a small section of a timeline in my normal preset and it errored. I changed to level 4.1 to 4.0 and exported it. it worked! I then exported all of the files required for my bluray in that same style level 4.0 set, however it still errored. All i can get to work is to export a stereo mp4 file but I'd like it in 5.1 In fact, I've forgotten everything I've tried so i can't be of much help but if you can think of it, chances are I've tried it. I'm now installing Encore CS6 (I was on CS5) to see if that works. If it does, great, but there is SOMETHING in the premiere 12.2 update that causes encore HELL. Do not update if you use Encore cs5.

I have a few thoughts here, given I also work in 5.1 all the time and create a heck of a lot of Blu-ray titles (although not with Encore, for reasons that will become apparent).

It seems there are a couple of different issues at play here and it could well be that the AME is at the root of all these issues, but I can offer some general advice that may help. Please bear in mind that successful authoring - be it for DVD or Blu-ray - is mainly dependent on correct asset creation & importation - and using Encore solely as an assembly tool, and never, ever trying to edit anything from within it. It does not like it, and it will get resentful.

That all said & done, let's go through some of your issues.

1 - Error code 3 "file can not open".

Things to consider:

A - naming protocols. I cannot stress the importance of this enough, as it really does matter. You should not use anything except alphanumeric characters, with no spaces at all - use underscores instead.

This also applies to you project folder structure on your local system - Blu-ray is supposed to be UDF compliant yet a lot of abstraction layers seem to ignore this. The general rule of thumb is to use naming such as

mainfilm_finalmaster_10_04_2019 and not something like Main Film, Final Master, 10th April

B - Only ever use Blu-ray compliant files - 1080p @ 25fps is not Blu-ray legal and at the very best Encore will attempt to transcode this and may well fail depending on your naming protocols. The allowed video resolutions & frame rates are as follows:

i/. 1920x1080 (aka"Full HD") allowing frame rates of 29.97i, 25i, 24p and 23.976p

ii/. 1440x1080 allowing frame rates of 29.97i, 25i, 24p and 23.96p

iii/. 1280x720 allowing frame rates of 59.94p, 50p, 24p and 23.976p

iv/. 720x576 allowing a frame rate of 25i

v/. 720x480 allowing a frame rate of 29.97i

As you will see, 25fps Progressive Scan simply is not allowed in the specifications, and even if you were able to import the file created this is no guarantee that it will work, or even be found on reload. Admittedly this is stupid, especially as 25fps PS is part of the SMPTE HD specs, but there you go. It is what it is.

Surround.

Encore does not handle surround very well at all and the whole implementation feels like it has been tacked on as an afterthought to me. You are pretty much stuck with AC3 or DTS Core AUdio as even though it is supposed to support DTS-HD Master Audio it is at best in passthrough mode only & I suspect it only recognizes the hidden core audio stream. It should support LPCM surround as this is a mandatory audio type in Blu-ray but for some reason Adobe chose not to bother. Personally I would recommend creating surround streams as elementary streams outside of anything made by Adobe. Use a DAW - this is why they exist.

sorry to come back to this but i dont know where to post.

TMPGEnc export for bluray discs has, after months of working perfectly, totally screwed up today and is now (despite showing a green tick in adobe media encoder) not exporting the full timeline, but instead  only a second or two of it.

I cant even work out how to open the TMPGEnc settings to see whether its deactivated itself or something like that.

Can anyone advise or help?

also, whilst I'm here, is it normal that I have to click "renew licence" almost weekly on the TMPGENC screen when starting up premiere?

I also want to report success. After a few hours lost I ended up on that thread. Thanks to all users for sharing this. Windows 7 compatibility and run as admin has unlocked the problem.

THANK YOU all lovely people for raising this issue, and to the Google search engine for indexing this page!  I've been wrestling with this problem and have stumbled across a solution in this thread that SEEMS to be working (I'm not counting my chickens... it's still writing the disk image now!).  It would give me this error once it'd 'imported' the H.264 Bluray file I exported from Premiere, but doing Stan's solution of "Run in compatibility mode" and setting it to Windows 7, and running as Admin, and it is now actually writing the disk image.

does anyone know if the october 25th update has fixed this?

has anyone tried to import an m4v created using the h264-bluray preset back into premiere cc 2018? I have tried using the one I created in cc2018 and cc2017 and both of them crash premiere.

Is this just my system?

There is a problem for some users with h.264 exports from PR 12.1.2. You can install PR 2017 and export from there. Try that first.