If you have a problem or need to report a bug please email : support@dsprobotics.com
There are 3 sections to this support area:
DOWNLOADS: access to product manuals, support files and drivers
HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects
USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here
NEW REGISTRATIONS - please contact us if you wish to register on the forum
Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright
Last Poly Voice Extractor
-
trogluddite
- Posts: 1730
- Joined: Fri Oct 22, 2010 12:46 am
- Location: Yorkshire, UK
Re: Last Poly Voice Extractor
I've just uploaded a new version of the "last voice extractor" to the top post. This should fix the problem which Adam pointed out regarding the "doubled up" notes (thanks again!), and it shaves a few more CPU cycles off the code.
For anyone who's interested, the problem was a silly oversight on my part. The module relies on there being a memory buffer shared by all blocks of four SSE channels, which a 'mem' doesn't usually do (each block of four gets a duplicate at a different address). The fact that it was always the fifth note which caused the problem was the big clue. This is now sorted - my latest favourite toy, the "Ruby Frame buffer", ensures that the address is truly shared across all poly SSE blocks. I also recalled that the sample counter is reset to zero for every note-on in an SSE block, so most of the code is now hopped over the vast majority of the time.
For anyone who's interested, the problem was a silly oversight on my part. The module relies on there being a memory buffer shared by all blocks of four SSE channels, which a 'mem' doesn't usually do (each block of four gets a duplicate at a different address). The fact that it was always the fifth note which caused the problem was the big clue. This is now sorted - my latest favourite toy, the "Ruby Frame buffer", ensures that the address is truly shared across all poly SSE blocks. I also recalled that the sample counter is reset to zero for every note-on in an SSE block, so most of the code is now hopped over the vast majority of the time.
All schematics/modules I post are free for all to use - but a credit is always polite!
Don't stagnate, mutate to create!
Don't stagnate, mutate to create!