Wave Alchemy - Triaz Native - No Kontakt -- Free for current owners!

[neverbeeninariot]

Even if I have to put all my drums samples in the USER dir and having them double on the disk now (TAL drum / ATLAS / ADSR Drummachine user here)

You can create a file system junction between your sample folder(s), and the location that Triaz expects them to be (user folder), no need to duplicate everything. If you're on Windows, there's a utility call Link Shell Extension (https://schinagl.priv.at/nt/hardlinkshe ... nsion.html) which makes this pretty trivial to do (right-mb-drag-drop->junction).

To an application, a junction looks like a regular folder.

I have a few sample based instruments but all my samples are in one location, and then linked to where those instruments expect to see them.

[neverbeeninariot]

Been playing around with the demo for a while today and have managed to get some seriously wonky dub beats out of it.

I really like the sequencer and step-modulation options, really cool, and that it exports MIDI perfectly with all the step mods (pitch, etc), is just awesome. Using the motion sequencer to drift between different layers, especially on percussion sounds is also tres cool.

A couple of quick(ish) questions for Wave Alchemy -

Is is possible to remove a sample from a layer? I can't figure out how to do this (maybe add right-click menu to the waveform view if it's not currently possible?).

Is there a table/list of CC's that used for the step (e.g. pitch) modulations?

Another quirk which I haven't found a solution for - when you randomise a sample layer, it uses the current Drum type, but this seems to also limit the selection to a particular Tag. It would be great to select from all 'Perc-Acoustic' samples without also being forced into a Tagged category like 'Click'. Is this possible?

Overall, I'm having a blast with it so far

[imrae]

Woo, exciting stuff!

As a Complete Drums owner: should I install this and start importing folders, or is there some slick integration in the pipeline I should hold out for?

For now, just drag all the sample pack 'folders' from within Complete Drums 2 (Drum Tools 02, Syncussion Drums etc) into the following location 'Triaz / User Samples' (this user samples folder is located in the location where you placed the Triaz content when running the Content Installer. Then open Triaz, click the 'Refresh button' next to the search filed in the browser and all those pack names will now show up on the left of the browser under the 'user samples' section. The tags on the right will now also show the first two layers of folder structure, and the samples will be revealed on the samples list just like the factory samples are.

For an update we will add a sample import menu like XO for example, where you can link locations to the browser. You can do this already if you know how to use symbolic links, but we'll of course add this as an update. There was only so much we could fit in in V1, and didn't want to delay the release more than we already have done

We will also make our most popular packs fully expansion ready for Triaz too. with installers just like the factory content.

Cheers! I do know how to make symlinks so can avoid wasting disk space. This is working fairly nicely but there are a couple of pain-points maybe worth highlighting now (as they are quite fixable )

triaz_capture.PNG

As we can see from the screenshot:

• The "Drum" category is based on the folder name and it only traverses one level to look for these. As a result, for this multi-drum-machine pack the directory level of drum machines gets picked up as the "Drum" names, when these actually live at the next level down.
• High-quality sample providers such as Wave Alchemy often use rather long filenames with prefixes identifying the sample pack. In this three-column view, that makes it impossible to read the sample names except be mousing over them individually!

It's worth bearing in mind that some other excellent sample packs order things differently, e.g. Samples From Mars packs are generally ordered Drum -> Processing -> samples. You'd think that would work better than WA's own packs, then! Well, not quite...

triaz-mars.PNG

The names have been pruned back to their numerical prefixes! These are used to help get the folders to show up in a standard order.

[Vortifex]

I've never really used a drum sequencer in my DAW because my DAW is a sequencer. Can someone explain how they use the internal plugin sequencer in the context of making a track? I like to vary my percussion through the entire track and something like this feels restrictive.

[db3]

I've never really used a drum sequencer in my DAW because my DAW is a sequencer. Can someone explain how they use the internal plugin sequencer in the context of making a track? I like to vary my percussion through the entire track and something like this feels restrictive.

Each preset can have up to 12 patterns which can be triggered by MIDI notes in the DAW (C6 upwards).

[neverbeeninariot]

I've never really used a drum sequencer in my DAW because my DAW is a sequencer. Can someone explain how they use the internal plugin sequencer in the context of making a track? I like to vary my percussion through the entire track and something like this feels restrictive.

The sequencer lanes allow for pitch, velocity, repeat, chance, and start position modulation on a per-step basis (this can also be exported to the DAW, MIDI or audio). Reminds me of working in my old Yamaha drum machine which had a similar step mod capability (albeit more restricted).

The motion sequencer can allow for things like blending between the different sample layers, panning, or FX sends etc. It can get quite dynamic, pretty quickly.

[Vortifex]

So you just build patterns in the plugin and trigger them as appropriate? I can see the benefits of the extra features like layering and motion sequencing. I guess I could always just disable host sync and sequence the samples in the DAW instead, or export patterns to .wav and chop 'em up.

Does this contain samples from Drum Tools 02? Just wondering if there's any overlap.

[neverbeeninariot]

You can build patterns in the plugin then trigger them from the host, or drag the midi to a track and use it for playback, or drag the stems out. There are also enough outputs for all the drum and FX channels.

If you're used to using the DAW for sequencing, then it might not fit your workflow, but it's worth a demo.

I've no idea which samples are included. I have a few WA packs and I'd be surprised if there wasn't some overlap.

[dermage]

You can build patterns in the plugin then trigger them from the host, or drag the midi to a track and use it for playback, or drag the stems out. There are also enough outputs for all the drum and FX channels.

If you're used to using the DAW for sequencing, then it might not fit your workflow, but it's worth a demo.

I've no idea which samples are included. I have a few WA packs and I'd be surprised if there wasn't some overlap.

afaik they do new samples for each product. Triaz has its own samples and they even expanded them. Of course samples may sound similar, but afair they record new ones for each sample pack/product (not counting bundles or Live packs of course)

[Vortifex]

Is there a way to exclude layers from humanization, or set it per layer? I did RTFM but didn't see anything about that so I'm assuming the answer is no.

[chroma]

Also the option of probability (0-100%) of generating a step in randomizer mode (like in ADSR drum machine) would make it even better. It is a best of all worlds combined in one.

Not exactly what you want, but
- randomize the drum kit (e.g. go to drum - randomize all)
- go to the chance page
- randomize all again

Now, you have probabilities for each step.
It's not very intelligent yet but all the pieces are there for them to improve it over time.

Even if I have to put all my drums samples in the USER dir and having them double on the disk now (TAL drum / ATLAS / ADSR Drummachine user here)

Not sure if you are on windows or mac, but on Mac, using 'Make Alias' didn't work, but doing symbolic links in a terminal did work. To do that, you do

Code: Select all

ln -s <source> <target>

where source is where your existing samples are, and target is some name at the root of the user library.

The auto tagging has some expectations that may not fit with the way Triaz wants to see them - e.g all my Noiiz files have the pack at the top, so it pulls that in as the list of drum types - so it may be worth rearranging everything anyways; I'm planning to do that soon. Some of the wave alchemy stuff just came up easily though (of course!).

[neverbeeninariot]

[*] High-quality sample providers such as Wave Alchemy often use rather long filenames with prefixes identifying the sample pack. In this three-column view, that makes it impossible to read the sample names except be mousing over them individually!

If you dig into the samples provided with Triaz, they are exactly the same as WA's other sample packs, they have long names with prefixes. The reason they show up in the browser with a short name is because they are all referenced in a file called sampleCache.json (\AppData\Roaming\Wave Alchemy\Triaz).

This file is very big, it contains at least all the factory samples, and any directories that have been symlinked/copied then scanned by Triaz. The difference is that the user content does not have a very friendly name (looks to be the file name), though you can add one. But yeah, not doing that for several thousand samples...

Code: Select all

Triaz factory
[
  "Agogo Acoustic",
  [
    "Blocks & Bells",
    "Agogo",
    "<path>)\\Wave Alchemy\\Triaz\\Triaz Expansions\\Triaz Core 01\\Blocks & Bells\\Agogo\\wa-triaz-blocks_bells-agogo-agogo_acoustic.wav"
  ]
],

User samples
[
  "wadm drumfire hat 002",
  [
    "drumfire df-2000",
    "hats",
    "<path>\\Wave Alchemy\\Triaz\\User Samples\\Drum Machine Collection\\drumfire df-2000\\hats\\wadm_drumfire_hat_002.wav"
  ]
],

[noddog]

Wow, this is a great product! I've been using XO along with Triaz-Kontakt and a few other samplers, but now I can see the new Triaz becoming my main drum solution.

Question: is there any way to copy kits and/or patterns from Triaz-Kontakt over to the standalone version?

[kraster]

Is there a way to exclude layers from humanization, or set it per layer? I did RTFM but didn't see anything about that so I'm assuming the answer is no.

Don't think so but humanize per track/Channel would be awesome.

[imrae]

[*] High-quality sample providers such as Wave Alchemy often use rather long filenames with prefixes identifying the sample pack. In this three-column view, that makes it impossible to read the sample names except be mousing over them individually!

If you dig into the samples provided with Triaz, they are exactly the same as WA's other sample packs, they have long names with prefixes. The reason they show up in the browser with a short name is because they are all referenced in a file called sampleCache.json (\AppData\Roaming\Wave Alchemy\Triaz).

This file is very big, it contains at least all the factory samples, and any directories that have been symlinked/copied then scanned by Triaz. The difference is that the user content does not have a very friendly name (looks to be the file name), though you can add one. But yeah, not doing that for several thousand samples...

Code: Select all

Triaz factory
[
  "Agogo Acoustic",
  [
    "Blocks & Bells",
    "Agogo",
    "<path>)\\Wave Alchemy\\Triaz\\Triaz Expansions\\Triaz Core 01\\Blocks & Bells\\Agogo\\wa-triaz-blocks_bells-agogo-agogo_acoustic.wav"
  ]
],

User samples
[
  "wadm drumfire hat 002",
  [
    "drumfire df-2000",
    "hats",
    "<path>\\Wave Alchemy\\Triaz\\User Samples\\Drum Machine Collection\\drumfire df-2000\\hats\\wadm_drumfire_hat_002.wav"
  ]
],

Ooh, that's interesting. If it's JSON then I could easily enough whip up a Python script that does clean up the names of several thousand samples

Would need to rerun (with tweaks?) each time the library is re-scanned, I guess.