As the titel says. I can't get it running. And there is no chapter in the manual.
horst
How to use the new Arpeggiator?
-
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
I didn't have any troubles getting it working in Waveform 11.0.26 on Windows 10. If your system is different you may get different results. It's difficult to give help with so few details provided. Because you have not told us what you did to try to get it running or at what point the failure lies, I will assume you have never used an arpeggiator before and give you the basics of how to get this one running.
MIDI note(s) -> Arpeggiator -> synth
Arpeggiator receives MIDI note data and expands it into arpeggiated runs that are sent to a synth. You can either use a keyboard as input or else a MIDI clip. Arpeggiator should be placed on a track immediately before a VST synth.
In this example I made a quick MIDI clip with some notes, set the Arpeggiator Clock to 1/16 and Octaves to 3 and then put TyrellN6 after it.
If the troubles you're having involve some other part of the process, please provide as many details as possible so that we can try to take the same steps as you to replicate any problems.
MIDI note(s) -> Arpeggiator -> synth
Arpeggiator receives MIDI note data and expands it into arpeggiated runs that are sent to a synth. You can either use a keyboard as input or else a MIDI clip. Arpeggiator should be placed on a track immediately before a VST synth.
In this example I made a quick MIDI clip with some notes, set the Arpeggiator Clock to 1/16 and Octaves to 3 and then put TyrellN6 after it.
If the troubles you're having involve some other part of the process, please provide as many details as possible so that we can try to take the same steps as you to replicate any problems.
You do not have the required permissions to view the files attached to this post.
Surely there must be consensus by now...
-
- KVRist
- Topic Starter
- 195 posts since 17 Jun, 2007
Hi pough, thank you. It looks the same here, but I don't get reasonable results. I think I have to make a screencapture film to show (but tomorrow, it is nighttime here). Sometime a note will play sometimes not, can't really explain. After hitting stop, the sound will remain, I have to kill the synth I have inserted to stop.
-
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
Which version of Waveform are you running?
Which OS?
Whats the 4OSC patch?
I switched to 4OSC and didn't have any issues. This is the first time I've tested Arpeggiator and I'm running the latest BETA release.
Which OS?
Whats the 4OSC patch?
I switched to 4OSC and didn't have any issues. This is the first time I've tested Arpeggiator and I'm running the latest BETA release.
Surely there must be consensus by now...
-
- KVRist
- Topic Starter
- 195 posts since 17 Jun, 2007
Good morning pough,
< Which version of Waveform are you running? >
The video is with the latest official one, 11.0.24, but with the beta 11.0.26 it is the same
< Which OS? >
win 10 pro
<Whats the 4OSC patch? >
It doesn't matter which patch or which synth or VSTi I select, it is always the same.
< Which version of Waveform are you running? >
The video is with the latest official one, 11.0.24, but with the beta 11.0.26 it is the same
< Which OS? >
win 10 pro
<Whats the 4OSC patch? >
It doesn't matter which patch or which synth or VSTi I select, it is always the same.
-
- KVRist
- Topic Starter
- 195 posts since 17 Jun, 2007
I have found the problem: as long as my launchkey mini is assigned to that track, the described situation occurs. Problem is: setting to 'no input' is not the solution as in that moment I touch the track, launchkey mini will be assigned automatically.
-
- KVRian
- 615 posts since 30 Apr, 2003 from London, UK
You can stop this happening by unchecking the option (it's on the right click menu of the input icon)midklang wrote: Tue Apr 14, 2020 9:53 am I have found the problem: as long as my launchkey mini is assigned to that track, the described situation occurs. Problem is: setting to 'no input' is not the solution as in that moment I touch the track, launchkey mini will be assigned automatically.
'He craved immortality so much, he was prepared to die for it.'
-
- KVRAF
- 2417 posts since 17 Jun, 2003
Have you got the launchkey mini mapped as a control surface? If so, does it still do it, if you remove that mapping?
"my gosh it's a friggin hardware"
-
- KVRist
- Topic Starter
- 195 posts since 17 Jun, 2007
No control surface. But even that should work.chico.co.uk wrote: Tue Apr 14, 2020 1:27 pm Have you got the launchkey mini mapped as a control surface?
I have submitted a ticket.
-
- KVRAF
- 4891 posts since 3 Jan, 2003 from Vancouver
A good starting point for interpreting the results is:
something = bad
nothing = good
I hooked up my nanokey2 and it only sends MIDI when I press a note. If Launchkey is sending MIDI data even when it's not being used then it would be probably be the reason the Arpeggiator is going crazy.
I did a search and found these:
https://support.novationmusic.com/hc/en ... transport-
https://www.reddit.com/r/ableton/commen ... g_with_my/
something = bad
nothing = good
I hooked up my nanokey2 and it only sends MIDI when I press a note. If Launchkey is sending MIDI data even when it's not being used then it would be probably be the reason the Arpeggiator is going crazy.
I did a search and found these:
https://support.novationmusic.com/hc/en ... transport-
https://www.reddit.com/r/ableton/commen ... g_with_my/
Surely there must be consensus by now...
-
- KVRist
- Topic Starter
- 195 posts since 17 Jun, 2007
pough wrote: Tue Apr 14, 2020 6:17 pm A good starting point for interpreting the results is:
something = bad
nothing = good
...
something is this:
00:00:00.000 f8 (don't know, what that means)
nothing else, but constantly.
Is this a matter for novation support? Or is it possible for Waveform not to listen at?