A client has me doing some work which involves "buttons over video" (as this feature is called by forum contributors). It occurs to me that it would be very neat to know when a TT contains Cells/Navpacks which include buttons (i.e. an action track in Sonic parlance) and then be able to "drill down" to the Navpack level to inspect and possibly edit what's there. This would be especially nice when I am not the original author.
I suppose this feature could be generalized and apply to all PGCs in all spaces. It would make identifying dummy PGCs in VMGM and VTSM space that much easier.
Michael
Request for "PGC Summary" window
I've added this to the top post.
I hope the programming team like the idea :-)
Hi Michael,
> One thing which I don't want to lose is the abilty
> to tell where a given attribute "lives"
I guess the window could be subdivided into sections indicating this - or could have a "show" button a la Tracer to jump to a highlighted item ?
> I'm seeing this as a floating palettte
I agree.
> at some point I would need to see a mock up to really
> get an idea of how this would look and work.
Well, historically Larry and John don't tend to work that way, but you never know !
> Question #1: Is this is an editable view of the displayed
> attributes or just a summary view
I think it would be best as a summary view for information only, especially if it has a "show" button.
> Question #2: Can I use the contents of this window to navigate to items in the PGC
I guess that's what the "show" button might do. As far as cell commands are concerned, maybe there could be a list of cells that have a command assigned and what that command is. Clicking on the cell number and choosing Show would take you to the relevant cell...?
Ian
Sounds promising...
Ian -
One thing which I don't want to lose is the abilty to tell where a given attribute "lives" in the structural hierarchy of the DVD. If information becomes too abstracted and/or summarized then it becomes less easy to work with in the actual DVD.
Meantime...
I'm seeing this as a floating palettte. I'm thinking maybe its tabbed so regardless of what's in the 2-pane main window, I can access a summary of the current PGC and the current container domain which would be either the VTS (for TT PGCs), VTSM (for VTS Menu PGCs) or VMGM (for Video Manager PGCs). That would be way handy, for example, for doing work with subtitle streams (!) where some of the information is at the TT level and some at the PGC level.
At some point I would need to see a mock up to really get an idea of how this would look and work.
Question #1: Is this is an editable view of the displayed attributes or just a summary view.
Question #2: Can I use the contents of this window to navigate to items in the PGC - i.e. can I click on an item and have this item revealed in the main window? [Could be tricky if we're talking about cell commands which could be used by more than one cell.]
I also just thought of another related new feature: a means of determining which cells are in use in a VTS and by which PGCs. I don't think there's an easy way to do that right now.
Michael
PGC Summary Window
A neater solution to the ideas discussed above might simply to be have an optional "summary" window. The idea is that this would show the most frequently-used attributes of the current PGC, it's cells and nav-packs. Ideally this would be user-configurable, allowing us to choose which items we would like in it, for the PGC involved, regardless of which "level" of the spec the item occurs at.
So, as an example, my default config for it would probably show:
Domain & VTS if applicable
PGC No, Title and PTT Nos. if applicable
Title List or Program Map twirly
Entry PGCs of relevant VTSM
Dummy Y/N
Playback Time
PGC UOPs twirly
Pre & Post Command twirlies
Cell-Commands ( With an indication of which is in use by which cell )
Next & Prev PGCs
List of cells containing buttons
Button Command twirly for each cell, if buttons exist
Button Navigation twirly same
- and I would like to choose to add or remove these and other properties, like Video & Audio attributes for example.
Michael, do you think this makes sense ? Larry, are these ideas good/bad/easy/hard/impossible ?
Ian
Actually this is a similar
Actually this is a similar request to my one for PGC durations displayed at a higher level, I think, and it raises a larger issue about the interface design:
Data is displayed in dvdAE as dictated by the spec - for example, no nav-pack information is displayed at the PGC level and vica-versa - I see this as both a strength and a weakness of the current interface. On the one hand it really reveals the logical structure of the DVD in a very explicit fashion ( a huge strength, imnsho ) and is 100% consistent and logical; on the other it can involve lots of "clicking about" to trace navigations details, and requires you to hold lots of information your head. A classic example would be cell-commands. You can see at the cell level which command is assigned but not what others are available, likewise at the PGC level you can see all the commands but not which cells ( of any ) they are assigned to.
Exactly how to address this difficulty without ruining the elegance of the current design is tricky. But - how about tear-off "information" windows ? Say you want to have the information for a title's VTSM information easily at-hand ( so you can keep track of which PGC is root, angle etc, say ) Maybe if you were able to drag this window out of the right pane and leave it "hanging" around while you click elsewhere...? Even better, if you could select only certain pieces of information and have them be "sticky" for as long as you wanted.
Alternatively and possibly better, what if the right pane could optionally be subdivided into sections - say, one for: PGC info, nav-pack info,VTS info etc, and each section simply retained the last relevant piece of information. So, in my above example, I could be looking at the cell-commands at the PGC level. I click the "split right pane" button and the top half retains the PGC info I was looking at, while a new section allows me to drill on down to the cell level...? These subdivisions might then be rearranged as I chose...
Just brainstorming, I'm sure there's a better solution that achieves the same results !
Ian
Post new comment