PIP with mix audio metadata in hdmv

[Willyfan]

I'm authoring a disk with a PIP feature. The picture part work ok, but I have some problem with audio.
I use DTS HD MA audio for primary, and DTS express for secondary stream. If I encode secondary with a pre-assigned attenuation for primary audio all work fine, but if I try to put in the secondary encoded file the metadata for different volume attenuation (DTS encoder accept a aaf file for this pourpose), I'm unable to have a correct result. The Primary audio still at hight volume for all time.
Someone have experience with this problem?

[rik1138]

When you say it works with a pre-defined attenuation, you mean just using the sliders in the DTS encoder?

You didn't mention authoring software, but if you are using Scenarist, make sure you have the 'Audio Mix App Flag' on your PlayList set to 'Applied Secondary...'

In case it's a problem with the audio encoding:
Do you get _any_ errors from the DTS encoder when it finished using the AAF file? (read through the .LOG file) Two things I can think of:
Are you making the AAF file correctly? (I've never done that side of it, but there's a detailed walk-through for making the files from Pro-Tools in the DTS manual... I gave that manual to our audio guy, and the AAFs he created worked perfectly)

Second, the AAFs are probably timecode based. When you import your WAVs (or whatever) in the DTS encoder, make sure you are setting a start timecode that is exactly the same as the one used in the source file where the AAFs were created (DTS will just default to 00:00:00:00 if you don't change it). (if the timecode in the AAF is no where in the audio, you will get an error. But if the AAF starts at 01:00:00:00, and your audio is over an hour long, that timecode will exist by default an hour into your DTS encode, so you won't get an error, but it won't work correctly.)
(And make sure the Enable AAF Metadata button is blue...)

See if any of that is causing your problem... I remember the timecode issue messing me up a few times...