Hi I am using an M1 and am unable to import .exs instruments into Logic 11.1.2 using any of the Alchemy Samplers. Instruments are not recognised and are greyed out when I try and import manually. All the online info is for slightly older versions, Has this function been removed? I am unable to find any info on Logic 11+ Any ideas?

 

I asked the AI if it could help us:

To open an EXS file in the latest version of Logic Pro (11.1.2 or 10.8+), follow these steps:

Method 1: Using Sampler (replacement for EXS24)

1. Place the .exs file and its associated .wav samples in the correct folder:
   
   • Sampler Instruments: ~/Music/Audio Music Apps/Sampler Instruments/
     
     
   • Samples: ~/Music/Audio Music Apps/Samples/.
     
2. In Logic, create a new track and load the Sampler plugin (not EXS24, which is discontinued).
   
   
3. Click the preset menu at the top of the Sampler window and select Load..., then navigate to your .exs file.
   

Method 2: Drag-and-Drop

• Simply drag the .exs file directly into Logic's Tracks area or the Sampler plugin interface.
  

Troubleshooting:

• If files don’t appear, ensure they’re in the correct folders and restart Logic.
  
  
• For compatibility issues (e.g., round-robin layers or single-sample files), try importing the EXS instrument into Logic’s Sampler first, then re-export it to ensure proper formatting.
  
  
• Older EXS files may require manual remapping if samples are missing or paths are broken.
  

 

Here: https://www.reddit.com/r/Logic_Stud...emy_sounds_all_greyed_out_all_the_sudden_the/
someone mentioned Alchemy's “Alchemy_Preset_Ratings_And_Tags.db” that was corrupted somehow.
Deleting the file seemed to work.

 

I asked another AI if it could help us:

It sounds like you're running into an issue with importing .exs instruments into Logic Pro 11.1.2 on your M1 Mac. You're right that some information available online might be outdated, especially when it comes to newer versions of Logic. However, let's go over a few things that might help resolve the problem:

1. Check Compatibility with M1 Mac (Rosetta 2)

• Logic Pro has native M1 support, but there could still be some plugins or instruments that rely on Rosetta 2 to run. Ensure that Logic Pro and any associated plugins are fully updated and running under the proper architecture.
  
  
• You can force Logic to run under Rosetta by right-clicking on the app and selecting "Get Info" → check the "Open using Rosetta" box. This may help with legacy plugin support, though it shouldn't be necessary for .exs files since Logic should handle those natively.
  

2. Verify File Format

• Ensure the .exs files are properly formatted and not corrupted. These files are for the EXS24 sampler, and Logic should still support them, but check if they might be in a format that newer versions of Logic don't recognize automatically.
  
  
• If you're sure the files are correct, try manually locating the .exs files and dragging them directly into the EXS24 sampler.
  

3. Permissions and File Path

• Since you're on an M1 Mac, ensure there are no permission issues or path restrictions that could be causing the problem. Sometimes, apps on newer macOS versions (especially on M1) can be more restrictive about accessing certain file paths.
  
  
• Try moving the .exs files to a standard location such as the ~/Music/Audio Music Apps/Sampler Instruments folder or another similar default path Logic Pro uses.
  

4. Test with Other Samplers

• Alchemy is capable of importing a wide range of instruments, but it doesn't natively support the EXS format. You can try loading the .exs instruments in the EXS24 Sampler (if it’s available in your Logic version) instead of Alchemy.
  
  
• Alternatively, you could try using Sampler (the new sampler in Logic) as it’s designed to replace the EXS24 in newer versions of Logic Pro.
  

5. Check for Bugs or Known Issues

• Logic Pro 11.1.2 should still support EXS24 instruments, so check Apple’s support forums or release notes to see if this is a known bug. Sometimes, functionality gets altered or broken in minor updates.
  
  
• If it's a bug, you could consider downgrading to a previous Logic version (if this started happening after the update) or waiting for a patch if it’s a widespread issue.
  

6. Re-scan Plugins and Instruments

• If the instruments are greyed out, it could be that Logic isn’t properly scanning your sample libraries. Try going to Logic Pro > Preferences > Plug-ins, and click on Rescan All to ensure everything is properly indexed.
  

7. Manual Import

• If manual importing isn't working, you might want to try a different method:
  
  • In Logic, open the EXS24 Sampler, then drag the .exs file directly into the sampler. It might bypass the greyed-out issue.
    

 

Thanks Radio & AI! None of the above worked for me, then I opened a new document in Logic and was able to access my .exs instruments through the "Legacy" menu once, I closed the song document and the instruments disappeared from the "Legacy" menu...I assume I have a database or mapping issue...but I will persevere - cheers!

 

I still hope you'll find a solution to the problem somehow. I'm a Windows Alchemy user and Alchemy Sound Designer user
14 Fre Soundbanks, http://ohlenbostelhelge.magix.net/public/alchemy.htm , but I have no idea about Mac. Here's another attempt from the world of AI:

1. For Logic Pro users:
   
   • Apple's integrated version in Mainstage offers updated functionality with preserved Alchemy interface
     
     
   • Legacy presets can sometimes be transferred by moving files to User/Music/Audio Music Apps/Plug-in Settings/Alchemy
     
2. General troubleshooting:
   
   • Ensure all data files are in default locations (Library/Application Support/Camel Audio/Alchemy)
     
     
   • Avoid custom install paths as they may cause loading issues
     
     
   • For missing libraries, try redownloading through Logic's Sound Library Manager
     

Important Note: Since Apple acquired Camel Audio in 2015, no updates have been made to the original plugin, making these compatibility issues permanent unless using Apple's integrated version in Mainstage or Logic Pro

 

Seems to be related to the updated Sampler plug...I opened the document in Logic 10.5.1 and .exs samples loaded saved the song document under new name...the exs instruments were then available in 11.1.2 in the new document, but not in the previous one...also exs only available in simple sampler, not full on alchemy - curious!

 

Absolute support desert from Apple!!! User angelonyc wrote:

I find the Alchemy documentation skimpy, considering how complex the virtual instrument is.. I'll check out Camel Audio's Alchemy's manual, and see how much carries over.. Thanx..

Apple did the same with the newest Mac
Pro.. No user manual, only a 6 page brochure pointing out some features.. After several phone calls, I was told to use the 2013 tower Mac Pro manual... A $5000 computer, with no manual...

The AI says:

Legacy EXS24 Compatibility Issues

• Users report the EXS24 plugin may appear grayed out or unavailable in Logic Pro 9.1/10.5+, especially when dragging instrument loops, though manual instantiation works. This suggests a Spotlight indexing or file-naming conflict.
  
  
• In Logic Pro 10.5+, Apple replaced EXS24 with "Sampler," which retains backward compatibility with EXS24 instrument files (.exs) but may fail to convert older formats like GigaStudio samples.
  

Workarounds

• Reindex Spotlight or relocate sample libraries to resolve path errors.
  
  
• For legacy projects, open them in Logic 10.5.1 first to auto-convert EXS24 patches to Sampler format, then save anew.
  
  
• Third-party EXS instruments may require manual sample relocation if files are missing or renamed6.
  

Current Status

• Logic Pro’s Sampler (post-10.5) fully supports EXS24 libraries but may lack specific legacy features like sample trimming beyond chopped regions.
  
  
• Plugin Manager can disable incompatible legacy plugins (e.g., 32-bit) causing load delays.
  

For detailed troubleshooting, check Apple’s support documentation on Sampler