Main menu
You are here
Individual MIDI outs and ins for each track
Hi, Forum. New QTractor user here.
Other than the Quick Start Guide 0.5.x by Seth Kenlon & Klaatu, I don't think there's any more online documentation for 0.5.x. Please let me know if I am wrong.
At the moment I am wondering if there is a way to give a MIDI track it's own MIDI in/out ports. I only get a Master and the options give me the choice for a player output(what is that?).
I am using a hardware synth and at the moment with only the Master MIDI port I have to change the MIDI channel to separate the MIDI data from software synths and other hardware synths. Other sequencers(unnamed) do this and is a pretty nice feature since it lets you use more than 16 channels of MIDI and stops one from having to change the MIDI channel on the hardware synths. This would also save a lot of setup trouble if working with other DAWs.
Am I missing how to do this?
Thanks,
Sean
re. Individual MIDI outs and ins for each track
the way to accomplish this is to create new MIDI buses which are at your disposal (menu View/Buses....)
you assign input / output buses to tracks.
MIDI buses are in fact ports when regarded from the outer world; MIDI buses / ports may address 16 MIDI channels each, as usual.
nb. current online documentation is one hell of a nice work of the respective authors / users. considering that the majority of its / their focus is / was on the audio stuff, it simply lacks one hell of info about most things regarding MIDI. if any, but the obvious :)
how about you taking some notes now and then help on the wiki? o.O)
your help will be most welcome.
cheers
Join SourceForge.net
Thanks, Rui.
I registered as seanbeeson at SourceForge.net. If you give me editing permissions I will see about added to it.
It wasn't so obvious that one wrote a new name and then the create button activates to add a new MIDI bus. Got it figured out now, however.
It all keeps getting better....
Thanks,
Sean
re. Join SourceForge.net
yay, Sean Beeson is now a member of wiki editors board .
take care that junkyardsparkle is in the process to import the (old) user manuals into the wiki (as seen in that other thread).
cheers
re. Join SourceForge.net
Thanks, Rui.
The questions is is should I add to what is already there(add new sections under relative topics) or make new how-to pages?
Sean
re. new how-to pages
new how-to pages sounds good.
what's already there is still the old manuals content. although pages that are titled after "Manual - ..." are about to be the new working version, where things may start to get improved with new material. isn't that so, junkyardsparkle?
seeya
wikistuff
Yep. The "Manual - *" titled pages are basically a copy of the old manual, which is a well written and nicely structured document, and have so far only been updated with information about LV2 in the relevant sections. I don't make deep and extensive use of the midi sequencer, myself, so please feel free to update/add sections related to that... or anything else, for that matter. I haven't used qtractor a lot recently, so I'm probably better able to do copy edits and cleanups to content that other, more experienced users want to add in a quick-and-dirty manner. If you want to add some "how to" or quick reference pages, maybe give them all a consistent "How to - " title prefix for easier collection? These would probably complement the in-depth manual well.
:-)
I understand. I agree also and have followed suit.
How-tos can also lead to finding their way into a manual. At any rate getting more of a knowledge base up under one place will be good. I already have another How-to in mind. I've turned to setting up my fluxbox desktop to verify somethings with Qt and KDE settings along with how they function under Gnome and after that I'll write it up.
Not sure if either of you saw the one I wrote up already.
Sean
Meta pages.
I'm going to create a "Meta - discussion" page on the wiki, since the notification system there works for me, and the one on this site doesn't.
Meta pages
Great Idea.
Sean
Add new comment