"FFT DLL" module:
Parameters:
i n p u t s
Size 512,1024,2048,4096?
Active 1 or 0
WindowType 0 to max 161 Hamming...
VoltageReference -2147483647 to 2147483647
AverageCount number to count until output
Peakhold fallback millisecconds ?
PeakReset 1 or 0 ?
ExponentialAverage
StartBand ?
EndBand ?
PeakCorrection ?
KAiserWindowFactor ?experimental
AverageAudioPeak
dBDisplaymode 12 24
Calculate2ndFFT trigger? way for inverse FFT?
o u t p u t s
EnergyPeak1
EnergyPeak2
PeakFreq1
PeakFreq2
RMS
RMS2
THD+N
THD+N2
AudioPeak
AudioPeak2
FFTOutput real and imaginair?
If you feel like it , could you please copy this list and correct or fill it in were possible. I'm trying to collect more detailed information on certain SDK modules.
Regards,
Casper
<font size=-1>[ This Message was edited by: Casper on 2005-01-05 08:42 ]</font>
<font size=-1>[ This Message was edited by: Casper on 2005-01-05 08:43 ]</font>
<font size=-1>[ This Message was edited by: casper on 2005-01-29 17:53 ]</font>
PlanetZ SDK MANUAL ( FFT DLL )
-
Shayne White
- Posts: 1454
- Joined: Tue Dec 11, 2001 4:00 pm
- Location: California
- Contact:
Well 67 views but nobody knows anything ??
I find that hard to beleave.
I'm beginning to think the creamware users are being devided into two camps.
The ones that share information and gladly help another person. Likely using SDK
The ones that only think of there DP money investment , and share no information what so ever.
I'm getting sad about this. I'm not asking for free devices , mearly trying to understand the SDK , and it's poor manuals.
I'm investing my free time and trying to share information in this forum. But if no one takes any effort in reakting, this forum is useless.
I find that hard to beleave.
I'm beginning to think the creamware users are being devided into two camps.
The ones that share information and gladly help another person. Likely using SDK
The ones that only think of there DP money investment , and share no information what so ever.
I'm getting sad about this. I'm not asking for free devices , mearly trying to understand the SDK , and it's poor manuals.
I'm investing my free time and trying to share information in this forum. But if no one takes any effort in reakting, this forum is useless.
maybe you got lost a bit by the overwhelming amount of new stuff ?
at least the question above and the one about pointer arrays indicate in this direction
that dll is in no way SDK specific. It's a regular part of SFP and native CPU code. The DLL is (to be) called with the usual parameter passing of the items you ask about.
If you don't know what to fill in or expect (as return) from several of the fields, you just dunno what a FFT is about, so why bother ?
In case you want to study FFT in depth there's certainly a ton of commented code examples in the Open Source scene.
I didn't answer the 'pointer array thread' because the reading alone made me shudder with disgust. But since we're at it...
A pointer is a endangered species in itself and pretty lost (or useless) in heavily memory managed 'modern' operating systems. Hence it once (>20 years ago) got a companion standing on safer ground (locked) and the two were named 'the handle' gang.
Since dealing with items on that level is a true PITA the stuff was encapsulated and named after the real world items they were supposed to represent.
Now it became part of the programming language's library and with a little help from it's friend (called code) it successfully made it's way into an object and tried to rule the world...
Short story - sophisticated environments should completely prevent to deal with items on that level and supply appropriate methods.
I'd suggest to get a little distance from typical programming details in the context of SDK and first try to get an overall viewpoint about the system's basic strategy and capabilities.
Even if it's called a SDK it's in no way related to traditional programming languages.
It certainly cannot do all and everything, but some limits at first sight can be worked around - more or less smartly, once you get more familiar with it.
You may be surprised, but there's a rich source in Alfonso's modular devices regarding the strategy you need to apply to achieve a certain processing in SFP
Your experience so far is absolutely regular. Just because release cycles are five times shorter than 10 years ago, doesn't mean that productivity (or mental capability) has increased accordingly...
cheers, Tom
at least the question above and the one about pointer arrays indicate in this direction
that dll is in no way SDK specific. It's a regular part of SFP and native CPU code. The DLL is (to be) called with the usual parameter passing of the items you ask about.
If you don't know what to fill in or expect (as return) from several of the fields, you just dunno what a FFT is about, so why bother ?
In case you want to study FFT in depth there's certainly a ton of commented code examples in the Open Source scene.
I didn't answer the 'pointer array thread' because the reading alone made me shudder with disgust. But since we're at it...
A pointer is a endangered species in itself and pretty lost (or useless) in heavily memory managed 'modern' operating systems. Hence it once (>20 years ago) got a companion standing on safer ground (locked) and the two were named 'the handle' gang.
Since dealing with items on that level is a true PITA the stuff was encapsulated and named after the real world items they were supposed to represent.
Now it became part of the programming language's library and with a little help from it's friend (called code) it successfully made it's way into an object and tried to rule the world...
Short story - sophisticated environments should completely prevent to deal with items on that level and supply appropriate methods.
I'd suggest to get a little distance from typical programming details in the context of SDK and first try to get an overall viewpoint about the system's basic strategy and capabilities.
Even if it's called a SDK it's in no way related to traditional programming languages.
It certainly cannot do all and everything, but some limits at first sight can be worked around - more or less smartly, once you get more familiar with it.
You may be surprised, but there's a rich source in Alfonso's modular devices regarding the strategy you need to apply to achieve a certain processing in SFP
Your experience so far is absolutely regular. Just because release cycles are five times shorter than 10 years ago, doesn't mean that productivity (or mental capability) has increased accordingly...
cheers, Tom
Thanks for sharing your point of view Tom.
Your right about the beeing lost part Tom. But you mention the cause as well. I'm a AudioDesigner Student ,and am used to C++ programming. Therefore using names like "pointer" , even if it doesn't work this way in SDK. The fact you talked about "the handle" already helped me! Thanks. I't gave me another angle to look at this al.
The 67 views part was just to give a little encouragement to get a reaktion on my question. Bad method maybe , i'm sorry about that! My apologies.
Hope someday i become a Levitating Fire-Breathing Pulsar Overlord
Greetings
Casper
Your right about the beeing lost part Tom. But you mention the cause as well. I'm a AudioDesigner Student ,and am used to C++ programming. Therefore using names like "pointer" , even if it doesn't work this way in SDK. The fact you talked about "the handle" already helped me! Thanks. I't gave me another angle to look at this al.
The 67 views part was just to give a little encouragement to get a reaktion on my question. Bad method maybe , i'm sorry about that! My apologies.
Hope someday i become a Levitating Fire-Breathing Pulsar Overlord
Greetings
Casper