DD audio reverts to 384

MrVideo

Active member
I have profiles that have conversion to DD2.0/DD5.1 that uses 640kbps. But, if I go in to do any changes to the profile, the audio reverts to 384. It is not checking to see what it is currently set to and keeping that value. You can't even set DD2.0 to 640. You have to hand exit the profile file afterwards and manually set it.

Please fix. Thanks.
 

Dan203

Senior Developer
Staff member
640 is not possible with 2.0. Even if you hand edit to 640 the internal code is reducing it to 384. That's a limitation of the encoder. 640 is only allowed for 5.1
 

MrVideo

Active member
I'm pretty sure that I've set ffmpeg to do 640kbps for DD2.0 via my own scripts. But, I have to admit that I don't remember checking the bitrate afterwards.

That doesn't dismiss the issue with VRDPro not honoring the value in the profile for DD5.1 when the profile is edited.
 

Dan203

Senior Developer
Staff member
I'm pretty sure that I've set ffmpeg to do 640kbps for DD2.0 via my own scripts. But, I have to admit that I don't remember checking the bitrate afterwards.

That doesn't dismiss the issue with VRDPro not honoring the value in the profile for DD5.1 when the profile is edited.
The rules in the dialog are designed to prevent invalid entries. You're doing something outside the scope of the product by editing the profile by hand. So when you do that, then load the profile into the dialog, any rules the hand edited values violate will be reset. That's how it’s intentionally designed to work.
 

MrVideo

Active member
Dan, you're missing the point. 640kbps is allowed for DD5.1. When set it will indeed do 5.1. The problem is that if the profile is opened for editing, the audio gets reset to 384kbps, instead of keeping the 640kbps that I had set it to. Forcing me to set it again.
 

Dan203

Senior Developer
Staff member
It should allow 640 if the output channels are set to either Automatic or Surround. If that option is set to Stereo or Mono it will limit the bitrate.
 

MrVideo

Active member
It does allow 640. I'll repeat the issue: When you edit the profile during a save, or manage the profile and you go to the audio tab, the value displayed is 384. It does not display the value that was saved in the profile.
 

Dan203

Senior Developer
Staff member
It does allow 640. I'll repeat the issue: When you edit the profile during a save, or manage the profile and you go to the audio tab, the value displayed is 384. It does not display the value that was saved in the profile.
I'm not at my desk right now to verify, but that sounds like a bug. Sounds like it's correcting the error on launch, but not enforcing it on input.
 

MrVideo

Active member
Easy to replicate. Just edit a profile and change the audio to recode to AC3, surround, 640.. Save it. Now edit the profile again and now the audio tab will show 384, instead of the 640 you just saved.
 

Dan203

Senior Developer
Staff member
Easy to replicate. Just edit a profile and change the audio to recode to AC3, surround, 640.. Save it. Now edit the profile again and now the audio tab will show 384, instead of the 640 you just saved.
When I'm not working I'm typically using an iPad for these replies, so it's not something I can replicate until I'm back at my desk.
 

Dan203

Senior Developer
Staff member
Well that turned out to be a bigger issue than I realized, but it'll be fixed in the next release.

Basically the problem was that the "rules" for the dialog were being applied as soon as the dialog was initiated, but before the profile values were actually loaded into it. So the rules were being applied using whatever the default value for each list item was, then being reapplied after the profile was loaded. But at that point some of the controls were restricted based on the default values and as such it prevented the correct value from being loaded from the profile. I'm actually not sure how many profile options this might have affected. I don't think there are many that have hard restrictions like that, but there were likely at least a few others.
 

MrVideo

Active member
What encoder are you using? I just did a test taking two wav files (L & R) and ran them thru ffmpeg and it had no problem encoding @ 640. My script is set for a default of 512. Both had no issues. Even the old aften let me do 512/640 for stereo to DD2.0.
 

Dan203

Senior Developer
Staff member
We are currently using ffmpeg, but we use to use an Intel codec so the limit might have come from that. It’s been a while since I looked at that code so not something I can remember off hand.
 
Top Bottom