Jump to content

MIOS and Fruityloops


Guest tub

Recommended Posts

Hi all,

I've just started collecting bits to make my pic 18F midibox. I wondered if anyone had any ideas on the best way of making a general purpose midi controller (mainly for fruityloops and cubase).

atm i'm thinking of going the MIOS route, but i can see that there might be advantages to using the MB64 firmware.

Help! :)

Link to comment
Share on other sites

Hi Tub,

you definitely want to go for MIOS: the old PIC16F firmware will vanish from my website sooner or later (to avoid unnecassary confusion) and the MIOS based version will provide some new, useful features like a remote control via MIDI, up to 128 banks, on-screen MIDI event & labels editing, jumpless pot group morphing... in addition to the known functions of course... :)

Btw.: if there are any beta testers who already own a MIDIbox64 and want to test the MIOS based version (which has grown up in the last months but isn't 100% compatible yet and comes with 0% documentation) just contact me.

Best Regards, Thorsten.

Link to comment
Share on other sites

Thanks TK, that's what i thought... but it's nice to know that you're on the right track sometimes ;)

I'm still unsure about what application to run on MIOS once I get this box set up though... the only app that seems to support everything so far looks like LC, but i don't need full logic control emulation.

Thanks, Tub.

Link to comment
Share on other sites

Thanks TK, that's what i thought... but it's nice to know that you're on the right track sometimes ;)

I'm still unsure about what application to run on MIOS once I get this box set up though... the only app that seems to support everything so far looks like LC, but i don't need full logic control emulation.

Thanks, Tub.

Why not try and make a 'for Fruityloops dedicated' application for MIOS, just like there is an LC?

There are a lot of Fruityloops users and i think it would be a welcomed addition to the already nice list of MIOS applications....

Link to comment
Share on other sites

Kinda what i'm thinking, although i've gotta build the thing before I start programming (or learning asm properly). I don't think fruityloops has any default midi bindings though, although you can link any controller to any parameter in FL, which is nice :)

I'm also going to try and write an app for MIOS that allows you to connect a drum trigger pad to an AIN and use it.. that would be awesome, and fairly easy.

Link to comment
Share on other sites

I can try it in my holidays next week, if you want to email it to me, TK, but my spare 18F is a suspect... all the DOUTS stopped working one day on my LC, and I swapped PICs, and it was working again...  ??? But I don't have DOUTs connected on my MB64 anyway...

will the MIOS MB64 work on Greg's PCB?

BTW, I can't remember why, but my MB64 always seemed to work better with v031 than the later versions. (I think it was a trial version, the first one with the dynamic pot jitter filter, and the PWM dimmer disabled) But I have a few ideas to reduce jitter now anyway (electronics mods)

bye, from Steve ;)

Link to comment
Share on other sites

I wondered if anyone had any ideas on the best way of making a general purpose midi controller (mainly for fruityloops and cubase).

atm i'm thinking of going the MIOS route, but i can see that there might be advantages to using the MB64 firmware.

the 'best' way ? I think you should have an extra look @ the MBHP gallery  ;)  the power & coolness of MBHP & MIOS is to build it how you want it.

General purpose is sold by Doepfer, Kenton & the likes  :)

You can link floops to whatever controllerbox you want; more, since Fruitystudio you can build 'panels' (like studioware in cake, I bet cub also has features like this) that match your HW designs even, check out the 'dashboards' in FloopsStudio.

greetz

Link to comment
Share on other sites

You can link floops to whatever controllerbox you want; more, since Fruitystudio you can build 'panels'...

The annoying thing about FLoops is that none of the links are set by default, so you have to make them all manually.. or make a template to work from unlike Logic and Cubase that have their controllers linked by default to values.

I guess there's arguments for and against this, but it makes it annoying to make a controller that works straight away for FL :/

Link to comment
Share on other sites

I think this is one of the best features of FL!

so, you just need to make a template within fruityloops, using the same controllers that cubase uses!  ;)

I think the real annoying thing is that fruityloops dosen't support motorfaders. But then again, I'd rather do my mixing in one of the high end applications, depending on financial resources!

BTW, can the rotary encoders on my LC be used to control fruityloops? I still haven't figured out how to get into GPC layer yet!

Link to comment
Share on other sites

BTW, can the rotary encoders on my LC be used to control fruityloops? I still haven't figured out how to get into GPC layer yet!

Of course!

Just assign one or two of the following IDs to the buttons of Layer A or B

#define ID_MBLC_SWITCH_LC       0x94    ; switch to Logic/Mackie Control Emulation (like radiobutton)
#define ID_MBLC_SWITCH_GPC      0x95    ; switch to General Purpose Controller mode (like radiobutton)
#define ID_MBLC_TOGGLE_GPC      0x96    ; like a "caps lock" key
#define ID_MBLC_HOLD_GPC        0x97    ; like a common "shift" key

Best Regards, Thorsten.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...