You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
as of version 1.4, transcoded playback is supported in flo (#20) under experimental features. I treated this as an experimental feature because the output is forced to mp3 for compatibility reasons (since AVPlayer does not support OPUS yet)
i remembered that, at some point, there was a rare bug where the track would "go back" to the first timestamp despite the track progress was correct. i was reminded of this bug when someone raised the issue on the Navidrome Discord for another player, but, i can't reproduce it last night while testing with 24 tracks using flo. still, i remember that flo has encountered this kind of issue before
so i need your help!
if you don't use the transcoding feature, you can skip this issue.
but if you do and encounter the issue, please share your findings here!
more information such as:
the "source" track format (e.g m4a, wav, etc)
the track duration (e.g 04:20)
the TranscodingCacheSize or ND_TRANSCODINGCACHESIZE value (if not explicitly set, it's probably 100MB)
the Navidrome version (e.g 1.4.0)
...would be super useful too!
The text was updated successfully, but these errors were encountered:
as of version 1.4, transcoded playback is supported in flo (#20) under experimental features. I treated this as an experimental feature because the output is forced to mp3 for compatibility reasons (since AVPlayer does not support OPUS yet)
i remembered that, at some point, there was a rare bug where the track would "go back" to the first timestamp despite the track progress was correct. i was reminded of this bug when someone raised the issue on the Navidrome Discord for another player, but, i can't reproduce it last night while testing with 24 tracks using flo. still, i remember that flo has encountered this kind of issue before
so i need your help!
if you don't use the transcoding feature, you can skip this issue.
but if you do and encounter the issue, please share your findings here!
more information such as:
TranscodingCacheSize
orND_TRANSCODINGCACHESIZE
value (if not explicitly set, it's probably100MB
)...would be super useful too!
The text was updated successfully, but these errors were encountered: