Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

ok so i switched the trigger to the queue button so the player would function as it used to in LB1, but now, no matter what song is requested, it adds this song: 
https://open.spotify.com/track/5wb8h2gUzyhmCwOtGp29z4?si=134bbf6e565044e9
to the queue and wont display anything in the song request queue text in OBS.

you have done amazing work here, but i don't need this complicated functionality added to the song request through playlists. i really just want it to put the !sr in the queue and display the title like it used to.
im not sure what i could be doing wrong as i only changed the trigger as you suggested to @DenStiveGudDK

also it stopped confirming the !sr in chat as well.

(+1)

Please see here, inside the queue button you need to edit the id variable (use Pull Data command and populate the ID with the viewer’s request) and it will work just the same as in the old LB :)

Yea i get what your saying, i'm just not sure how to populate the ID with the viewer’s request.


I wish there was better documentation on this particular issue, as i know i'm not the only one who would prefer the player to be more like it was in LB1 (not that you dont have enough on your plate with ext. updates for LB2, so im not complaining, just wishing). as the new playlist implementation messes up playback and forces me to constantly switch playlist or be forced to have random playback after the que ends.

(1 edit) (+1)

Actually, I made very extensive documentation for LioranBoard 1 and 2 regarding Twitch triggers and populating variables.

But, now that I think about it, the whole button for displaying the current song requests would have to be completely reworked too. I do not want to do it for a few reasons:

  1. Spotify doesn’t have an endpoint to retrieve your current queue. The extension would have to remember every track you ever added and write to a file constantly in case LioranBoard crashes. You would also have to always add tracks only through the extension itself.

  2. If you already have tracks in your queue prior to using the extension in LioranBoard, there’s virtually no way for me to tell how many tracks are in there or what track is next. This means that if your viewer requests a new track, it will be added to the queue, but there’s no way for me to tell when it’s actually going to be played as I can’t see the queue itself.

  3. You can’t decide to stop playing SR requests for a while and return to them later or maybe in your next stream. Once you clear the queue, all requests are gone.

The old extension was very hacky and buggy at times, I honestly didn’t like that. I also asked several frequent users on what they’d prefer and their answer was a playlist.

What I could do though is to automatically switch to the last playlist you listened to once the last track in your SR playlist finishes. And if someone requests a new song, it would automatically switch back to your SR playlist.

Cheers! Christina

(1 edit)

i understand completely, thanks for taking the time to explain. your solution is not only an amazing fix, but i think its much better and very smart, yet somewhat simple. Cheers, id really look forward to this implementation when you can find the time!

and of course you are right there is extensive docs, i guess i actually was complaining that there wasn't more of a hand holding this is how you switch the buttons for the player, for that i apologies, its not necessary. i could have taken the time to review the LB2 documentation. thank you for all your amazing work.

(+1)

I will try to implement it sometime this week - I can send you a testing version so you can let me know how it works for you :)

that would be amazing, whenever you have the time. thank you!