I never did get 3.0.5, although I "have" a copy of it I was given.......but let's not go into that here.
Oh, ok. The thought was if you had it or could stand it up for testing purposes it could be extremely instructive - are the problems with the "Chrome like" behavior I see with menus at track points due to bugs/limitations of 3.0.5 that were fixed in later versions? IF 3.0.5 can't do it then your efforts with 3.0.12 while appreciated will be for naught.
As for single long MLP files, this is the best way to do it & the way I generally approach the job - there is one reason only to split out the tracks & that is when you have so much graphical content that adding single streams will tip you over the contiguous limit of images before they get seriously squished as Chrome does
According to Chrome's manual and my experience thus far if one stays less than 20 images in a single stream there's no serious squishing going on. I've only been up to 12 and it looks perfect.
I am building a single group project here - one surround mix with 14 tracks and a stereo mix in the same group (PGC Block authoring) that has 3 "PGC Menus" (the ones that go in the "Language" section and are not track associated), one single track image per track and am embedded playlist for each track.
I'll be taking screenies as I go along......but it may be faster to talk it through so if you want to try this, send me a PM with a phone number and a good time to call.
Thank you for the offer! At this time I'd have to recreate assets and set up for the project and I'm in the hip deep in another project unrelated to DVD-A (too many irons in the fire as the saying goes). I'll file away the offer for possible future use.
Quick Questions:
1 - Is the project folder structure correct?
2 - Are the buttons complex? If they are simple geometric shapes a separate _BTN layer is not needed.
3 - Are the naming protocols correct?
4 - Are the _HL and the _LB (button image files) properly indexed and *not* RGB?
1 - To the best if my knowledge yes, the layout (screen shot in post #173), the folder structure's correct - the IMPORT/AUTHOR/COMMAND programs found their files. No errors were seen (or if errors were given they were corrected).
2 - no, I was staying simple - square blocks or underlines, just something visible.
3 - As far as I know the _LB, _HL, _... were all present and accounted for. Seemed weird the _LB ones couldn't be auto-created by DAC if needed.
4 - yes, indexed - just as I use with DLP.
I actually did create a DVD-A that played on the Oppo-103 - just that the ONLY menu that ever appeared was the one from the 1st track. Didn't look all that pretty (since I was concentrating on the naming and structure instead of aesthetics) but it worked/played. The buttons worked but the highlighted button didn't change with the track. Since that's, for ME, the only thing DAC offers over Chrome I bailed out and did the project as static stills and track points in Chrome. Took about 1/20th the time that I spent with DAC
QUICK question for you: if you re-run AUTHOR step does it wipe out all the navigation you've set up for the buttons on all the menus? Getting everything 100% CORRECT isn't always done the first time thru the Import, Author steps - it was a real painful experience to redo the button navigation and linkage setup