I think this problem could be linked to the changes in the layout API and the order of the loading of the video elements.
Please try to add layoutmetadata with index property to parallel videos so they render in the correct order, something like:
var layout1:LayoutMetadata = new LayoutMetadata();
layout1.index= 10 ;
var layout2:LayoutMetadata = new LayoutMetadata();
layout2.index= 20 ;
Tell me if that worked,
Actually I just checked this out today as I have to build a VPAID compliant player, and I can confirm the OP's bug.
By default VPAIDSample is setup to run a linear pre-roll before a content video in a serial element.
But what actually happens is that the preroll and the content video play at the same time, and if you use the "pause" button the content video pauses but the eyewonder preroll keeps running in the background.
So I do agree, there is also a layout issue, but there is also some kind of issue with the preroll example itself.
I will see if I can figure this one out.
This is kind of a weird one, maybe I do not have a good understanding of VPAIDElements yet....
But if I modify the VPAIDSample to make it create only a VPAID Linear element, and assign that to the mediaplayer, it won't play.
Should a VPAID ad unit play using the mediaplayer's play() method like any other media?
I can provide a log of the console traces from this, it's odd because it looks like it's doing something, I'm just not sure what as yet.
Reason I am investigating this is because I have another project which uses VAST, but want to add VPAID to it as well. When I get a VPAIDElement in that player, it also doesn't play...