Patch Database?

Started by ElliotG, February 18, 2018, 01:06:50 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

ElliotG

I've been thinking about creating an online patch database... I find the forum exchange model less than ideal for searching, and evaluating patches.
I'm looking for input...  I put the example together in google sheets.  It used the filter capability of the spreadsheet to do a structured search, freeform text search is also support by the tool.

Do you think this idea has merit?
Is this a good start at a "taxonomy of sounds" are there key elements missing?  Is there a good reference taxonomy?
Should this be done per "machine" one for the SY300, one for the GT1000, one for GR-55 or build on superset?

I would like the sheet to auto-populate if the expression pedal or CTL switches are used.

Too complicated to maintain? 
Something else available that gets most of the way there?

The example: https://docs.google.com/spreadsheets/d/1nMHMnk1ttXqowWPlk5I7nj0u1pbZhNmZtwtaV-Qao4s/edit?usp=sharing

An image of the spreadsheet is attached.

Let the fur fly...

shawnb

I like the idea - a much more user-friendly & searchable tool. 

I am not sure I like duplicating the data somewhere - as it would become out of date overnight. 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

gumtown

#2
Is it possible to use the current system but obtain a bulk download from a chosen Category/Folder,
say if you chose "SY-300 Patches"
that a combined zip bundle could be downloaded of all attached files within that Parent folder
and all child folders beneath.

Similar to project code zip bundles used on GITHUB.

I remember helping administer a patch database on the old Boss GT Central Forum site, it turned into mess real quickly and required constant maintenance.
Free "GR-55 FloorBoard" editor software from https://sourceforge.net/projects/grfloorboard/

admin

#3
Quote from: gumtown on February 20, 2018, 02:04:45 AM
Is it possible to use the current system but obtain a bulk download from a chosen Category/Folder,
say if you chose "SY-300 Patches"
that a combined zip bundle could be downloaded of all attached files within that Parent folder
and all child folders beneath.

Similar to project code zip bundles used on GITHUB.

I remember helping administer a patch database on the old Boss GT Central Forum site, it turned into mess real quickly and required constant maintenance.


Years ago we attempted to use Database features built into our SMF platform we built this forum upon.
https://www.simplemachines.org/
https://www.simplemachines.org/community/index.php?action=search2;search=database


Goal was clone the patch librarian functionality of Institute of Noise
http://www.instituteofnoise.com/L6/patches.asp

But it was extremely buggy, and never worked.  we have thousands of patches.

Our current scheme of using a dedicated thread for posting each patch, results in further discussions and method of use details about how to use of the patch. 

hading

I proposed using Github to do this some time ago, but Elantric seemed to think it would drive traffic and discussion away from here so I never pursued it any further.

admin

Quote from: hading on February 20, 2018, 07:59:50 AM
I proposed using Github to do this some time ago, but Elantric seemed to think it would drive traffic and discussion away from here so I never pursued it any further.


We do restrict access to patches for members only 


- but We already have folks reselling our patches on Ebay

https://www.vguitarforums.com/smf/index.php?topic=17734.msg126337#msg126337
https://www.vguitarforums.com/smf/index.php?topic=22218.0

Smash

I think restriction is absolutely the right way to go.

I get a lot of contact through demos of VG99 patches on youtube and I always try to drive them here.

ElliotG

QuoteYears ago we attempted to use Database features built into our SMF platform we built this forum upon.

Goal was clone the patch librarian functionality of Institute of Noise
http://www.instituteofnoise.com/L6/patches.asp

But it was extremely buggy, and never worked.  we have thousands of patches.

Our current scheme of using a dedicated thread for posting each patch, results in further discussions and method of use details about how to use of the patch.

Thank you for the feedback and history lesson- that was very informative.       
The forum model is certainly easy to administer, and meets the forums objective as a site for education and conversation.  Is this the desired end-state?  If this is the case, I understand and can support this decision.

If this is still open, It would be nice to have something more searchable, that characterizes the patches and user ratings, while providing the opportunity for communication.   Would the team at SMF be up for creating this capability?  It is amazing what can be done in HTML5.


shawnb

Quote from: ElliotG on February 20, 2018, 04:04:12 PM
Would the team at SMF be up for creating this capability?  It is amazing what can be done in HTML5.

Short answer, no.  I've been helping out over at SMF, and they are working hard to get a new version out the door.  The technology stack at this time is php/mysql. 

It is possible there are better mods out there these days, as SMF has matured a lot in recent years.  The list of available mods may be found here:
https://custom.simplemachines.org/mods/

I haven't seen a good solid mod that sounds like this.  I'd worry about how to implement, because I don't want to have two places to search for mods, and that would be confusing and unmaintainable. 

I wonder if a very smart query against the existing patch database might produce a friendly .csv version of your idea?  Solve the searchable problem, and, leverage the existing DB and use the existing data.  No data migration effort.  Just thinking aloud...
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

shawnb

#9
I hadn't noticed this thread before - similar idea:
https://www.vguitarforums.com/smf/index.php?topic=13227.msg96660#msg96660

https://www.vguitarforums.com/smf/index.php?topic=13227.0

I'm still mulling over the "smart query" idea...   More to come...
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

shawnb

#10
OK, attached is my attempt at automating ElliotG's idea... 

This is in .csv file format for use in Excel.  Just open it in Excel & add Data Filters on the 4th row (the one with the headers) and go to town!

The BEST part about this is that I can schedule it to run every night - it can always stay current. 

This file lists *ALL* patches in any of the patch exchanges on VGuitarforums.  Links to the topics & patches are provided. 

I made an attempt at analyzing the post & subject text & gleaning the instrument, FX & other qualities of the patch.  (We could argue for days about what terms to use!)

I'll be refining this over the next week or two then post it somewhere on this forum.

Feedback welcome,

EDIT:  I had uploaded a test version.  This one should work better!
EDIT2:  Added a screenshot...
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

admin

#11
Looks fantastic!

1st patch " LINK" is
https://localhost/vgf20/index.php?topic=12019

which the final working vetsion should point here:

https://www.vguitarforums.com/smf/index.php?topic=20637

shawnb

Just uploaded one that doesn't point to my test environment...    You'll have better luck with the links in this one...
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp


shawnb

Hmmm...  I suspect caching somewhere - do a shift-F5 on your browser & retry. 

I just downloaded & got the correct one... 
Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp

shawnb

Address the process rather than the outcome.  Then, the outcome becomes more likely.   - Fripp