Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI/UX Improvements #61

Merged
merged 11 commits into from
Jan 24, 2024
Merged

UI/UX Improvements #61

merged 11 commits into from
Jan 24, 2024

Conversation

damontecres
Copy link
Owner

@damontecres damontecres commented Jan 23, 2024

Changes

  1. Use a marquee on selected items when the title is too long
  2. Use a unicode icon for tag & performer counts (this is easier than using an svg image)
  3. Updates to the video details page
  4. Only show rows if there's actual content
  5. Add ability to force a scene to play via transcode

Demo:

stashapp.mp4

@damontecres damontecres added the user interface Relates to the app's user interface/experience label Jan 23, 2024
@damontecres damontecres merged commit e2b0afe into main Jan 24, 2024
2 checks passed
@damontecres damontecres deleted the feat/ui-ux-improvements branch January 24, 2024 21:25
damontecres added a commit that referenced this pull request Feb 10, 2024
Add fontawesome and use the same icons that the server web UI does on
the scene cards rather than the unicode ones added in #61.

Also adds the studio name if available to the card until #89 can be
done.

Here's what it looks like now:
<img width="257" alt="Screenshot"
src="https://github.com/damontecres/StashAppAndroidTV/assets/154766448/d22e52cb-ba7a-4f4a-adaa-b04769e4109a">
damontecres added a commit that referenced this pull request Apr 18, 2024
Closes #232
Closes #59 

Don't always forced AV1 files to transcode. This allows devices that do
support AV1 to direct stream and devices that do not support AV1, can
trigger a manual transcode (see #61) via the action button at the bottom
of scene details.
damontecres added a commit that referenced this pull request May 25, 2024
The server will provide a stream labelled "Direct stream", but this is
aimed towards the web UI player. In some cases, an Android TV device can
direct play the video even when the web UI cannot.

This PR changes the direct play vs transcode decision. The app will
check what video/audio codecs the device reports as able to decode. If
the video has a supported video codec and supported audio codec, the app
will attempt to play the video directly no matter what.

A user can still force transcoding (#61) if needed. This PR also adds
the ability to force a direct play as well.

In advanced settings, a user can specify specific codecs which should be
considered as supported for direct play even if the device doesn't
report them as supported (`ac3` and `pcm` audio is a good example of
this). Several audio codecs are included in this list by default, but
can be removed if needed.

That said, the attempt is just that, an attempt. Since the server does
not expose finer grained parameters, such as H264 profiles/levels, these
parameters are _not_ considered in the decision. This means some videos
may not actually direct play, but users can force the transcode in these
situations.

Finally, there is an advanced setting to enable a debug overlay during
playback which explains the decision to direct play vs transcode.

Closes #270

Related to #59, #232, & #233

Ref:
- https://developer.android.com/media/platform/supported-formats
- https://developer.android.com/media/media3/exoplayer/supported-formats
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user interface Relates to the app's user interface/experience
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant