INTERACT FORUM
Windows => Plug-in Development => Topic started by: scthom on April 03, 2005, 01:11:44 pm
-
What is the format for the Encoder plugin "Settings" string (new SDK)?
It's not clear from the SDK text and sample plugin what the format should be.
Are you looking for something like "Bitrate=900 Quality=5"?
Is this the string that is parsed for the GetInfo function?
TIA
-
Bump.
John Gateley, I also sent you an email with the same question(s).
-
Sorry, I thought I'd answered all your e-mails.
The "settings" string contains ALL of the settings for your encoder. It is stored as a single string in the registry, or perhaps many places in the registry (such as one setting for ripping, one for burning, one for the UPnP server). (the encoder does not store this, the invoker of the encoder does).
Basically, you take all the configurable options of your encoder, and package them up into a single string, or take the string and set all the options.
Basic example: the encoder handles flavor ("vbr" or "cbr") and bitrate
(some number - for simplicity, the number is used for both flavors).
Then an encoding string might look like "flavor=vrb&bitrate=128".
You are responsible for writing the code that parses the string and turns it into the actual options needed by your encoder, and for generating the string so that the invoker of the encoder can store the options for later use.
Hope this helps,
j
-
Sorry, I thought I'd answered all your e-mails.
The "settings" string contains ALL of the settings for your encoder. It is stored as a single string in the registry, or perhaps many places in the registry (such as one setting for ripping, one for burning, one for the UPnP server). (the encoder does not store this, the invoker of the encoder does).
Basically, you take all the configurable options of your encoder, and package them up into a single string, or take the string and set all the options.
Basic example: the encoder handles flavor ("vbr" or "cbr") and bitrate
(some number - for simplicity, the number is used for both flavors).
Then an encoding string might look like "flavor=vrb&bitrate=128".
You are responsible for writing the code that parses the string and turns it into the actual options needed by your encoder, and for generating the string so that the invoker of the encoder can store the options for later use.
Thanks, I posted it here first and didn't hear for a couple of days and that's when I sent the email.
That makes sense. Don't forget to update the text in the SDK for future encoder programmers :P