New DAW. Lookin for a beta-testers

[maxwellthen]

This sounds really cool, I'll definitely check it out if there's ever a Mac version!

[_al_]

Never even used a tracker, but I do respect the loyalty of you tracker guys.
What's the deal with these things?
Is it just the nostalgia they invoke that gets you in the zone?
Or is there something in their workflow that lets you work faster and more creatively?

Either way, I hope this goes well for you guys

[jens]

or is it in Debian etc. like FL Studio was for decades?

You probably mean Delphi. Debian is a Linux distro.

[mjolnir]

the GUI looks nice.
I don't know how to use Trackers.
I've seen them in use, but I don't know where to begin.

[art&sound]

If it ran on Mac and had VST3/CLAP I would be all over this thing.

[mjolnir]

I'm not really in a position to beta test, but I wanted to say, bravo! nonetheless... thanks for creating/developing.

[eLawnMust]

I would but I use XP so no go... hell, I haven't even used all the old trackers yet... Trackers are just 'Step Sequencers With Interactive Detailed Digital Readout' In many ways simpler than piano rollers as being a 'spreadsheet' one can see how different tracks align row-by-row thus it's like a piano roller where you can see all the tracks in a single roller but better as you can manipulate oddball segments of different tracks all at once...

Unfortunately this tracker looks very busy like renoise which is too busy for a fast workflow... One can take any DAW & load as a VSTi the ReViSiT Tracker or Skale Tracker (Very good sound, very fast workflow) inside your host...

Looking at the bottom of the page it appears there is a piano roll option... The test is how stable it's gonna be which is top priority (Old AXS 3.04b STILL crash-free)...

I recommend using Aodix 4.2, I have a thread right on here on it... Best fluid piano roller-tracker combo & machine view hookups which are the best... I even run Skale Tracker inside Aodix (tracker inside a tracker)-


Work can be done in part or whole in either taking advantage of strengths in both... Aodix is great with MIDI plugs as well with all kinda hookups in a machine view fashion making it all easy..EASY!...

Aodix even runs the old freeware Usine VSTi inside it just fine-


Machine view MIDI hookups all DAWs should be like this-


Patternless is the way to go for better music compo & Aodix has it (old DeltaSP as well), Fluid piano roll you can even slide notes under one another if you wish-


Just hit chords & they punch right in-

[Charlie Firpo]

Elawnmust, does the "new" (i think i saw someone did some fixes on it?) version of Aodix support vst3?

About the new tracker, i wish the best of luck to the Op. Hope that it will see the light of the day. I looked at the screenshots and it looks impressive. Both Pianoroll & tracker interface. Best of two worlds.

[eLawnMust]

Some of us could care less about VST3... If you don't know music it's not going to make it any better I don't care what 'gimmick' or 'upgrade' there is & boy there's plenty out there...

Plenty of combo piano roll-trackers have come & gone, Aodix still updated all old issues fixed

Aero Studio (mouse draw only)
DreamStation II (very nice)
Frinika (no good)
VersaTracker (too old, sounds bad)
BeroTracker (single instrument tracks, nice envelope drawing)
Psycle (single instrument tracks, LUA piano roll, sorta updated)
Aodix 4.2 Enhanced (as previously mentioned, updated)
BUZE Tracker (Vertical like Aodix, Vertical envelope lanes, way more function than FL studio)
BUZZ (very weird, like using a different program)
Renoise (glued-in extension sort of BS)

The best one's are where the piano roller is vertical & follows closely to the tracker, Aodix & BUZE being tops that way...

Concentrate on learning/making better music than 'VST3' you then can make music in anything new or old for f**k's sake, I do it in some with just high-quality samples & internal or VST FX...

[Charlie Firpo]

Elawnmust, i hear you. It was just a question People can make great music with whatever they choose. From your list above: I loved Dreamstation 1 & 2.

[gentleclockdivider]

Renoise (glued-in extension sort of BS)

Dude , seriously .

[DJ_Indikator]

VST3/CLAP support is finally done. But it definitely needs more in-depth testing. As for the formats themselves - VST3 has too many helpers and too much mosaic documentation. Some things have to be literally searched for bit by bit on the Internet. Steinberg's own documentation system is completely confusing - a bunch of sites, a ton of links. Of the ton of SDK files, you actually need 3 dozen. Very difficult. With CLAP, the situation is completely opposite - everything is simple and clear. One header clap.h, and an extensions system. Very easy to embed into the code. True, unlike VST3, some difficulties were precisely in the lack of documentation. Of course, the comments in the header files are written very well and clearly, but some things were not immediately clear. For example, start_processing / stop_processing is it even needed or not? But overall - a good format. Information about the product is still there www.mak-sa.net/software

In the near future - I continue to do UNDO/REDO and write workflow documentation.

Cheers

[eLawnMust]

Elawnmust, i hear you. It was just a question People can make great music with whatever they choose. From your list above: I loved Dreamstation 1 & 2.

Yes, DS1 was quite good for the time... Proof being some of the excellent example tunes that came with it... Still good as a MIDI sound module for MIDI-Out programs...

DS2 was quite the cadillac for a combo tracker-piano roller, robust covering everything needed without unnecessary feature set... You could change the 'sex' of any VSTi-VST loaded in as well (VSTi-to-VST or VST-to-VSTi)... I liked the vertical envelope controller lanes for MIDI CCs or you could create automation track in arrange view for VST params...

[Xenakios]

For example, start_processing / stop_processing is it even needed or not?

Yes, calls to those have to be done by the host. (From the audio thread, which can be a bit irritating since you need to keep track if you already started processing for the plugin. Calling start_processing again while the plugin is already processing is an error.)

It may useful to write a custom Clap plugin for host testing purposes, using the Clap C++ helpers with all the behavior checks turned on. If the plugin or host has some bad behavior, those will be caught in the debugger.

For example processing started/stopped state is checked when the host tries to call process like this by the C++ helper class :

Code: Select all

template <MisbehaviourHandler h, CheckingLevel l>
   clap_process_status PluginProxy<h, l>::process(const clap_process_t *process) const noexcept {
      ensureActivated("clap_plugin.process", true);
      ensureProcessing("clap_plugin.process", true);
      return _plugin.process(&_plugin, process);
   }

[Drew Lake]

I would love to try this out but on Windows 10 it crashes to desktop as soon as it tries to scan my VST folders.