not a dev, but have you tried uninstalling/reinstalling tuna? running obs as admin? sounds like it doesnt have permission to save settings? thats my 2 ideas.
- Thread starter univrsal
- Start date
colehughes
New Member
Are there instructions to installing in Linux? I'm using Ubuntu 22.04 and trying to install but I'm just unfamiliar. I haven't gotten it to work yet so any help is appreciated. Thanks!
PaiSand
Active Member
It's a deb package, so I guess it's meant for Debian and Ubuntu flavours.
lovemem0re
New Member
how can i make
{title}
{artists}
instead of
{title} - {artists}
?
thanks!
{title}
{artists}
instead of
{title} - {artists}
?
thanks!
lovemem0re
New Member
thanks a lot.
i did something like this :)
i did something like this :)
eze_414
New Member
Ran into a similar issue with an M1 Mac. I tried "Add new" on Song info outputs but it never shows up on this list. Am i not saving the .txt file to the right directory? Or a permissions thing perhaps?
TekNeil
Member
Having the same issue.
TUNA just stopped working recently, not displaying anything via SPOTIFY. Checked the auth details and all looked OK. Re-entered them, no change, still not working. Then today I can't auth because of the above error.
1.96 btw.
radgegamer
New Member
This was my issue too. I assumed that the Client ID and Client Secret were required (which I believe is the case for controlling Spotify which I don't need). Really disappointed with the support though. I posted asking for help and the dev just replied, 'Can't replicate the issue, it's a problem on your end'. When I asked how to fix it, they again just replied 'I don't know'. I might be old school, but when people ask me for help on something I make, I try to answer their questions and help them until they're satisfied, especially when it's public simply because 1. makes you look better to everyone else that you genuinely try to help and 2. just maybe answering the question will answer the same question for many others so they don't need to even ask.
Regardless, I worked it out myself in the end, but if the dev tried to help a little more, they may have been able to help me much quicker.
TekNeil
Member
I can't disagree with you there mate, I think it's got much worse as times gone on, exponetially so over the past 5 years or so.
Regardless, that's not to say dvelopment projects like this aren't appreciated.
PaiSand
Active Member
Never had an issue with this plugin with the exception when I installed it and did wrong one step. I myself help others with similar issue long time ago. Never an issue with Spotify since then, including all the OBS and Tuna updates.
Clearly, you guys had a problem and wanted a magical solution. If no one else can reproduce the issue you're facing, how come you can fix it?
Too many variables and differences on each computer can lead to unexpected results.
The redirect URI is the one you have to set in the Spotify Devs site and points to https://univrsal.github.io/auth/token (you can create your own if you wish) as it's shown on the video where it's explained how to do the spotify devs thing, and it's accesible in the Overview tab under the How do I display the information? / Spotify
And yes, this was the issue I had when installed Tuna years ago.
By the way, in order to be able to edit your posts you need to be older in the forum and post more often. Been helpfull.
Clearly, you guys had a problem and wanted a magical solution. If no one else can reproduce the issue you're facing, how come you can fix it?
Too many variables and differences on each computer can lead to unexpected results.
The redirect URI is the one you have to set in the Spotify Devs site and points to https://univrsal.github.io/auth/token (you can create your own if you wish) as it's shown on the video where it's explained how to do the spotify devs thing, and it's accesible in the Overview tab under the How do I display the information? / Spotify
And yes, this was the issue I had when installed Tuna years ago.
By the way, in order to be able to edit your posts you need to be older in the forum and post more often. Been helpfull.
Last edited:
TekNeil
Member
Nobody else? Literally two of us had the same issue. How can I fix it? Well, as an ex web developer (Many years ago now) I work methodically and narrow things down. Checking each field was the first port of call which instantly made me realise the first two fields aren't needed for simply pulling information. But they were pre-filled by my browser, and generating an invalid redirect.
I can't instantly recognise incorrect auto-filled fields on somebody elses coding without having the time to delve into it, which I don't have the time for. Hence seeking support, not a 'Magical solution'.
Anyway...
univrsal
Active Member
The client id and secret? The browser has nothing to do with them and can't "pre-fill" them, the only way their value can change is when the user enters something into the fields. I'm always open to being proven wrong if it's an easily reproducible issue.
Try resizing the dialog, switching to the dark theme (which is more compact).
From the documentation of this plugin:
If the information refreshes slowly, you'll have to use your own API Credentials
However, I've added an extra label, that clarifies this in the dialog now.
I tend to put as much effort into my responses as the person asking for support did put into his request. The template for opening a new issue also states:
univrsal
Active Member
universallp updated Tuna with a new update entry:
Increase dialog size and add extra label to spotify ui
Read the rest of this update entry...
Increase dialog size and add extra label to spotify ui
Read the rest of this update entry...
OpenFields
Member
universallp, the downloads are still version 1.9.6.
radgegamer
New Member
It's called trying buddy... trying! I build things too, not plugins, but very similar web products and I could quickly reply with 'works for me, it's your problem' too which is soooo much easier, but I at least try to give suggestions of things that might cause the issue. You're right, you can't fix something you can't replicate easily. I've worked in many industries where fault finding of intermittent problems is near impossible.. I work in the truck industry. Do you think my customers would accept that I can't replicate their issues on another truck so it's their problem? I get that it's a free plugin, and I do appreciate the developer building it and developing it as time goes on, but, no one asked for a magic solution, or someone to become arsey because we got poor support. It takes nothing for a developer to have a quick think for a minute and suggest a few things, especially on a public forum of any type simply because it then may save them the hassle of repeating it 20 times privately. I mean, do we just build things to have people moan it doesn't work these days or do we listen and try and find the faults and fix them or tell the users what the issue is on their end? Of course, there are a lot of variables.. But the person that builds the thing is the best person to advise where to start looking. Sure they might give you wrong advice.. but at least they'd have tried rather than 'no idea'. Generally with anything else on streaming that I'd worked with, if I need any assistance on anything, the community and the developers really try to help. And I'm not saying the developer here is bad in any way, I've given honest feedback as to what I experienced as someone trying to get help and how it could have been approached differently and why. If I was the developer, I'd appreciate the feedback and try and do better next time. So clearly us wanting a magical solution is bullshit, and if you had issues and got the same reply you'd feel exactly the same way. But thanks for your input, it's been invaluable! no really! it has!
radgegamer
New Member
I get that, but to be fair... what more could I have told you at the time than explain what the issue was, what my settings were, what I had done to get to that point and how I kept replicating the issue? I'd assume you know I'm using OBS, since it's an OBS plugin, and it turns out the answer was in my question in the end.. I'm not saying what I did to fix it was the actual proper solution, but it worked for me so I can only assume it was due to the help you gave. If I hadn't given all the information you feel I could have, then a simple question asking for the other info would have had me giving you exactly what you needed. At the end of the day, it's a good plugin which is why I asked for help rather than think 'This doesn't work, it sucks' and move on. The fact it didn't work, and I wanted to try and fix it shows it's a good plugin since I didn't give up. I get giving support can be a pain, but like I said, I could see other people's threads, I already looked for similar or same-fault threads and didn't see many people giving any more information than myself. And because I could see other people's threads, they'll see mine, and if the help was there, maybe more questions are answered leaving you more time to build awesome products. By feedback is no way a reflection on the plugin, I just felt let down by the support. It's an honest opinion and I stick by it for the experience. If I didn't have that experience and have to work it out myself then I'd have been singing it's praises 100% rather than just 99%. It's not an attack on you mate, it's just feedback.