Xem Posted December 9, 2011 Report Share Posted December 9, 2011 Hello, i built a MB-6582.. I have a problem about the encoders sesibility.. they have a step of about 10 units. With an half turn i pass all the range of the filter. so half turn of the encoder equals to 255. i've seen this video: and it seems that the behaviour of my MB-6582 is not normal. Am i wrong? Is there a way to change the encoders sensibility? Thanks! Quote Link to comment Share on other sites More sharing options...
jojjelito Posted December 9, 2011 Report Share Posted December 9, 2011 Did you get the prescribed encoder component? Some other encoders are 12 detents per revolution, some 16, 20, 24, 48 etc. If you get a 48 steps per revolution it might explain your observation. Might be worth checking out. Quote Link to comment Share on other sites More sharing options...
Xem Posted December 9, 2011 Author Report Share Posted December 9, 2011 (edited) maybe i did the wrong choice, i do not remember.. is there a way to fix the problem via software? Edited December 9, 2011 by Xem Quote Link to comment Share on other sites More sharing options...
Hawkeye Posted December 10, 2011 Report Share Posted December 10, 2011 (edited) Are you aware of the input accelleration? If i do a quick half turn of the cutoff encoder, it will approximately change half the cutoff range (eg from 000 to 800), if it is done slowly, single-step increments are possible and i can turn "forever". Also note, that when you press "Shift", while turning the knobs, it will go into constant-slow (unaccellerated) mode. Maybe this helps. Not that i had looked into it, but with a recompile you can surely change the accelleration behaviour of the encoders, if it is too fast... Edited December 10, 2011 by Hawkeye Quote Link to comment Share on other sites More sharing options...
jojjelito Posted December 10, 2011 Report Share Posted December 10, 2011 Whoa! How did I miss that? Strange, just never thought of it. Must go observe it. Quote Link to comment Share on other sites More sharing options...
Xem Posted December 10, 2011 Author Report Share Posted December 10, 2011 If i do a slow slow half turn it do all the range (FFF).. If i press shift it takes 1 turn and half.. even if it turn it fast.. so.. what can i do? Quote Link to comment Share on other sites More sharing options...
Hawkeye Posted December 10, 2011 Report Share Posted December 10, 2011 (edited) depends on what you want... you could patch the software to assume constant "slowness" like the shift button is always pressed, but this would require some software assembly work, or exchange the encoders against the recommended encoders: but this would require some hardware assembly work :twitch: Greets, Peter Edited December 10, 2011 by Hawkeye Quote Link to comment Share on other sites More sharing options...
Xem Posted December 10, 2011 Author Report Share Posted December 10, 2011 i prefer do it via software =D, but.. can i assume constant "slowness" and when i press shit assume constant "Slow slownes"? i just ask this because i think there is a constant numeber of tic of the encoder to let trigger the encrease of the value, so if there are mechanical vibrations, recognized by the encoder as value entrease, nothing should happen. this constant seems to be multiplied by 3 when i press shift. I assume this looking at the sidv2 as a black box. I have the source, but i don't know what to search for.. And so on... i do not have tools to compile it.. is there a kind of guide? Quote Link to comment Share on other sites More sharing options...
Hawkeye Posted December 10, 2011 Report Share Posted December 10, 2011 (edited) i am not sure if you can get any slower than when shift is pressed in software - maybe your encoders are just "too quick"... maybe you are also using the wrong "encoder type", which can be changed via a recompile... to do that... well, you need to get the MIOS8 compilation toolchain up and running, but it takes some time and is a bit complicated... start reading here: http://www.midibox.o...n_development[]=toolchain then here: http://www.midibox.o..._toolchain_core then read a bit on encoder types: http://www.midibox.o...p?id=encoders[]=encoder&s[]=types then look in the assembly "config" file for the mb6582, where you can adjust encoder types: http://svnmios.midib...82.asm&peg=1024 If you manage to compile your mb6582.hex file in a "legitimate" timeframe, you can play a bit around with those, maybe choosing another type will improve the situation ... on the other hand, a set of new encoders is less than 30€ on mouser, and it will probably be quicker and more cost-effective, if you consider your time spent... Edited December 10, 2011 by Hawkeye Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.