Re: Is still someting going on here? Any dev-activity?
Posted: Sep 25th, '16, 09:55
obviously there's a lot of things needed just to recode the basic foundation for a new sequencer
- get rid of the arduino stuff (well, that's me, i don't want to use that stuff)
- start a new project, figure out how to initialize the cpu IO (this can be borrowed from the existing FW)
- code for dealing with shift-registers (for LEDs and buttons) - i already got these from my x0x FW so i can just use em
- code for dealing with the i2c eeprom - this i'd have to figure out, since i2c isn't my fav
- code for interrupt-driven, buffered MIDI input output - i can borrow that from my x0x FW too
- figure out how the cpu controls the actual instruments
that's gonna have to be done regardless of what direction the actual sequencer will go (authentic or not)
from there, it's all specific
one very important thing to figure out is the pattern structure
that depends on how the sequencer works, and that requires chosing what features we wanna have in it
i've done an approximation of the 303 sequencer, without actually having seen a real 303
so i know what it takes to do it ... it's basically "black box" modeling
and it can be done, with enough effort, patience, and collaboration
to do it for the 808, it'll take:
- someone who *knows* the behavior of the 808, to answer all kinds of questions, both in the big picture but also about small details
- someone who has an 808 and can perform specific tests (black box modelling, remember? )
- figure out what are the differences between the 808 and the yocto and whether that would cause a problem with the sequencer approximation ...
- decide what extra features can be squeezed into the yocto without destroying the authenticity of the 808 sequencer, and without those new features looking like aliens in the workflow
- figure out the pattern structure, and any other memory structures (tracks? )
once these things are solved we can begin building the big picture for how the interface should look like (a diagram will help here, or just anything that looks like a map, or even plain text)
and at that point, things will be very clear and the sequencer can be implemented
- get rid of the arduino stuff (well, that's me, i don't want to use that stuff)
- start a new project, figure out how to initialize the cpu IO (this can be borrowed from the existing FW)
- code for dealing with shift-registers (for LEDs and buttons) - i already got these from my x0x FW so i can just use em
- code for dealing with the i2c eeprom - this i'd have to figure out, since i2c isn't my fav
- code for interrupt-driven, buffered MIDI input output - i can borrow that from my x0x FW too
- figure out how the cpu controls the actual instruments
that's gonna have to be done regardless of what direction the actual sequencer will go (authentic or not)
from there, it's all specific
one very important thing to figure out is the pattern structure
that depends on how the sequencer works, and that requires chosing what features we wanna have in it
i've done an approximation of the 303 sequencer, without actually having seen a real 303
so i know what it takes to do it ... it's basically "black box" modeling
and it can be done, with enough effort, patience, and collaboration
to do it for the 808, it'll take:
- someone who *knows* the behavior of the 808, to answer all kinds of questions, both in the big picture but also about small details
- someone who has an 808 and can perform specific tests (black box modelling, remember? )
- figure out what are the differences between the 808 and the yocto and whether that would cause a problem with the sequencer approximation ...
- decide what extra features can be squeezed into the yocto without destroying the authenticity of the 808 sequencer, and without those new features looking like aliens in the workflow
- figure out the pattern structure, and any other memory structures (tracks? )
once these things are solved we can begin building the big picture for how the interface should look like (a diagram will help here, or just anything that looks like a map, or even plain text)
and at that point, things will be very clear and the sequencer can be implemented