Moved Samples — Destroyed Project

Hello.
Over the last few days, i've been trying out working with samples in Maschine. Whats possible, what not, best practices … Wether i like it or not.

Something that particularly interested me was … #1 how Maschine and also my projects will react if i moved samples in finder … #2 and what will happen if projects break and i put the samples back to their original place.

— RESULT —
During #1 … i showed Kontakt (!) the new location and as i played the track it sounded choppy and out of tune and faster than it should.

After #2 … it still sounded like that.

— QUESTIONS —
a) What happened? Why does Maschine (maybe its Leap?) behave like that? (Just curious)
b) How can i move and rename samples without messing projects up. Not asking for "Safe with samples." :) … I need the option to move and rename samples, because i will do that.
c) How can i restore such a broken project?

Thank you for reading this far and im looking forward to your answers. :)

PS:
For the last couple of weeks, often when i close Maschine (DAW) macOS says that Maschine wasn't shut down correctly.

Find more posts tagged with

Accepted answers

All comments

Fuokki

If you move a sample from the project folder to another location, Maschine will lose track of it, and you’ll have to manually set the new path;
Maschine will recognize these samples again in their original locations;
The issue with changes in playback speed and sound quality most often occurs due to differences in sample rate between the audio interface and the project.
For example, the sample might be at 48 kHz while the project is at 44.1 kHz, or vice versa. Additionally, in some DAWs it’s important to specify whether a sample is mono or stereo before adding it to a track, as this can also affect playback.

b) Copy the sample instead of moving it.

P.S: "Maschine wasn't shut down correctly" Welcome to the club😁

Fuokki

And one more thing about the sample playback speed: Sampler and Audio often detect the sample’s tempo incorrectly, so you have to set it manually. For example, I process vocals in another DAW using plugins that introduce latency (Maschine doesn’t have plugin delay compensation), then bring the vocals back — but the tempo ends up being off.

Alex0815

Hey, Fuokki.

Thank you for your input. I appreciate it! :) I checked these points before I came here. Sadly none of them apply.

=========

Meanwhile I tried to recreate the problem … but couldn’t even get this far.

1. I put the sample in an audio module … and also in Kontakt where it opened correctly in Leap. … Two groups, patterns, scenes. Happy me.

2. Then I closed Maschine … and moved the sample to a different folder. (Didn't copy. I need a system that can handle stuff like this reliably.)

3. Reopened the project … and as expected the sample in the audio module played perfectly … and I had to show Kontakt the new path.

4. BUT … although I was able to trigger the sample via a pad and I heard it playing … Neither Kontakt nor Leap displayed the sample. Not even Leaps interface showed up. … Just its expansions.

On a good not: The project played fine this time … and nothing sounded choppy or otherwise wrong. … But as mentioned, I didn’t recreate the first project entirely.

NEXT …

I saved the file … to see if Leaps interface shows up when I reopen the file. … Guess what: It didn’t. The project didn’t even remember the new folder I had just assigned before I saved the project. *sigh* :D

So for now, …

- given all of that … and that macOS gives me an error message whenever I quit Maschine (Glad to know it's not just me)
- Maschine suggests „New Project.mxprj.mxprj“ as a new file name
- Double-clicking a project opens Maschine … not the project
- the acquisition of iZotope is an ongoing process
- there are resources needed for the AKAI colab …
- and Tahoe’s waiting to be embraced

… i won’t bother about these findings that brought me here in the first place anymore and take a looong walk until the Audio Industry inkl. NI successfully ported their products to macOS Tahoe. … It’s fine. I can wait. And to be clear, I ain’t mad at all!!! Software is a complex beast. It is! … It’ll all be fine again soon.

I just talked to a reseller who’s totally happy with its system … but he’s on an older macOS. … So yeah, I’ll just wait and then switch to Tahoe.

Still interested in thoughts and ideas out of curiosity, though. :)

Quick links

Unanswered questions