Quick note about feedback, bugs, etc.

I got some feedback recently that inspired this update, which is a bit about how the team works.

The main thing I want to say is that if you have a bug that is destroying your use of Dynaframe, Please (seriously..please...) let me know.  You can message me on here, on the discord, you can directly message me, or email me at joe@geek-toolkit.com.  If you want to just know the status of a bug or an issue, let me know.  I'm always glad to discuss, and sometimes things slip through the cracks. It's the nature of the complexity of this software, and the amount of different users we have.  

If you have feedback, you can also use all of those channels to let me know, but the best is to file an issue here: Geektoolkit/DynaframeProIssues: This is a public repo to track issues and feature requests for Dynaframe Pro, a Patreon Supported project (github.com)

The way the team works is when a feedback item comes in, we look at the 'cost' of the fix in time and effort, and compare that to the direction we want the software to go in.  Many things align with work we already have planned, and so we push the work to then (the Exif items were all in this bucket and will be 'fixed' with the new overlay engine...when we work on it we review those bugs to see how to incorporate that feedback).

That being said, you may have an item that just makes the software unusable for you. Let us know please.  If it's something we can't fix, we may be able to at least give you a workaround to get you by.  Sometimes, like a recent item involving non ASCII characters, it just takes me digging in for a night (btw next build will handle non ASCII characters, so that should remove the question marks! )

Sometimes, sadly, we can't fix something...or we can't fix it at this time.  A good example of two of those is overlays/infobar on top of videos...and HEIC.  We do investigations every month to see the state of things and to try to push things like that forward.  Sometimes we spend half a month just trying to solve those issues, and we have to drop them to continue to drive the project forward.  It doesn't mean we're giving up, but you may not see movement on them for months at a time (HEIC has been particularly painful, but we keep trying).

There were a number of reasons I put this project behind a Patreon.  One was to filter out the feedback I was getting to people that were investing into the project...and then to work hard on addressing that feedback.  I may not be doing a great job...but I'll work to get better. So please...if you have feedback that you don't feel is getting addressed, please contact us.  At worst we can have a dialog about why something is the way it is, at best we can fix it. 

Thanks,

Joe Farro

on behalf of the Dynaframe Team