Jump to content


Samplitude Members
  • Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location
  • Interests
    Music, Hammond organ, synthesizer, piano

Recent Profile Visitors

1,463 profile views

Nordlead's Achievements

Professional Member

Professional Member (4/8)

  1. Und auch checken, dass die zu importierenden Dateien sowie die Verzeichnisse keine "exotischen" Sonderzeichen haben (Akzente u.ä.), das mag Samplitude nämlich gar nicht.
  2. Klingt gut, viel Spaß damit! Ich habe mir letztes Jahr auch eine Musik-Workstation konfiguriert, ebenfalls mit einem Ryzen Prozessor, sogar eine Nummer kleiner, dem Ryzen 7 3700X. Ich bin ebenfalls sehr zufrieden, das System läuft stabil, schnell und wird (im Gegensatz zu den älteren AMD Prozessoren) praktisch nie richtig warm (und damit laufen auch die Lüfter nur auf Sparflamme). Wenn man sich die Benchmarks anschaut, gibt es keinen rationalen Grund mehr für dieses dauernde "AMD Bashing" bei Audio-Anwenungen. Sogar Steinberg empfiehlt für das aktuelle Cubase Intel i7/i9 oder Ryzen Prozessoren. Nur mal zum Vergleich, von wegen Single Core Performance (und man beachte die Leistungsaufnahme):
  3. I think this is not only limited to Hebrew words: I regularly have problems with file names or folder names that I got from people e.g. from Czech Republic or Serbia where there are lots of "accents" on the characters. Samplitude refuses to import such files or to open or save in such folders. I usually rename them and use "simple" characters instead. But that's of course not very attractive when you would have many files to handle ...
  4. Hi, if scanning doesn't show you the plugin you have either put the relevant plugin in the wrong folder or you're scanning the wrong folder. Open settings with "Y" and check the "User VST Plugin folder" under Effects-VST. Typically the VST/VST2 lie under C:\Program Files\VSTPlugins\ Does your other VSTs work?
  5. I’m already here again, it actually worked! I had to switch the monitoring setting at least to "Hardware Monitoring / Hybrid Engine", then the Blobs and all activities were directly audible.
  6. Hello, I came across this article because yesterday I was a bit more involved with Melodyne as well. I've seen in several tutorials that when you click on the "blobs" you can hear the corresponding sound. I can confirm this, it doesn't seem to work in Sam (here ProX3) either when using Melodyne in the object editor. However, it works in the standalone version of Melodyne! Maybe someone still knows a tip on how to do this within Sam? Thanks!
  7. I just checked my own order conformation that I’ve received via E-mail from Magix. There were these points concerning SpectraLayers: SpectraLayers Pro 4 (PC & MAC) Serial number: P2-xxxxx-xxxxx....... Download the program: http://dl03.magix.net/spectralayerspro4.exe Download for Mac OS: http://dl03.magix.net/spectralayerspro4.dmg Program activation: Start the program. Copy the serial number from this e-mail and paste it into the input field of the work clearance document. So, this is the way you should have gotten your serial number and the download path for SpectraLayers. The serial number on the pic is my original Sam X3 number. I’ve just painted it black, just to be sure that nothing happens with it
  8. I also got these 3 + 9 DVDs. What’s written on the both Pro X3 DVDs? One should be "Program DVD" (and here should be a label with the serial numbers) the other one "Content DVD Sounds & Loops). See the picture attached. I can’t remember anymore where Spectral Layers came from, but please also check your order confirmation oder delivery papers...
  9. Hi again, I’ve found this in a German recording forum from 2013. This was the original answer from the Samplitude support: Mit dem Focusrite Scarlett USB wurden kontinuierliche Spikes im Treiber festgestellt, die zur Auslösung von LAB in Samplitude führen. Dies deutet auf ein Double-Buffering des Interfaces hin. Audiotechnisch ist das Interface aber in Ordnung und funktioniert ohne Fehler im Audiosignal. Zur Deaktivierung der LAB Fehleranzeige folgenden ini-Eintrag verwenden: "[Setup] DisableDroppedASIOBufferSWDetection=1" Translation (online, I hope it works to understand): With the Focusrite Scarlett USB continuous spikes in the driver are detected, which lead to triggering of LAB in amplitude. This indicates a double buffering of the interface. However, the audio interface is fine and works without any errors in the audio signal. To deactivate the LAB error display, use the following ini entry:"[Setup] DisableDroppedASIOBufferSWDetection=1". So, if your system has "enough" performance power, your basic asio/buffer settings are OK and you don’t hear any "audio errors", then you can ignore this error and disabling it this way. Btw: according to my researches (then and now) many users do have exactly this problem, and only with focusrite interfaces / drivers but not e.g. with the "Magix low latency driver" (while using the same interface)...
  10. I've had the same problem in the past with various Music Studio versions (2013 and 2014). At that time I found somewhere the solution for this problem that is obviously caused by the Focusrite interface or driver. I've just tested it also with my new Pro X3 - and it worked as well! Add this line in the INI file (according to your version, e.g. "Sam_x64.ini"), as a new line below the [Setup] entries. DisableDroppedASIOBufferSWDetection=1 (Just to be safe, please copy and rename the original INI file first to have a backup if there would be any problem!) After restarting your problem should be gone.
  • Create New...