Julian Rohrhuber
Julian Rohrhuber
Wouldn't it be more useful if you could query SuperDirt what samples it has actually loaded, and what synths are available? It would be relatively easy to do this.
@ndr-brt yes, exactly – this would be the issue to discuss and then solve it in the most general way.
Or, actually, these are two somewhat related issues: - a way to query the current sound library ([#199](https://github.com/musikinformatik/SuperDirt/issues/199)) - a way to query the harddrive for sounds to load into...
How does this integrate with the `asOSCArgEmbeddedArray` and `asOSCArgArray` interface?
Just to think this through in context: we have then three messages: - `asRawOSC` - `asOSC` - `asOSCArgEmbeddedArray` It would be good if: - the semantics would work together well...
Ah yes, that makes sense. What do you use it for? Maybe the use helps to find the right name.
Also, the `*newFrom` interface is connected to the `as` method. E.g. because there is `Dictionary.newFrom(collecton)`, we can write `[1, 2, 3, 4].as(Dictionary)`. > Could we create a subclass class of...
> Maybe I could rename it to `parseOSC`? There is at least a precedent with `String.parseJSON` and `String.parseYAML`. Yes, that is now much clearer, thanks! > I'm relaying OSC messages...
I had thought your addition may be a good occasion to improve the documentation by an example, but yes, if this is not easily possible, I won't object of course!
For some reason I never saw this note, @thgrund sorry!