fix(ui): reorder and add missing config options#1993
fix(ui): reorder and add missing config options#1993ReenigneArcher merged 10 commits intonightlyfrom
Conversation
ReenigneArcher
left a comment
There was a problem hiding this comment.
These comments are some of the rationale behind re-ordering and such.
| </tbody> | ||
| </table> | ||
| <button class="mt-2 btn btn-success" style="margin: 0 auto" @click="add_global_prep_cmd"> | ||
| <button class="ms-0 mt-2 btn btn-success" style="margin: 0 auto" @click="add_global_prep_cmd"> |
There was a problem hiding this comment.
Button looked odd in the center, so moved it to left side.
| <label for="adapter_name" class="form-label">Adapter Name</label> | ||
| <input type="text" class="form-control" id="adapter_name" placeholder="Radeon RX 580 Series" | ||
| v-model="config.adapter_name" /> | ||
| <div class="form-text" v-if="platform === 'windows'"> |
There was a problem hiding this comment.
v-if not needed here, since parent div already has it.
| <div class="mb-3" v-if="platform === 'linux'"> | ||
| <label for="adapter_name" class="form-label">Adapter Name</label> | ||
| <input class="form-control" id="adapter_name" placeholder="/dev/dri/renderD128" v-model="config.adapter_name" /> | ||
| <div class="form-text"> | ||
| Manually specify a GPU to use for capture.<br> | ||
| <pre>ls /dev/dri/renderD* # to find all devices capable of VAAPI</pre> | ||
| <pre> | ||
| vainfo --display drm --device /dev/dri/renderD129 | \ | ||
| grep -E "((VAProfileH264High|VAProfileHEVCMain|VAProfileHEVCMain10).*VAEntrypointEncSlice)|Driver version" | ||
| </pre> | ||
| Replace ``renderD129`` with the device from above to lists the name and capabilities of the device.<br> | ||
| To be supported by Sunshine, it needs to have at the very minimum: | ||
| <i>VAProfileH264High : VAEntrypointEncSlice</i> | ||
| </div> | ||
| </div> |
There was a problem hiding this comment.
This was on the va-api tab previously, and it was the only option there. I thought it made more sense to put on the A/V tab... and not sure it applies to only va-api anyway?
| <div v-if="currentTab === 'advanced'" class="config-page"> | ||
| <!--Address family--> | ||
|
|
||
| <!-- Network Tab --> |
There was a problem hiding this comment.
Added new Network tab.
|
|
||
| <!-- Advanced Tab --> | ||
| <div v-if="currentTab === 'advanced'" class="config-page"> | ||
| <!-- Channels --> |
There was a problem hiding this comment.
setting was re-added
| </div> | ||
| </div> | ||
|
|
||
| <!-- HEVC Support --> |
There was a problem hiding this comment.
setting was re-added
| </div> | ||
| </div> | ||
|
|
||
| <!-- AV1 Support --> |
There was a problem hiding this comment.
setting was re-added
| </div> | ||
| </div> | ||
|
|
||
| <!-- Capture --> |
There was a problem hiding this comment.
setting was re-added
| </div> | ||
| </div> | ||
|
|
||
| <!-- Encoder --> |
There was a problem hiding this comment.
setting was re-added
| </div> | ||
| </div> | ||
|
|
||
| <!-- Software Encoder Tab --> |
There was a problem hiding this comment.
Moved to end, like shown in the display
make some options appear depending on the value of others
0591cfd to
22604cb
Compare
Description
adapter_nameoption on A/V tabTodo:
Screenshot
Issues Fixed or Closed
Type of Change
.github/...)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.