2011 Bravias no aac

Hi there,

I own two 2011 model Bravias and had to comment out the "just remux h264 with aac audio" matching rules from the parent sony2012 profile to get audio from mkv/h264/aac. Can anybody confirm that native aac doesn't work in all cases?

CU,
Low

[NX3]

Confirmed issue, you'll find lots of postings about this (many by me!) a few changes to the profile and get it fixed easily enough.

Some info here and the fix I used with profile

viewtopic.php?f=11&t=3662&start=40#p66363

Ok, I see. Thanks for pointing me to the right thread.

Just one more quick question about this profile of yours: In the sony2011 section there is a rule that transcodes aac audio to ac3 if the container is "*". I'm sorry, but I'm not familiar yet with wildcrads in matching rules.

Does the wildcard mean that ANY container with aac audio remains untouched videowise? Or does it mean that only the audio part of the ruie is executed as some kind of post-processing while at the same time other rules are applied to the file which match as well, like e.g. the "just remux mkv/h264/aac to mpegts" rule from the parent sony2012 profile?

CU
Low

[Illico]

Does the wildcard mean that ANY container with aac audio remains untouched videowise?

Yes, any container will be change to mpegts, any video will be remuxed, aac audio will be transcoded to ac3.

Doesn't such a rule where the container is wildcarded render all other rules useless where the video that comes with aac audio has to be transcoded as well? If so, is it wise to use wildcards if we are not sure the TV can cope with any kind of video?

If in the parent profile sony2012 there is a rule that just remuxes mkv/h264/aac to mpeg2ts/h264/aac, can we override this with an audio transcoding rule in the sony2011 profile without changing the sony2012 profile itself? Matching rules have to be unique across all parent and child profiles of a particular device, don't they?

Just when I think I got how matching rules work, new miracles emerge.