Looking at the CDLC submission format, I was wondering if there should perhaps be a few things added to it?
1. Download counter reset: A bit explanatory. If someone releases a CDLC, and they update it, with let's say, a newer version that fixes something from the last one, they would be able to reset the Download counter. Let's say, Song 'X' get's 100 downloads. If the creator of Song 'X' releases and update, then let's say the same 100 people will download the song. The counter would now be at 200 Downloads, all done by the same 100 people. I would just think it would be a bit more accurate, if the counter was reset with each revision of the project.
2. Problems/Fixes Column: If anyone has ever been on Songsterr, and looked at a Pro Guitar tab, people would see a section where people who have looked at the project, and submitted errors, that the author can then fix. But this will be easier to see then just a comment saying such a thing, and for other users to view and either (A.) Agree with and ask the author to fix it. Or (B.) Say the fix is not needed, and the original chart it correct. The author can then release an update, and take the error off the list. It's simply just for organisation and easy to see.
Looking at the CDLC submission format, I was wondering if there should perhaps be a few things added to it?
1. Download counter reset: A bit explanatory. If someone releases a CDLC, and they update it, with let's say, a newer version that fixes something from the last one, they would be able to reset the Download counter. Let's say, Song 'X' get's 100 downloads. If the creator of Song 'X' releases and update, then let's say the same 100 people will download the song. The counter would now be at 200 Downloads, all done by the same 100 people. I would just think it would be a bit more accurate, if the counter was reset with each revision of the project.
2. Problems/Fixes Column: If anyone has ever been on Songsterr, and looked at a Pro Guitar tab, people would see a section where people who have looked at the project, and submitted errors, that the author can then fix. But this will be easier to see then just a comment saying such a thing, and for other users to view and either (A.) Agree with and ask the author to fix it. Or (B.) Say the fix is not needed, and the original chart it correct. The author can then release an update, and take the error off the list. It's simply just for organisation and easy to see.