Quote:
I found out that when you set value:
<Audio SamplesPerSec>1
it produces 48kHz audio, if you set
<Audio SamplesPerSec>2
you video will have audio with 44,1 kHz.
Thanks milos, great first post.
I actually tried this exact thing yesterday, but it didn't work for me. I did however just now verify that it
does work with the AAC encoder, but not with the LPCM encoder which is what I was trying to do.
In other words, I have to choose between MKV with 48KHz PCM or MP4 with 44.1KHz AAC.
Given how bad Youtube's downsampling evidently is, the latter would probably be better. But in cases where I want the best audio quality on Youtube, I have to conclude that Power Director isn't really suitable.
The best compromise I can think of is to produce MKV with 48KHz PCM, and then outside PD, using another tool, remux the MKV with PD's audio stream downsampled to 44.1KHz using a high quality resampler. I expect that the actual quality lost by the pointless upsample-then-downsample procedure in this workflow would be dwarfed by Youtube's conversion from PCM to AAC anyway.
In my case I was very happy with Kdenlive on Linux (which is where I spend most of my time anyway). It had no trouble at all with the source clips and actually did what I told it to do with respect to the output format. But if I wanted to do something more complicated that benefited from PD's capabilities, I'd probably live with the above compromise.
(As an aside, I couldn't believe that after downloading trial versions of about 5 different products, including Adobe Premiere Elements, every single one of them failed to import at least one of the clips I was working with for one reason or another. On Windows, only PowerDirector actually imported the source clips flawlessly!)
It's really quite frustrating how little control they give you for rendering output, and what bizarre constraints are imposed with the options they do give you. I have a ticket in with Support for this question. They replied quickly but it was clear they didn't understand my question. Maybe we'll see this improved in a future release.
Thanks everyone for your interest and help!