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

Allow processing in blocks #250

Open
superbock opened this issue Feb 13, 2017 · 1 comment
Open

Allow processing in blocks #250

superbock opened this issue Feb 13, 2017 · 1 comment

Comments

@superbock
Copy link
Collaborator

Right now, madmom supports two basic processing schemes, online (causal) and offline. The former only requires past data, whereas the latter needs the whole sequence/signal to be present at once (e.g. Viterbi decoding or bidirectional RNNs).

When processing is purely online or requires only a certain context, it could be computed in blocks. Thus it would be great to have a block_size parameter added to process() methods. E.g. it can save a lot of memory (and can be faster, too) to process everything in blocks of 2048 frames instead of whole length pieces.

@worldveil
Copy link

Curious if this is still an issue? It seems like some processors, like the RNN beat tracker have an online mode, but many data processors, ie: spectrogram difference, don't. I do see the use of FramedSignalProcessor, does this enable the paradigm you're suggesting or are there still missing usecases?

Otherwise, I assume the prescribed way to go about block processing is just to window / frame the signal yourself and do it that way

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