stryd_one

Just like your computer, the core needs an Operating System installed, so that you can run applications. For the MIDIbox core, that's MIOS. OK :) http://wiki.midibox.org/ http://www.midibox.org/forum/index.php?action=search http://www.ucapps.de/

I should just mention that the hardware was also tested with the pre-compiled hex file in the distribution zip, and the J5 gates did not work. I'm of the opinion that this indicates a problem with the core, and my advice was to remove the aout module and just work on those gates first....

Thanks for removing it chaos, and especially for your good attitude. I wish all people were as cool about it as you! I hope that your money woes are resolved very soon. The problem here is not really the price - the problem is that it is not legal to sell a midibox without TK's permission. If you saw a midibox on ebay, they were also breaking the law.... I think it's safe to say that it's not so much about the law, as it is about respect for TK's work - because he does all this for free, it's not really fair for others to make money out of it. If you would still like to sell it, perhaps you could post in the Sale Requests section of the forum....?

Translation: "I need to spend more time reading the forum and wiki and ucapps." This controller would need to be a custom app.

Welcome aboard man. I noticed you posted in ithe italiano forum also - crossposting is always a good idea for multi-lingual support, but it's a good idea to post a link to the other thread in each of your threads, so they are cross referenced. Speaking of good ideas, it would be helpful if you could paste (not type) the logs from mios studio. It's probably best if you do not connect any other modules if you are having problems, that makes it easier to isolate the cause of the problem. I should direct you to the 'troubleshoot!' link in my signature ;)

LOL how much?! Thanks for letting us know, cicalone.

KDE is always an option for those users (like me) who prefer it (adding it to ubuntu and switching to it, is just a matter of adding one package) but because Gnome is a bit more user friendly, it'll be the default.

Reason I figured you hadn't read my whole post is that the last 1/3 of it explains the difference between MIOS, and MIOS Studio, and MIDI-Ox... But you still keep saying "MIOS" wehn you actually mean "MIOS Studio". Perhaps it's information overload.... My take is, use MIOS Studio whenever possible. It is possible to use it for MIOS upload, and for Application upload (as per the table above) because they are both hex files. It is not possible to upload SYX files from MIOS Studio, so you must use the alternative (MIDI-Ox)

BEEFCAKE

Heh, you did it again. You probably haven't had a chance to read my whole message yet ;) MIOS studio can only upload sysex in the form of hex files that it converts, but can't send normal sysex files - so for the upload of the .SYX file generated from your INI file, you must use a generic sysex utility like midi-ox. [table] [tr] [td][/td][td]MIOS/App HEX Upload[/td][td]MIOS/App SYX Upload[/td][td]Special upload features[/td] [/tr] [tr] [td]MIOS Studio[/td][td]Y[/td][td]N[/td][td]Y[/td] [/tr] [tr] [td]MIDI-Ox[/td][td]N[/td][td]Y[/td][td]N[/td] [/tr] [/table]

Yeh, it says 2009 not 2109 ;)

Ahh OK, I assumed (there goes that word again!) that you grabbed it from the wiki link, which is pointed to the new one. Sorry! Look, as I said, MIDI-Ox does work 99% of the time. Especially if you already know that your core, midi interface and java runtime are working 100%, it's not a big deal. The thing is that the other 1% tend to go really really south, sometimes mysteriously (because it should not be possible to make it this bad) ending up in a need for reburning a PIC or even a new one, and almost always resulting in many hours of support time (doh) In johnc's case, if I were him I honestly wouldn't bother changing back to MIOS Studio, because he has experience and lots of gear all working. Chances of being in the 1% are pretty low for him. In your case, however.... ;) Glad you like the forums man. The feeling is entirely mutual. Yeh the organ guys are hella helpful. They probably get tired of me always saying nice things about "the organ guys" :D Oops, new posts... Johnc, I'll explain why I felt it necessary to voice my disagreement... but first: you should know by now that I'm only a moderator for janitor duties bud. It's not like there is any "rule" that says <booming God-voice> "THINE SHALT ALWAYS USE THY ILLUSTRIOUS MIOS STUDIO WHEN UPLOADING" or "THY SHALT NOT COVET THY MIDI-OXEN!" </booming God-voice>:D Even if there was, I would have no involvement in writing or policing it. This whole thing: Is just a bit melodramatic ;) That day is still here, and it will not ever go away. Edit: now that I think about it that really is crazy talk. You feel like you shouldn't voice your thoughts, because someone else voiced theirs, and it wasn't the same? Does that mean the other person's thoughts are unwelcome? You don't seem to think so, but why do you feel that way about your own? Why should either opinion be exclusive? You kinda make out like my opinion has changed the forum forever, but not yours? Where's the fairness in that? Should I keep m own opinion to myself so that the forum can have an environment where all opinions are welcome? That's a paradox.... The whole thing is layers of parodox... I think you might be letting your emotions get the better of you man ;) That said, obviously I've helped with troubleshooting a lot of cores over the years, and in the process that has developed through that experience, when someone's core is going screwey and we're talking about uploading hex files, the first thing I do is make sure that they're using mios studio, and in the correct manner. I tend to try to avoid getting even to that stage, by recommending the safest option in the first place. That's not only for the person to whom I am responding (esag' in this case) but also with respect to any others who may read the thread in future. Even if you consider that esag is safe enough to try midi-ox, you never know who may read this post later on, and what their situation is. Obviously, different situations result in a different chance of failure. In your situation or mine, that chance is very low. In esag's maybe a bit higher... in the mystery-man's stuation...who knows.... Maybe his core is emitting blue smoke, and he will try MIDI-Ox instead, and make it worse ;) I'm being silly, but the point is, it's best to play it safe. As for esag's situation in particular, to be honest, "1%" is just a figurative number to say "not many" but it's probably more like 10+ in reality. Given that esag is already having some difficulty, he's also in another danger-zone that's more like 80% attrition. I don't think it's really a good idea, in this case. But my opinion should not dictate your actions, or your willingness to respond. If you've got an opinion, voice it! If everyone in the world kept their opinion to themselves when ever there was disagreement, we'd never talk at all - and nobody would learn squat, and this forum would be about banging rocks with sticks to make noise. Seriously man, all respectful input is good input I reckon, and you've always been respectful. Even though I have voiced a disagreement with you, I hope you feel I've shown you respect, as I try to do so equally for everyone. Oops another post. *phew* esag: try not to confuse MIOS (The MIDIbox Operating System which runs on the PIC chip in the Core module) with MIOS Studio (the java application that runs on the PC). MIOS Studio is specifically designed to talk to a midibox and perform midibox-specific functions like hex uploads and debugging, which is why you haven't heard about it elsewhere. I'll explain what the two do a little, hope it helps. At the least, it should give you some good search keywords. The OS: MIOS. You shouldn't need to worry about it. It's equivalent to windows on your PC, it functions as a platform to run your applications. It will pretty much just sit there and behave itself, if you treat it right :) The app: The app starts off as C code, which is compiled to generate ASM code (sometimes TK just starts there). The ASM code is assembled, and that generates a .hex file. That's the final midibox application. Same deal as an .exe file on your PC basically. But like a PC, you have to copy the app onto the PC to run it.... The upload: Normally, you have to use a hardware programmer to 'burn' a hex file onto the PIC chip. The MIOS BSL (bootloader or bootstrap loader) which is already installed if you buy from smash or mike, accepts sysex data to upload code over MIDI. Think of it like copying an exe file from one PC to another over a convenient interface, say, ethernet cable. While it does this, it also sends some messages from the core's midi output, to allow you to monitor what it is doing, and if it's successful. I'll come back to that. The procedure: MIDI-Ox: With MIDI-Ox you can send a .syx file with the required sysex data. Sysex file handling is a generic kind of utility for midi, as you seem to have gathered. There are many apps that could do this job, but MIDI-Ox is very popular. In order to obtain the .syx file, you have to use a utility to convert the application .hex file (see 'The app:' above) to syx. There is a Perl script which does this. Then, you just send the file to the midibox, when it requests a code upload on startup. MIOS Studio: MS basically does the same thing as the above, but in the one app. You open the hex file in MIOS Studio, and it converts it to sysex data (like the perl script would) and sends it to the midibox. The big differences are 'wait for upload request', 'smart mode', and the awareness of the core's protocol for reporting it's progress (see 'The upload:' above). These three features respectively provide: the restriction to send the file at the correct time, the restriction to only upload when the core says it is safe, and reporting of any errors in a human-readable manner. These are very handy to have, but they are not required for a successful upload. MIOS is very flexible, so as I mentioned above, any sysex sending app could do it. Naturally, the custom-built app for this purpose, has some bells and whistles.

Patient! HAH! (Get it?) (Apparently, bone marrow donation has strong wordplay karma)

Sweet! Hope you're not too sore and he's bouncing off the walls and develops a strange compulsion for mixing mud and wheels... or 'The Knack' :D PS: You give good gifts but you're too skinny to be Santa! Hehehe... That dude is gonna have the best xmas ever.

Thanks this! Noted your recommendation, and I'm glad it behaved well for you :)

Well is it 8 devices or 8 ports? You don't need one port per device, devices can share ports. The PIC core will probably never support more than 4 IIC_MIDI modules due to timing constraints. This is a router, not a midi interface, so there is only "standalone mode".

LOL!!

Yo dudes. Long time no speak! FYI we now have a repository from PPA. The team URL is: https://launchpad.net/~mbuntu The PPA URL is: http://ppa.launchpad.net/mbuntu/ubuntu There's a project registered although I doubt we'll need it. It's all empty... for now...

Yo, I did see a place that did it locally... Never tried them or priced them out though, so google beats my advice here... keep us posted man! I'm pretty interested in this myself...

Duh it is! Sorry, I was thinking 8 in total, and completely forgot the two on the core. *facepalm*

You said your queston was for TK, I hope we can all help :) You can do that, and more, on one single midi port, no need for a router in most cases ... This one supports 8 ports, in and out, and the data can be routed in any way you wish, so it would be ample for your needs :)

Hate to be argumentative but I don't agree with the above. As I always say - always use MIOS Studio, in 'Smart Mode', with 'Wait for upload request' turned on. The reason for this is simple - it does error checking, so if something goes wrong, not only is it less likely to break stuff, but also the user will know, and can post messages to the forum. Another good reason to use MIOS Studio is that there's lots of experience in using it so lots of people here are familiar with any errors/feedback that may occur, so there's more support if something does go wrong. If I had a dollar for every time I've seen someone toast a core by uploading with MIDI-Ox, I'd buy you all a beer. 99% of the time it's not a problem, but I'd never recommend to anyone to risk being the other 1%. Off-forum support via email or chatroom or whatever is often a lot more productive, but if you go that route, please remember to come back here and share the experience, so that others may benefit from it :)

"in the meantime"? I don't see how that doco could be improved, it's pretty much bang-on! Kinda proves the point really - I mean, when you work from that doc, it's pretty hard to get it wrong. It shows (graphically!) how the whole INI file thing makes it easier to modify the functionality of the box without having to understand some code. PS Props to the miditzer community for the help!

Hehhehe, somewhere in my mother's house, there is actually a tape of me singing and "playing guitar" on my first tune, at age 4.... Even if she can find it, and even if I would speak to her, either of which require a thin layer of ice on the surface of hades, there is no chance I'd share the recording online :D