n0ne

he doesn't get it quadroubled but doubled, would you know how that would be possible?

Yes, that is what happends! Argh that's a bummer. Would it be possible to double it then? Because these are the same encoders Luis uses on the KDJ and he mailed me that he get's a resolution of 72 with software. Would it be sufficient to change the mode to DETENTED (1)? Or will I have to do some additional programming. Thanks a lot... it's not a happy answer but at least I know what the problem is. Maybe I'll just get other encoders. Jeroen.

64e, with 32 pots, 60 buttons and 2 encoders. I'm sure I did not, I've made other changes too. (but also tried it with a clean copy of midibox64e) If you mean modes, no. And if not, I only have one kind of encoder. If I change my speed setting via the menu buttons to fast I get an increasement of 3 per pulse, I'll have to check what happends when I set it to slow... Will try... I got 72 lines with the MIDIIO128, when reading the encoder as buttons, when it's read as an encoder I get 36 lines. Another thing that has got me confused is when I look at the picture: http://www.ucapps.de/mios/mios_encoder_modes.gif, I see that the NON_DETENTED type uses the on AND off of both pin's, so this is the same as what I see while monitoring the output of MIDIO128. Since I got 72 lines there, and the NON_DETENTED picture as a quadrubled resolution I would think that indeed my encoder has a resolution of 18 instead of 36, TK are you sure that every on/off coulpe is one pulse? I hope it's clear what I mean :s. Jeroen.

Hi, With the MIDIO128 I get 72 lines in one turn, so that means 36 pulses. (and those are 18 from C and 18 from C#). So I could conclude that my encoders do send 36 pulses, but there's something going wrong at the firmware side. Does anyone know what might be going wrong? thanks, Jeroen.

That is very weird, I was told they have a resolution of 36, but I'll go and ask again. But it still doesn't explain the 36 pulses I get.

well they do work correctly, only the resolution is not quadroubled :s... so I guess they're connected correct. :(, thanks though, Jeroen.

then do you have any clue why it is nog working :s

Thanks, for the quick reply, I've got this: That's correct right? Jeroen.

Ok, I came up with some different sollutions, since the one first suggested by Luis didn't work. After I just tried something myself, wich worked, Luis also suggested that method to me. I'm not an assembler programmer, so if you spot a mistake I'll be happy to hear it! This is what works for me, It sends two different notes on, one for each way when turning. When you stop turning it sends them both off. Also, it sends a note off every time just before it sends a note on. This is so that traktor doesn't keep on increasing the pitch bend because it's stopped everytime. I haven't really tested it enough to see if this really works like that, but you could always remove the first 0x00 and call to MIDI_EVNT_SEND. I have only tested thisone with traktor 3, but I am pretty sure that is also works with traktor 2, also because Luis suggested it to me. Also there is the scratch function, wich I will be using soon in combination with a button. So when the button is pressed you can scratch, when it's not you can pitchbend. You have to assign the note of the scratch function to scratch on in traktor and the cc to the scratch itself (set it to incremental). This works pretty sweet :). This one both worked in traktor 2.6.1 and 3. and these are my timers It's still a bit messy... but I am still working on it. This is what Luis suggested me first, doesn't work for me, but please try so we can find out why :D: And then the timer also changes a bit (different midi values) I'm also nog happy about the pitchbend yet because: when you keep turning the encoder at the same (slow) speed the pitch bend keeps increasing, and that is not what I want. This is a problem of traktor because that is just what it does with the buttons. But I have already thought about a solution for this wich I will try soon and post it here too. Hope this is usefull for anybody, to all the future traktor midibox builders: scratching an pitchbending is possible with an encoder! Bye, Jeroen.

Hi guys, I already asked this in another topic in the MIOS forum, but didn't get an asnwer, so I hope that this is the right place to ask... in midiox I notice that my non detented encoder (ALPS EC11E1830401) only sends its original 36 pulses, in the mios specification it says something about making the resolution higher with the software. Why isn't this working? am I missing something? Hope someone has an answer since I didn't find it in the forum. Greets, Jeroen.

Hi guys! TK, thanks a lot for your input! Yesterday and today I invested a couple of hours in learning some extra assembler, and oh my g00d, I just went on and programmed it myself :D... pretty cool I think ;). Only problem is that traktor still doens't work correct, so I've mailed Luis from kdj again, and am awaiting his answer. I'll be sure to post my code when it works, so other people can use this function too, i guess it's something traktor users really need. A bit off topic but: in midiox I notice that my non detented encoder (ALPS EC11E1830401) only sends its original 36 pulses, in the mios specification says something about make the resolution higher with the software. Why isn't this working? am I missing something? Hope someone has an answer since I didn't find it in the forum. Thanks again TK!, Jeroen.

Ow and by the way... my idea for a pitchbend would be something like: When encoder is toutched, send - CC 48 with VALUE 96 when the jog is turned right. - CC 48 with VALUE 32 when the jog is turned left. and then start a timer of x ms. When x get's zero send CC 48 with VALUE 64. And everything the encoder is touched again the timer get's reset to x, this would probably be a solution right? Only I have no clue at the moment how to implement this :-X. Jeroen.

Hya Guys, On the NI forum I found out that a guy by the nick of 'jamesh' had the same problem as me: the pitchbend in traktor wouldn't work with an encoder, and his question isn't really answered on the forum yet, so I started to look for a solution too. I've posted a link on the NI forum to this topic too, so that jamesh might share what workarounds he has found so far. I've mailed with Luis, the maker of the kontrol-dj (www.kontrol-dj.com), who has already made a working solution for this problem, so ofcourse I was really interested. And being the kind guy he is he told me how he did it, so mabye we can use this to make something work in MIOS. This is what he mailed me: Here is also described how he uses it to scratch, I got traktor to scratch with an encoder a bit, but it didn't really work properly, so maybe we could look at this too, for me, personaly, this has no priority at all. I myself have done lots of different programlanguages, but no pic assembler yet, I'm now learning it and have already made two shift buttons wich I found in some topic 8) ;), so I'll get there. So in this topic I'm asking if there might already be something similar to this? And maybe the traktor enthausiasts are willing to help me in making such a function. Thanks a lot in advance for any help, and I know it gets said a lot, but never enough, what a great project this is!!!! thanks!, Jeroen.

ah thanks, but I already got it working :D... just ran the id change app and put back the borrowed 220 resistors :o on the ltc. Everything works fine :) Thanks again :), Jeroen.

wh000000000000000t! it worked :D.... was a bit lost because I didn't realize that the picture of the gameport connector was from the backside, so the pin was wrong :D... cant believe how seweeeet it was to see MIOS 1.8... ready on my lcd :). thanks so much!, Jeroen.

thanks, will try that :).

I was just going to write about that, but I saw a red text saying that someone had replied :D... I mailed mike to ask wich pic header id he put in it for me and he said: I only burn the primary mios bootstrap loader, because everybody takes another configuration. So after you have finished your project, you have to configure it over a midiport. So I guess this means that I will have to arrange midi ports for my pc? So that I can upload mios etc and then use the header change program to make use of my to com port? Could this be the problem? because I am getting a lot of midi message's even though I connected j5 a0-7 to ground :s. Thanks for the replies :), Jeroen.

Hi marcel, thanks, I did notice that my lcd was upside down yesterday (because of the text on the back ;P). It is very strange, now mios studio says that I am recieving a sysex message of less than 8 bytes :s, and in midiox I don't even see a sysex message. I checked eveything and improved some of the soldered points. Now miosstudio is showing me this: timestamp 1799780000 us: [F8] Timing clock timestamp 1799808000 us: [FC] Stop timestamp 1801013000 us: [F8] Timing clock timestamp 1801493000 us: [FF] System Reset timestamp 1803100000 us: [FC] Stop timestamp 1803494000 us: [F8] Timing clock timestamp 1809896000 us: [FC] Stop timestamp 1810914000 us: [F8] Timing clock timestamp 1816740000 us: [FC] Stop timestamp 1819570000 us: [FC] Stop timestamp 1819629000 us: [F8] Timing clock timestamp 1819956000 us: [FF] System Reset timestamp 1820890000 us: [F8] Timing clock timestamp 1822971000 us: Sysex message: F0 00 00 01 05 timestamp 1828129000 us: [FF] System Reset timestamp 1828548000 us: [FC] Stop timestamp 1829216000 us: [FC] Stop timestamp 1829629000 us: [F8] Timing clock timestamp 1830444000 us: [FF] System Reset timestamp 1831778000 us: [FF] System Reset timestamp 1831778000 us: Sysex message: F0 00 00 01 05 the sysex messages are no longer 2 seconds appart but longer. I also get a lot of note changes and stuff but I filtered those, that's probably because my ain ports aren't clamped to ground since I did not connect my ain module yet (but this can't cause my problem right?). Can I conclude that the pic header is correct since I do get some messages from the core? I dont know the effect of a wrong baudrate. I also checked all the +5v and grnds according to the diagram, they're fine. Any help would be greatly appreciated since I'm a bit stuck :s. Thanks, Jeroen.

Hey guys, Wayyyyy cool project here :), to bad it's not working yet 8)... II finished my core and ltc yesterday and its not working correctly. I've got my parts from mike's shop... Things I see: -Red led on ltc burns -Green led goes on when I send something with miosstudio -Lower bar of lcd black -Checked the voltages on core and ltc -This is what my midi in port monitor shows: timestamp 153852000 us: [FC] Stop timestamp 153852000 us: [C0 00] channel 1: program change 0 timestamp 153852000 us: [C0 00] channel 1: program change 0 timestamp 154669000 us: [C0 00] channel 1: program change 0 wich repeats about every 2 seconds. My problems are 1. that I do not know if the pic header is set correctly, so if the 1 for the ltc baurate is working.. 2. Is my core working? :s 3. I can't upload mios, the core doesn't respond, also not to a sysex dump request from serge's app. Anybody know what the problem might be? I've read arround a lot and checkt a lot of the other core/ltc trouble shooting topics. I hope someone can give me some help. Thanks a lot, Jeroen.

If I am correct: you can still use the ledrings since they give the status of up to 128 virtual pots, wich you control with the encoders... Jeroen.

Hi, I'm also working on something like that. But I decided to make it standard for 2 decks, with possibilities to siwtch between decks too, this way you always have contact with 2 decks at any time, wich makes more sence to me since you'll want to mix things in most cases 1 deck wouldn't be sufficient in my eyes. Also, if I had to start over I would use rotary encoders instead of pots. 1. because the ledrings look freakin sweet, and you can also control much more virtual pots. With one pot you can also control multiple things in traktor, but you don't have the endless turning you have with encoders. So consider this. Good luck, can't wait to finish my own, and am curious about your projects! Jeroen.

Hey guys... I am, like every newbie, very sorry if I'm asking a easy to find (stupid ;)) question... put I'm really going banana's and have been searching around for far to long :p... Ok so you CAN hook up pods to the 64e, but why shouldn't you be able to hook up the rotary encoders to the 64? (I'm not saying its not possible but I don't really se an anwser :s). As far as I get it the only difference between the 64e and 64 is that the 64 doesn't have the two AINX4's :s... so shouldn't you be able to use two of the DINX4 pins on a MB64 for a rotary encoder? And the rest of the 30 pins for buttons?... I'm really lost here ??? Any help would be apreciated, greets, Jeroen.