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
fixed: broken rfft implementation used in audio visualizer api #7047
Conversation
this replaces it with a working version using kissfft
I would be thankful for PR of the relevant project updates we need. |
…was missing an include
how about moving this to depends as @wsnipex volunteered to do this? |
All in favor for doing it, if it makes things cleaner. Thanks in advance @wsnipex |
if we move to depends we'll have to redo the VS parts but it's simple enough so I can take care of that part |
yes thx in advance to whoever moves it to depends :) |
had a quick look at it and now I'm doubting the benefit of moving to depends. The lib is ~4 files, but the changes needed to move it to depends will be roughly the same :)
|
maybe we should go for fftw then. this is available on the various Linux distros, and also available as pre-built for Windows. |
I think we should just merge it as is. Its not very likely that this lib will change. |
no need to rush. we are going to use fftw anyway in addons. there have to be a really good reason for going with kiss and breaking the strategy of getting rid of libs folder. |
One point for kiss is: I understand the code and the algorithm it 2015-05-03 11:21 GMT+02:00 Rainer Hochecker notifications@github.com:
Fingerprint: 4606 DA19 EC2E 9A0B 0157 C81B DA07 CF63 1A99 5A9B |
we could also add the sources of kiss to some "contrib" folder within the xbmc project files. |
@FernetMenta isn't that what the lib folder basically is? |
Nope, why crating a lib here? Those two files could be added to the project without compiling a lib and link it statically to the app. Adding an additional VS project is really bad for those 2 files. |
They could be added into main project. i chose this method to maintain a clean separation between our code and 3rd party. The project is statically linked so end result is the same. |
On windows all works very well :) I will use fftw in my GSoC proposal for my xconvolver addon. So we will see how good it works. |
http://www.fftw.org/install/windows.html <- First two sentences. |
agree with @FernetMenta - we should add some sort of 3rdparty folder and can add those source files directly to the xcode and vs project files (and the makefiles of course). No need to tinker with libraries in that case. |
+1 on moving it to contrib and directly using the files. |
That's true, but I think they don't wanna support Windows :) kiss FFT Readme ;)
There is also some support for SIMD in kiss FFT. As conclusion we need both :) |
@fritsch mind if i replace this PR with this one here: https://github.com/Memphiz/xbmc/commits/kiss_rfft (which basically split the commits properly and moved the source to xbmc/contrib/kissfft) Also @notspiff how can i test this - i tried all viz i have (windows and osx) but not a single one wants freqdata (so fft isn't called for any of them). |
Use nastyfft from my gits. |
@Memphiz you are welcome. THX much.
|
this replaces it with a working version using kissfft
This is a follow up of: #7039