I've been working on Lightroom all morning renaming files. Suddenly I don't have the option to enter the "start number".
I relaunched Lightroom with another catalogue but had the same problem.
Then I uninstalled and reinstalled Lightroom.
Still no joy.
Can anyone help me?
Bridget
This is the Encore (DVD authoring) forum.
I think you want this forum:
Uploaded the .iso to the same folder on dropbox.
Burn to disk and see if that also has the jumps. If so, test your disk on a different player/tv.
I've got some killer stuff in the works, thanks to your help. I am combining the techniques from the test file you sent me along with the one from the YouTube video above, and it's coming along almost perfectly and exactly as I had desired. I'm very excited to see this one through!
The one last little piece (at this moment, I guess you could say) is I'm trying to add a sound for when one scrolls through the menu options, and then a different sound for when one selects that option. Right now, I can't get any sounds for either of those activities. This would really seal the deal.
After dealing with a few other issues, I finally have a working version of my project that I was able to successfully output into a Blu-ray folder structure, however, when I playback the exported version, any menu items that are not buttons or background disappear from the menu.
Here is how my menu looks in the preview window in Encore…
Versus how it looks when I open the BDMV folder in VLC:
This is just an example of one submenu (I'm using a multi-page menu structure), but it's the same for every page of the menu. All of the buttons and highlight layers for buttons show up, but all of my menu titles vanish. I also burned a disk before I noticed the problem and can confirm that this issue is replicated on the disk in an actual Blu-ray player.
Here's how the layers for particular menu page looks in Photoshop if that'll help diagnose the problem.
Any suggestions would be greatly appreciated. I looked around and can't seem to find anyone else with similar problems.
Encore does not preview multipage menus, so it is hard to tell what you have.
I have not found VLC to handle menus very well at all. In fact, the only one currently that works for me is PowerDVD.
"Audio Options" is a text layer in the Audio 2 page, so it will only show up there.
The format in Encore user guide (links on line are messed up) is:
Page 0 is everything below any other multipages (so Bonus Features down in this image). There is only one Background for a multipage menu, that applies to all pages.
I suppose you could have your "(#) Audio Menu 1" instead of "(#) Page 1," but you need the "(#)" to be "(#1)" Audio Menu 1" (If it is page 1). Otherwise, Encore has no way of knowing what page number it applies to. I have never tested without the page #. It is possible Encore has sorted it, but I would not chance it.
"(#) Scenes 17" and so on are each a page?
How did you create the pages? Editing in photoshop? or in Encore?
I created the pages in Photoshop as a single Photoshop document and imported them into Encore. I didn't realize you're supposed to number the pages, but navigating them works just fine the way I have them set up. The only issue I'm having is that the on-screen name for each menu page – which is just a text layer rather than a button – disappears once I build the project. This proves true in both VLC and after it is burned to a disc playing in a Blu-ray player (Xbox One, in this case). I have a total of 21 pages: Main menu (page zero), bonus features, 17 pages of scene selection, and two audio options pages, and for each page I want to have a separate title that's not tied to the primary background.
I found a workaround that works… sort of. If I just dump the text layer into one of the other buttons, it does become visible, but that's created some odd problems of its own where suddenly the white text on some of the pages is inexplicably grey (again, only after it's rendered out a Blu-ray folder structure; it appears correct in both Photoshop and Encore before exporting).
In theory, non button objects should still be visible on menu pages, but for some reason that's not proving true for me in practice.
Yes, odd. I'll take a look in the morning.
I think I'm forgetting something, but I can't remember whatever it is! So, with that said....
No, it does not appear that a text layer on anything other than Page 0 is visible in the final - unless it is in a button group.
The problem with that is that the extra text adds to that button's total size - and some test placements would overlap with another button's area. This will throw an error if you use the "check project" in the build tab.
If you place the name inside the first button next to it (English), it won't overlap the others, but clicking on the Audio Options text will pick English.
An alternative that works is to add an additional button group, place the text in there, and in Encore link the button to itself. It will show as a button if entered (but you can avoid that using button routing) or if hovered over on a computer, will have no highlight, and will do nothing when clicked. But the text will show.
I did not test not numbering the pages, but yours appears to be working.
I guess that’s as good a workaround as any. Frustrating that there isn’t a way to make it work the way it’s supposed to, but I’m coming to find that’s a common theme with Encore.
I can understand the frustration here - getting supplied files to the correct specs can be an unbelievably frustrating experience.
It should be perfectly permissible to use both HD & SD on one disc in Blu-ray. The difficulty, as you have discovered - is always the file type needs to be correct. The best place to begin is to know what your spec legal options are (so we can discover if the issue is in Encore (in which case we need to find an alternate solution) or in what you are trying to attempt. If you are going to be doing a lot of this, I can warn you in advance you will end up collecting some very eclectic software along the way as utilities seem to help no end. You have an issue right there though, as Mac are just not Blu friendly. Worry about this later and I only mention it as you earlier dismissed the TMPG tool as a suggested workaround for being too expensive which at $100 is - for what it is capable of - incredibly cheap.
I know I bought it just to attempt one file format conversion, which it did a pretty good job of that time although did let me down on a completely different project but I ramble on and digress, as I am prone to doing. Sorry.
So - back to the specs. Blu-ray has several legal frame rates & sizes 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
Better still, you also have 3 different codecs available to you
1 - H264/AVC as .264, .avc & .bsf (the latter may not be in Encore)
2 - VC-1 (as .wmv - this is the old Windows Media Video 9 type)
3 - MPEG-2 - not (and this is important) configured for DVD though and available as .m2v, .mp2s & .mpg.
The first thing to take note of I think is that the SD resolution needs to be interlaced - you cannot use 23.976 or 24p, and you most definitely cannot use 25p or 29.97p - everything in SD must be interlaced so all footage in SD NTSC must therefore be at 29.97, ideally upper field first but if source was all BFF then it is vitally important to not change this without checking the results on an old style glass monitor, as LCD panels will not reveal interlacing artefacts and if you get those in the final encode it will ruin your day.
I am banging on about this at length because unless I am reading you incorrectly, in post 7 above you detail a file that is still giving issues, and it is an NTSC SD piece at 23.976 progressive scan - this is just not Blu-ray legal.
The best rule of thumb is to think of it this way -
A - Progressive Scan is always 23.976/24fps.
B - Anything in old style PAL or NTSC resolutions will be interlaced.
Yes, there is an exception but it is so rarely seen it can by & large get ignored.
Your biggest problem is the wide array of source file resolutions - it looks like some were MPEG-1 or half size MPEG-2 (there were some odd things done in early days of DVD) and the easiest way out is to plan the assets out in advance - it seems to me a certain amount of re-encoding may well be necessary but this will depend on your original source. Are you still having trouble? I ask as I am late to this party
NB - I do find it very strange that Stan was able to import MPEG-2 DVD encoded files for use in a BD project with no issues for re-transcoding (first reply above). I would take a wager that it would get re-transcoded during disc build, or may even trigger a fail although I could be wrong.
Neil, thanks for jumping in. Very useful info.
SD on BD is an interesting issue. I interpreted some comments in old posts as saying this worked, but in each one I found, it was not clear whether the expert was confirming what I am now saying (that an MPEG2-DVD transcode is "BD legal"). Except for this one from Jon Geddes: "...Encore and the BD spec allows for standard dvd formatted mpeg2 files to be authored onto a Blu-ray disc without any transcoding."
Re: How do you place 10 hours on a BD with Encore?
I went back to the test files I used, and can confirm that MPEG2-DVD format exports from PR a) import to EN as "do not transcode" for both DVD and BD and b) once built (to m2ts streams - using a folder output for convenience) show the same characteristics as the m2v files (bitrate, interlacing, etc).
But there are differences in the 2 formats that carry across to the m2ts. The MPEG2-DVD is GOP M3/N15 and interlaced bottom field first, while the MPEG2 Blu-ray is GOP M3/N12 and interlaced top field first. The source file was a classic Sony camera SD DV clip. I see that, for no good reason, I used MPEG2-DVD VBR max 7; MPEG2 Blu-ray CBR 10.
I did burn this to disk, and it plays back on a BD player to HD TV with no apparent difference between the 2 types.
For me, running Windows 10 (Feature update to Windows 10, version 1803), I got the cursed "error Code 3" even when building an ISO image (I have not used Encore to burn the BLURAY disc in a long time -- Windows 10 does that natively). I spent some hours yesterday trying to resolve it. Eventually I tried running Encore in "Windows 7 Compatibility mode". That resolved the issue.
It seems something has changed in Adobe Media Encoder. I'd not tried to used Encore in months. Yesterday I tried it. I use Windows 10 (Feature update to Windows 10, version 1803). It did not fail on the import step, however I did get "error code 3" when trying to build the ISO image; this was resolved by running Encore in Windows 7 compatibility mode.
Some users have reported success running in compatibility mode for windows 7. And at least one reported that this worked and then stopped working. In any event, I did not test that option.
New reports of success today (in old threads), so I gave it a try. I am running Win 10 Pro 1803 17134.472. I first opened Encore as usual, and ran a new test project using H.264 Blu-ray format export (from 2019.0.1 - the problem exists from at least 2018.1.2 through current, 2019.0.2). I built to a BD image (.iso). Project fails with the Code 3, ves error.
I then selected the "Adobe Encore.exe" file, and in properties/compatibility set it to run for all users in compatibility mode and as administrator. The same project was successful. The .iso plays successfully.
So I would add this as a workaround.
Thanks for posting this! This is an old thread regarding a different Code 3 error. See the note I added here:
Thanks for posting this! See the note I added here:
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
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
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?
