Thanks for the comments. not sure where to start with the comments.
But my goal is not really to compete with any of the websites out there (actually did not even know about korgfans). Im trying to improve the wheel and not re-create it as somebody mentioned.
I think my site has several Pro's compared to some others, for instance, its fully automated, if somebody uploads a patch, it's already there and ready to be downloaded and demos to be listened to so it requires lower maintenance, so no more waiting on siteadmin to upload things etc. Only thing that is manual is updating patches for now and adding categories (which is done by just adding a folder on the server).
Also RSS feed is available which could be expanded to be category specific etc. Also linkable images which generates patchnames & downloads on the fly that you can place on websites/forums that i did, not sure if will be well recieved but hopefully it's useful to atleast somebody.
Patch upload sizes can be adjusted to be able to upload samples etc (otherwise submission via mail works fine meanwhile).
It's a nice idea. Part of the reason why I got involved with KorgFans was to try to create a socially driven patch library, but no-one was sharing any patches there and the platform we used took most of the features we needed away from us.
Since I have written my site from the groundup myself this won't be a problem. And if I need to create a new feature or change anything, I just dot it myself and if I don't know how to do it I learn how to do it lol.
The only thing I would add to that is a brief description of the sound(s) in question.
The patchbrowser looks weird now since there are like one patch on the site only, and there are actual two view settings that displays the patches in different ways: List view & Grid view. In list view there is no brief description (but perhaps could be added) and shows maximal amount of info in a table with sorting capability. But in grid view there is a short description for every Patch.
I don't really think you need different sections for M3 & M50. Otherwise you could also make sections for various flavours of Triton too.
These can be easily adjusted, I was not sure what categories to have at the start so I just thought of those. Have to research abit more regarding patch compability between M3/m50 and the different Triton formats, but on the other hand, I don't think there are so many patches for the tritons and have them all in same category and have the specific model in the name like "Brass Collection [Extreme]" could work perhaps.
Not a whole lot of people are gonna google "where can i upload my triton patches for all to have?"
Not perhaps exactly that but maybe they are looking for patches for korg synths and if you search for korg patches on google atleast on google.se(sweden) my website turns up on the first page, and i have not done any search engine optimization or anything (have no experience in it either tbh), and will most likely to improve when there are actual content on the site (hopefully). And if an user finds the website to download patches, even if his intentions were not to upload patches he could be encouraged to share.
And as stated this was made as a hobbyproject, if it does not go anywhere, it's not the end of the world so it does not really matter, atleast i learned more about coding and only lost like 10dollars on the domainname
. I will be submitting some more patches later this week. But when I' get my kronos i will be programming alot more, I don't find the Radias-exb that inspiring to program on, but that's just me, everything is so spread around on different pages, with Kronos with the better resolution and graphical UI they have packed in more info per page for the VA engines so IMO it will be much more intuitive.
who might have patches for these models available. If your keyboard model is not available on the site I will be more than glad to add it. cheers
