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

Maschine still painful when using DAW's

Discussion in 'Feature Request Archive' started by CakeAlexS, May 12, 2015.

  1. Mr Mahogany

    Mr Mahogany NI Product Owner

    Messages:
    722

    This is me EXACTLY. Its used to be easy up till 1.8 to just load kits ,try sounds,load kits ,try sounds as much as you needed as fast as your computer allowed. Now, like Eddie, I have to give up trying to work quickly. I really would use 1.8 but I have 20 expansions many of which only work with 2.0 Right now I wish a company with deep pockets ,like Steinberg, would make an irresistible offer to NI to license the Maschine format and make a simple pad controller that loads Maschine expansion format. I would dump Maschine the next day. I think NI has decided to focus on stand alone users and are not going after DAW users like recording artists and such. The hope seems to be that folks will want to drag and drop and use 2 sequencers ,not worrying about wasting time when changes or experimentation is needed
     
  2. Eddie Jag

    Eddie Jag NI Product Owner

    Messages:
    319

    I would love to keep the Maschine VST as everything EXCEPT the midi and arranger part. Why dont work like Komplete Kontrol and just write midi DIRECTLY into the DAW? How is that so difficult. They could even assign the pads to notes instead of channels and just lay them out like it is in Battery. I just dont understand this ludicrous concept of them trying to FORCE this DAW down our throats. No one that I know who is serious would ever consider using Maschine as their DAW. I mean it's laughable... I don't even know where to begin trying to arrange in their mess of "patterns" and "scenes" that can only duplicate the same pattern per group. It's just so far fetched for them to believe that anyone actually gives a **** except for the super casual beat maker. I use the standalone to get groves and ideas and get somewhat of a master pattern down. From there I would open a DAW and have to drag and drop everything back in. Then I try to avoid using Maschine cuz its a hot mess. But obviously if I need to tweak drum parts, which I always do I have to go in and fiddle with the clunky VST again. I just dont understand how Komplete works so simply and amazingly and they still can't get a halfway decent crossover from VST to DAW without forcing people to write their music in their shitty excuse for an arranger.
     
  3. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    That's where ARA integration comes in. Both could actually work side by side quite happily.
     
  4. Eddie Jag

    Eddie Jag NI Product Owner

    Messages:
    319
    Please explain. I'm not familiar with ARA.
     
  5. Pandeiroman

    Pandeiroman New Member

    Messages:
    3
    +1 On this issue NI! Please help streamline integration workflow with DAW's - specifically Logic X here. I have been trying for months since purchasing Maschine Studio & Komplete Kontrol S49 to find the best way to integrate it into my Logic productions to no avail. Just trying to create a simple default Logic Patch for the Maschine plugin to help speed up the long tedious process of selecting corresponding midi & audio channels to work with maschine 2.4 in Logic (10.2.1) only to find that when I then change a group (i.e. try out different kits) all my audio and midi settings to the DAW are reset to default and I have to start from scratch again. This is beyond frustrating and totally disappointing for a professional piece of software (that isn't cheap either!) in 2016. PLEASE address this so we can continue to want to support your platform!
     
  6. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    Link in OP. Thx.
     
  7. jlarrucea

    jlarrucea New Member

    Messages:
    8
    +1 NI Please fix this! No possible full integration with Ableton Live (Drum Racks) until the Sounds Output settings int he Group are kept when loading a new kit!
     
  8. Mr36

    Mr36 NI Product Owner

    Messages:
    8,454
  9. jlarrucea

    jlarrucea New Member

    Messages:
    8
  10. Kristyan

    Kristyan New Member

    Messages:
    15
    I suggest that people who are annoyed as I am by this "anti DAW integration workflow" state, should give bad reviews of maschine on the main music gear databases (Thomann, Audiofanzine, musicradar, musicianfriends etc...)
    If just 20 peoples do that, they will begin to fear about loosing money and maybe spend one or two weeks to fix this design error instead of trying to make maschine a DAW.
     
    Last edited: Feb 27, 2017
  11. Keir @ NI

    Keir @ NI Community, man NI Team

    Messages:
    2,652
    I'll drop my reply from another thread here for clarity.

     
  12. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    Off topic. This has nothing to do with the feature request which is hopefully going to be implemented by NI. Please go somewhere else if you don't want to talk about the enhancement (see opening post). Not helpful we aren't asking for patronising lessons on how to make music here or being told to sell up.
     
  13. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    I'll paste the OP below as you seem confused. This is the topic. As stated NI has already acknowledged they are looking into this.

    Somebody posted a link earlier on their statement perhaps you should read that.
    https://www.native-instruments.com/forum/threads/sound-i-o-persistency-when-loading-groups.313419/

    FYI "NI's Concept" isn't just your concept. NI provided a plugin, and it looks like they are finally doing something.

    There are several threads about this going around as well, and so far I see 23 likes on the OP.

    Saying we don't need this is unhelpful to say the least on this thread. The idea that many of us haven't considered or aren't using your suggested workflow either is also proposterous.

    What's more proposterous is somebody stating these essential enhancements aren't at all necessary, we should all adopt his workflow and that we should accept the situation. Or buy other gear. That shows a total lack of understanding imho.

    Again if you don't want to discuss these enhancements, in the politest possible way may I please ask you to sling your hook. This is an actual issue, if you don't think it is you haven't read the OP properly or tried to reproduce yourself.

     
    Last edited: Mar 2, 2017
  14. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    You didn't read the thread links I and others posted I assume. See my quote above.
    (1) Is already in beta, so it's a certainty, we shouldn't need to hope. When it gets a full release is another question.
    It stands to reason though that if (1) is a valid, then (2) and (3) are valid as well (2 is debatable as to whether it is an optimal solution to the problem, there could be better solutions), yes I will keep pushing.
     
  15. CakeAlexS

    CakeAlexS NI Product Owner

    Messages:
    5,431
    Well I immediately regret my boasting post so gonna delete it...Cheers.