I put a collection of videos on YouTube to help new users getting started using EaSeq (described in this post).
I know that it is slightly off, compared to the other tutorials here, to post links to video tutorials. But now that they are made, then I thought that it would be appropriate to mention them here.
There is much of EaSeq that is not covered here, and I will have to add new videos / instructions in steps. As I am rather untrained in making video tutorials, then I'd appreciate to get feedback on topics that you would like to see demonstrated or that needs to be explained better.
I am making a page on EaSeq's website that also covers this, and it will be updated as new tutorials are being made.
I watch the 27-minute video through, and I only have a few minor points:
When programmers make a video on some software they wrote (but its also true for presentations and live demonstrations) they often make the mistake of conflating "why you should use this software" with "how to use this software". I know this because I am the worst offender :P and you actually do a pretty good job of explaining why feature xyz is useful -- but this is still a bad approach. A "why to use" video is advertising. Sell the strengths of the software, (which EaSeq has plenty of!), because that's all most people want to know -- what can this software do for me? I don't care how or where the button to do xzy is, I'll learn that later, for now I just want to know what your software can do and if its worth downloading. When you make a video on how to do something, then those videos should be framed around a specific analysis goal.
You speak clearly and in a relaxed way, which is enjoyable for someone like me who has 30 minutes to burn on a Saturday afternoon - but it may be a little too slow-paced for most people. Most people outright refuse to watch videos beyond 5-10 minutes, and the best "why you should use this software" is 3 minutes and under. Even the zoom transitions used were slow. Again, I suck at doing this too even though I know better, because it's not easy to cram 1000s of hours of work into 3 minutes, but it's important.
The resolution is pretty low on this YouTube transcoded version. You should perhaps try reuploading to Vimeo in full resolution and see if that looks better - another option which is something I do a lot is to lower your native screen resolution to something lower before you hit record, so that what you see as you record is closer to what your viewers will see after some lossy compression, etc.
As for EaSeq itself, I think it's a great project and a huge step in the right direction for Bioinformatics. There are obviously multiple implementation things I don't fully agree with -- and that's true of all software I use -- and EaSeq is no different, but the real single biggest issue I think you're going to face going forwards is the Windows-only thing. I get that the software is aimed at Biologists more than the computer scientists, so theres a case to be made that Windows is what the target audience is running...
but I dont know... maybe. But my gut feeling is that something like 80-90% of people who have access to the data are running Linux or OSX, and the 10% who are using Windows are not going to hear about EaSeq via word of mouth due to... um... herd-immunity. In short, you may find that you need the blessing of the established bioinformatic core before the people you are targeting will find out about the software in the first place, and those established bioinformaticians probably don't have a Windows Licence Key laying around to test your software out. Perhaps i'm being to negative, but it's an honest concern I have for what I believe is a great vision of how bioinformatics could be done.
Thank you very much for your honest and comprehensive feedback - and for taking the time. I appreciate your line of thinking and agree with many of the points - also the less pleasant ones.
The video was thought as how to, and not to "sell" the program. I made a demo movie last year that was aimed at giving editors and users some whys, but I am am amateur when it comes to selling stuff easeq.net/demo) I'll kept in mind to make clearer distinction between why and how.
I am usually criticised for speaking too fast, so I did my best to slow down:-) point taken. Very true. You'll never see a 27m video from me again. It is also much less challenging to record shorter stretches.
That is odd. It is HD when I play it.
Windows. I am not going to disagree on this one either. If I am capable of it, I'll port it using mono - but that is a big if and presumably not done overnight. On the other hand then MS seems very dedicated to make .Net a crossplatform IDE, so I might get better tools for that soon.
Implementations. It is hard to make a tool that every one will agree on as just right. I read your posting on peak finding being a poor representation of richer data. It was thought provoking, but I did not manage to make up my mind, and will have to get back on that. It would be interesting to contemplate on how that can be improved. I am offline for the next days, but will post in that thread when I get back.