Announcing Waveform 9 Public Beta

Discussion about: tracktion.com
Post Reply New Topic
RELATED
PRODUCTS

Post

dellboy wrote:
chico.co.uk wrote:
dellboy wrote:Setup a template with two audio inputs and two midi inputs,which is the maximum for tracktions antiquated input system with two different midi keyboards as inputs. (other daws allow the same midi input to be used on every track)
This isn't the place for "I don't know how to do this, so I'm going to moan that it can't be done", it's a beta testing thread, but you've been able to do this for years in Tracktion, although it's not very obvious, or intuitive.

Go to the Settings tab, Midi Devices, and click "Create new Virtual Midi Input". Call it whatever, let's say "Test". Click on the new "Test" input in the list. In the properties for the Test input, click on "Select Midi Inputs", and assign whichever hardware keyboard or controller you want associated with that.

Repeat for however many midi inputs you want to use simultaneously on multiple tracks. You can set them to use different midi channels, if that's what you send from your keyboard, to seperate key zones, or whatever.

Assign the new midi inputs to as many multiple tracks as you like, when you're recording.

Please post separate threads for things you want to do, but don't think you can.
Goodness, I do believe that I have found the answer to my problem.

In the midi filter you have to deselect whatever midi channel you do not want to play by greying them out.

I have been trying to select the midi channel I want by selecting it white.

Now I can set up an 8 track template with vsts assigned and use my midi keyboard to select tracks.
Yes, that deselect thing will work, if you want to have multiple midi channels on that input. Say, leave only 2 and 4 "selected", and grey out the others.

If you want to have just one midi channel per input, it's easier to type the midi channel number into the field below there, for that input. Eg, to set an input to only listen to midi channel 10, set it up like this;

.... apparently I can't post a picture, I get an error saying the "board attachment limit has been reached". Some bug with the forum software.

On the input properties, underneath where it says "Midi Filter" and the list of 1-16 buttons, there's a field for "Channel". Just type the number 10 in there, and that input only gets input on midi channel 10.

If you create 16 virtual inputs, numbered 1-16, you can swap between filtering one midi channel or another easily enough. I'm not saying this is ideal, or obvious, but it will work, and once you've set it up once, and maybe saved a template, (or whole track presets) you're good to go.
"my gosh it's a friggin hardware"

Post

aMUSEd wrote:Why are presets for Reaktor ensembles exportable but not presets for plugins?
The earliest plug-ins stored their "presets" in either .fxb files (b for bank) or .fxp (p for patch; "preset" should be reserved for ones supplied by the plug-in authors), but there's a lack of these on my PC, so it appears newer versions of VST use something else, which I'm investigating...
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

jabe wrote:
aMUSEd wrote:Why are presets for Reaktor ensembles exportable but not presets for plugins?
The earliest plug-ins stored their "presets" in either .fxb files (b for bank) or .fxp (p for patch; "preset" should be reserved for ones supplied by the plug-in authors), but there's a lack of these on my PC, so it appears newer versions of VST use something else, which I'm investigating...
I'm referring to Tracktion presets - ie the ones created when you right click on a plugin and save as preset. I have all mine saved that way with tags and this took a lot of effort to organise them all this way, it would be useful to be able to back them up and export them for use on other systems.

Post

The Tracktion ones appear to have a .preset suffix (the VST3 standard appears to be .vstprefix). But you'll be wanting to get the tags as well...
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

jabe wrote:The Tracktion ones appear to have a .preset suffix (the VST3 standard appears to be .vstprefix). But you'll be wanting to get the tags as well...
Do they, I can't see any on the HD except for the presets saved for reaktor ensembles which have a .trkpreset extension. If I right click on my saved plugin presets under 'Search' all I get is the option to add tags but nothing about where they are or import.export.

Post

Sounds like a possible bug in this beta version, with presets saved in previous versions.
"my gosh it's a friggin hardware"

Post

aMUSEd wrote:
jabe wrote:The Tracktion ones appear to have a .preset suffix (the VST3 standard appears to be .vstprefix). But you'll be wanting to get the tags as well...
Do they, I can't see any on the HD except for the presets saved for reaktor ensembles which have a .trkpreset extension. If I right click on my saved plugin presets under 'Search' all I get is the option to add tags but nothing about where they are or import.export.
Looks like it might just be the ones where the names begin with #T. I haven't been searching via the DAW, however.

The ones beginning with #T have theirs saved in Windows 10 under
c:\Users\yourname\AppData\Roaming\Tracktion\Plugin Presets\pluginname\
and then \factory\ for supplied ones and \user\ for user ones.

Aside from those, the only other likely looking ones are the *.trkpresets, which you know about, and a couple called presets.trkpresets, which don't look like one would be able to copy a single patch/preset from.

Looks like I'm not being much help!
[W10-64, T5/6/7/W8/9/10/11/12/13, 32(to W8)&64 all, Spike],[W7-32, T5/6/7/W8, Gina16] everything underused.

Post

Anyone else getting a lockup when you press record ?

I decided to leave it rather than shutdown,and after 45 seconds it came to life on its own and started to record and respond to the keyboard input.

I then tried to shutdown but was unable.

So basically I cannot beta test at this stage as the program for my setup is unusable.

Post

tatanka wrote:Does checking evrything from the reports on installation means you automatically get all crash reports ? I dont like automatically sent things normally but in this case would be helpful cause I definitely dont have the time to sent evry report. And I am sure there will be a lot, loading my first plugin (kontakt.....) into the new rack view just causes first crash after no more then 5 minutes....

Think I will stay on the new chord track/midi pattern things to explore if I hopefully find a normal, single plugin that loads without crash....
Turning on "Send Crashes" in the "Maintenance" page doesn't send the whole log file, effectively just the last line of the crash log. This is incredibly useful to help us narrow down crashes however and in particular it can help us recognise when we've fixed things.

For example at the moment I'm seeing a lot of crashes being reported when deleting an Edit. I think this may be due to a bug we've found closing a Rack. When we make this change, in the next version we can compare the number of automatic reports for the same line to see if this has improved the problem.

The other main useful place for this is plugins. If a plugin is the cause of a crash this will get reported. We can then easily see how often this particular plugin (and plugin type) gets reported. This will help us identify problematic plugin without users having to manually report them and give us an idea of what the most problematic ones are.

I'm also hoping that providing this kind of info to the plugin developers will help them work with us to fix things. It's a lot more compelling to say "This plugin has crashed in our software 10,000 times" rather than "We've had a user report this plugin has crashed". It shows that there probably is a business case for them to work with us to fix it.


For additional information, all data sent to us is completely anonymous. The only uniquely identifying piece of information is a random 128-bit UUID that is generated the first time you open W9. It doesn't relate to anything on your system.

If "Send System Info" is on we collect some basic system info such as OS version, CPU speed and amount of RAM to get an idea of of systems W9 is being used on so we can target our testing to similar cases but again, this isn't uniquely identifying.

Finally, we only send the logs to the server twice during the app's run, once at startup, once at shutdown. If the app crashes, we dump the current log to a file and then send that when the app next starts up. This means there's no constant pinging to the net. We don't doing any logging on the audio thread and the overhead of this is completely negligible (it takes about 10,000 times more CPU cycles to to draw a single pixel on the screen than to log one event and that happens 30-60 times per second!).

You can always use the "Show Usage File" to see what is being sent to us but it's mostly boring stuff like what plugins have crashed and what type of modifiers are most popular etc.

I hope this helps clarify the feature. Dave

Post

Thank you Dave for clear explanation,

so I will leave evrything on for the beta-testing period, helps you and helps you and me saving time on sending and replying to reports. good idea :tu:

Post

chico.co.uk wrote:
dellboy wrote:Setup a template with two audio inputs and two midi inputs,which is the maximum for tracktions antiquated input system with two different midi keyboards as inputs. (other daws allow the same midi input to be used on every track)
This isn't the place for "I don't know how to do this, so I'm going to moan that it can't be done", it's a beta testing thread, but you've been able to do this for years in Tracktion, although it's not very obvious, or intuitive.

Go to the Settings tab, Midi Devices, and click "Create new Virtual Midi Input". Call it whatever, let's say "Test". Click on the new "Test" input in the list. In the properties for the Test input, click on "Select Midi Inputs", and assign whichever hardware keyboard or controller you want associated with that.

Repeat for however many midi inputs you want to use simultaneously on multiple tracks. You can set them to use different midi channels, if that's what you send from your keyboard, to seperate key zones, or whatever. Assign the new midi inputs to as many multiple tracks as you like, when you're recording.

Please post separate threads for things you want to do, but don't think you can.
Geez. I’ve been trying to figure out how to do that for ages. Thanks!!
iMacPro 1,1 | 64gb | OSX 10.15.7
http://www.gesslr.com
http://www.storyaudio.com

Post

this got me a smile
Quad Core | 16GB DDR4 | 240 GB SSD + 1 TB HDD | FLStudio ASIO | 1 GB Video | W10 x64

Post

If it's a public beta, shouldn't there be a public link?

Post

putting my cynics hat on( did I spell that right?) Tracktion require a log in so they can spam you with offers and stuff.( but, to be fair most devs that offer a public beta scheme do require some kind of contact info). :)
Music is the language of the soul.

The best music comes from the heart of the performer or composer.

Post

putting my cynics hat on( did I spell that right?) Tracktion require a log in so they can spam you with offers and stuff.( but, to be fair most devs that offer a public beta scheme do require some kind of contact info). :)
Music is the language of the soul.

The best music comes from the heart of the performer or composer.

Post Reply

Return to “Tracktion”