1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

[SOLVED] So I bought maschine .... logic midi madness

Discussion in 'MASCHINE Area' started by doeLauw, Dec 15, 2010.

Thread Status:
Not open for further replies.
  1. doeLauw

    doeLauw New Member

    Messages:
    8
    Sorry guys need to vent a bit. Read a lot of almost similar topics and solutions and tried them all, sorry if this is "another" post. While doing this I also hope to get a bit of feedback, maybe I missed out something. Ok here we go;

    Been looking at maschine for a long time. I'm quite new to poducing and haven't got many plugins. Tryed battery and other drum instruments. Like maschine becouse it seemed very hands on and capable of editing your sounds without swimming trough tiny faders and knobs on screen. Combined with a good sound browser and seqeuncer seems like a done deal. Not to mention having a drum pad in your studio is also worth 200-300, maschine controller is quite good.

    Only thing that kept me from buying is that I saw many examples, demo's and videos of hip-hop like artists. Which is totally not my thing. I make progessive trance, uplifting trance and between.

    Took the dive and got maschine.

    I expected to be able to use a workflow I saw in a 1.5 demo movie before. That made me say, jup maschine is worthy for my money. The workflow I saw;

    Maschine as plugin, lay out beats, record or drop your patterns in your daw, able to arrange this and fine tune midi a bit.

    My problems while trying this:
    • Maschine always plays patterns it has loaded while playing your daw, ok we can work around this by selecting a empty scene before we go back to the daw.
    • Logic seems unable to record midi from maschine, seems a plugin restriction.
    • Drag & drop midi makes NO sence. It doesn't do what your expect.
      • When you choose a root note for midi export and playback your would expect maschine to reserve midi notes for the the pads and groups. It's just not doing that.
      • Root note is ONLY working for the pattern you drag first, after this it ALWAYS goes to c0 c-1 etc except if one is taken. Not 16 notes lower or higher as you would expect.
      • It doesn't reserve 16 midi notes a group? Jup you can't trigger al 16 pads with midi notes.

    I also tried to run maschine stand alone and sync up with the midi clock from logic.
    • Midi sync works well.
    • Unable to record into midi! Why the hell isn't maschine stand-alone able to trigger midi notes in it's native mode. Going into midi mode on maschine is pretty lame. Setting a pad to midi out makes it a controller and not a sample player.
    • I can't get logic to send midi notes to maschine without a plugin like midiO, but this can be my failing (hint anyone?).
    • Sending midi to logic to trigger the pads gives the same problem as running the plugin. Not al the pads an be reached by midi note and the root note logic is just as nuts.

    Now I'm praying that 1.6 midi improvements as mentioned do anything about the problems I have to get a nice workflow with maschine and logic. Beside that I also have a minor hope that I'm missing something, that someone says ... DUDE do this and then it works the way you expected.

    Thanks for reading!
     
  2. sowari

    sowari Moderator Moderator

    Messages:
    27,759
    • Logic seems unable to record midi from maschine, seems a plugin restriction.


    this is a Logic or rather Audio Unit Plugins limitation.

    MIDI Drag n Drop works if you set up the Sounds to MIDI Batch Setup correctly. please re-read what it says in the Manual and try again. if it does not work, please give an exact detailed explanation of what you are trying to do.

    i don't understand Unable to record into midi in fact i don't really understand any of the last bit :confused:

    please give examples, - preferably with some Factory Kits/Sounds - so i can understand what you are trying to achieve.

    and..... the Maschine Controller is meant to be able to play the sounds within the Maschine Software and act as a MIDI Controller for other software. so for me, putting Maschine into MIDI Mode is a huge bonus and is not lame.

    sowari
     
  3. doeLauw

    doeLauw New Member

    Messages:
    8
    [edit]Forgot to say thanks for your reply![/edit]

    If I setup midi drag and drop according to the manual it doesn't do what you should expect here is my problem.

    Group A: 16 pads, 16 sounds.
    Group B: 16 pads, 16 sounds.
    Group C: 16 pads, 16 sounds.
    Group D: 16 pads, 16 sounds.

    Screenshot: screen01.jpg

    Made maschine trigger each pad in 16 length. Set export midi dialog to "notes" and root note "-2c". You can see the exported group A B and C, din't export D since maschine starts to ask for it's root note again ... which is wrong. At export group C you can already see maschine going wrong! You can clrearly see midi triggering group B pads while it should trigger group C.

    This is also what I mean in the second part, running into the same problems with maschine stand-alone. Then I have a extra problem .... which might be just me. I'm also unable to send midi notes from Logic to maschine, there for I use a plugin called midiO.

    Yes off course is the whole midi controller feature a huge bonus. In fact this counted in getting maschines the first place. But it should not be necessary to put maschine into midi mode to trigger it natively. Meaning stand alone maschine should send midi notes in native mode .... hey I think this is my whole point. "Maschine should stick a midi note to a pad, for triggering AND sending."


    SOLVED!

    Yes i should pay better attention to the manual, but still it doesn't work as they ment it to be. Midi settings for each pad stick to the root note C3 .... this is the problem. Either manual edit pad by pad. But the quick way to do it is using midi a channel for each group.

    Fastes way to proper midi programming pad triggering in Logic:

    Right click group A from the scene menu. Chose Batch midi, now LEAVE the root note at C3, higher is possible lower isn't. But higher doesn't leave you much room for more pad groups. So suggest you pick midi channel 1 and root note C3. Repeat for group B to H leave the root note at C3 and group group B midi channel 2, group C channel 3 ..... etc.

    Now you might want to store this default setting somewhere, as a logic template is a good idea. Even better update your current template.

    Now enjoy proper midi dropping and pad triggering.

    Ah and don't forget you can make extra midi tracks for maschine, allowing you to play for example your kicks at group A toghter with your bass at group B. Right click track header chooser reassign>mixer>maschine.

    Now I'm loving it!
     
    Last edited: Dec 15, 2010
Thread Status:
Not open for further replies.