stryd_one

Sounds like your LCD is drawing too much current, and the PIC is starting and stopping over and over. When you turn those pots down, it allows enough current for the PIC to run. If that's the case, it's possible that you've shorted something on the screen. If you disconnect the backlight wiring completely, how does it go? Did it ever go longer than 4 or longer than 2? What effect did turning each of the pots have?

I don't know what the official policy is ;) but I reckon build logs are cool! There's nothing quite as good to learn from, as seeing it done. I love that you've kept a partslist online. Will Google keep it hosted? or will you need to host it here?

LMAO

Sounds like it's time I started working on the MIDIbox Master Keys project...

I'm no MB64 expert but can't you change the notes that the buttons send?

There ya go then, there's the source of your noise :)

Hi all, We shouldn't really have any need for this now, but I thought it worth saving here so it isn' lost in the SDC Forums...

Wow mate that's a heck of a score. I would use recycled gear but it's really hard to find identical parts in larger amounts like that. You must have pleased the rackmount gods ;)

Yeh I like that too... Looks familiar to me, was it a Cisco or HP box by chance?

If you mean clock speeds, yes :) If you mean a delay as in an offset, no

Yes please :)

Cool :) Go for it :)

Yeh and they're nice to look at too :) Good luck with the box!

ohh 3 against 4 is boring, you can do that with triplets :) I'll do that and 5:4 just for kicks :) Nah roxanne is straight 4/4...

Wise's switches would likely be fine, but I thought it worth mentioning something you haven't yet considered is throw length.... No point having a soft touch button if it takes too long for it to throw the switch, know what I mean?

Sounds like a short circuit mate :(

The regulator shouldn't get hot with just the LCD and core.. If you remove the LCD just for now, then you can narrow the problem down to something wrong with the core or PSU. What are you powering it with?

;D F@*&'n eh baby, I am one excited MF right now. OK so I now have what I consider to be the first working alpha build (v0.1 Build 48 heheh). It's verrry raw, but has 4 subclocks fully working, with twin patchbay routing to tracks, to play a step or increment to the next step, on one of two tracks each with 16 steps,(it's only on a 452 right now, a 4620 will improve that somewhat. It's fully expandable, once I get it on a 4620, even without the sram it will have enough to carry around 12 tracks and 6 subclocks and all I need to do is change a couple of defines.) Note offs are working, relative note numbers are working, the event engine is working including manually buffered recursion and function priority (so that modifiers on tracks will work before the previous tracks play midi data) BTW moogah, this means that your request for an "if this happens then do this" capability is now implemented. I always wanted the feature and when you asked for it, I had to find a way. The end result is that the majority of the operation of the sequencer is run in this manner. I'm really glad that I did this now, as it made the design more modular. There is no user interface to speak of, all the values for the sequence are initialised and can be changed once I hook something in, but at the mo, it's just hardcoded sequences and a start button implemented by a midi note heheheh. I need to make fairly major changes to the structure of the data storage, both to improve performance and to prepare for the SRAM extension, where only the next data needed from each module will be stored in PIC RAM and it will be pre-read as required. I also need to pass the clocking and track stepping functions into the event engine so that those events will be able to trigger events in other modules, basically meaning that you can syncronise track and subclock start points and such. So yeh, there is lots left to do, but the sequences can be hardcoded and played. I just made a contrapuntal 16:11 polyrhythm, a thing where one track modulated the current step or the start and end steps on the other track, and a weird thing with a 1/16 clock and a 1/5 clock, patched to two tracks like this: play step advance to next step Clock A track 1 track 2 Clock B track 2 track 1 And track 2 playing in reverse just cause I wanted to hear something weird. So you guys who wanted to hear a demo, what do you want to hear? Remember, only 4 clocks and 2 tracks for now...

Read the first post in this thread :)

MB-Link wins :)

Correct again. Don't worry about asking questions, it's all good. You seen my postcount? That is spamming :-[ Sometimes it is actually better to start a new thread, as it reduces long threads and makes it easier for others to find answers when they search... But not to worry :) Here it is: A search for the function on the forum will give you the juice.

I think the problem is that we are still finding out about how and why SDCC works, and every time we answer one of our questions, we make some more! Welcome aboard the rollercoaster ;)

Oh my bad, sorry... :-X

This should be a snap, although I suspect that a more flexible method would be to map the same CC to both Ableton track faders, with one inverted in software :)

Nothing happens? How do you mean? This is becoming clear that it's a wiring issue....