I tried disabling spectograms and a bunch of bugs appeared:

• Trying to submit audio files yield that error:

/home/pythonsnake/repositories/mediadwarf/lib/python2.6/site-packages/SQLAlchemy-0.8.1-py2.6-linux-x86_64.egg/sqlalchemy/types.py:753: SAWarning: Unicode type received non-unicode bind param value.
  return impl_processor(process_param(value, dialect))

• The thumbnail is set to a nonexistent file,

  /mgoblin_media/fake/thumb/path.jpg
  

Maybe we should rather define a default audio thumbnail for that kind of situation?

Hi everyone,

Apologies in advance for raising this as a ticket if it's inappropriate. I couldn't find a direct contact for the project so this seemed like a next-best place to put it.

I just donated to the FSF campaign to support MediaGoblin, which I think is an excellent idea. I did however notice that on this page:

​http://mediagoblin.org/pages/campaign.html

The "What We'll Do With Your Money" is a bit vague. It says you'll keep donors informed, but it doesn't say what you'll actually spend the money on.

This raised a bit of a flag for me. I've been burned before by an optimistic-sounding free software kickstarter which took my money and never delivered anything tangible. Not to suggest that's what you plan to do (nor do I actually think that the kickstarter planned to do that themselves), but it's always something I keep in mind.

The only reason I personally decided to donate was that I found the FSF press release, which did say what you're going to spend the money on:

"If they reach their goal, the team will use the money to support a full-time project lead to organize volunteers and advance the project to a professional level. With this support and more hard work, Webber estimates that MediaGoblin will be ready for widespread use within a year."

I think it would be really awesome if you could put something along those lines on the donation page as well, so people can see what they're giving money to be spent on. With some luck it might increase the donation rate. :)

Good luck, I hope you reach your goal.

Cheers,

Angus

As Elrond suggested, MEDIA_MANAGER for all the media types must point to the new MediaManager classes. Currently, this is enabled only for "Image" media type. The attached patch makes MEDIA_MANAGER point to a class derived from MediaManagerBase for all the other media types. I have tested it manually for all the media types.