Apologies. The tone was rude and not called for. Plus I know it's sure way not to get what I asked for. Geist is a decent product, Fxpansion. Just was getting frustrated.
These days I am more so focusing on an efficient workflow and reproducability (mispelled). I want to move across Guru, Geist, and Maschine and DAWs in the most beneficial way as to not stifle my creativity.
I got a new PC system built. Although I had to convert over a lot of DAW projects (e.g. Sonar 8.5 to Sonar X1, X2, etc). 95% of my conversion time was spent trying to manually search and find all of the samples that a GURU .gru or .kit was looking for. At potentially 16 pads x 8 layers x 8 engines for one .gru, this was gruesome. It took me over 6 months to convert all of my projects that contained GURU over to work properly again.
So I bought Geist a few years ago and sat on it, thinking that I would install it and replace GURU once my requested features and bugs were worked out. Meanwhile, when I saw this wasn't happening, I moved and invested in Maschine and BPM. I bought Maschine for the browser, sample tagging, and VST support, and heavy development support path. I bought BPM just to rip the samples into Maschine and perhaps Geist.
Fast forward, I finally installed Geist last night and started investigating moving GURU based projects over to Geist. While auto search is available in Geist, I still had no idea where to start looking for samples due to no expected path estimates being shown. So I took this for granted and then just decided to try and least load some .gru songs (letting Geist search my whole PC for samples). I walked away and came back an hour later, only to play the loaded song and hear it not play properly. Most of the engines samples were not playing. And for samples that were chromatically assigned to pads in certain former GURU engines, they would not play at all in Geist. I loaded several other GURU songs and proved the same. --> So I came to the conclusion that eliminating GURU was no longer an option since I literally had 100's of tracks that used GURU as my main drum/sample backbone. -->
Then after I loaded Geist presets (equivalent to Guru songs), and had no indication of what was loaded (no name listed anywhere in the GUI), this turned me off a little more. After spending months just trying to get GURU songs to work on a new PC, I was not going to go through this again with Geist. Hence the unnecessary outburst.
In a perfect world, if I could mash together Maschine's browser, and sample tagging, vst support, with Geist's graph and sample FX editing, I would. Although I may potential still use Geist on a limited basis. I am going to investigate how I should build my future kits and songs.
1) Build up kits, either natively in Maschine, then export tracks to Geist only in cases where I need to use graph manipulation on tracks, while running Geist as a plugin in Maschine.
2) Continue to use GURU for its kit name and song name listing functionality to build/load kits --> and then re-sample the "Best of" my library into Maschine for goto GURU favorites. I've already also spent about a month converting all of my DR-008 kits over to Battery since this product was phased out. It had a good run too.
Too bad Maschine's kits aren't in XML like GURU's were, because I could've easily written Python scripts to generate a rudimentary GURU Kit --> Maschine Kit converter and been done.
Anyhow, Geist is a great product nevertheless. Just tired of revamping my studio everytime a producted phases out, etc. I am now reluctant to make Geist my drum sequencing backbone like GURU. So now I am evolving to invest in more longevity- based solutions so that I can get back to production and away for system adminstration. Word to the wise, never put all of your eggs into one basket as I did.