Update documentation regarding Ableton Live export limitations and features

src/routes/faq/Faq.tsx

@@ -19,9 +19,10 @@ function Faq() {
         </h2>
         <p className="text-sm font-mono">
           Several reasons. The main one is that the EP devices uses a custom FX processor that is
-          hard to recreate in a DAW one to one. Also, fader automation is not exported yet, so if
-          you used fader automation, the result will differ. Sample stretching algorithms are
-          different as well.
+          hard to recreate in a DAW one to one. Recorded fader automation is exported to Ableton
+          where Live has a matching parameter. TIM automation is omitted because Live has no direct
+          equivalent for the EP's real-time stretch control. Sample stretching algorithms are
+          different as well, and choke groups require Drum Rack tracks.
           <br />
           <br />
           Initially this project was intended to export notes and samples so you could continue

src/routes/home/Export/ExportProjectDialog.tsx

@@ -23,7 +23,7 @@ function sanitizeFileName(value: string): string {
 }
 
 const NOTES: Record<ExportFormatId, string> = {
-  ableton: `Please note that the exported project won't sound exactly the same as it does on the device.`,
+  ableton: `Recorded fader automation is exported for LVL, PTC, LPF, HPF, FX, ATK, REL, PAN, TUNE, VEL and MOD. TIM automation is not exported because Ableton has no equivalent for the EP's real-time stretch control. Choke groups require Drum Rack, and the EP effects and stretching algorithms remain approximations.`,
   dawproject: `Unfortunately, the DAWproject format does not currently support the "Sampler" instrument, so you will need to manually assign the samples in your DAW.`,
   midi: `The simplest format supported by any DAW. But you have to assign the samples manually.`,
   reaper: `Only basic sampler features are supported`,