TBH i DK if that’s posssible without having to get past the original guys who wanna act like code factory 2.0 in this situation, so. This is also the main reason why I’m not wasting $3 on every vocalizer voice on droid
Actually, klango audio conferences will be implemented into klango directly while klango chat will remain a program, at least that’s my current plan. My reasoning is that they are 2 completely different things. Klango conferences are audio conferences based on my own TeamConference protocol, which achives a similar sound quality as teamtalk and has build in encryption and is in general more lightweight. Klango chat is a chat only feature. How ever, i might change this if the community wants it, it’s just my personal stance on it. If i would change it though i would just combine klango chat and conference and integrate them both into klango, integrating them both as a klango program doesn’t make much sense because i have to bundle the dll and directives any way.
yep sadly 🙁
Yeah we need to fill klango back up, that’s really important haha. But well… someone told me that audio conferences might be there soon. Who knows.
TBH i DK if that’s posssible without having to get past the original guys who wanna act like code factory 2.0 in this situation, so. This is also the main reason why I’m not wasting $3 on every vocalizer voice on droid
How are audio conferences related to code factory?
no it’s not that, it’s this Klango in general. Also I’d probably make a seperate klango program for conferences probably.
or the other thing I would do is I would have klango chat as part of the conferences like elten where you can just chat while the conference is active
Actually, klango audio conferences will be implemented into klango directly while klango chat will remain a program, at least that’s my current plan. My reasoning is that they are 2 completely different things. Klango conferences are audio conferences based on my own TeamConference protocol, which achives a similar sound quality as teamtalk and has build in encryption and is in general more lightweight. Klango chat is a chat only feature. How ever, i might change this if the community wants it, it’s just my personal stance on it. If i would change it though i would just combine klango chat and conference and integrate them both into klango, integrating them both as a klango program doesn’t make much sense because i have to bundle the dll and directives any way.