Feature request: extract XYZ data metadata

[griffinboy]

@griffinboy
@Christoph-Hart
@DanH

Sorry to bother you! Important! : )

[Christoph Hart]

@griffinboy sorry I'm on vacation right now so my ability to write code is limited.

In order to load a sample map dynamically, you can use the {XYZ::SampleMap} wildcard, followed by the samplemap ID (without the .xml extension). So if your samplemap is called Piano.xml, then the string you pass into loadFile() is "{XYZ::SampleMap}Piano".

so that as we load in a samplemap into the c++ sampler node, we can set the loop point parameters correctly.

Remind me again, what's the problem with the loop points? They should be passed on correctly with the sample start applied to the range already, no?

[griffinboy]

@Christoph-Hart

edit This issue is solved. Read my message below this post.

---

okay the issue is that when we load a sample map into the c++ sampler, we need the Loop metadata to set the Loop Parameters of the c++ node.

Sure, I can just load in a sample map and internally use the loop values, the result will sound correct. However, the actual parameters will be in the wrong locations.

[griffinboy]

@Christoph-Hart

Update

You can forget it! Client decided that they didn't need this feature. Thanks for your help thus far. I no longer need to solve this!

[DanH]

@Christoph-Hart client was me

[DanH]

@Christoph-Hart is there a way to extract the volume info from sample maps for a c++ sampler?

[Christoph Hart]

@DanH Ideally it would be baked into the buffers directly but I don‘t think I‘m doing that already.

[DanH]

@Christoph-Hart it would appear not

[Christoph Hart]

@DanH weird actually it should factor in these properties already, including the loop xfade:

https://github.com/christophhart/HISE/blob/61b6f7467eaa51fbad7a9bad60adbcc4d73204ad/hi_core/hi_sampler/sampler/MultiSampleDataProviders.cpp#L217

Let me check if that's the case and if not why it skips that code.

[Christoph Hart]

so:

the function is indeed called when loading a samplemap and

• volume
• pan
• pitch

is correctly applied to the buffers, I haven't tested the range properties but they should work too if the other ones are processed.

Are you sure that this is not something else on your side?