Jump to content

sonofprent

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by sonofprent

  1.  
    My initial impressions are that this is loads better than before- Very nicely done indeed! :)
     
    Yes, I read it, and think it makes sense to change the behaviour, so that incoming CC values will also be stored in the edit buffer.

    Only value changes caused by ModWheel, Velocity, Aftertouch, Knobs and Wavetable shouldn't be stored.

    It will be an option which is enabled by default (because I guess that most people will like it), and could be disabled in setup_*.asm (for the minority who doesn't like it).

     

    In addition, I will add a "CC dump request" which will allow to synchronize a MBNG with the current patch CCs.

     

    Behaviour of SHIFT button will be configurable as well, and switched back to the original "slow" switching like in pre-42 releases.

     

    Back to topic: help to find best matching speed parameters, please! ;-)

     

    Best Regards, Thorsten.

     

    Not to pester but Just wondering if you also added this option to that firmware build? (just in case I missed it!)

     

     

     
  2. Yes, I read it, and think it makes sense to change the behaviour, so that incoming CC values will also be stored in the edit buffer.

    Only value changes caused by ModWheel, Velocity, Aftertouch, Knobs and Wavetable shouldn't be stored.

    It will be an option which is enabled by default (because I guess that most people will like it), and could be disabled in setup_*.asm (for the minority who doesn't like it).

     

    In addition, I will add a "CC dump request" which will allow to synchronize a MBNG with the current patch CCs.

     

    Behaviour of SHIFT button will be configurable as well, and switched back to the original "slow" switching like in pre-42 releases.

     

    Back to topic: help to find best matching speed parameters, please! ;-)

     

    Best Regards, Thorsten.

     

     

    That's fantastic, thanks muchly Thorsten! I'll look into doing some speed tests once back with the SID next week- in theory anything that does the full range in a single turn is what I'd like, though others who have tested may find something that works better, in which case I will bow to their superior judgement!

     

    Thanks again for this, great stuff indeed! 

  3. I don't know if you caught my post on this or would consider it an improvement but how do you feel about removing the 'non destructive' external CC thing- ie you can save changes after externally tweaking CC's. Thanks for looking at the encoder speed btw- I think the new approach (shift for slower) will be much more useable.

  4. I can see the logic in those situations, though I think it would have been better implemented if say velocity, pitch bend and mod wheel weren't saved and everything else was- I can't see the bonus in being able to control everything but not save it. That said it isn't the end of the world.

     

    I've still not tried the encoder thing- realistically wont get round to it for a while.

  5. It seems i may have stumbled upon a semi-completed ml303 v4. since the project has now been discontinued and the website shut down, i was wondering if anybody on here may be able to help with diagrams/schematics, eprom software and any other information that may be about? Any help would be greatly apprciated.

    help me breathe life into this sleeping beauty?! ;)

×
×
  • Create New...