Open henryk86 opened 6 months ago
https://github.com/toniebox-reverse-engineering/teddycloud/issues/156 This could reduce the pain.
It is not possible to differentiate the tonies itself. A workaround may be to use predefined tags in the tonies.json
https://github.com/toniebox-reverse-engineering/teddycloud/issues/157 may help with that, too.
This issue is more related to the library view than the functionality around it.
the two other issues are focused on the tonie webcard view.
If I use boxine to fill my creative tonie and then put it on the box, teddycloud caches the content to the library with an audioID where of course no data is found.
so if I use a lot of such creative tonies, I have a lot of number tafs in my library without any information.
maybe the solution is as easy as „don‘t use boxine to fill your creative tonies“. Then I would expect a hint in the documentation not to use boxine if using teddycloud.
or a some how defined solution for that (separate folder for creative tonies? Any more information fetched from boxine (are there any?), …)