stryd_one

bugfight says: with all going at once max power for chip indicates 18.5 by my calc

Nah he wants white... I thought I had some :(

Sick!

Yes that's where the trouble was.

I asked about the midi interface working with other devices. As in, can you send sysex from your PC to another synth successfully? If you loop your midi cable from output to input and send sysex, do you recieve exactly what you sent? Can you paste it in here? (both in and out) (That's Test PC2) I think I already asked what midi interface it is? Have you checked the blacklist? Some interfaces have "issues" hahaha bzzzt sorry try again ;D that confirms that the LED blinks, nothing more :D That's a good move. Did you test for shorts as well, or just to make sure the pins/sockets were all connected?

http://www.midibox.org/forum/index.php/topic,11489.msg91464.html#msg91464 hahah I thought my memory was bad!

Tools for fixing your MBR are also included with windoze.

Oh you suck up with the best of them, you can stay ;D

Totally.

Is the core working with other firmware?

Maybe the noise is coming from the cv then... you sure it's OK? all flat when you read it with a scope?

Just keep it and wait until we (humans) do something stupid again. ;D

Might look at the code for you in a bit, have no clue what that deos.... but maybe this will help: ;; store row*2 offset in IRQ_TMP1 to simplify the addressing of blm_row_green and blm_row_red array SET_BSR blm_selected_column movf blm_selected_column, W, BANKED rlf WREG, W andlw 0x06 movwf IRQ_TMP1 = IRQ_TMP1 = ((blm_selected_column<<1)&0x06);

OK someone asked about how to use the tags and I thought this was a prime example of a frequently asked question which was hard to find, and often had interesting information in the threads, and most of all it was hard to find in a search... so it would benefit from tagging I searched for OSC and got hits for all kinds of things (*try it) so i narrowed the search to osc -oscil (Now I don't get hits for the word oscillator) and ticked 'show results as posts' so I see some text. 11 pages of hits, scrolled through and ctrl+clicked the relevant ones to open in new tabs, then went through the tabs one at a time, tagged them all with 'opensoundcontrol'. Why not 'osc'? because there are obviously* other uses for that term ;) Enjoy the tag! (You'll be reading for a day or two I guess heh)

Word.

Ahh you guys are too kind! Truth be told, I now slightly misuse a work PC when I'm on the forum (in my own time of course, although I sometimes take a quick break from work and midibox for distraction)... and, if I stopped spending money on midibox parts I could probably fork out for a decent PC :D The Celeron is the one in my lab though, cause I don't want to splash solder all over a laptop I don't own hehehe I compile on the work PC (for speed) and transfer with a USB memory stick to the lab (for midi) to upload though, and that is a pain in the ass! But I only have myself to blame.... oh... and MEC. and Optrex. Those bastards, they're dealing DIY audio crack, I got the monkey on my back!

The decision against IRC was made a long time before this poll. Everyone involved is well aware of people's (often uninformed) opinions, and they are always taken into account; so no amount of polls, nagging, begging, suggesting, asking, or otherwise discussing IRC vs flashchat vs whatever, will change the situation any. Maybe in future there will be an IRC chat, maybe flashy will return, maybe we will chat via carrier pigeon, maybe not :) Patience is a virtue :)

Damn mine won't be the first rackmount then :'( :D

I'd say it's possible if you know how, or are willing to learn from professor google :)

They always scrub up nicely with a good re-paint huh!

Well the links you pasted sure are! What's the obstacle?

Ahahah OK so you skipped all the failed tests ;) Your test results don't add up man... TEST CORE4: all connections have solid readings except at Rx with 0V. Makes no sense. What core are you using? SmashTV Core R4? test in4: failed Again makes no sense. By the end, you are connecting the 5V power supply that connects to pin8 of the opto, direct to the LED, and then to ground. The only way these last two could fail is if you have a broken trace on the PCB... test in5: failed again, makes no sense. Did you try this with the LED and the protection diode in both directions? That's four tests.... Can you please paste the logs of the midi tests like 'inout' and PC2, provide details of your PSU.... wait, i just noticed that you said you are powering through USB..... No hub, right? Have you tried other power? How about a 9V plugpack/wallwart via the onboard regulation? Does your core have anything else attached? (DIN/DOUT/LCD ?) how does it go if you detach them? I'd buy a couple of new opto's now - one for testing with and a spare ;) Is this midi interface confirmed to be working with other devices? With sysex too? What is it?

foo &= bar; is like saying foo = foo & bar; so octave &= 0x7f is like octave = octave & b01111111; // pseudocode- you can't use binary representation in sdcc which means that the top bit will be masked out, limiting the variable to 127, so void OCTAVE(void){ // octave doit Ãtre compris entre 0 et 127 inclus octave &= 0x7F; } That's all you need - although, I don't know if I would put it in a separate function like that, it'll take more time to jump to the code, than to just do this one instruction whenever it's needed.

I don't think that reflecting upon the problems we experienced in the past is productive in this case, so no, sorry.

Gotta watch out for laptop HDD though - 5400RPM drives are teh suck when you hit the pagefile. Of course in a DAW you fix the pagefile and have lots of RAM... if you have more money than stryd_one... My PC is a Celeron II 333Mhz that my neighbour donated, out of pity for the computer tech that couldn't afford his own computer. It works, I don't need an upgrade *that* badly ;D