Feature request: extract XYZ data metadata

[d.healey]

@griffinboy Ha you're impatient today

[griffinboy]

@d-healey

Yeah it's naughty of me

The timeline of this project I'm working on became really stretched, so now that I'm finally approaching the end I'm too excited to resolve the final barriers.

[Christoph Hart]

@griffinboy that's not so easy, the buffer that is passed with the ExternalData is already truncated with the sample-start and sample-end values. But why do you need this, just playback the part you want to play?

[griffinboy]

@Christoph-Hart

Wait, does the xfade get baked into the sound file then?

My client was hoping to take some sample maps that have already been created, and load them into a custom c++ sampler.

And then mess around with the loop points etc.

But if what you're saying is true, then I can't do that

[DanH]

@griffinboy @Christoph-Hart

[Christoph Hart]

Does your project really have different xfade values for samplemaps or can you just use a project wide constant for this?

[griffinboy]

@Christoph-Hart

I think we could maybe get away with having a default length.
Knowing the real loop start is important though, which I can't extract it seems

[Christoph Hart]

@griffinboy but the real loop start is correct in your first post, no?

[griffinboy]

@Christoph-Hart

Oh you're correct, because it's chopped off the start of the sample

[griffinboy]

@Christoph-Hart

Seperate but related question:

How does one load a samplemap (xyz) into a c++ node from hise script?
And can the hisescript read the sample map metadata?

I'm wanting the hise script to be able to read out the saved loop points, so that as we load in a samplemap into the c++ sampler node, we can set the loop point parameters correctly.

else I'll have to do a funny loop where we use global cables to send the loop points extracted from the xyz data inside the node, into hise, which then uses that info to set the parameters on the c++ node.

[griffinboy]

@griffinboy

@Christoph-Hart

Bump! Sorry