lovegaoshi

One quick and dirty solution is to probe the length of your media file with ffprobe (which is in the ffmpeg package), then segment it into shorter chunks and do...

~我默认歌单倒是没问题。重构的时候发现fetch params只要credentials设置了就会412~ 也有可能是没带UA ``` >>> import requests >>> requests.get('https://api.bilibili.com/x/web-interface/nav') >>> requests.get('https://api.bilibili.com/x/web-interface/nav',headers={"user-agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36"}) ```

这是因为随机播放就是真的随机，随机算法又是写在调用的播放器里，不在这里 我的解决半法，改react-music-player： https://github.com/lijinke666/react-music-player/commit/ee814eeca32494169a0dbd3b020f31fe8ca8eddc

是不是我打开的方式不对？获取不到视频? https://api.snm0516.aisee.tv/x/tv/index/space?mid=355371630 vs. https://api.bilibili.com/x/space/wbi/arc/search?jsonp=jsonp&mid=355371630&pn=1&ps=50&tid=3&wts=1706550433&w_rid=df52530dc11517998ba715a2e17293ba

use [he.decode](https://www.npmjs.com/package/he/v/0.3.1)

if u come across the docs ud notice, nextTrack indeed doesnt exist on Event.PlaybackActiveTrackChanged. https://rntp.dev/docs/api/events#playbackactivetrackchanged

currentindex +1?? its not like shuffle is nqtively supported yet On Wed, Mar 6, 2024, 8:31 AM Jackie-gurung ***@***.***> wrote: > Yes. > what can be done to get next...

I can confirm by opting out of bridgeless with` load(bridgelessEnabled = false)`, everything works as intended. RNTP also has a notification no longer working issue as mentioned in the PR...

its bc ur current exoplayer queue is the very last item and your android version is < 13. maybe setting exoplayer repeat mode to repeat helps, u can try taht.

i can see this in example by just commenting out title and duration in onUpdateCurrentTrackMetadata(). it only messes up when replacing currentIndex Tracks. though I dont see the same behavior...