Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get the list of used tracking parameters #59

Open
alkoow opened this issue Apr 13, 2023 · 2 comments
Open

Get the list of used tracking parameters #59

alkoow opened this issue Apr 13, 2023 · 2 comments

Comments

@alkoow
Copy link

alkoow commented Apr 13, 2023

Is there a way to get the list of tracking parameters that are used (aka mapped with a L2D parameter) in a model? If not, this information could be useful in plugins that manage many parameters.

For example, a query on Live2D parameters in the current model could be great:

{
	...
	"messageType": "Live2DParameterListResponse",
	"data": {
		...
		"parameters": [
			{
				"name": "MyLive2DParameterID1",
                                "mappedWith": "MyCustomParameterID1",
				"value": 12.4,
				"min": -30,
				"max": 30,
				"defaultValue": 0
			},
			...
		]
	}
}
@DenchiSoft
Copy link
Owner

There's currently the InputParameterListRequest and the Live2DParameterListRequest. Although neither of those will give you any information about existing mappings.

I'm not opposed to adding that information, but do you have any specific use-case for this?

@alkoow
Copy link
Author

alkoow commented Apr 17, 2023

I am developing a plugin to emulate "cycles" on Vtube Studio. Unlike auto breathing which goes back and forth between 0 and 1, cycles allow you to come back directly to the original point (when you reach 1, you come back directly to 0). You can also choose the step and speed of the animation.

The purpose of this plugin is to simplify the process of creating L2D models for riggers, especially for frame by frame animations. The philosophy behind this plugin is that one parameter for a given model = one specific cycle created.

That being said, if you have multiple models, this means that some cycles that are not used will still be processed. The idea behind this API enhancement is to control that by starting only cycles that needs to be used.

2023-04-17.19-17-36.mp4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants