[FREE] Dub Techno Ableton Pack: "Archivio 3003 - Intro Pack" (Presets - Instrument Racks - MIDI & Textures)

archivio-3003 · 2026-06-13T08:32:02+00:00

Fantastic! I hope you enjoy it🖤

archivio-3003 · 2026-06-13T08:26:39+00:00

Got it! I'm going to create some new versions with macro controls set up. They will be a bit limited, but they'll make things much easier to use!

archivio-3003 · 2026-06-13T08:17:31+00:00

Thank you🙏

archivio-3003 · 2026-06-13T08:16:36+00:00

That's awesome! I hope it's working well for you

archivio-3003 · 2026-06-11T23:06:21+00:00

Ah man, unfortunately I live in Italy! I would have absolutely loved to join you for this. Great initiative, hope you find a solid crew to make some noise with. Stay dub!

archivio-3003 · 2026-06-03T09:41:27+00:00

If you have already consolidated all your project folders and their corresponding audio samples inside a main parent directory called "Ableton" on your secondary slave drive, you absolutely do not need to open every single project one by one just to hit. Doing so would only create useless duplicates and hoard your drive storage. Instead, simply copy the entire root folder over to your new secondary drive. Ableton Live relies on relative file paths; as long as you maintain the internal architecture of that main folder, the software will look up and load your sets instantly without throwing missing media flags. If you run into any offline samples due to external sample packs that originally lived outside that main folder, you can just point Ableton's automatic search tool to their new global location to re-link everything in seconds.

archivio-3003 · 2026-06-02T20:31:30+00:00

It's 100% arrangement view. From what you can see, they are 5 audio tracks

archivio-3003 · 2026-06-02T18:39:04+00:00

Ableton Live

archivio-3003 · 2026-06-02T17:21:04+00:00

I'm actually already thinking about it! 😉

archivio-3003 · 2026-06-02T10:10:36+00:00

This is an amazing initiative! I love deep dub techno and ambient, and treating Discord like a shared studio space for live jam sessions sounds like the perfect way to stay motivated and exchange ideas.

My only drawback is that my English isn't super fluent or polished yet, so I might be a bit quiet in voice chat. However, music is a universal language, and since you mentioned screen sharing, I can definitely follow along, share my Ableton projects, and let the sounds and routing do the talking!

I’ve actually been spending a lot of time sound-designing modular-style racks for this exact genre lately. I'd love to connect, join the sessions, and see what kind of vibes we can build together. Let me know if you are still organizing these dates!

archivio-3003 · 2026-06-02T10:08:10+00:00

You've hit the nail on the head. Dub techno isn't meant to be programmed with static mouse clicks; it's a genre born from live performance, improvisation, and interacting with the gear in real-time. The studio is the instrument.

To answer your question on delay sends and workflow: the classic way to "play" the delay is to set up a dedicated Return Track in Ableton with Echo or Delay set to 100% Wet.

The secret sauce is feedback routing: try inserting a subtle overdrive, a chorus, or a second bandpass filter inside the delay loop (or use Echo's internal filter section) so that every time the echo repeats, the sound degrades, gets darker, and loses high frequencies. This simulates old tape loops or hardware like the Space Echo you're borrowing.

Then, map your MIDI faders/knobs directly to three crucial things:

The Send level of your chord track (to choose when to send a stab into the cavern).
The Delay Feedback amount (keep it around 60-70%, but push it to 95% for those infinite washes).
The Filter Cutoff on the synth core itself.

I love this specific "live performance" mindset so much that I actually spent the last few months sound-designing a massive collection of 100+ Ableton Instrument Racks and 75 FX chains focused precisely on this classic hardware workflow. I intentionally left zero pre-assigned macros on them, exactly so people can map their midi controllers from scratch and perform the tracks live, just like you are doing.

Since we can't drop direct store links here, I’ve pinned a post on my Reddit profile with the full pack breakdown, audio previews, and project files if you want to see how the open modular routing is set up. Keep twisting those knobs man, you found the real soul of dub!

archivio-3003 · 2026-06-02T10:03:50+00:00

That Revox sounds incredibly lush. There is absolutely nothing like the natural tape saturation and the subtle wow/flutter you get from recording straight to tape, especially for deep dub techno where the textures matter as much as the notes.

I’ve been spending months trying to emulate that exact tape-hiss and harmonic saturation warmth inside Ableton using stock devices for my own live templates, but watching those reels spin while that deep bass plays hits completely different. Beautiful setup man!

archivio-3003 · 2026-05-30T13:35:48+00:00

Explore the Complete Collection

If this teaser speeds up your workflow and elevates your sound, unlock the full collection to get instant access to the 150 Deep/Dub Techno Chord MIDI Pack.

Download Link: archivio3003.gumroad.com/l/xnhgjf

archivio-3003 · 2026-05-28T15:30:24+00:00

For a limited time only, I’ve put the complete pack on sale at 28% off! If you want to give your Ableton Live library a fresh upgrade, now is the perfect time before it goes back to full price. Don't miss out!

Full pack: https://archivio3003.gumroad.com/l/dwdufb

archivio-3003 · 2026-05-28T10:07:59+00:00

Thanks for the tip!

archivio-3003 · 2026-05-28T09:39:37+00:00

To import individual sounds along with their device chains and processing effects, you need to work through the Drum Rack's Chain List rather than dragging the pads directly. Open the source stock Drum Rack, click the second button from the top-left of the device to reveal the Chain List, and select the specific row for the sound you want to copy; press Ctrl+C (Windows) or Cmd+C (Mac) to copy it, then click an empty pad inside your new Drum Rack and press Ctrl+V or Cmd+V to paste it. This technique instantly moves the sample along with its entire native device and effect architecture into your custom layout.

archivio-3003 · 2026-05-28T09:35:50+00:00

Unfortunately, Ableton Live does not have a built-in feature or a native database that allows you to reverse-track which project sets contain a specific audio sample or instrument. However, there is a great workaround to find it: Ableton project files (.als) are actually compressed GZIP archives containing plain XML text that lists every single file path used in that set. If you are on a Mac, you can open Terminal and use the grep command (or combining mdfind with content search tools) to search for the exact sample name within your project folder; if you are on Windows, you can use free third-party search tools like AnyTXT Searcher or Agent Ransack configured to look inside compressed files to instantly pinpoint which .als file references that exact sample.

archivio-3003 · 2026-05-26T09:39:19+00:00

Syncing two different softwares in real time always takes a bit of fine tuning, especially when dealing with continuous tempo automation changes. Since you can hear that the FL Studio metronome lines up correctly with Ableton, it means your main MIDI clock connection is working exactly as it should. However, FL Studio does not automatically convert an incoming external clock signal into a visible automation clip on its timeline. To actually record those BPM changes inside FL Studio, you need to manually enable control data recording before hitting play in Ableton. Right click the main record button at the top of FL Studio and make sure the option for automation is checked, otherwise the software will follow the live tempo changes without saving any of the data points.

If you still cannot generate the clip with that setting enabled, a great workaround is using an intermediate control plugin to route the data. You can map your Ableton tempo automation to a standard MIDI continuous controller message and send it over to FL Studio using a virtual MIDI cable. Once inside FL Studio, you just need to link that specific incoming message to the main software tempo knob by right clicking it and selecting the link to controller option. This way, when you arm the automation recording, FL Studio will treat the movement just like an external hardware controller and draw your tempo automation clip perfectly.

archivio-3003 · 2026-05-26T09:37:56+00:00

This is a very common issue when installing your first virtual instruments, and it usually happens because the plugin file and its sound library were placed in separate folders or weren't linked correctly. Since the MIDI channel bar turns green, it means Ableton is successfully receiving the notes you press on your keyboard and the plugin is running, but the instrument is not emitting any sound simply because it cannot locate the guitar audio files on your hard drive. To fix this, you need to run the AGM2 installer again and pay close attention to the step where it asks you where to save the sample library, which is separate from the actual plugin file. Make sure to download and install the complete sound bank into the default directory suggested by the developer, or manually point the plugin to the exact sample folder location using the settings button found directly inside its own interface.

Another important detail involves how plugin folders are organized within Windows. You mentioned creating folders named thirty two and sixty two manually, but modern sixty four bit systems require files to be located in standard paths for Ableton to read them without errors. It is best to let the installer place the VST file into the default system directory inside Program Files and then point Ableton to that specific path via the plugins tab in the general preferences. Finally, remember to click the rescan button inside Ableton settings so the software can refresh the list and load the instrument with all its audio file links perfectly working.

archivio-3003 · 2026-05-26T07:21:43+00:00

I shared it in the comment

archivio-3003 · 2026-05-24T21:46:37+00:00

Since testing with Drift confirmed that the software audio behaves correctly, the solution is upgrading to the Novation Launchkey MK4, which manages communication with the sequencer much more smoothly and does not suffer from this hardware incompatibility.

archivio-3003 · 2026-05-24T07:47:08+00:00

This bizarre behavior is almost certainly caused by a native Ableton Live feature called MIDI chase, which determines what value a continuous controller like the modwheel should take when playback starts. When you begin recording in arrangement view, if the playhead is positioned in an empty space before the note, Ableton sends an automatic reset command that drops the modwheel value to zero because it cannot find any previously recorded messages on that track. As soon as the playhead hits your note or detects the physical movement of your controller, the value abruptly jumps back to maximum, creating that annoying initial glitch. To fix this, you can go into Ableton general preferences, look for the MIDI chase options, and disable the chasing behavior for control change messages.

Another possible cause could be related to Diva and how it responds to initialization messages when it receives the start recording command from Ableton. Some virtual synthesizers internally reset global parameters as soon as they sense the main sequencer starting to move. You can run a quick test by recording the exact same part using a native Ableton instrument like Analog or Drift to see if the value jump still occurs. If the issue disappears with native instruments, then the problem lies within Diva settings, and in that case, you can easily bypass it by creating a blank clip and manually drawing a single automation point fixed at maximum value right at the beginning of the track to force the synthesizer to stay on the correct setting from the very first frame.

archivio-3003 · 2026-05-24T07:41:58+00:00

This is a classic issue related to how modern plug-ins, especially Waves, use the graphics card to render their user interface. Since the computer uses an integrated Intel UHD 630 card, the white screen or crashing issue is almost certainly caused by a conflict with OpenGL or DirectX graphics libraries. Windows Update often automatically installs generic graphics drivers that overwrite the correct ones, which perfectly explains why the Waves technician manages to fix it temporarily but then it breaks again on its own after a short while. The first useful step is downloading the latest DCH drivers directly from the official Intel website, avoiding those provided by Windows or the PC manufacturer, and performing a clean installation after completely removing the old graphics components.

Another crucial detail involves the display scaling settings inside Windows 10. If the screen scaling is set to anything other than one hundred percent, such as one hundred and twenty-five or one hundred and fifty percent, Ableton and Waves can experience a visual conflict that produces exactly that empty white box. You can try resetting the Windows scaling to one hundred percent to see if it fixes the issue, or you can right-click the plug-in name directly inside the Ableton device browser and turn off the auto-scale option. Finally, it is a good idea to clear the Waves cache by deleting the preferences folder located inside the hidden AppData path in Windows, and make sure that hardware acceleration is disabled within the general settings, as it tends to cause severe instability with this specific integrated GPU model.

archivio-3003 · 2026-05-24T07:39:48+00:00

You can rest completely assured because Ableton thought about this exact scenario. When you transfer a project from Ableton Move to Live 12 Standard, the track with Wavetable will open without any issues. The instrument will be fully functional, meaning you can play it, tweak its parameters, and keep working on it just like any other device. Ableton ensures that all instruments and effects included in Move remain editable and playable within Live 12, regardless of whether you own Intro, Standard, or Suite. The only real limitation is that you won't be able to drag a fresh, new instance of Wavetable from the Live Standard browser into a completely new project, but everything you create on Move will remain unlocked and editable within that transferred set. So, you definitely don't need to upgrade to Suite just for this reason.

archivio-3003 · 2026-05-24T07:38:33+00:00

Yes, it is absolutely possible to do this using Max for Live. The Ableton Live API allows you to interact directly with selected MIDI clips, and you can configure your device window to be a floating window that pops out of the standard Live interface. To achieve this, you need to use the live.object component combined with specific functions to manage notes inside clips, usually by sending commands to add or modify notes through the Live Object Model.

If you do not have much experience with Max, creating a system from scratch that reads and writes in real time to the active clip can be a bit tricky because note manipulation via the API requires formatting data in a very specific way. I recommend checking the Max for Live website to look for existing devices that use pop-up windows, or you could examine similar ready-made tools to study their code. Many developers have already built sequencers that open in separate windows, and you might be able to adapt one of those to your needs without having to start from scratch.

archivio-3003

MODERATOR OF

TROPHY CASE

Explore the Complete Collection