-
Notifications
You must be signed in to change notification settings - Fork 105
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
CLAP 1.2.3 #432
CLAP 1.2.3 #432
Conversation
773e346
to
069d784
Compare
* Add a description of the expectation of request_callback timing Without making a requirement, indicate the intent of the timing. * Add an apostrophe * Add host can starve feedback from alex * more review feedback * notjusthosts
per conversation on discord, oct 29
fc4a9c3
to
ab54bc5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some comments on the location extension.
LGTM also. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some questions and suggestions regarding the location extension
How much information should a host provide to a plugin through the location extension? Should it provide all the information it can, or only information about the plugin itself? |
I'm not sure I understood well your question. Think that you have a very large project, all you need to know your location is: Here from the root track group, take the third track, then the 6th device and here we are. Does that clarify the question? |
comment refered to a previous version of the ambisonic extension.
I've squashed some changes to the scratch-memory for |
@abique
Okay, I was assuming that since the location API allows the host to tell the plugin its index within a parent element (i.e. in your example, the device is on the 3rd track), it could also provide information about other parts of the project structure which are not directly related to the plugin itself. For example, if a plugin is the 2nd effect in an effects chain, could the location API provide information about the effects before it and after it in the chain? I was assuming it could, since I don't see what the purpose is in telling a plugin it is the 2nd effect in the chain if it cannot also know what devices are the 1st and the 3rd. But if I'm wrong about that, as it seems that I am based on your comment, that would explain my initial confusion about how the location API is supposed to provide that information. All location information would be as simple as your example - it can only provide the minimal amount of information needed to identify a device's location within the project tree, similar to a filesystem path. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should the undo, scratch-memory, location, and gain-reduction extensions be listed in the README alongside the other extensions?
I had suggested on discord and I think alex agreed that
If 'display' bugs people then |
Maybe I like |
We can wait for those to be stable. |
include/clap/events.h
Outdated
@@ -266,6 +271,12 @@ enum clap_transport_flags { | |||
CLAP_TRANSPORT_IS_WITHIN_PRE_ROLL = 1 << 7, | |||
}; | |||
|
|||
// clap_event_transport provides song position, tempo, and similar information | |||
// from the host to the plugin. There are two ways a host communicates these values. | |||
// In the `clap_process` structure sent to each processing block, the host must |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wrote must here, and I think that's right, but lets all be sure that we don't want a null transport in process to be valid. If a null transport in process is valid we should change this to 'may'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or maybe 'may and is strongly encouraged to'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Transport is allowed to be null in the process struct, because some hosts may not have a transport, for example a mini host that runs a distortion effect in a guitar pedal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Corrected in #443
ab437e3
to
7087e88
Compare
I just saw this comment. Either way is fine with me, if you have a preference I'm happy to change it from the current gain_adjustment_display to gain_adjustment_reporting. |
After our (painful, long) conversation yesterday I think the best name is |
the conversation was painful and long because of me, by the way! Again sorry for that but I think we got a better result for it :) |
basically expand some comments around ranges, meaning, and so on.
05fc5ff
to
406a11c
Compare
Co-authored-by: Dalton Messmer <[email protected]>
added zig bindings to language bindings section.
Co-authored-by: Alexandre Bique <[email protected]>
No description provided.