Is there a way in matrix to setup a nested asset in either a parse file, paint layout, or standard page, but have the nested asset be changed out for another asset based upon a GET variable or something similar?
Yes, using a nested asset listing and dynamic root nodes based on a GET variable.
What if i need a page to nest a child asset directly below it but there are multiple child assets? is there a way to tell the asset listing or nested asset area to nest the child asset where id=x?
Possibly. You can change the root node of an asset listing to a specific asset ID using dynamic parameters. However, you would then need to target the child asset specifically. I'd have to see some example hierarchies and asset types to work out what the best way to do this would be. What problem are you trying to solve? Perhaps there is a simpler way to achieve the required outcome.
I have a page that needs to nest 2 standard page assets, one asset list.
This is basicly what im working with
Root
|–Parent Page
|----Child Page
|------Video 1
|------Video 2
|–Asset Listing
I need the "Child Page" to display some of the metadata from its parent as well as a list of all the videos below itself AND embed the requested video below itself along with some metadata about that video.
Hmmm, interesting. Are there always only two videos below the child page? And is there a way to determine the difference between the two? Could you use naming conventions on them (for example, is one hi-res and one low-res)? You could use a nested asset listing and targetted sort orders and things.
Also, getting metadata from the parent into the child page is going to be interesting, unless the same metadata values are set on the child itself. There is no way to expose metadata from another asset. I'm wondering if multiple paint layouts on the parent page itself isn't the answer, i.e. not actually having a child page at all, or if it's there, not actually displaying it directly.
There will be multiple videos per child page. Is there a way for a child asset to inherit default metadata values from its parent? If so, that would provide me with a way of applying the parent metadata to the child videos and then i wouldnt need to pull parent metadata?
I considered creating a pain layour for the videos and then nesting the video asset into the parent page and expecting the paint layout to print out the video and its metadata as i need it but there again i would need to be able to change the nested asset dynamicly.
No -- children only inherit the metadata schema, but not the values.
[quote]I considered creating a pain layour for the videos and then nesting the video asset into the parent page and expecting the paint layout to print out the video and its metadata as i need it but there again i would need to be able to change the nested asset dynamicly.[/quote]
What's the planned navigation from video to video? I'm missing a key understanding here of what you're trying to achieve, because I don't understand why you have both a parent and child page and I don't know what the asset listing (in your original diagram) is for either. :)
The asset listing will basicly be the navigation. It will be a list of all of the videos under a child page with a link to play them.
I thought about creating a design which would contain the video asset details and have the nested asset listing of all of the other videos and apply this customization to all of the videos… BUT in the diagram above there will be 200+ parent pages so therefor i would need 200+ design customizations because in each of the parse files would need to be some hard coded information about the parent asset and this information would not be in the metadata of the video so i couldnt include it dynamically.
I'm still not sure why you can't just do this with a Paint Layout applied to the parent pages and have the videos as children of the parent pages themselves. What's on the child pages?
Sorry i can explaint this better. Its a very complex design and i cannot be too specific because this is for a client and if they view the forums its better if they dont see me asking questions 
The page that was designed and given to me to work with has content from its parent page, all child asset videos and some content that's just common between all of the videos in that particular section. I need to pull, say, the parent assets info and include it on the page below it no matter what video is playing. If i assign that information to EVERY video it becomes VERY VERY redundant. I want to place this common information in an asset via metata data then when you view the page which has the video, have it pull this common information into the page and display it. But there are 200+ variations of this common information and each version will be used with roughly 30+ videos.
Yes, but I still don't see why you need both a Parent Page and a Child Page (from your original diagram). Why not have 200 Parent Pages (each with their own common information) and use a Paint Layout to nest in both the asset listing that creates the navigation for the videos as well as another asset listing that actually displays the selected video itself?