In this stage we see too many possibilities, too many ways we can walk. That's normal.
- A good idea is to keep on swimming in this chaos for a few days and then try to decide on some things and ordering everything in our minds.
- We discussed a while on realtime issues and complexity issues:
Following Toons' opinion there are two extremes for us. I made a little figure of them:
The first one shows the most difficult one: extracting information from the signal upon which we want to apply the effect.
The second one is complexer, but easier. Here we have the whole spectrum of chosen tracks we want to use to extract different features from the music. Best is to use them all at once as an input, then the algorithm can choose the tracks it needs for the solution. This feature vector is then used as an input for effects that are applied on different tracks of choice (not necessarily the same tracks that are used as input for the feature extraction.)
-28feb2007-
There is another well defined extreme I thought of: It's like the second idea, but using only the master tracks as an input for the extraction algorithms. This means you have your 'intelligent effect box' and you plug into it a stereo mic or the outputs of the stereo masters of the mixer. The algorithms have to segment the music then or at least they have to do their thing without knowing specific knowledge about the input. They must be able to deal with noise from the public. This is a problem we won't handle. - I talked also a lot about the interface of the effect blocks and extraction blocks. Probably the best and only choice is to use a modular structure. But in that case I want to have as soon as possible a standard interface.
- We will never reach the stage where we implement the effect in C or something like that, the farthest we'll get might be simulink (modular and realtime). It might be the right time to switch to simulink sometimes already.
- Obviously I forgot a lot of details here... someone?
No comments:
Post a Comment