Re: Official Yocto BUGS list
Posted: Sep 19th, '17, 18:12
http://antonsavov.net/cms/projects/n0nx0x2.html
this.. an approximation of the 303 sequencer for the x0xb0x
a closely-related project which also needs a lot of work (by poor me) is c0nb0x
and i have a bunch of unfinished VST plugins sitting around staring at me, and bags of ideas..
another idea that sits and gathers dust is my attempt to make the yocto "internal PSU mod" external, so that i can safely stick my hands into the box without any chances of getting zapped by 230VAC
anyways..
the discouragement comes because i'm pretty sure that the people who i hoped to get involved into a discussion about a new firmware rewrite (mostly users) will now sit and wait for firmware fixes by two or three other developers, thus they are not likely to care about discussing ideas for a firmware which will take much longer to become a usable reality
i have no idea when (or if) the moment will come when i can work on a yocto firmware
but if that moment comes, if i have no better plan - i will probably attempt to make a "personal rewrite", starting from scratch and just writing code chunk by chunk without having a good idea what the end result would be like.. and this will probably be a bumpy ride and might not reach a usable state at all and get burried in dust
this.. an approximation of the 303 sequencer for the x0xb0x
a closely-related project which also needs a lot of work (by poor me) is c0nb0x
and i have a bunch of unfinished VST plugins sitting around staring at me, and bags of ideas..
another idea that sits and gathers dust is my attempt to make the yocto "internal PSU mod" external, so that i can safely stick my hands into the box without any chances of getting zapped by 230VAC
anyways..
the discouragement comes because i'm pretty sure that the people who i hoped to get involved into a discussion about a new firmware rewrite (mostly users) will now sit and wait for firmware fixes by two or three other developers, thus they are not likely to care about discussing ideas for a firmware which will take much longer to become a usable reality
i have no idea when (or if) the moment will come when i can work on a yocto firmware
but if that moment comes, if i have no better plan - i will probably attempt to make a "personal rewrite", starting from scratch and just writing code chunk by chunk without having a good idea what the end result would be like.. and this will probably be a bumpy ride and might not reach a usable state at all and get burried in dust