Tweet
I’m on 2.0 and USB Midi doesn’t work with a Korg Nanokey studio. Downgraded to 1.9B and USB midi works fine.
-
-
One thing in particular I've come to appreciate and use heavily from this update is the filter resonance control. Thanks for that, 1010 team.Comment
-
on 2.0, the screen flickers very much.Comment
-
Hey, I am on 2.0 as well and next to still having the issue of long samples loosing the loop points mid-play (and then they suddenly appear again a bit later), I also have this display problem (since 1.9), where I want to switch the pad or seq with the grid in the upper left corner and get this glitch.Comment
-
hi Steve , I still have this problem, also under the latest firmware. I uploaded a video in this thread: https://forum.1010music.com/forum/pr...-pad-edit-view
-
-
The original title for the post included something about "project transition" - any word on what that's about? Is this referring to a change in focus regarding the Black Box or something else?Comment
-
2.0 Sometimes specific PADs stop to play, touchscreen or MIDI not triggering it. Also COPY\CUT-PASTE in SEQ not working sometimes.Comment
-
Finally used 2.0.0 for a project.
At this time, for this version, display issues are the most significant feedback behavior I've encountered.
I do not have video.
I copy/pasted 3 sequences for organizational purposes. When I hit play after pasting, the screen image started "shaking" in horizontal slivers. stops shaking when play is stopped.
I got it to go away.
I saved the project, loaded another, and came back. I wanna say the issue persisted after I reloaded the project. I think I power cycled and that cleared everything up.
I'll make a video if it happens again.Comment
-
on 2.0.
while playing with any pads are muted.
If you do a Save As, (again, while playing), the subsequent new file will keep playing except no pads are muted anymore.
I would have expected the mutes to carry over.
As I'm writing this, I feel like I've seen other posts about not being able to save pad mute state, so I guess this is nothing new. But for the state of the pad mute to change while the player is running... that threw me off.
Comment
-
On 2.1.0; it seems that the multisample functionality no longer works. Two of the 64 samples load, with one being mapped across most of the keyboard and one other mapped to a single note.Comment
-
I haven't set root notes (this wasn't necessary in previous versions). I'll try this and check to hear if this makes a difference.
The behaviour I was expecting was to be able to put 64 samples into a folder, then have them automatically map across the keyboard when using the 'load all' function - one sound per note (as in versions previous to and including 2.0.5)
Where should I send the set (too large to send via the chat)? -
To be clear - there are two distinct ways to load a directory of samples to a pad.
1. load a directory of samples that have their Root Note embedded in the wav metadata. We write this when MX sets are created in our box. You can also set/save this TO your wav files inside our box, one file at a time. This method is best for melodic sounds that need to be pitch-shifted to interpolate.
2. load a directory of samples that do NOT have that Root Note metadata. In this case, the sampler will load all files alphabetically, starting at C2. This method is great for loading drums, sound FX, one-shots, etc. There is no interpolation in this method.
In both cases, the samples are "mapped" across the keyboard in some fashion - but very different from one another. Can you confirm which method you are attempting?
-
Comment