Skip to content

fix(types): accept multichannel as valid speaker-separation for conversational summary model - #286

Open
pylrn wants to merge 1 commit into
AssemblyAI:masterfrom
pylrn:feat/conversational-summary-multichannel
Open

pylrn wants to merge 1 commit into
AssemblyAI:masterfrom
pylrn:feat/conversational-summary-multichannel

Conversation

@pylrn

@pylrn pylrn commented Oct 26, 2026

Copy link
Copy Markdown
Contributor

Summary

Clarifies and verifies that multichannel is accepted as a valid speaker-separation option for SummarizationModel.conversational.

The SummarizationModel.conversational docstring previously listed only speaker_labels and dual_channel as required speaker-separation options, omitting multichannel — the recommended, non-deprecated alternative to dual_channel. This caused confusion (e.g. cross-referenced in AssemblyAI/assemblyai-node-sdk#71) as users were led to believe that the deprecated dual_channel parameter was required for conversational summaries.

Changes

  • assemblyai/types.py: Update the docstring for SummarizationModel.conversational to specify speaker_labels, multichannel, or dual_channel, noting multichannel as the recommended approach and dual_channel as deprecated.
  • assemblyai/__version__.py: Bump version from 1.8.2 to 1.8.3 to satisfy the repository's version bump check workflow.
  • tests/unit/test_summarization.py: Add parametrized unit test test_conversational_summary_with_speaker_separation verifying that multichannel, speaker_labels, and dual_channel are all properly validated and serialized alongside summary_model="conversational" and summary_type="bullets".

Verification

  • pytest tests/unit/test_summarization.py passes (9/9 passed).
  • ruff check assemblyai --config ./ruff.toml passes cleanly.
  • ruff format --check --config ./ruff.toml assemblyai passes cleanly.

…rsational summary model

The SummarizationModel.conversational docstring listed only
`speaker_labels` and `dual_channel` as valid speaker-separation
requirements, omitting `multichannel` — the recommended and
non-deprecated alternative to `dual_channel`.

This caused confusion because passing `multichannel=True` alongside
`summary_model=SummarizationModel.conversational` is fully supported
by the API but was undocumented, leading users to incorrectly assume
they had to use the deprecated `dual_channel` flag.

Fixes AssemblyAI/assemblyai-node-sdk#71 (same root cause applies to
the Python SDK docstring).

Changes:
- Updated `SummarizationModel.conversational` docstring to list
  `multichannel` as the recommended speaker-separation option, with
  `dual_channel` noted as deprecated.
- Added parametrized regression test
  `test_conversational_summary_with_speaker_separation` covering
  multichannel, speaker_labels, and dual_channel to confirm no
  client-side error is raised for any of these valid combinations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant