Propellerhead Forum

Propellerhead Forum (https://www.propellerheads.se/forum/index.php)
-   Feature Suggestion Forum (https://www.propellerheads.se/forum/forumdisplay.php?f=7)
-   -   The official (yeah right) "We need a better Patch finding/categorizing system" thread (https://www.propellerheads.se/forum/showthread.php?t=133033)

Koshdukai 2010-11-10 16:18

Better, more Agile Patch finding/categorizing system, please!
 
Sorry for "The Official" thing, but these "Official" threads trend make me giggle a bit.

EDIT: Title was «The official (yeah right) "We need a better Patch finding/categorizing system" thread»
changed to a less annoying «Better, more Agile Patch finding/categorizing system, please!»

Ok, on with the subject: It's been talked here many times about various solutions to help users quickly find the patches they're after.

Seeing other products browsing capabilities, genre and sound type filtering of patches, and how quickly one can find something out of TeraBytes of samples+patches, I'm starting to be a little "jealous" of that ease of use available today (and for a while now) on other apps.


I'm not asking for a new ReFill format, since that wouldn't help the non-ReFill based patches and sample files.

I'm asking for an hybrid tag based system possible to use with existing ReFills, Patch and Sample files, maybe through a <filename>.tag addon file that lives side-by-side with any of the ReFill (it should work both outside or inside the ReFill if it supports the inclusion of those .tag files, to keep them "together" with the ReFill), Patch and Sample files, or/and a large generic default.tag file, that keeps importing whatever single <filename>.tag files it finds (I'm thinking of patch, sample and refill producers that would add their own official "factory" TAGs when releasing their products)

The important thing to this TAG idea is that, besides using the "official" tags, the user could add their own on top of the ones provided by the refill producers, to better customize their organization setup, while still having access to the basic default classification the original author of the patches.

This user appending of Tags would also come in handy where no tags existed (older ReFills, Patches, etc)


Adding to this, patch/sample browsing really needs some indexed cache pre-loading at the app start, and using a low-priority background process of refreshing that index/cache to keep it as up-to-date/synced as possible to what's really on-disk.

Bottom line is, we really need a reavaluation on the way we find'n'load patches'n'samples.

If Drag'n'Drop from the OS file system was implemented, this wouldn't be as critical for non-ReFill based files, because we would be using existing OS tools to find and pick the correct file to drop on the rack or device.
(This wouldn't solve the ReFill browsing, unless drag'n'dropping a ReFill into the Rack would automatically open that ReFill browsing window).

jlgrimes 2010-11-10 18:59

Quote:

Originally Posted by Koshdukai (Post 814649)
Sorry for "The Official" thing, but these "Official" threads trend make me giggle a bit.

Ok, on with the subject: It's been talked here many times about various solutions to help users quickly find the patches they're after.

Seeing other products browsing capabilities, genre and sound type filtering of patches, and how quickly one can find something out of TeraBytes of samples+patches, I'm starting to be a little "jealous" of that ease of use available today (and for a while now) on other apps.


I'm not asking for a new ReFill format, since that wouldn't help the non-ReFill based patches and sample files.

I'm asking for an hybrid tag based system possible to use with existing ReFills, Patch and Sample files, maybe through a <filename>.tag addon file that lives side-by-side with any of the ReFill (it should work both outside or insise the ReFill if it supports the inclusion of those .tag files, to keep them "together" with the ReFill), Patch and Sample files, or/and a large generic default.tag file, that keeps importing whatever single <filename>.tag files it finds (I'm thinking of patch, sample and refill producers that would add their own official "factory" TAGs when releasing their products)

The important thing to this TAG idea is that, besides using the "official" tags, the user could add their own on top of the ones provided by the refill producers, to better customize their organization setup, while still having access to the basic default classification the original author of the patches.

This user appending of Tags would also come in handy where no tags existed (older ReFills, Patches, etc)


Adding to this, patch/sample browsing really needs some indexed cache pre-loading at the app start, and using a low-priority background process of refreshing that index/cache to keep it as up-to-date/synced as possible to what's really on-disk.

Bottom line is, we really need a reavaluation on the way we find'n'load patches'n'samples.

If Drag'n'Drop from the OS file system was implemented, this wouldn't be as critical for non-ReFill based files, because we would be using existing OS tools to find and pick the correct file to drop on the rack or device.
(This wouldn't solve the ReFill browsing, unless drag'n'dropping a ReFill into the Rack would automatically open that ReFill browsing window).


I agree a tagging system would help organize my refills. Something could be done similar using Favorites but Reason has so many 3rd party available sounds alone that tagging is majorly needed (even if it is up to us users to organize it).


Drag and Drop (especially for samples) is majorly needed as well.

lowlifebware 2010-11-12 00:39

Quote:

Originally Posted by Koshdukai (Post 814649)
Sorry for "The Official" thing, but these "Official" threads trend make me giggle a bit.

Yeah, what is it with these jerks, they must think they f**kin own the place!

JiggeryPokery 2010-11-12 01:45

Quote:

Originally Posted by lowlifebware (Post 815106)
Yeah, what is it with these jerks, they must think they f**kin own the place!

I thought we did...

Smash the state! Anarchy in the Arctic!

Right, time for a Horlicks...

Oh, and OP supported ;)

Koshdukai 2011-01-28 11:50

*bump*

-.-'

BonezMcCoy 2011-01-28 12:05

Agree with tags and would obviously love drag and drop.

Dogboy1973 2011-01-28 13:33

Quote:

Originally Posted by lowlifebware (Post 815106)
Yeah, what is it with these jerks, they must think they f**kin own the place!

:confused: Guess you're going to blame me for that one :rolleyes: :)

Koshdukai 2011-01-28 14:12

LOL! :D

c'mon... you have to admit that all this "The Official ..." threads trend is a bit weird, when made by fellow common forum users ;)

Koshdukai 2011-01-28 15:13

These are some of the "patch browsing" experiences I tried and wouldn't mind having on Record/Reason, where Instrument/Type/Character/Source/Timbre/Articulation/Genre/etc... would simply be factory and/or user added TAGs:

Korg:
http://www.soundonsound.com/sos/feb0...es/korg3.l.jpg

btw, Meta Information per patch, like Author, Company/Producer/Publisher, etc would be nice-to-have, but it could also be just implemented through TAGs, where these would be just one of the many tags attached to a patch.

NI:
http://www.native-instruments.com/fi...tributes_l.png

Arturia:
http://cachepe.zzounds.com/media/qua...00baf67202.jpg


Even this very cumbersome patch selection system (not quite the same as the above examples, but), allows for TAG-like filtering/selection (Arturia's Minimoog V):http://www.soundonsound.com/sos/mar0...g11banks.l.jpg

jlgrimes 2011-01-29 06:52

Tags would be nice but the main weaknesses of the browser is:

1. Slow, Slow, Slow, Slow, Slow
2. No drag and drop.
3. Searching for lost samples is a nightmare, I just end up using windows search which finds the samples much much faster.


All times are GMT +2. The time now is 06:06.