Re to my post:
my new Re:
heading here out to whom has a clue about programming etc.:
speaking theoretically:
could a code be written so that “collect samples” would work this way: )???)
all samples in the project are collected
_they get stored within that new project related folder that is created automatically (same name as project)
_ these samples get stored as a dublicate, each with a slightly changed name.
On the ending for example. for example add -“c1” ( c stands for copy)
Q: is this correct, can this be donne by programmers ?..if anybody ever would want to do
further:
i just opened crunch elk.
i think such “sample collect” functionality would ideally be implemented in the crunch elk editor.
The programm could also be written so that a “kind of a log” is created about the collected samples.
so when a copy of a sample with ending -c1 allready exists, the next copy would be named -c2.
Also could such log folder also allow the user to get insight of what samples he has doubled, and how often a sample has been copied.
again: this is doable by a programmer right ?
next Q:
so where is the problem ?
will elektron ever do ?
would you give Elektron any trust to move something ?
how about the community to set up a fund raiser for mr. @mzero
maaaaybeee this could be a doable path ?
i´d be willing to pay 100$ for this functionality…looking at 50$ to be a more reasonable number
(i´m not willing to setup any dynamics. thats just not my part,
but maybe we here as a group can get something together…?)
- I REALLY WANT to see a better sample handling within the DT*
( i had the DT now for years ! I can overlook its value and functionality vs. other Gear i have or what is availbale on the market. ( having also a OT mkII here, …unused)
it would be a good spent 50$ or 100$ to me.