Category implementation

[lukas-w]

Just some thoughts.

• Projects
  • import_lsp: Detect links to soundcloud
  • Detect length of uploaded files. Possible?
  • Remix relationship (suggested by @theguitarplayer)
• Screenshots
• Tutorials
• Samples
  • Detect length of samples.
• Presets
  • Have a field pointing to the instrument (Instrument database?)
• Themes
  • Allow adding screenshot
• SF2, see SF2 category, uploading compressed files #10

[Sti2nd]

What is your idea on the "detect links to soundcloud" option?

[lukas-w]

When importing the old data, we could automatically detect links to Soundcloud in the project's description, and save that Soundcloud ID in a field. Having this information, we can embed a Soundcloud player in the project's description.

[theguitarplayer]

I have another thought for a category/subcategory. How about a remixed/to be remixed category? In the past, users have wanted their song remixed or have remixed someone else's.
An idea is to put all the remixes of a certain song on one page. This will eliminate the necessity of giving links to the origional, and will clarify how the project is to be rated/voted.

[Sti2nd]

I like the idea of connecting different remixes/revisions of one song on one page! I don't exactly understand how you were thinking this could be done automatically @theguitarplayer , if you included a link it could be automatically detected as remix... You must do something manually to make lsp reckognize it as a remix.

[theguitarplayer]

yes, that's a problem, unless users comment links to their remixes

On Thu, Jun 5, 2014 at 4:17 PM, Stian Jørgensrud notifications@github.com
wrote:

I like the idea of connecting different remixes/revisions of one song on
one page! I don't exactly understand how you were thinking this could be
done automatically @theguitarplayer https://github.com/theguitarplayer
, if you included a link it could be automatically detected as remix... You
must do something manually to make lsp reckognize it as a remix.

—
Reply to this email directly or view it on GitHub
#12 (comment).