SampleMaps and expansions issue.

[d.healey]

@CyberGen said in SampleMaps and expansions issue.:

Is that possible?

Not as far as I'm aware.

[CyberGen]

@d-healey

Not as far as I'm aware.

Oh no, that places a big limit on my project.

@Christoph-Hart, could I kindly request that you open this up?

I'm trying to have multiple independent sound sources that can load samples from all downloaded expansions, not just the active one. Ideally, all samplemaps should be available at all times.

Thank you.

[bendurso]

@CyberGen And what if you load the samples and samplemaps into the main plugin? Then you could use them in all the expansions I think.

[CyberGen]

@bendurso Yes, that is true. I had thought of that. But I would much rather keep using expansions if possible, It offers other advantages. I'd like to keep the ability to keep adding features/sounds/instruments through expansions to the platform as it grows (expands) over time.

[bendurso]

@CyberGen Maybe you could create a manual installer that always sends the sounds/samples to the main plugin, while everything else is treated as an expansion (images, presets).

[d.healey]

@CyberGen Not at my computer at the moment but do expansions have a getSampleMapList function? Perhaps you can use it to load sample maps from other expansions.

[Lindon]

@CyberGen you can load any sample map/expansion sample map .....I know its what I do in Horizen, so put your ch1 files in the LinkOS folder, and call the load with this string :

{EXP::YorurExpansionName}YourSelectedSound

....for cases where the sample map is in the expansion.

So for every expansion you will need to keep a list of the maps in that expansion, and when the user selects a map - check which(if any) expansion its in and use the above...

[d.healey]

@Lindon @CyberGen This one

[Lindon]

@d-healey yes - if you want a "bald" list - Im doing this however:

{
  "ExpansionName": "84 All Year",
  "Key": "Not Set",
  "Desc1": "80s reimagined ",
  "Desc2": "",
  "Image": "84expansion_small.png",
  "VoiceCollection": [
    {
      "VoiceMapName": "{EXP::84AllYear}84_Banger",
      "VoiceDisplayName": "84_Banger",
      "VoiceTags": [
        "84 All Year",
        "Keys"
      ],
      "DataFile": "84AllYear_exp.json"
    },
    {
      "VoiceMapName": "{EXP::84AllYear}84_Chimewars",
      "VoiceDisplayName": "84_Chimewars",
      "VoiceTags": [
        "84 All Year",
        "Pluck"
      ],
      "DataFile": "84AllYear_exp.json"
    },

etc. etc...

[CyberGen]

@Lindon @bendurso @d-healey Thank you guys, these are great suggestions. Much appreciated. I haven't had a chance to sit down to try to implement them yet. I'll let you know how these work out as soon as I give them a try.