stryd_one

Heya ptitjes :) I think you were around when I was talking about using CAN in a sequencer the other night in the chat room... The implementation would be similar to a couple of things that you mentioned in case 2, IE: having broadcast messages rather than ID-based communications, and messages triggering a core to transmit another message in response. I think Case 3 would be essentially the same, except that the triggered message would be sent to another port (not CAN but DMX or ethernet or IIC MIDI or something). If you want to go ahead with this idea, please let me know, maybe we can work on this together? That said, I am extremely aware that in doing things like this we are pushing the boundaries of what is practical with an 8-bit micro... It's easy to bite off more than you can chew, be careful ;)

How about a Fatar keybed and case with a nice controller brain for AUD$100? KAWAI MIDI KEY MDK61

Last time I used FL I used SPP for these functions and everything could be mapped to a midi event, so I will be very surprised if it's not possible. If you don't have a multimedia keyboard there are all manner of ways to remap your keys and create custom shortcuts.

Heya shobley. I'm glad you've taken so long, because I am now the 2nd slowest midiboxer :D This is from TK's voltage test document. Take note of the bold parts: Pin 11 should not be connected to J5... Please check : mbhp_core_extract_measuring_vdd.gif MIDI Troubleshooting

Translation: I need to read the wiki and come back later ;D

Welcome aboard!! Hmmm, I don't think those are SID chips ;) Depends... You should be more concerned with the driver, than the dimensions. Don't confuse Operating System (MIOS) with Application (MBSID) Not to worry... You will probably notice that I've raised as many questions as I've answered ;) You can find a lot of information on ucapps.de and the forum and the wiki. I definitely recommend a LOT of reading on those sites, and you will see that mostof your questions are answered :) Good luck!

...which is probably a good thing because it allows for a plexi (or similar) plate to protect the screen...

Well quantising just means that you are making a value fit within a predefined set of values ...so the way you and I and most people think of quantising is on the time scale, rather than quantising on the pitch scale. Only people who work with CV really say 'quantising' to mean 'harmonising'. It is technically correct, but I think that because traditional sequencers only quantise on a time scale (not pitch) then we don't think of it that way.

That will be a switching PSU, so not really suitable for an MBFM.

Congrats neb! Take your time and work on a copy when you feel like it. There's no rush, but it would be a shame to roll back to the original and lose all of your changes forever.

Heheh I see you are counting from 0 when typing english and not code. This is how you know you are spending a lot of time coding ;) You are thinking about quantising the timing of the values, but sneak is talking about quantising values to a certain range (IE, note-to-scale) Terminology mix-up there for sure ;)

Yarr, why are pirates pirates? Cause they Arrrrr! Pirate paraphernalia always welcome here :D

What? Peanuts?

You're optimistic buddy ;D Yeh It is possible, but impractical to the max! No hijacking / flaming please playbo$$. I have a rule - if I need to edit a post that many times I haven't thought it through enough :)

1 - You'll have to ask AC if the Sensorizer has enough codespace for the log conversion tables... 2 - Easy

My Five Dollars and Two Cents: Thanks dude always encouraged :) I also think that I like about 90% of what you've done in this particular instance, so thanks :D I think that when you are making small changes, here and there, it is OK to just go ahead - and I don't want to discourage anyone from updating the wiki any time they see fit. I think the final rule is always that it can be rolled back to the original, so go crazy. Just don't take it personal if someone trashes all your changes ;D That said, maybe when making such large, high profile changes, especially with regard to projects or documentation where any person has invested a good deal of effort, it may be best to put a quick post here to see if it's OK. I would maybe recommend making a copy of the page you intend to replace, and editing that and presenting it on the forum for opinions. We can come back to these ideas later.... Cool. Linguistics are tricky in such a a varied international community, so any clarifications are good. The dogmatism is in such an obvious place with good reason ;) Without it, what happens is, people read half of it, get all excited about the fully sick MBFM, come to the forum asking questions that are answered later on in the page they are half way through reading, and then we tell them to read more, and they take it personally and get all offended, and then we have another thread where we explain at length that we really aren't bastards, just that we know the best answer is already written down ::) ;D We'll come back to this subject later too... I know what you mean, but I said I'd come back to this.... I think that before you slice a bunch of people's stuff up you prooobably should ask first. I do know what you mean, but yeh. That wasn't yours, hands off ;D If you want some solid background documentation you can feel free to come and be my typist for a few weeks :P This is why editing on the wiki is encouraged. I don't think that relegating pages to a deeper level in the tree due to lack of supporting documentation is the solution, I think increasing the documentation is the solution. I don't think that relegating pages to a deeper level in the tree due to being of a specialised nature is the solution, I think that's the problem - people with specialised requirements will have looked a lot and are less likely to bury themselves in the wiki to keep searching - they need it up top. Agreed here. No harm no foul ;) Hehehe That's actually not what I meant to say, but I thought I'd add...it is like saying "No harm was done, so there is no problem to speak of" True. I think that after some time to 'evolve' the wiki structure becomes obvious and links will naturally move to a more logical position anyway, as with your links mentioned above Unfortunately, sometimes we do roast someone who has searched and searched to no avail. Most of the time, the sad reality is that we roast people because the questions they ask make it obvious that they have not made sufficient effort in their search... It's usually easy to spot the people who posted before spending a significant time reading. Sometimes I get it wrong, and you'll know when that's the case, cause you'll see me apologise :) Most of the time, we end up defending ourselves. See I told you I'd come back to that ;) That is true though, and help with that task is always encouraged, so thanks again :) That's the idea! Well that depends on the person. What if they're looking for a sensor project or drum machine or algo sequencer? ;D You're assuming that the reader is already someone who wants to invest time in the midibox documentation like you do and like I do. Maybe they're checking it out to see whether they want to do that kind of reading or skip to the next site? I like your edits but I think that is the core failing in your adjustments - you've edited too much with your own perspective and not the perspectives of other possible readers. MMmmm peanuts. What? Oh - This is where (See, I came back to it, eventually) a copy of the original is a very good idea - no harm editing the wiki but leaving it mid-edit in public spaces is a bit intrusive. nebula Midibox Addict *** Posts: 109 I think that's a bloody good effort for a dude of 100 posts!!

Follow TK's link. Follow link to documentation on wiki courtesy of ultra. Remember advice from TK on future compatibility. Question Answered!

Think of it as silicone offsetting ;) Edit: This topic has been moved to Miscellaneous. LOL Good idea!

Yeh please keep it on the forum :)

LIDL?

LMAO yeh.. I always tell people that if they want to see Dragon products do proper speech recognition without training it for a year, they need to remember it's an American product, so the vowels sound nothing like English spoken anywhere else. Fake a thick yankee accent and voila! It works!

Yeh altitude can you please edit that post? :) Edit Thanks!

Hey neb, you ever considered just disconnecting power to the fuser?

Stryd_one's Law: Sequencer projects will always require a time commitment which is an exponential function of the complexity of the design and the originally predicted timeframe. Meaning: It's gonna take way longer than you think because it's not as straightforward as it seems ;)

You have to edit the ASM files and reassemble the application to change encoder types. Do a 'find in files' for the string 'ENC_MODE_DETENTED' and you'll see it. That goes for 1.7303 and 1.74685 also, people :) Edit: and seq 2.4. Wow this is the hot topic in the chat!