that’s definitely a possibility, though environment in a studio can and should be controlled if at all possible. All of my gear is in a temperature and humidity controlled basement studio. The temps never fluctuate much between 68F and 74F and the humidity is kept at a solid 36-41% at all times. None of my gear are ever exposed to direct sunlight either (unless I’m playing an outdoor gig).
I really want to move my Force to a humidity controlled studio, but at the moment the humidity is somewhere at the “clothes and bags get moldy” level. Yet the coating hasn’t deteriorated so far (granted I only moved from a humid place to an extra humid place three months ago).
1 Like
I run a dehumidifier in my room for a couple
of hours a day, force is sticky free
1 Like
Do you live in London too?
Moved to Da Nang, it feels like you don’t even have to drink water, just take a couple deep breaths and you’re not thirsty anymore. And it’s not even typhoon season yet. Honestly, I’m worried about roof leaks the most.
1 Like
I just ordered one, praying that it doesn’t go sticky 
9 Likes
Congrats - and welcome to the Force family! Feel free to chime in if you have any questions or need some tips. I
2 Likes
You should have a air quality test done not only for your gear but for you and the families health.
It arrived, initial impressions are good, quite a few WTF moments but already seem to prefer it to MPC One as it seems more direct for what I want to do. Noticed that the jog wheel seems a bit laggy when scrolling lists of many samples in sample edit, like if I twist it fast it and settle on a sample it would end up on a sample a few away, is that normal?
Not checked on mine but idea off the top of my head is perhaps related to the storage medium and its speed? SD card too slow maybe? Do you have an SSD in it? Advise getting one if you don’t have already!
1 Like
Ahh, yes I was using a SD card but loaded the samples into ram (it was a MPC project) I have a SSD fitted too, it is most likely user error but I thought I’d check if it was a known issue when lots (over 100) samples loaded. Most of the samples are less than a few seconds long, drum hits, basses etc.
What firmware are you on (as of this post, 3.2.3 is the latest). Also, if you have auto-preview on it might slow things down as it buffers the content you’re scrolling into RAM to playback.
1 Like
Don’t forget to reset preferences after updating.
And try not to save anything (other than Synth & FX Presets) to, or delete anything from, the Internal drive.
And disable ‘AUDIO TRACKS AUTO WARP’ in Preferences>AUDIO/EXPORT.
You’ll also want to create a ‘Temporary Files’ folder on the root of the SSD you installed and point to it from Preferences>PROJECT LOAD/SAVE>TEMPORARY FILE LOCATION.
And avoid using auto-save.
And for faster audio previewing, disable ‘SYNC’ and ‘WARP’ from the ‘AUDITION’ edit tab.
4 Likes
Thanks for the tips @HisNameIsAlive and @StudioES 
Man this thing is both awesome and obtuse, some things are super quick and easy whilst others are buried away and not at all logical, the manual seems to assume you just want to play with the lame cheese all preset content…
Anyway I loaded in a MPC project which is all just samples, but the Force has some of the track types as midi, even though they are playing internal samples - is there any way to change that as when I go to track edit it just has a bunch of midi CC stuff instead of the samples, which is useless since the track isn’t playing midi it is playing samples. On the tracks where the Force has loaded them correctly the track shows me the samples which is what I want on the other (midi) tracks.
Any ideas if this is possible?
I hear you, but like all new gear - there’s always going to be a learning curve. In comparison, my first Elektron device was a convoluted mess as well. And let’s not get started on trying to learn Roland’s gear lately - LOL!
Force operates on a true 1:1 track relation, where 1 track can only = 1 instrument. On MPC, 1 track can have multiple instruments on it, hence the need to import and convert the projects into Force as you see.
On Force, the only way to edit the samples (or Drum Program, or Keygroup, etc) is to make sure that particular track is selected, which makes complete sense since it’s a 1:1 track relation.
2 Likes
Thanks and yes I think you are right about the learning curve, I expected a certain amount of complexity due to the number of features/functions, I’ll definitely persevere with it for now.
The MPC project just had 1 track per program, but it seems like the force split some of the tracks out as midi tracks referencing the MPC program I think, I’ll have to check the MPC project on my MPC to see what happened.
Bit shocked that the cursor keys don’t seem to be more widely used, like for moving around notes and sequencer pages etc, I’m not really a fan of touchscreens and find the editing to be pretty fiddly for clips, I use a stylus which helps a bit, but if the cursor buttons were implemented better, I think editing would be easier.
Cheers for the help
Another odd thing, I loaded in a Electribe2 Ableton set, it loaded in fine, and played as expected, but the Force would not let me save it, it started saving then halfway through it gave an error saying that it had not been saved.
Any Electribe2 owners had success with this?
Are you saving your Force Project to a user-installed SSD, USB stick, or SD Card? Force will default to the Internal Factory Storage, which you can dangerously fill up fast (don’t save anything to this spot).
Yes saving to SSD, although I got the Force used - what amount of free space should there be on the internal drive, I think I have about 2.7gb free which I thought seemed a bit low.