<h1 dir="auto">🚀 Feature request</h1>
<ol dir="auto">
<li>Enable multilabel classification mode and regression mode for the widgets in the model repo.</li>
<li>Create the corresponding tags that can be read from the model card.</li>
</ol>
<h2 dir="auto">Motivation</h2>
<p dir="auto">Models for sequence classification by default support three modes: binary/multiclass classification, multilabel classification, and regression. However, the widgets in the model repository support only multiclass mode (where probabilities of classes sum to 1). This can be misleading for the users who taste the models using the widgets. For example, my model <a href="https://huggingface.co/cointegrated/rubert-tiny-toxicity" rel="nofollow">https://huggingface.co/cointegrated/rubert-tiny-toxicity</a>, which is intended for multilabel classification, but the widget normalizes the predicted probabilities to sum to 1, which leads to confisuion of the potential users of the model.</p>
<h2 dir="auto">Your contribution</h2>
<p dir="auto">If you show me where to start, I could start working on implementing this feature. However, currently I don't know what part of the Huggingface repository is responsible for widgets and underlying computations.</p>
<h1 dir="auto">🚀 Feature request</h1>

<p dir="auto">There seem to be differences between S2T and Wav2Vec2 which are hard to understand reason about that may be fixable.</p>
<h2 dir="auto">Motivation</h2>

<p dir="auto">Adding something like AutomaticSpeechRecognitionPipeline might be desirable and would be hard to do in current state. If/When new multimodal models are added it is going to add more and more complexity. Aiming for consistent API is desirable IMO.</p>
<h2 dir="auto">Description</h2>
<ul dir="auto">
<li>There are no <code class="notranslate">AutoProcessor.from_pretrained</code>.</li>
<li>Wav2Vec2 cannot use <code class="notranslate">skip_special_tokens</code> for the decode variant (because it skips <code class="notranslate">&lt;pad&gt;</code> tokens early leading to removing all duplicate letters from the output. IMO it's a "bug" as <code class="notranslate">&lt;pad&gt;</code> in the context of CTC is not a special_tokens (at least until letters are resolved).</li>
<li>Wav2Vec2 uses 1 forward pass, where S2T uses  generate function. It would be nice, if there could be 1 interface only. (maybe just overload the <code class="notranslate">Wav2Vec2ForCTC.generate</code> ?</li>
<li>S2T overloads <code class="notranslate">input_ids</code> with float tensors when <code class="notranslate">generating</code>, which works in practice but does seem like a piggy-back of the generate function and is definitely confusing to use. If <code class="notranslate">generate</code> is generic enough maybe then <code class="notranslate">input_ids</code> should be renamed to reflect that (<code class="notranslate">input_ids</code> are IDs everywhere in the rest of transformers. It could be a simple internal variable rename, I don't imply we should change any function signature anywhere, just that the variable is not necessarily IDs. Isn't it a bit like <code class="notranslate">inputs_embed</code> ?</li>
<li>Wav2Vec2Processor returns 'input_values' where S2TProcessor returns 'input_features'. They seem (at least in appearance) to be the same. Would it be better to use only 1 name if they do ?</li>
</ul>
<h2 dir="auto">Your contribution</h2>

<p dir="auto">Happy to contribute with PRs but I lack the more general view to be sure about what direction to take, and where are the "better" fixes.</p>