[Narwhal]

somewhat like the mempot idea except using encoders and better manipulations I suppose.

[stryd_one]

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 ;)

[Narwhal]

The code as posted does not work.  It's not stable and totally goes nuts if the encoder isn't turning at all.  But don't worry I'm working on it.  I'll post code and results soon.

[stryd_one]

Quote

It's not stable and totally goes nuts if the encoder isn't turning at all

It shouldn't even be called unless the encoder has moved... I think you made a boo-boo ;D

[Narwhal]

Well the whole purpose of the first if:

if (!((oldsensor1 ^ sensor1) & !(oldsensor2 ^ sensor2)) )

is to figure out of the wheel had been turned.  It should be this though:

if  ( (oldsensor1 ^ sensor1) | (oldsensor2 ^ sensor2) )

I got it working last night and it is quite fast.  There are exactly 512 state changes using a 128ppt encoder, when I spin the wheel a complete turn, I get exactly 512 on the LCD.. NICE!

If I spin the wheel at the fastest, the highest MaxInc on the LCD I get is 0x30.  This is how many state changes are counted during 1 timer interval.  You need to spin the encoder as fast as you can to see what its limits are.  By adjusting the timer delta to a shorter interval you can tune this value down.  Longer timer intervals will cause this number to increase.  The idea being, that you never want this value to get anywhere near having its high bit set with the fastest spin you can possibly put on the encoder.  As you approach 0x80 you run the risk of your increments appearing to be decrements.  But you can increase the timer interval so it interrupts less often to run the timer function.  There is plenty of headroom right now to support even higher ppt encoders.

I've attached the new main.c that is set to use an encoder that is attached to the pic's port C (J10) via pins RC4 (23) and RC5 (24).  It's a lot like the encoder speed test, except that I don't yet have adjustments for speed.

Attached File(s)

•  main.c (9.71K)
  Number of downloads: 40

[stryd_one]

See, memory like a goldfish... A day after I write it, I forget how it functions ;D
I was actually thinking of calling it a different way but that works!
[me=stryd_one]does the "it's working" dance[/me]

I think you guys oughta be using the new structure though...makes it a lot easier to try the new .c files too :)

[rasteri]

Here's a minor update to the code. It now runs on 452s again (optionally) and has all the settings like voltage reference in #defines at the top of the source.

it doesn't use stryd's cool new logic yet (haven't had a chance to test, but I will, I promise!).

Attached File(s)

•  main.c (9.24K)
  Number of downloads: 41

[stryd_one]

As well as being about 10* faster (= more decks and/or more accurate), If you're searching for codespace... that logic is a good way to get a couple hundred lines of code back too :)

The algo should drop right into your code too, the original that I wrote was based on your app. I'd be happy to make up a mod for you to upload and test.

While I'm at it, I can also make this app work with the new MIOS structure... There's nothing to it really, just fix up the includes and use the skeleton's makefile :)

[rasteri]

You're far too bloody helpful :P

I've added and tested your code, works perfectly. It's attached. I'm pretty sure direction should be a signed char though :P

TBH the code ran fast enough anyway, even with a 2048 step wheel (attached), but I could see it being a problem when buttons and stuff get added.

If you wanna convert it to the new MIOS structure, knock yourself out. I haven't downloaded it yet. I hate having a job...

Attached File(s)

•  encoderwheel0.5mm.pdf (5.02K)
  Number of downloads: 87

[stryd_one]

Quote

I'm pretty sure direction should be a signed char though :P

LOL! You might be right ;)
Edit: BTW the reason it's not signed is that my draft version used 1 for forward and 0 for back. That saved two clock cycles but you only lose them elsewhere so I ditched it.

Quote

TBH the code ran fast enough anyway, even with a 2048 step wheel (attached), but I could see it being a problem when buttons and stuff get added.

Quote

If you wanna convert it to the new MIOS structure, knock yourself out.

Well here's the thing - the encoder driver should really be a mios module, so it can be included in other apps easily :) Also, why stop at one deck? Hey, why only decks? It could be a scrubwheel for a linear sequencer or the likes... I can think of lots of uses.

This lines up with what I was saying in the traktorizer thread about you DJ guys pooling your resources. It's kinda madness to have three dudes working on the same thing at the same time and not working together. Moving to the new structure will make that a LOT easier, it'd definitely be my first move.

If you've not upgraded yet maybe it's not a good time... But I'd have that pretty high on my list if it were me :) Give me a shout when you're ready and I'll go ahead, it should only take a short time.

[NidStyles]

Just out of curiousity on this project. What about pitch control?

The set-up I'm working on uses a Laptop running Traktor and looking for some sort of MIDI controller I can use to scratch and cue, but still use the analog mixer I have. The only way I see it working without using two soundcards out of the laptop, which is not feasible.

Basically the set-up would be with 2 MIDI controllers like this, my laptop running Traktor, and the AEM-100i. I want to be able to use a headphone for cue purposes and have the outputs coming through the mains out of the AEM...

I'm not asking for it to be done for me, just looking for some guidance on getting where I want to be with this. I've looked at the 'Commercial' offerings, and the only one that fit's what I'm looking for is the Denon DN-S5500. That's a lot of money though. I'd rather try my hand at this and learn something from it. ;)

I looked at the Traktorizer one, but then I found this one, and this one seems more capable of doing what I am looking to do with it.

I'm new to this digital world of DJing, and the only work I really have done with MIDI is from synths and drum machines. No programing it or anything of this nature. I have programming experience using C/C++, and a little ASM. Never done any PIC before, but from what I can see it's very much the same.

[rasteri]

Adding another fader would be really easy. We're talking another 6 lines of code. And coz it's just a pitch fader you can use a cheap crappy one.

[Sasha]

What is the limitations of this controller? (stryd`s mod) I mean, what is the number of supported i/o without sacrificing the encoder performance? I hope PIC could do much more than it is doing right now with encoder, fader and few buttons.

[NidStyles]

Quote

Adding another fader would be really easy. We're talking another 6 lines of code. And coz it's just a pitch fader you can use a cheap crappy one.

Then my only other question would be on the resolution. I mean say I was to set it for around +/-5% or something around that range, what could I expect for the actual resolution? I know the software would most likely effect that, but as far as actual signal output I would expect it to be adjustable and pretty refined at lower +/-%'s. Just trying to get an idea of what I'm in for, and how I should go about this.

Thanks for the help.

[rasteri]

Quote

Then my only other question would be on the resolution. I mean say I was to set it for around +/-5% or something around that range, what could I expect for the actual resolution?

Well, you get 128 steps, so over a +/-5% range that'll give you an accuracy of 0.078%. That's probably good enough - numark TTX turntables are less accurate (0.1%) and they're usable. Just.

[NidStyles]

:D NuMark TTXs. That's riot. I stopped DJing in the 90's when they started releasing decent DDTTs. Never used one, so I can't comment. I'm a Tech man, always will be I guess.


As for digital though I was looking at the Denon, and Pio offering's having resolution down to .02% at +/-4%. .07% is workably good though.

Thanks for all the replies.

[nILS]

You can get 10bit resolution (1024 steps) off the pitch-fader if Traktor can take that.

Sasha: If you put a little effort into timing you can easily use a pair of these in a traktorizer.

[rasteri]

Whoops! found a bug. Thanks to Simon for pointing it out.

Attached File(s)

•  main.c (8.33K)
  Number of downloads: 57

[NidStyles]

Quote

You can get 10bit resolution (1024 steps) off the pitch-fader if Traktor can take that.

Sasha: If you put a little effort into timing you can easily use a pair of these in a traktorizer.

Supposedly Taktor supports 14bit MIDI. I have read of examples of people having issues with it reading that high though. Something with the VCI-300 apparently, and Taktor Not reading anything over 7bit. I have no idea how this would translate in the software used in the Scratch wheel, or anything else. I haven't even taken a look at the code yet. Been swamped at work like usual.

[Simson91]

Some pictures of the box and a little sideview. Sorry for the bad quality of the pictures (my digicam is simply crap) and the poor drawing :)
I'm still looking for conductive paint, couldn't find any, does anyone know in which kind of store I should look for it, in germany?

Some things I'd like to add is a little power LED which woun't be a problem but I'll try to design it like the speed calibration strobe of an real turntable and maybe one or two real cool looking buttons but thats future stuff.
Simon

Attached File(s)

•  HPIM6398.JPG (147.23K)
  Number of downloads: 90
•  HPIM6400.JPG (92.86K)
  Number of downloads: 111
•  sideview.jpg (44.86K)
  Number of downloads: 76