stryd_one

Send it over bud :)

..........and I screeeeeeaaaaaamed.......... http://www.youtube.com/watch?v=sEr8SYqTc3s Edit OK what are you supposed to put between the youtube flags? http://www.youtube.com/watch?v=sEr8SYqTc3s

You'd probably want a slider for that, have you considered the infinium faders? They go up to 256 steps, I don't know if that's enough or not.... You seem to be a bit cagey with the information, or maybe you're not sure yet? Heh, yeh, I got that bit the first three times ;D But as you can see with the one example above, the right answer needs the right question... You've said only half the question.. the more you tell us the more specific help we can give. If you tell me why you need more than 7bit and what for and how much you do need etc, then I can be more helpful... Also, seeing as you'll be bitbanging the SPI, then you can leave the IIC pins which are assigned to the MIOS functions in place and use other pins for your SPI, so that will open up your options too, you can use 452, 4620, 4685 :) It is possible to recompile MIOS with different pin assignments for it's IIC functions, as they are bitbanged also, but I wouldn't recommend that.

The ebay ones, i got some from him and they do work, nothing special though. You get what you pay for. The allelectronics ones are basically tacts in a nice housing, so... You know those :) Hope you don't mind I fixed your links up...they didn't work :(

Sounds like your pedal doesnt have the right kind of pot in it.... Look for TK's value-scaling algorithm :)

How about we collect up all the videos in this thread, and if there are enough collected to warrant a separate thread in each forum, I'll split the thread up? I don't think we need a separate thread for each midibox when there are only a dozen or so videos all up, and some of the midiboxen only have 1 or 2 videos... Should be easy to find the particular model you're after by hitting ctrl+f ;) You've probably noticed that there aren't many sticky threads on the forums, so I think this one needs to be something a bit special to warrant that... We'll see...

As to whether the powdercoat will burn under the laser, it will depend on the methods and materials used... Most often it's all good, but YMMV...

All the arctic circle stock was taken by the penguins. Antarctic circle stock has been eaten by wayward kangaroos. Sorry huck!

Heheheh no sweat dude :) And don't stop saying dude or it'll make me stand out more ;) As someone who's new to the site, your perspective on documentation and such is invaluable... This is a good example, too - I would have seen the 'B' and gone ahead without thinking twice, only because I've seen such things before... Only a newbie could find such an oversight....so don't be afraid to make changes or suggestions or whatever :)

Ahhh PWM... It's like the $64000 question around here lately! There's a PWM peripheral on the PIC, has anyone aside from TK used it and feels like explaining it to us all? I've got a rough idea, so I'll step up and learn the rest if needed... But I don't want to reinvent the wheel if someone already knows ;) Anyhow, that's just the one output, not 4-16, so I don't know if this is the right way to go for you e-toy.

Heya matoz, we talked about this is the chatroom, did you get it working?

No sweat man :) I'll be in the chatroom in 5, if you need a hand :)

In SDCC at least, the register keyword causes the variable to be stored in Access ram, which means you don't have to perform bankswitching to access the variable. At compile time, it will generate a warning to tell you that it has done this, and if you allocate more registers than there is access ram, it won't link after that. They do? ;) Nah... That's about how the access ram works. If you are using the data ram banks, it will have to use either indirect addressing (takes the location of the variable and loads it into FSRxL and FSRxH, then reads it using INDFx/POSTINCx/POSTDECx/etc) or by switching to the correct bank and reading it by name (banksel blah, Movlw Foo, etc). Access ram allows you to just specify the variable's name, without having to load the pointer to the variable into FSRs, or switch banks ('movlw foo' will always work no matter what bank you are in or what values are loaded into the FSRs) MIOS_PARAMETERx is a good example. SDCC always uses indirect addressing when pointers are implemented (places the pointer in FSRxL/H). And it recalculates the address every time you use the pointer :( This is by design, so if you want to use pointers you should be careful about how you do it if code size and speed are a concern. There's no need for a pointer to a register (access ram) obviously, and a pointer to another address which is stored in access ram will be slightly faster to calculate because of the lack of bankswitching/FSR loading, but given the overheads involved, it's not really worth your trouble. Registers/Access RAM are really best used as a temporary variable which is fast to access, or perhaps to pass variables to a function without specifying them as an argument which would use the stack. (As Wilba called it, writing ASM in C ;) It's probably bad practice in C but it can make for faster code in the end). Not at all! I took a while to respond because it's a fairly indepth topic so I wanted to take my time on it :) Hope this helps! That's a different issue... You only need to do that if you are trying to store a single variable which is larger than a whole bank - which is generally something that should be avoided.

Heh, I'll try one more time... What for?

Glad it's working :) Maybe the PIC got zapped with elecromagnetics somehow....

Thanks Cimo, but that's not it. I tried refreshing and reloading, tried clearing cache, etc etc. Tried it from two browsers on two PC's. Are you still working on this AC? It's gone really quiet, but it's not quite done yet...

So you've updated the wiki with this new information, right? ;)

Firstly, thanks twinny that's great! :) Also.. I was thinking, why not make this thread for other midibox video also? (Not just SID)

abc: this is not aimed just at you, but at everyone and anyone. This is the second time in less than 24 hours I have seen someone speak rudely to twin-x. I generally try to keep out of other people's arguments (and suggest everyone else do the same) but there is a trend forming here and I intend to put a stop to it right now. Let's show a bit of respect for twinny here please. Maybe because you're new here you don't realise that these forums and wiki are hosted by twin-X. Its not like he just sits back and watches it, he puts hard work and his personal time into this community and without his work this place would not exist. Even if you do not respect that, at the end of the day you're in his house, so be polite. IE, NOT: But maybe: Both of these things really say the same thing, but they carry a very different mood. This is the web, and this is a particular corner of the web where we have many different languages and cultures mixing together, so sometimes it is impossible to avoid being misunderstood. If you are being nice, and someone misunderstands and thinks you are being rude, the solution is not to be rude to them. Suck your ego back in and make friends, don't go playing some game where you must be right and they must be wrong. I do not wish to hijack this thread or start a big discussion on this matter. Just be nice to twinny. Period. *that means: don't reply to this post. just do it.* Now back to our scheduled programming. (get it? programming? ohhhh nevermind) ;)

Yeh, restraint is not one of my strong points ;D No offense was intended of course!

Yep, let it go guys. We all feel the same :( Someone else will take care of it if needs be. Just enjoy your midiboxen and make music :)

Stop buying weird LCDs! ;D

Sorry, 4685 has a different memory organisation to the 452 and there's a good chance that the LC won't run.

heh the two FAQ's was the one that made me go "what?"

Yup, I'm with you on that one, like throw 1 = feedback, throw 2 = External In (grounded when not inserted) Guess if you like his method you could do throw 1 = grounded, throw 2 = External In (feedback when not inserted) While I'm talking about the sidechain... you could passive mix the input and the feedback...