stryd_one

A good idea for sure... Implementing it would fall into a basket over there labelled "way over my head" :)

Hmm then we'd need a user-configurable parameter to mute and unmute the mixer, for each of the SID outs... And if you repatch the thing to a different channel on your desk, it won't work... And that's assuming the desk can be automated... And if it's muted when the SID isn't at a 0 crossing, it'll click anyway... I think this one can be put down to "the usual SID bugs"

Welcome back from rehab!!! Yep Nope :( I'm spewin that I didn't grab the last few mouser had now :( Errr maybe ... I think TK has pushed the PIC to the limits of it's processing power this time, not just RAM :(

kris: Did you mean 'now to finish' mate? :) Wise: Life is really good at getting in the way for some of us. Don't sweat the year in hiatus, it's good to see you back at it :)

LMAO!! I am so jealous that you got to play with a cray 1 !!!! Even if it did take a few layers of your palm as an entry fee ;) I notice you were kind enough to spare us a graphic recollection of tearing your hand off the board ;) :'( it took me 5 reads to decide which was the funniest part, and I think I have a winner: ;D

Weird man. I thought it was OK on the v3 core though? If the 'bad' song name breaks on the v2 core maybe it is the PIC after all, and some bad RAM like you said....

a dry solder joint on the LCD data lines maybe?

Sorry mate, what I meant was to test that there is no break in the circuit. It doesn't need to be connected at all, just set your multimeter to the one that beeps when there is a circuit made between the probes. Somewhere between the core and J2 on DIN#2 is a break or bad solder joint there I think...

If the PIC works OK in the v3 core I think it's OK... After the screen glitch, does it crash or?

Hey version 1 wooooop! Hehehe I bet! Congrats man, right on target :)

Wicked :D I'll take a mineral water at your Melbourne gig heheheh Maybe one for after the gig, but I'd do that with your other switch statement in main.c too... Thanks for being thrashed by this "feature" so we don't have to!

Yeh but as Wilba said it will still cause a click :(

Re: Any C Sequencer examples? Thread has a possible solution to this. If you compile the app now, and search the output file for the switch statement, you'll see a nice tidy table, and you may notice that there are now only 5 temp variables used, instead of the previous 37 The trick is, if you have a single statement in each case, then SDCC creates a jumptable, so it's nice and clean.

Thx Wilb :) Sounds like the only way around it is an external VCA...

Heya bud. Try these. I've broken that notorious switch statement down so as to make a nice clean jumptable. The app now uses five temp variables instead of 37, and doesn't flip around like it used to. 25-26 should work now :) This is definitely the way to go with switch statements in SDCC. Let me know :) Edit: Does 'i' really need to be an int? mclock.h mclock.c mclock.h mclock.c

That's no good... Do you know what causes the click?

Hey whomper I think it's awesome that you're giving these bug reports for v3, but it might be best to put them all in the same thread, so that when TK returns he can see them all quickly and easily :)

Yeh it mentions an LSI controller but not which model... Fortunately it also has the protocol info in there, so you can compare that to the hd44780 datasheet and if they match, you win ;)

It seemed all OK but after submitting everything, instead of saying " your order is placed" or something, it said something like "Please contact these guys" and gave company names and addresses of a few distributors.

Damn, no online samples for us down under >:(

OK so we can only sample 5391-bst3 (not the lower LSB -5) but what about the 5391? Should I try for BST-3, BST-5, BSTZ-3, or BSTZ-5? Edit: Hey guys seeing as they are tight with samples don't everyone try at once. I am in a certain position which means that I am very likely to get some, which I will then share around... It's early days yet, you won't miss out :)

Yeh it might well be overloading things. 9V 500ma is no way going to be enough. Maybe someone can tell you how much exactly you'll need given those LED's.

great minds think alike. I looked at the ASM for just that and it didn't seem to go wrong, but when you posted, I double checked it to be sure, nd realised that I forgot to add the 1 to the case. That's exactly what happened. SDCC creates temporary variables to handle functions, called r0x00, r0x01, etc. in this case up to r0x37, and where it flips back to the first one, is where it goes awry (mclock.asm line 2686). Just for comparison, the vX uses 37 of these variables too.... but that's for 5 files. The most in any file is 12, the least two. SDCC really made unclean code of that switch statement. LMAO you'll be right about that I swear... Although timing is almost surely going to become an issue I think. But the split-switch should work...

Hey wasn't your plugpack 14VAC@1.3A? How many amps is the 9V?

Just go to the store and get a 9VAC 2A Plug pack. Of course, that much current might blow the thing to bits for all we know, because we still That's three times now :P ;D