INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Encoder Settings String  (Read 1729 times)

scthom

  • Citizen of the Universe
  • *****
  • Posts: 621
Encoder Settings String
« 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
Logged

scthom

  • Citizen of the Universe
  • *****
  • Posts: 621
Re: Encoder Settings String
« Reply #1 on: April 05, 2005, 09:53:18 pm »

Bump.

John Gateley, I also sent you an email with the same question(s).
Logged

John Gateley

  • Citizen of the Universe
  • *****
  • Posts: 4957
  • Nice haircut
Re: Encoder Settings String
« Reply #2 on: April 05, 2005, 11:52:31 pm »

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

scthom

  • Citizen of the Universe
  • *****
  • Posts: 621
Re: Encoder Settings String
« Reply #3 on: April 08, 2005, 09:57:38 pm »

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
Logged
Pages: [1]   Go Up