Install A Hard Drive in an Akai Force (Step by Step)
HTML-код
- Опубликовано: 24 июн 2023
- Need a guide to install the hard drive in your Akai Force or MPC X, MPC X SE, or Akai MPC Live II? This is the guide you have been looking for. The process is the same for all of these devices to get your hard drive a screw driver and follow along and we'll have you back to making music in no time.
If you find the helpful - don't forget to like and subscribe. Also if you want to support the channel you can buy me a coffee at:
ko-fi.com/cap10nrgmusic 
Видеоклипы
Thank you for this. Has given new life to an old HDD I had swapped out in my Xbox One X.
Nice! As a former Xbox addict myself lol I’d say it’s a good choice. I still play call of duty, but not too many other games lately. Tried to pull away from all that. Lots of wasted time that could be better used making music. Not hating video games by the way I do love them. That’s the problem, lol… too much sometimes I think 🤔
Thank you for your video 🙂👍
You’re welcome! Please sub if you liked the video - if you have any questions feel free to hit me up!
NTFS is a file system of Windws, for me it's better to format ssd drives, pendrives in exFAT. Anyway nice wideo. Thank you.
Good tip! Either works fine - exFat might be getter if you are working on MAC and PC I see your point. Thanks for checking out the video
Dude, are you gonna make that video about how to select patches on external synths in Reason, using The Combinator?
Hey Matt - I actually did work on that video a while back - I thought I put it out actually, but I cannot seem to find it so now I am not sure whether it made it to the light of day or not.. I can tell you a couple things - first one of the main difficulties in using a combinator for real world instruments (or even VSTs and Rack extensions) is the lack of feedback from the device being controller. For example - there is no way to (using a combinator) read the position of a knob on a controlling device. The combinator can poll it for changes - but if you start up a combinator - it doesn't initially know the position of the knobs on your controller, synth, vst, or even rack extension. It is not until you start moving knobs on the combi that it updates the values on the devices, and unless you mapped the knobs back to the controls on the combinator - moving them on the device doesn't know what's going on. The other thing I found when I did this build was that - though you could change the patch on a physical synth in some cases - it was tricky and you would have to map each synth to a combinator -add the synths to your setup - and the combinator (again) could not get feedback from the synth - nor is there a list feature to combinators - so you would be stepping through patches blind. You COULD if say you used a few patches - like GRAND PIANON, STRING QUARTETTE, and WIND CHIMES (just a few example sounds) you could build a combi that told your synth to "JUMP" to those patches by sending all the correct CC information when you clicked a button. But the amount of work to do this is HIGHLY prohibitive. Even if I demo how to do it - it would be up to individual users to implement this feature because it would be a lot of work - and vary depending on the synths used by each person to have a specific play list of sounds.
You could blindly step through sounds with a combi on a real world synth - but again no feedback (that's why I say blindly) you would have to look at the synth screen to know where you were. Does all this make sense? I can put together a single sample of how to do this but when I tried it with my CS1x it was pretty much a "The Juice was not worth the squeeze" scenario.
@@Cap10NRGMusic Ah right. I'm a little confused, sorry, but I will try to get through this when I get back home to my synths (I'm away right now). Thankyou for your response.
Hello. I have an advance question.
Do you know if the SSD can have multiple partitions on it?
I would like to use 3 partitions with ext4, ntfs, exfat?
If you don't know then Good Video anyway. I'm trying to decide if I want to buy an FORCE. Or make my own MPC like DAW.
Thanks for the comment! Just curious as to why you’d want 3 partitions with different formats. It’s an interesting question. The drive can be partitioned - and will show up as multiple drives if you created partitions on a pc or Mac. As far as formatting- I think you are stuck with the default - which incidentally is Mac and pc readable so you should be good there. I hope that helps you out.
Now, as a software developer myself… I am intrigued, so I have a question for you. Do you want to develop your own MPC DAW? Are you talking from the ground up, or are you building a VST? Are you trying to build some proprietary? That would be just this one thing or are you looking to build something? That’s kind of multifunctional and allows the use of other VSTs? Let me know. I’d love to check it out if you decide to build it. I’ve also thought of writing some software to give me functionality that I don’t seem to have in certain devices, but then I think about all the other functionality I would need to create that is in those devices… And I have never gotten into it because I just thought you know what the things I don’t have are so few and the things that I do have that I would have to create just to have that functionality are so many that the work would not be worth the effort, or the rather would not be worth the effort. Like, as in the juice would not be worth the squeeze as they say. Anyway I hope that helps. Let me know what you decide to do. I’m very curious. And thanks for checking out the video and if you would subscribe to the channel, I would appreciate it.
@@Cap10NRGMusic
I am putting together a game plan, man-hour budget, and money budget. I came across your video because I wanted to see the circuit board of a FORCE, but I didn't know the SSD bay was on the bottom belly.
I wanted 3 partitions just to breakup a 4Tb disk. I wanted to hide some partitions from different users when they go into PC (tether) modes on the MPC Live(s). Each vocalist uses a different OS.
I use all the popular operating systems. I am thinking about creating a DAW from the "ground up" that can be installed on all my computers (and maybe embedded devices). I am at the point where interconnecting all my stuff is becoming too tedious and time consuming. I want to make a DAW that I can compile to alleviate some time. I want MIDI over OM3 OM5 cabling and the use of my server grade hardware.
I never thought about making an (alternative) MPC DAW. People already have done that. But it can probably be done if I clone the internal SD cards or read the EEPROM chips. But I don't want to target the akai boxes because they are limited to those RockChip arm architectures that only come with 2 configurations (I think). 2GiB and 4GiB of RAM is too low. (I think) AKAI uses linux on their boxes. Cakewalk had expansion pack VST/VSTi(s) and dxi(s) (instruments) back in the late 1990s, but they never were re-compiled for x64. I still run x86 vsts with Bandlab Cakewalk just for all those sounds and plugins from 1997 (when I was a kid) to 2023. But I think it might be time for me to make my own DAW because I want to run sound fonts and other technology formats on my modern hardware. Modern VST have less control than previous generations. Alot of the programmers don't know audio tricks and algorithms that we 30-40 year olds know from before 2010. I think the technology of VSTi and the interfacing is getting worse. Back in the 1990s, I could change parameters to anything and have a step sequencer and jump to a sampler or Melodyne. I can't do that anymore with my x64 boxes. I have some crazy Ideas and I want it all within one DAW. Alot of mastering tricks that I learned or made up along the way. Gaming and all the stuff I do.
I don't know if I'll FOSS it or go proprietary. The FOSS community is usually behind on modern coding really advance Video and Audio Tooling. Its difficult to find FOSS programmers that are rock stars. I don't know. I'm still putting together a game plan (during this christmas break). The only reason, I am tackling this is because I am not the average CSC, EE, pro. Alot of my knowledge is self taught by fixing pro gear and making up my own softwares on the fly. It would overburden an average senior programmer. I have 3 studios and 2 repair shops. Simplifying all that knowledge into one daw is tough. I already have previous version of my little daw on freebsd and linux. Now I have to port it to microsoft and mac. Just planning for that will take me about 3-4 weeks. I think I am going to have to write a DSL or programming language (on top of LLVM), so that I can bounce it to embedded and desktop architectures. Yeah tacking this is kind of crazy, but I'm tired of the bugs. I spent 6 hours one day trying to upgrade a vocalist/artists MacOS setup to to ventura so they could run the latest MPC Beats. I'm just want to get rid of the Apple, Linux, and Microsoft shenanigans.