![]() ![]() Part of what I do, outside of the work I do on our Technical Support team, is to gather the information here in the forums and pass it along to the appropriate teams. #Microsoft snagit alternative trial#While I cannot provide any form of roadmap I can pass your feedback along to the development team (I meet regularly with the Technical Product Managers so your feedback will be heard) and though the forums here are often quite lively, I would like to point out that they are not the only source of feedback used we send numerous surveys out to trial users, users that have not upgraded, users that have contacted our Sales team, not to mention the data we collect in person or via the anonymous data collection we do (which can be turned on or off in the application preferences). #Microsoft snagit alternative update#My apologies for the delay, some unexpected time off crept in and I'm just getting back into the swing of things as to your question? Unfortunately there is no way that I can promise any sort of roadmapping (we mention as such in both this month's feature request round-up as well as the community update provided by TechSmith Leadership) in any real capacity. ![]() Failing something like this, I am very sorry but I believe the game is truly and finally up. Maybe too radical, but at least there could be a solution if TS moves very fast and prioritises resources to do this. One step in the right direction I believe would be if TechSmith draws up a list of what it understands to be the main concerns of users, publishes this with their solutions and we vote on it! Can we trust and believe in any new version? There is a problem here that grows with every passing day that TechSmith does not solve the problems users have spent valuable time identifying for TechSmith. ![]() One option is to go back to an earlier version, but I would say TechSmith has lost a lot of credibility because even if you solve user dissatisfaction, there is now the question of trust. The new interface whcih makes work processes much longer and inefficent- many steps backwards - captures being rendered as "beanstalks (long and thin), extortionate time to finalize a video recording that is X hours longer than the orignal and has to be cut ( I tried to save TechSmith by suggesting a user defined maximum recording time based on the length of the original some years ago but received the usual "brush off". In general the reasons are similar to those expressed by others. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |