stryd_one

Wow talk about getting mixed up! Hehehe First link in my signature ;) Up to 128 DIN pins, and 128 DOUT pins, which is 4* DOUTx4 boards and 4* DINx4 boards - each D*x4 board has up to 4 Shift Registers, each providing 8 pins, for a max of 32 pins per board. It helps to get your terminology correct to avoid confusion. Well, that's AINs, and that's different to DINs; but you were on the right website, and for AINs your answer was correct. I'm glad you un-lurked!

Heheh.. I've had this thread open ever since the 1st post, waiting for me to get time to study the schematics....Because I know how to switch the filters with the midibox, but the filter itself I have no idea about ;)

Why the SMD parts?

Hmm maybe a little too high, yes.... But I am confused: Where is the 5.8V? Good idea! It's best to wait, and be safe ;) You got that right!!

Well yeh, I was basically thinking, a linear sequencer with a few very short sequences, EG 2 seconds would be ample to record a crab on the fader, then you can press a button to play it, and/or loop and manipulate it as it plays. I prefer analog turntablism; so I reckon if you're gonna have new tools, it makes sense to do something new with them, otherwise you're better off sticking with vinyl ;)

I meant doing it in hardware though... I guess if all the apps support it, why bother eh? Bingo.

http://www.ucapps.de/cmios_fun.html If you're gonna write code it helps to know what code you can use ;)

That's why I volunteered my email address - if anyone's ISP sucks and doesn't update their DNS regularly, I'll show them how they can fix it :)

Go with that then mate... Unlike you, I got the binary values in my spreadsheet from some webpage, so it's not exactly guaranteed ;) Your working looks good to me. I'm really glad we decided to try this, at 10 times better performance it allows room for the pic to do other handy stuff. Has anyone considered recording/effecting/playing back their scratches? I mean the movements of the turntable/encoder, not the audio it modifies...

Heh we were just discussing these in the chatroom... They're so nice.... After all this time we're still trying to think of a way to use them for the SID/FM/Seq :(

Awesome. I have a pdf and a bunch of HTML etc saved here if you want? Shout out if I can help any other way!

I wasn't sure, so i searched for the pin names you mentioned, and I found this: http://www.midibox.org/forum/index.php/topic,10898.msg84291.html#msg84291

I'm guessing: Serial Output Serial Clock Multiplexer Edit: Tags need to be separate words, in lower case ;)

Thx man, let me know :) I'm dying to know if it actually works... looking at the encoding and the equation I'm sure it will, but I lack the hardware to really find out...

Very little progress here I'm afraid. Please give it a try if you like :D

In case you didn't notice this: If you have any problems or questions please drop me an email s t r y d . o n e @ g m a i l . c o m (cut out the anti-spam spaces)

Sounds good!

Try star-like wiring. Re: AIN ... entries talking ... Re: The Dub Master MIDIbox 64 -work in progress-

Any of you turntable encoder DIY freaks wanna try this quadrature decoder? // Top of file.. declare as registers register unsigned char sensor1,sensor2,oldsensor1,oldsensor2; register int sensordirection; .... .... .... void yourfunction(whatever){ unsigned char direction = 0; // Default to an error/no movement ..... if (!((oldsensor1 ^ sensor1) & !(oldsensor2 ^ sensor2)) ) { // If this was fwd/back direction = -1; // Default to reverse if (oldsensor1 ^ sensor2) direction = 1; // Set if fwd } sensordirection += direction; oldsensor1 = sensor1; oldsensor2 = sensor2; Compiles to _00115_DS_: ; .line 97; main.c if (!((oldsensor1 ^ sensor1) & !(oldsensor2 ^ sensor2)) ) { // If this was fwd/back MOVF _sensor1, W XORWF _oldsensor1, W MOVWF r0x01 MOVF _sensor2, W XORWF _oldsensor2, W MOVWF r0x02 MOVF r0x02, W BSF STATUS, 0 TSTFSZ WREG BCF STATUS, 0 CLRF r0x02 RLCF r0x02, F MOVF r0x02, W ANDWF r0x01, F MOVF r0x01, W BNZ _00119_DS_ ; .line 98; main.c direction = -1; // Default to reverse MOVLW 0xff MOVWF r0x00 ; .line 99; main.c if (oldsensor1 ^ sensor2) direction = 1; // Set if fwd MOVF _sensor2, W XORWF _oldsensor1, W MOVWF r0x01 MOVF r0x01, W BZ _00119_DS_ MOVLW 0x01 MOVWF r0x00 _00119_DS_: ; .line 102; main.c sensordirection += direction; CLRF r0x01 MOVF r0x00, W ADDWF _sensordirection, F MOVF r0x01, W ADDWFC (_sensordirection + 1), F Which is around 140 instructions faster than the old way = you can scratch faster = leaves more room for other fun stuff on the chip :) If you want to see my working you can check out the attached spreadsheet. You can thank narwhal/karnlund for convincing me that I was correct, that this could be done with logic, thereby making me actually try it ;) Edit: Whoops! My excel equations were correct, but my pseudocode i made from them, had an error... Fixed. quadrature.zip

I kinda like the [iurl=#msg95703]this style[/iurl], 3d bottom-up... gives a nice oversight of what sits where, without obscuring the traces tooo much. As for normal layout shots (2D) Kicad has a nice 'High Constrast Mode' feature where it pales and greys the layers that you aren't on, and highlights the layer you are on... that makes for nice pix too.

Absolutely dude! My to-do list now includes firing an email to the developer.

That's a good idea... There's a nice little space there to put it in too :) If cimo doesn't put it in his design, you can add them in very easily. Come and see us in the chatroom if you need advice on kicad usage. These apps have a specific purpose of course, so they tend to have unusual interfaces. Learning either eagle or kicad without any advice is tricky I guess....

Oh, good news I should mention: dj3nk seems to have accidentally discovered the source of the alignment problems with the boxes! Yay! He edit a page to make it fit on his screen size... What he did was to reduce the width of the box. Prior to his edit, we had for example two boxes, left and right, each at 48% width. Sometimes this would render ok like this: _ _ |_| |_| Sometimes it would render like this: _ |_| _ |_| He changed the boxes to 46%, in an attempt to make it fit on his screen, thinking that it was a problem with his screen resolution being smaller than average. Of course, it's a percentage of width of your screen, so resolution does not matter. What he really did, is make an accidental discovery: the percentage of width handler in the boxes plugin, does not take the border into account, so 50%+50% = 100% of width...... +borders = ~104% width, which forces the right box onto the next line. 46%+46% seems to work perfectly every time :D

I spotted that a while back... The good news is, bash highlighting (and the others) still work - you just need to edit the page and save it again. I hope it's OK, I restored the old version and you can see it is working fine now :)

Yum! They look good mounted too huh! Now everyone's gonna want me to get square caps too hehehehe