stryd_one

Hahahah! Yeh I used to do hardware repairs in a small, rectangular, all-concrete basement... When a PSU cap went off it would reverberate around the room and it was like a horde of angry pixies bashing you in the ears with baseball bats ;D

Breathing. © Copyright 1805BC, stryd_one_says_blow_me_studer Industries, Un-Ltd.

Oh so THAT's what you were talking about when I said the word...However I said it in a different context, meaning amperage as a *measure* of current. I did it in an extremely slap-hazard manner as I was unaware that we have the tech grammar police patrolling the boards ;) So anyway: "How much current will kill you?", is correct. It requires an answer as a number of amperes such as: "60mA across the heart", because you are requesting an amount, which requires a unit of measurement. "What amperage will kill you", is also correct, but it requires an answer as a numeral without necessarily including the unit of measurement such as: "0.06 across the heart". This is because the unit of measurement has already been specified in the question. In fact, this version of the question is more versatile, as either answer would work here. For "ohmage", it's similar: What resistance is that pot? 10k Ohm. What's the ohmage of that pot? 10k. Now, either can be used depending on phrasing, and when the talk gets into colloquialism as it does around here, stuff like : Comes out... it would be better worded as: "variations in current caused by variations in impedance" but "variations in amperage caused by variations in ohmage" is, strictly speaking, also correct. They're actually saying different things though. The former, is talking about the actual flow of electrons, the physical state of it... and the latter is referring to the *measurement* of that flow of electrons. That said, I had mixed my phrasing, and the grammar was a shocker, but ther's nothing wrong with the use of the word amperage itself. Which just goes to show that just because the people that wrote your book know about electronics, doesn't mean they know about English ;) Now mind you - just because it's correct grammar, doesn't mean you won't sound funny to a professional if you use it in the real world ;) hands up if you care, people ;) Viva la resistance...or ohmage...or impedance or whatever.

Bump! (oops, I did it again) Can we get durisian's code merged in? This issue has come up a couple of times... Please let me know if I can help :)

Hot! Anyone seen these for sale? (the encoders, not the studer ;) )

Yes, you could do this, but it would be more expensive and take more time than buying a dedicated device. Sorry for the reply in English... there were no replies in French ;)

Bump! (see, I do it too sometimes) :D Great ideas man... Wouldn't surprise me if you could do similar soft-bending with the SID too (which has already kinda been done for things like the VCA fix). I totally agree with you about the bent instruments, that's probably because most of them are not made with a goal in mind, but are just people tinkering with them at random... the sounds follow suit ;) In contrast, if we have full knowledge of the hardware and software, we are able to really dig into the guts of it, and produce results which have a certain purpose to them as far as the output data (sound) goes... I'll definitely help out with this if you need it. PS domnsampling good. raucous good. One man's trash is another's treasure I guess ;)

I was watching this like "yeh, yeh, I see where you're going, get to it already, yawn..." then i skipped a bit, and skipped again, and ......WOW that looks cool! And that openeeg project is of great interest to me as well. Cool linkage guys!

Man, that thing is tasty. Thanks muchly for sharing the layout!!

Maybe I'm missing something but what about: mb64 --> PC1 --> PC2 Where PC1 generates the clock and forwards incoming messages from the mb64, to PC2? This allows the mb64 to control either PC, if you want it to.

Hahaha I've only just now read this thread :) BTW, Sorry for the flood of replies... I'm catching up on lost time... only 16 pages to go... can't you guys type slower?! ;D

Sorry mate, only the specified chips will work with the FM project.

Don't sweat bud, it's easy in C :) No need for inline ASM. Question is... how do you want them to flash? I mean, is it just constant flashing, or flashing synced to something or a specified speed or...? Is it constantly blinking while the box is one or only when using a certain feature or your CS, etc etc...? Also, are you already using the user timer? Regardless, the basic theory is that you need some kind of timer, which might be the user timer directly calling the LED flashing (I don't like that way in most cases) or a counter variable (can be incremented by user timer, or every 1ms in the SR_Service_*, or by incoming data, etc, and then someplace else, you read the counter and set the LED appropriately)

Search 'LC 2.0 alpha' ;)

What he said!

Pics please! :) 64ms? noooooo... TK said worst case is 12ms... perhaps you mis-read, but 640us (best case) is 0.64ms :D As said above, It's unlikely that they will work as they are audio faders and will be a logarithmic taper not linear (search the forum/google to find out what that's all about)

How's that? ;)

All of them! Check out the page on ucapps, and there's a wiki FAQ explaining the difference.

Interesting :)

I agree! It wasn't the bumping that was the problem, it was the repeated bumping and not much input... Bad SNR...

Glad it's panning out. If I were you, I would continue to use the IDE which I'm comfortable with. If you want to switch, then I would recommend code::blocks, because there are a few others around here to help with support, and it is documented. You don't need to integrate with MPLAB any more now that the apps have been migrated to GPUtils ;)

Aircraft 'steering wheels' are known as a 'yoke' :) Are you sure it's serial and not joystick port? Or maybe it's a joystick port for a non-PC (like say, a C64 ;) ) Have a google around for joystick pinouts.

Wow, nice! Damn the sink, full speed ahead!

If you use a DINx4 module (four of the shift registers that give you 8 digital ins each) you can add extra buttons (your MPC pads) to the default clockbox app. I think this would be your easiest way. You'll definitely have to be able to write code in C to do this, but it should be easy. Good luck, and don't forget to use the search!

LMAO! Great stuff seppo. Congratulations, I know you put a lot of work into this!