stryd_one

http://www.midibox.org/dokuwiki/windows_toolchain_core Get into it. And cosmo, please, pretty please, with fricken sugar on top - use the code tag, and copy and paste errors. I won't help you again in future if you don't, because I figure that if I have to ask more than once, you don't really want my help anyway. Please see the Golden Rules of Troubleshooting #1 #4 #5 and #6. Edit: I'm still wiriting that doc, so if you finrd any problems please let me know and I'll fix it right up and walk you through it. I'll jump into the chat room now and will be there for a few hours.

Whatage? ;D

I am literally writing the how-to document on this right now.... hang on for a few hours :) Edit: Short answer for you- you need to make sure that the paths are set correctly

Well it seems that your PC isn't writing correctly to the LCD... You might as well hook it up to a core module and test it in the real-life environment it will be used in :)

You're right sasha it would be heaps easier with the pins around 90 degrees....

I don't see them? Is that the right number?

You make such good use of that CNC man, I'm so glad you have it available to you :)

Awesome, thanks TK!

Condolences mate. I hope the midibox helps cheer you up.

Hot.

[me=stryd_one]hits nILS with a drill press and steals the MP3[/me] "Here you go TK" ;D

Have you tried the ain-din-dout 128 app to see if the encoders behave there? I assume the app uploads in mios studio without errors?

Yeh the wood work and panels really work well together, nice seq!!

Damn Twinny what'd you do to it?! :D It's not just fixed, it's faster than ever!

Well, you don't *need* to upload it, but, you should still receive an upload request and if you try to upload MIOS again, it should work. And no you're not lame. New maybe ;)

Man that is tasteful. I agree with sasha on both points there...

I disagree! :) Nice one man!

Let us know how you go with yours man... I've had my kit sitting here for about a year or two waiting for that free afternoon to come along hehe

MMMMM that's some goood sh*t maan.

1) Use the search, this has been done before, I'm sure. 2) What's up with the near-duplicate posts? 3) What's up with the freaky tag? (deleted) 4) Did you read my post about SNR? 5) .... actually no ... I think that covers it :)

Thanks mate! @all: Show your love .... button's in the top right corner ... Buy Twinny ein bier ;)

Slowdowns and even complete dropouts have been occurring ever since the switch to the new host. It started out as the occasional laggy period, but has been getting progressively worse. The whole midibox.org site becomes unavailable, and the various error messages seem to be indicating that the host is overloaded. Once I was sure that it was not just me, and that it was not a temporary issue, I started to collect any error messages I received, so I could PM them to Twinny - but that's not many, because usually it just times out. Here are the two messages (yes, only two, sorry :( ) I've grabbed so far, with the URL I was attempting to load, then the date and time (Melbourne Time - that's Aus. Eastern Daylight Time): http://www.midibox.org/forum/index.php/topic,11102.msg86645/topicseen.html#new 270308 1717 Connection Problems Sorry, SMF was unable to connect to the database. This may be caused by the server being busy. Please try again later. http://www.midibox.org/forum/index.php?action=unread;all;start=0 280308 0100 Fatal error: Out of memory (allocated 262144) (tried to allocate 19456 bytes) in /home/midibox/public_html/forum/Sources/Subs.php on line 267 Messages like the last one seem to be most common, but they always fail in a different line of code, so no particular page or code seems to be causing the problem - it's just that the line shown is where the server simply lacked the resources to perform the task. I'm guessing that Twin-X is already aware of these problems, but if you'd like to help, I would suggest taking down as much detail as you can, and storing it somewhere in case he needs it (he may ask for the errors to be posted here, I don't know) @Twinny: Please let us know if there's anything we can do to help :)

Totally dude, the opto's are flakey!

The same problem has also recently (in the past two weeks) been caused by a working opto inserted backwards, a dodgy midi interface, a bad upload to the PIC, a short circuit, and a driver configuration problem. Feel free to just throw parts at the problem at a guess, but if you don't get lucky, then you could waste time and money. Hmm. If it's a bad optocoupler, then you'll find out in the midi troubleshooting (that you said you'd done, and then said you hadn't)... Do those tests, and you'll be well on your way. When you've done those tests, you'll have logs regardless of your core's working status. The logs, and the other results of the tests, will indicate the source of your problem(s). May I direct you to my signature, rules 1, 3, 5 and 6. Hopefully 8 will not be far away :)

Right underneath the sticky post that says: Please Read Before Posting New Topics: What is a "User Project"? Nice one ;D