stryd_one

;D The way it should be, if you ask me :)

Good news guys, I've been doing some experimentation and have figured out what's going on with all this drama about large data storage and arrays. I'll write a documentation on the wiki shortly with full instructions. Before I do, I just need to find out some info about memory use on the 4620 so I can document that too.... But that's one for another thread. In short: Arrays can be addressed with >8bit indexes, no problem, but they attempt to allocate more ram than is available. The symbolic name trick from vangelis (and the sdcc manual) posted previously works like a charm :)

The results are in: the arrays can be addressed with >8bits (so array[1024] is still OK) but any variable including the array's total size, is limited to 256bits. This limitation can be overcome by using a customized linker script. I will document this on the wiki shortly.

That is definitely the answer, by the way. Worked for me the other day. It seems the pointers are required for the arrays.

Yeh I think the POKEY would be a much better candidate... but the speakjet should keep us busy for a while before then ;)

That thing would make it soooo easy... OSC over UDP or MIDI over TCPIP (as opposed to MIDI over Ethernet, which doesn't use an IP stack) would be a snap... But the low baudrate could introduce timing problems, it'd be like using a 90% full pipe. Pretty costly too, I'd hate to buy one and find out it won't work :( Do they do samples? ;)

AC that sounds awesome!!!

I don't think that's supported... You can put the PIC from the 2nd core into the 1st core and program that. I think that this won't work because messages sent via MBLink aren't notified in the same way as normal MIDI.

Is that a compile error or linking/assembling?

How about this one from cmios.h.... It's an 'int' and sdcc says int's are 8-bit only.... What if you change it to a char?

Ohhh I understand now sorry.... Man that's a pickle. Whatever is wrong with it, sure is not obvious! I personally would put some code in there to get the app to send the variable's values in sysex strings, so you can see exactly where it falls over...

Moogah I think you're using a different technique to artesia - he was using flexible rubber tubing. You're doing it pay_c's way, by cutting solid acrylic rods, right? .... Just thought I'd clear that up, causeI think you might be comparing apples and oranges ;)

Hi AC.... I've looked this over and there's only one thing I'm not so sure about - the /100000 . Even with TK's tweaked libsdcc, only 16 bit divides are catered for. Have I missed something, or is this algorithm not going to work? Anyway you could get around it by doing a right shift and dividing that... Otherwise therre's our old friend __ASM ;)

Basically, the watch dog timer (WDT) resets the PIC if it locks up. What's the plan there HawThorn?

Sure, just fly me from Australia ;)

There's no way I could describe it better than this: http://www.howell1964.freeserve.co.uk/parts/76489.htm

Hi JB, welcome to the board :) If you are interested, it would be great if you could make a wiki page about your project. I would be happy to make the pages for you, so all you have to do is type :)

Hi Hai, This is maybe not the best place to discuss PICBasic projects or standard MIDI File players, as the MIDIBox project is neither of the above... but you may be able to use the onboard RAM or EEPROM of the PIC, depending on which model, otherwise you would need an external storage device Good luck Stryd

Heya AC, just so you know, I also plan on replying to that post but I've been a bit busy and haven't had time to research it... I'll let you know.

It's all about dollars. Projects, as you both know, being in the industry with me, get a fixed budget. Once the budget runs low, things that might normally get fixed but aren't critical faults are deemed, as OG said, "good enough" by the bean counters. I don't blame the developers themselves - the guys actually cutting the code, but their upper management. But they're just doing what they have to do to run the company at a thick profit and keep the pockets of the few nice and full, and giving the consumers 'close enough' to what they want to keep them buying. It keeps the company going and that keeps the consumers happy. This is why money talks. If the company stands to lose a lot of money from a bad reputation caused by saving a measly few grand for developing postfixes, they'll spend the money, and save face. No threat of a bad rep means no need to spend the money, means no fixes :(

Thx Seppo :) Hope you enjoyed the holiday!

That makes two of us. I heard those 6582a's and I instantly wanted some :)

I'd also wanna test it with highpass and bandpass... Would you mind measuring what freq does the oscillator roll off at? No point in making the high point of the filter cutoff higher than that.... I checked the datasheet, but to make the formula work I need to know what rate is the SID clocked at. If anyone knows off the top of the head, could you tell me, otherwise I have to code-dive ;) FCMax = Filter Cutoff Maximum C= capacitor value The E thing is scientific notation (exponential), where the E represents "times 10 to the power of" You could say FCMax = 8.2*10-5/C The C value is measured in whole farads. Nanofarads are farads*109 pmaCalc will take this equation: (I highly recommend that software! Really, check it, it's free, and it's small, and it kicks serious ass, test it for 10 minutes. No I don't work for them hahahah) 8.2E-5/(CE-9) Just punch in your value for the capacitor where I have the C. For 6.8nF: 8.2E-5/(6.8E-9)=12058.823529412 for 2.2nF 8.2E-5/(2.2E-9)=37272.727272727 For 22nF it's 3727.2727272727, which is a lot lower than we thought.... Now how do we know that changing the values might not change the linearity of the cutoff? Speaking of which, making the curve exponential would be fantastic ;) Full range, and good control in low freq's.... Nice.

heheheheh 2 months till oktoberfest, AC ;)

I know it's not flameage :) You two especially are too nice for that :) I know about this stuff because it's my job to fix busted IT systems... Unfortunately. hehehehe Oh and yeh, I did used to write them, but that was maaany years ago (Back when payloads were nasty and trashed your motherboard permanently or nailed your hard drive. I grew out of such things). LOL @ 'am I on crack'. I know what you mean, I didn't believe it at first myself.... Took me a while to find this link cause it's old as dirt, but here 'tis. http://www.us-cert.gov/cas/bulletins/SB2005.html Scary huh. What's really scary about this is the number of people, myself being one, who before reading this, are convinced that Windoze is by far the buggiest thing around. Shows the power of propaganda to fool the masses, and what large fools we make of ourselves by believing it. I'll get to that other post in a bit :)