-
Notifications
You must be signed in to change notification settings - Fork 13
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
next step in documentation: samples #34
Comments
Most of things I learned by converting the c++ examples from the fmod
directory:
C:\Program Files (x86)\FMOD SoundSystem\FMOD Studio API
Windows\api\core\examples
…On Sat, Apr 10, 2021 at 3:34 PM Bart Van Loon ***@***.***> wrote:
After completing the API documentation in #33
<#33> , I'd like to add some more
user friendly documentation like how to get started, installation, etc...
Now, I'm a fairly new an inexperienced user of FMOD myself, so I was
wondering if others might perhaps want to share some (simple or advanced)
example code using the library here that I can incorporate in the
documentation?
That would be great. :-)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#34>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADCIHP3APCJQ34MH6VEAM4DTICR4XANCNFSM42W2J7QQ>
.
|
Ah yes, that's a good idea. I'll look into it. Thanks @marcelomanzo ! |
I'm stuck trying to implement the Here's what I have right now:
which results in a segfault. Setting the @tyrylu, or anyone else, do you have more experience with this? |
I doubt that there is anyone who tried this, but there are some obvious issues. The first are the null callbacks, they will cause a crash at some point (at least the required ones), then there's the param desc initialization, it looks really weird. I would likely do something like: |
Hey, thanks for your reply.
Ah yes, I can see that. However, because the problem goes away when
OK, I see. Let me try that. I reckoned it has to be a pointer to an array of pointers (https://fmod.com/resources/documentation-api?version=2.1&page=plugin-api-dsp.html#fmod_dsp_description shows
Not everywhere. I started doing that after I realised that that's what I got back when retrieving a
Ah, yes, that's a good catch. Probably the
Yup, got that done in the dsp_inspector sample I committed today.
Aha! OK, trying again tomorrow with a fresh mind. :-) Thanks a lot for the insights. I am already thinking about have an entire (thin) layer on top of |
ok, I haven't really made progress in terms of getting any further, but I do believe my understanding of the matter has improved somewhat. Here's a small non-working example, cleaned up keeping the latest comments in mind:
A strace tells me that the segfault happens on a I'm still out of ideas here. For the moment, I'm focusing on reimplementing the other examples from upstream. |
I still think that |
Hm, I don't think that's right:
The problem lies somewhere with assigning two parameter. The following works just fine:
as does this:
So, defining and declaring one of these parameters (either one) seems to work just fine. It allows me to inspect the However, as soon as I set So, progress of a kind, but still hitting this wall. Thanks a lot for your help. |
Alright, here's the current state:
As far as I'm concerned, this is ready to be tested on non-Linux platforms and then merged. I have worked with Python 3.9. I'll test the samples with 3.8 and 3.7 as well, but I don't expect any problems as I've tried to stay away from the most recent language features. |
Done. Nothing to report, all works fine. Just a note: py-flags states that Python 3.6+ users should consider using the Flag and IntFlag classes of the standard enum module. Those are very similar to the flags.Flags class. This could remove the currently only outside dependency of pyfmodex. |
Okay, i'll test the samples on Windows (likely Python 3.9), maybe discover why the dsp info example reports weird data. We, as it seems, likely require python 3.6 as the minimum supported version and drop pyflags altogether. |
That would be great.
yes. 3.[789] is fine for me. |
The samples PR is merged and pyflags is no longer required, so i suppose we can close this one? |
waw, nice. yes, I suppose we can, just need to check if the samples still work with TIMEUNIT moved from flags to enums (#37). |
ok, some minor changes needed to be made, all grouped in #39 - ready to be pulled |
After completing the API documentation in #33 , I'd like to add some more user friendly documentation like
how to get started
,installation
, etc...Now, I'm a fairly new an inexperienced user of FMOD myself, so I was wondering if others might perhaps want to share some (simple or advanced) example code using the library here that I can incorporate in the documentation?
That would be great. :-)
The text was updated successfully, but these errors were encountered: