Please can you tell me why,when i import a vocal and tune it in audio,when i go back into the sampler the vocal has sped up? And if i stay in audio it just loops the vocal and if i then clear the event (vocal) it completely erase the vocal. Just want to tune up the vocal and slice it onto different pads. Please it that makes sense give me some advice. Many thanks.
Instead of hold the note repeat. Just lock it..instead of going through all that hassle. Overall..great tips. I can definitely incorporate this with samples.
Love it. Had mine a week now and I'm in love with the workflow. One question: can you arm a sequence to end at the end of it's run time, rather than just MUTE all the time? Seems it would free a live performance up if I knew I was about to bring one sequence to an end, in readiness to start another when it does.
Not that we know of, however a good way to use Maschine in a performance scenario would be to arrange patterns via scenes and trigger the individual scenes in the "ideas" mode".This means you can structure your performance.
Also, there is a Reaktor ensemble that can be utilized for programming mute states into the patterns, which could be used in the same way you're describing - essentially, programming everything to mute at the same time, i suppose 🤔.... You can download the ensemble from the NI forums, and here's my notes on the dude's notes: RECORDING MUTE STATES IN PATTERNS: The key is loading the "Mute.ens" ensemble multiple times onto Sounds within a new Group; the ensemble is found under the User Effects in the EFFECTS section of the Browser👍.... The creator dude's directions are as follows: 1. Create a new Group with an instance of this on as many Sounds as you want mutes to route, and make sure every pad in use is set to C1 2. Anything you want to mute then gets routed to a pad on this Group (be IT single Sounds, multiple Sounds, or entire Groups) 3. Create a new pattern on this Group for the length of how long you want to record (or just create a clip in Arranger view) 4. Hit record and press the corresponding mute Group pads to mute the signals and press again to unmute - this records as MIDI data which can then quantized, edited, deleted, moved, etc.) 👍 *** Maybe not the first choice for newbies, but as a relative noob myself, i like to know early on what options exist for workarounds and the like 👍🌌
Hello, How do you automate when it comes to working with patterns or scenes? It seems like a crucial thing to have parts fade in and out filter cutoffs change over the course of your song etc. If I automate in a pattern it seems to effect all the others in the group If I start duplicating pads to new groups it gets cpu intensive quickly, If I record the master I’m stuck with printed chunks of audio instead of the plug ins themselves. Is there really no other way to do something so basic?
We are not sure if automation on Maschine's timeline is possible, however, automation in Maschine exists within a group. You can Automate on a sound level, a group level or the master level. Automation in Maschine works a bit like clip automation in Ableton.
Resample the pattern to another pad and duplicate it as many times as you want to add different variations of automated FX. That takes up way less CPU. Take it a step further and resample the patterns that you just automated so the automation is baked into audio. Don't forget to rename them as you go
Would be nice if they did one with actual music in it rather than that repetitive and annoying techno.The same 4/4 beat. That's not a challenge; but its still a useful tool.
Really useful video, thanks!
Cheers
thx you opened up a new world for me
I might pick up a maschine+, love the workflow. Seeing that there’s not much going on in this project and the cpu already hits 60% makes me hesitant 😬
Great video thanks
dope man!
Arpegio modes, I have never used. Sweeet. Can you explain why you put swing only on the kick??
Please can you tell me why,when i import a vocal and tune it in audio,when i go back into the sampler the vocal has sped up? And if i stay in audio it just loops the vocal and if i then clear the event (vocal) it completely erase the vocal. Just want to tune up the vocal and slice it onto different pads. Please it that makes sense give me some advice. Many thanks.
Instead of hold the note repeat. Just lock it..instead of going through all that hassle. Overall..great tips. I can definitely incorporate this with samples.
Per step editing is super handy too ❤❤
Oo also for effects
This would be awesome to give some movement.
So now automation is per pattern right? It was saved per group which was well annoying.
And you dont need record armed to save automation?
Love it. Had mine a week now and I'm in love with the workflow. One question: can you arm a sequence to end at the end of it's run time, rather than just MUTE all the time? Seems it would free a live performance up if I knew I was about to bring one sequence to an end, in readiness to start another when it does.
Not that we know of, however a good way to use Maschine in a performance scenario would be to arrange patterns via scenes and trigger the individual scenes in the "ideas" mode".This means you can structure your performance.
Also, there is a Reaktor ensemble that can be utilized for programming mute states into the patterns, which could be used in the same way you're describing - essentially, programming everything to mute at the same time, i suppose 🤔.... You can download the ensemble from the NI forums, and here's my notes on the dude's notes:
RECORDING MUTE STATES IN PATTERNS:
The key is loading the "Mute.ens" ensemble multiple times onto Sounds within a new Group; the ensemble is found under the User Effects in the EFFECTS section of the Browser👍.... The creator dude's directions are as follows:
1. Create a new Group with an instance of this on as many Sounds as you want mutes to route, and make sure every pad in use is set to C1
2. Anything you want to mute then gets routed to a pad on this Group (be IT single Sounds, multiple Sounds, or entire Groups)
3. Create a new pattern on this Group for the length of how long you want to record (or just create a clip in Arranger view)
4. Hit record and press the corresponding mute Group pads to mute the signals and press again to unmute - this records as MIDI data which can then quantized, edited, deleted, moved, etc.) 👍
***
Maybe not the first choice for newbies, but as a relative noob myself, i like to know early on what options exist for workarounds and the like 👍🌌
I guess you could make it longer then at the end keep some empty space so it will be quite.
Hello, How do you automate when it comes to working with patterns or scenes? It seems like a crucial thing to have parts fade in and out filter cutoffs change over the course of your song etc. If I automate in a pattern it seems to effect all the others in the group If I start duplicating pads to new groups it gets cpu intensive quickly, If I record the master I’m stuck with printed chunks of audio instead of the plug ins themselves. Is there really no other way to do something so basic?
We are not sure if automation on Maschine's timeline is possible, however, automation in Maschine exists within a group. You can Automate on a sound level, a group level or the master level. Automation in Maschine works a bit like clip automation in Ableton.
Make a new group with the filter fx. Route everyting you want filtered to that group. See the group as an FX bus.
Resample the pattern to another pad and duplicate it as many times as you want to add different variations of automated FX. That takes up way less CPU. Take it a step further and resample the patterns that you just automated so the automation is baked into audio. Don't forget to rename them as you go
Would be nice if they did one with actual music in it rather than that repetitive and annoying techno.The same 4/4 beat. That's not a challenge; but its still a useful tool.