Version 12 release date?

[jules]

It shouldn’t be that hard to have a proper editor like the one we had until Tracktion 6.

That made me laugh! The old one got scrapped because it was literally the hardest, most unmanageable disaster of a feature that we ever had! And TBH it's my fault, because I should have foreseen the problems it caused.

Waveform (and all DAWs) have ridiculously complicated GUIs. And the GUI evolves rapidly. If you allow every UI element to be individually set by a scheme, then we can't add or change any part of the thousands of existing GUI components without manually checking and updating every single built-in scheme. And users have their own custom schemes which won't handle the new stuff we're adding. The sheer number of GUI elements vs number of schemes means that the numbers are impossible - we got rid of it because it was slowing our development down massively.

I think Dave's new system is genius because it packs a lot of control into just a few parameters, so we can move fast on changing things, while being confident that people won't end up with black-on-black buttons or invisible widgets!

And W12 looks great, IMHO. But if there's some particular GUI element you have an issue with, maybe point it out and it's something we could fix if we agree that it could look better.

[FigBug]

Googling info on it was so much easier when it was called Tracktion. Calling it "Waveform" is a bit like calling it "the" in terms of distinctiveness for googling. Should have stuck to the name for the DAW and changed the name of the company instead of the other way around.

You are probably correct, however it was so much easier to rename the product than the company. It started getting weird once we had other products. Waveform can't be worse to Google than Live, Logic, Audition, Reason -- they are all just generic words.

[UnionS8]

Googling info on it was so much easier when it was called Tracktion. Calling it "Waveform" is a bit like calling it "the" in terms of distinctiveness for googling. Should have stuck to the name for the DAW and changed the name of the company instead of the other way around.

You are probably correct, however it was so much easier to rename the product than the company. It started getting weird once we had other products. Waveform can't be worse to Google than Live, Logic, Audition, Reason -- they are all just generic words.

Yes, but followed by a version number it gets better. Not so much Waveform. I'm still getting different medical Waveforms 11 and 12 Nevermind. A thousand thanks for an excellent product

[Matttochistic]

I always search for "Tracktion Waveform (version #)" and get plenty of results. Using the "exact phrase" quotations helps even further.

[Bennett]

The problematic midi output seems the same in either version: a kind of a midi-hiccup when playing buzz strokes on pads on the TrapKAT controller. This is midi based and definitely not audio. Now, I am not much of a drummer, but my buzz strokes are absolutely disgusting and unusable in Waveform.

I am concerned that the data is missing and I wonder if other data is being thinned out or hiccupped. Again, this issue isn't reproduced in any of the other DAWs I have on my computer, so I'm sure that this is not related to my relative weakness as a percussionist.

I’m experiencing the same thing using a Yamaha DTX and Focusrite interface. It’s dropping midi notes to BFD1 2 and 3. This does not happen in my other hosts or earlier versions of Waveform.

[FigBug]

I’m experiencing the same thing using a Yamaha DTX and Focusrite interface. It’s dropping midi notes to BFD1 2 and 3. This does not happen in my other hosts or earlier versions of Waveform.

I think this issue is your drums sending 2 note ons before sending a note off. A lot of electronic drums send the note off X ms after the note on, they don't actually detect when the stick is lifted off of the drum surface.

So if you are drumming slowly, it sends note on, note off, note on, note off and it all sounds ok.

But once you get going really fast it sends note on, note on, note on, note off, note off, note off.

Look in the settings for your drums and see if you can configure the time to the note off.

Otherwise I'll need to rework the midi input to reorder the incoming events. (I want to do this anyway, but it won't happen in the very short term)

[Bennett]

I’ll try to grab the midi log for you. I don’t think the controller is sending two note on messages but I will confirm.

Thanks for your help!

[Bennett]

I’m experiencing the same thing using a Yamaha DTX and Focusrite interface. It’s dropping midi notes to BFD1 2 and 3. This does not happen in my other hosts or earlier versions of Waveform.

I think this issue is your drums sending 2 note ons before sending a note off. A lot of electronic drums send the note off X ms after the note on, they don't actually detect when the stick is lifted off of the drum surface.

So if you are drumming slowly, it sends note on, note off, note on, note off and it all sounds ok.

But once you get going really fast it sends note on, note on, note on, note off, note off, note off.

Look in the settings for your drums and see if you can configure the time to the note off.

Otherwise I'll need to rework the midi input to reorder the incoming events. (I want to do this anyway, but it won't happen in the very short term)

There's definitely something going on with the note on, note off. Please see the attached BFD3 logs. I did a snare buzz roll and when using BFD3 standalone, the note on-off messages are neatly ordered. When in Waveform, you can see how the note on-off are "mixed up". The same thing happens when you do any quick articulations, example: double bass. Is it normal for Waveform to send continuous CLOCK messages as well?

[fde101]

Is it normal for Waveform to send continuous CLOCK messages as well?

It should be: the standard is for those to be sent 24 times per quarter note to keep everyone in sync:

https://en.wikipedia.org/wiki/MIDI_beat_clock

[SonnyBoy]

It shouldn’t be that hard to have a proper editor like the one we had until Tracktion 6.

That made me laugh! The old one got scrapped because it was literally the hardest, most unmanageable disaster of a feature that we ever had! And TBH it's my fault, because I should have foreseen the problems it caused.

Waveform (and all DAWs) have ridiculously complicated GUIs. And the GUI evolves rapidly. If you allow every UI element to be individually set by a scheme, then we can't add or change any part of the thousands of existing GUI components without manually checking and updating every single built-in scheme. And users have their own custom schemes which won't handle the new stuff we're adding. The sheer number of GUI elements vs number of schemes means that the numbers are impossible - we got rid of it because it was slowing our development down massively.

I think Dave's new system is genius because it packs a lot of control into just a few parameters, so we can move fast on changing things, while being confident that people won't end up with black-on-black buttons or invisible widgets!

And W12 looks great, IMHO. But if there's some particular GUI element you have an issue with, maybe point it out and it's something we could fix if we agree that it could look better.

Hi Julian,
Many thanks indeed for your reply.
I admit I had to exaggerate a tiny bit, so we can have this topic back on the table - although I’m glad I managed to make you laugh on 1st April
I am very much aware of how hard it was to update every GUI component in connection with the colour scheme.
In my opinion however, T5/T6 was the best GUI ever in terms of simple/sharp design, simplicity of use, and no-frills user experience.
Therefore a reasonable suggestion would be extending Dave’s system to just a few more settings, which to me are so essential that, believe it or not, I still only use T6 (although I’ve bought all subsequent versions).

These settings would not have to change with every upgrade, since they are typically “hard“ features:
1. Different colours to distinguish between native Tracktion plugins, third party plugins and virtual instruments;
2. Waveform contrast - I would like the option to have it plain black on a pastel or light background (as opposed to dark grey currently);
3. Different colours (other than green and red) for muting and soloing;
4. Separately settable colours for the play cursor (black is also used for other features and is less easy to distinguish) and the loop (in/out) markers;
5. Loop markers without black borders - a simple colour is more visible and sharp than one with borders;
6. Simple grey/black nuances for the volume/pan filter - currently the colour changes along with the loop markers - this is a weird one;
7. And finally the possibility to switch between rounded or sharp corners for the buttons. I understand some people like them square and others like them rounded - I know there is a whole design debate about this. T5/6 buttons have curved corners, similar to Pro Tools and Cubase. I personally find it more pleasing and it gets me to focus on the content rather than on the component.

I am attaching a T6 screenshot with my current custom colour settings, so you can have an idea of what the above-mentioned suggestions are about.
Many thanks for your patience and a huge thank you for what you’ve done for the musicians community (whatever that means…) over the last 20 years.

[jabe]

(If only it was still called Tracktion, though

Googling info on it was so much easier when it was called Tracktion. Calling it "Waveform" is a bit like calling it "the" in terms of distinctiveness for googling. Should have stuck to the name for the DAW and changed the name of the company instead of the other way around.

I know what you mean. I tend to put both words into searches.

[Bennett]

I think this issue is your drums sending 2 note ons before sending a note off. A lot of electronic drums send the note off X ms after the note on, they don't actually detect when the stick is lifted off of the drum surface.

Otherwise I'll need to rework the midi input to reorder the incoming events. (I want to do this anyway, but it won't happen in the very short term)

Bump. Any progress on reworking the midi input?

[rockstar_not]

I bought 11 pro. Presently at 11.5.2 Seems 11.5.18 wont fully install - should I be thankful for that?