Giter Site home page Giter Site logo

yocto_808's People

Contributors

homoelectromagneticus avatar rv0 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

yocto_808's Issues

Decide on coding style

The current source code is a mix of different coding styles.. This does not help with readability.
for example we have:

bla() { 
  // code
}

and also

bla () 
{
  // code
}

Not to mention very inconsistent use of spaces

I'd love to do a quick automated reformat of all the code at once, but I don't want to make the decision on my own. Personally coming from a PHP past, the first way is more natural to me, but I think generally the 2nd is used more for C code.. What to choose?

Slaving to external MIDI Transport messages, then going in Edit mode, stop from external and not sending any external tempo anymore and press Start button make the sequencer unable to be internally clocked anymore in Pattern Play mode.

Sorry for the long title.

It seems related to a behavior/feature? that when having slaved the sequencer transport from an external MIDI Clock with the MIDI Slave mode, the Edit mode becomes slaved to the external MIDI Clock and pressing Start, Stop and Start again doesn't reset to the beginning of the pattern but continue where it stopped, as if it was a MIDI Continue message.

Personally I can't see the benefit of this and if it's a feature, I can't see why it's not available when using the internal clock. So I would suggest to get rid of it as it can produce the simili bug mentionned in the title.

EDIT: even more annoying when having Edit mode becoming slaved to external MIDI Clock and pressing Start and Stop, then sending a Start message from an external source... it will also act as continue. So it's more like that in Edit mode while clock is being slaved to external MIDI clock, the Stop button will act as "pause".

Track mode needs (sync) rework

While the pattern modes have been updated and contain a completely new way of doing sync, the track modes were left untouched. This will lead to unexpected behaviour and possibly bugs when switching from Pattern to Track or Track to Pattern.

Stop bar follow when length > 16 steps

Hi.
It's quite annoying to have the pattern follow the bars/steps when it's longer than 16 steps. It is quite difficult and annoying trying to enter the correct steps.
Would be great to have this feature disabled by default and enabled with some key combination.
Thanks for looking into this!
Flavio.

[Expander mode] BD sound change if it's not the only one triggered at a time

Try to send a sequence to the Yocto in expander mode in which the BD sometimes is alone and sometimes is triggered at the same time as another instrument. Then keep only the BD volume turned on, you should hear that its sound changes depending if it's triggered alone or not.

Also it can be noted that the Accent slot can also be set up to be triggable by an external MIDI note but this won't produce any result, while will still impact the issue described above the same.

No error handling on communications with the I2C EEPROM

Currently, no error handling exists for communications between the Yocto's EEPROM and micro. This means that if the ATMEGA1284 gets an unexpected NAK from the EEPROM, or if the ATMEGA1284 receives fewer bytes during a sequential read than it expected, stuff breaks and the user has no idea that something has gone wrong.

Even the most basic error handling (re-trying, etc) would be useful here.

Trigger 2 does not work

Trigger 2 is not outputting standard V-Trig pulses per the Yocto's original specification. At first glance, the Trigger looks more like the "S-Trig" standard. What's worrying is that the output pulses are not correlated to what's programmed into the Trigger 2 pattern. The exact behavior is a bit different when the Yocto is in different modes, which points to a software problem. Additional discussion at http://www.e-licktronic.com/forum/viewtopic.php?f=17&t=1519.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.