stryd_one

Tried ebay?

Correct :)

Very pretty... but not really very functional otherwise... Seqv4 already has an integrated solid state storage (SDcard) :D Sequencers don't have samples to edit... The problem with doing fancy graphics, is that it can take valuable processor time, which I would personally prefer to see being used to make the sequencer more functional/keep accurate timing... It's possible to make special designs which allow you to use an externally controlled display, but as TK has mentioned in the seqv4 thread, and as lucem and I know from our designs... it's not trivial...

;)

Fun! As for testing.... do you have a scope?

Hi Daniel, That suggests that either: Your faders are wired incorrectly - if that is the case, you could cause a short and blow up the parts, so I would turn it off immediately and triple-check it... or maybe, your PSU is extremely noisey...

You can only edit wiki pages when you have registered and logged in to the wiki :)

OMG I have heard some funny drummer stories in my time but that one is definitely in the top 5. I just woke up my flatmate with my raucous laughter :D Pr0nsync © LyleHaze 2009

A good demonstration - notice that in comparison to that, the CF pic has the backlight a bit brighter, which reduces contrast with the lettering, which means the lettering does not look as bright... Yep, CF didn't adjust their display perfectly either ;) Edit: or, the one-sided backlighting on the CF means that it needs to be that bright... Probably not your fault - some cameras have 'polarised' lenses so that they can help with lighting, and that makes it impossible to get perfect shots of LCDs...

Hope you're feeling better soon goblinz.... No doubt right now you are finding out from first-hand (heh) experience, why opposable digits are so convenient... ... and probably why us martial artists like thumbs so much (lots of nerves in there that really hurt!) Be sure to let it rest, and heal up properly; busted fingers can be a real problem in older age... I think the standard excuse for late homework is "my dog ate it"..... but that will suffice :D Sorry for joking about your pain but it's so damned surreal I couldn't help it! A tornado?! :o

Sounds like a common effect in counterfeit chips. Microchip might like it if you sent them a quick email to let them know... Box looks yum! :)

You should be able to use 'make' to do it - try the quickstart install guide on the wiki to make it work with the new stuff :)

Not sure if this is related, but maybe the wiki is out of whack... Twinnie? I noticed that someone had edited/broken the front page, so I went to revert it, but noticed that the last edit was by an IP address, not a username - strange... Then when I saved the page I was returned this error message: Fatal error: Call to a member function getUserData() on a non-object in /home/midibox/public_html/dokuwiki/inc/common.php on line 1287

Heya pablop :) You mean this one ? Did you maybe use the template in the zip file from this section ? It's verrrry olllld and won't work... You should be able to follow the instructions for creating a new template found here though, but you will need to change at least one step: Where it says to type 'make.bat' you just type 'make'. There may be other changes required.... That documentation is quite old...

Sorry that was a lotta pages to visit, I guess I mangled the info :) Anyway, it's still not freeware, it's crippleware: Edit: At least it fits the pattern now :D

You could fix it in software, just search for LEDDIGITS to find appropriate code; but it's much easier to rewire it ;)

Thanks stever, rock on!!

The old fashioned term is 'self-tapping' screws... They're not for everything, and my PT10 is not handy right now to compare, so be sure that the PT10 is designed to have these particular screws, as using the wrong size/thread/etc on the wrong materials will cause them to explode from the screwhole outwards :( I'd cover my *ss by emailing pactec and saying "Is this one going to work?" so I could get a refund if it didn't.... The good news is that, so long as they aren't too wide, you have a lot of room for error :) OT: If you've ever done a lot of manual tapping (like our resident furniture experts will tell you), you'll know why it's a nice feature - two turns in, one turn out... two in... one out... two in... one out... omg...this is boring... two out... one in... two out... one in.... wait... i'm going backwards.... two in... one out... two in................................zZzZzzzZzZzZzzzzzz It's like uncorking wine, on acid, with no tasty juice at the end. No fun.

Quick hint: Solve one problem at a time. You'll find it's far more effective ;)

It's just not there :) midio128 is an app itself, and it only includes the very basic code needed to handle digital inputs and outputs. Anything beyond that (like encoders etc) needs to be added in by you. Those will be C apps - that line is there to specify the type of value that the function will return. For a highly simplified example, let's say I have a function to write a variable to a bankstick. The function can be called "WritetoBS", the variable we write could be an 8-bit value - known as an "unsigned char" in C terminology. We could define the function like so: void WritetoBS(unsigned char myVariable) { // this says 'void' which means this function does not return anything, it just does what it's told and that's all // your code goes here // in C, lines starting with "//" are comments - they are just for humans to read, and ignored by the compiler // just like a semicolon in assembly /* with most compilers, you can also start a comment section like this and then everything after it is a comment until you close the comment section like this */ } Then you can use that function to write your variable like this: WritetoBS(123); Now this is all well and good, but, what if the write to the bankstick fails? It would be nice if your application were aware of it, so that it could retry, or notify the user or something, right?... well to do this, we can use a return value. In that case, we could define the function as so: unsigned char WritetoBS(unsigned char myVariable) { // note that this function returns an unsigned char // your code goes here // we will somehow determine the success of the write to the bankstick // and we will set a variable called 'writefailed' accordingly // so that we can use it like this: if (writefailed == 1) { return 1; // this is where we return the value to the caller. it's 1 if something failed... } else { return 0; // ...and it's 0 if everything went OK } } Now we can call this function like so: thereWasAnError = WritetoBS(123); // this function will now know, whether the write to bankstick function was successful if (thereWasAnError) then doErrorHandling(); // and if it failed, it can do some error handling Sorry you had to wait... real life is kicking my ass right now. You can be sure, that if you get my attention like you did, you'll get an answer... sometimes it might just take a while. Of course you can feel free to give me a friendly reminder if it seems like I have forgotten you, as sometimes my memory fails, and even more often, my PC that arranges my schedule fails too ;) You're very kind, but I'm just a janitor :) TK gets all the credit here. Although, it is tempting to try and bask in his glory ;) It will only return the number that represents the state of 8 pins == one Shift Register == DINx1. You can do this easily with a for loop in C, somethng like so: (pseudocode, check it first for errors!) unsigned char DIN_States[NUM_DINS]; // declare an array to hold the DIN pin states. Do this in your header file, or at the top of your C file, not inside a function where it would be temporary! NUM_DINS is a #define which tells the app how many pins you use. In your case, it would be 128. .... .... // here is your function to read all the pins unsigned char counter; // a declaration for (counter = 0, counter < NUM_DINS; counter++) { // do the below until you have all the pin values DIN_States[counter] = MIOS_DIN_SRGet(counter); // store a SR's pin states in your array } However, that's just one way to do it. You could also use the USER_DIN_NotifyToggle() functions, to set only the pins you change, rather than all of them, which could be better for performance. It really depends on what you need.... Does that help at all?

Sounds like a good deal! :D I'll try and meet you in the chatroom to fix this up, so we can do the lengthy troubleshooting in there, and just put the good parts in here ;)

I can't think of any app that employs online updates, that hasn't had major troubles with them. Java is the #1 candidate, but flash and acrobat are definitely high on the list. I recommend you to only install these toys from pre-downloaded full installers (not the type that download the files from the internet to install them, the big one that needs no net connection to work), and after installing them, immediately disable the online updater. Doing so will avoid troubles like this one. Don't even get me started on the f***ing mess that the java updaters make on your machine....... Another classic misbehaviour is the fact that these tools rarely uninstall correctly (read: completely) and instead leave behind files and, most notably, registry entries. To compound the matter, the installers tend not to overwrite existing settings with 'known-good, out-of-the-box' settings, instead preferring your existing (in this case, broken) settings. As such, while uninstall/reinstall can be educational, it doesn't always fix stuff. Damn. Some software shops even go to the extent of supplying a "real" uninstaller, which actually does a full (read: complete) uninstall, and has to be separately downloaded (Symantec comes to mind). If the software you're having troubles with doesn't have such a tool provided (or you can't find it - eg, the symantec uninstaller used to be highly secret and not available unless you held an enterprise license worth several tens of thousands of dollars) then you can go the manual route - searching the registry (use Registrar Lite, not regedit.exe - hot tip!!) and removing the entries as needed, and manually deleting program files/common files/etc. Beware that if you do this stuff you might just trash your PC. If the preventative measures I've suggested are too late (like this one) or the manual cleanups don't work or are too risky, then your only real option is to file bugs with the project in question. If you're an advanced user, you will probably be alone in reporting the issue, so it will look minor, and you can expect to be largely ignored, then spend weeks on testing to prove to the devs that the problem really is with their software, then be asked to completely reinstall your system to a reformatted drive, which will fix the problem and they'll probably blame some other app, then you'll be largely ignored for some time afterwards and maybe get a fix in the next minor release, if you're lucky.... Don't you wish all software was written by TK? I sure as f*** do!!! In the meantime... try the 'manual uninstall', and turn off your updates this time ;)

Also: Layer mutes+chord track+arp=fun.

Sorry johnc I still have your other thread open in a tab but have been very busy. Will reply soon!

Yes please! :D