![]() ![]() Should you be aware of the location of a document that might be of use, (which must be hosted on the DAW manufacturer’s site or a known partner), please do let us know so we can include a link to it. ![]() The document links below are to facilitate fuller use of the controllers once set up with the DAW of your choice. Separate ‘set up guides’ on the site and in the DAW manufacturers manuals/online documentation will assist you with this. Please note, that this documentation is not about ‘how to set up your controller’. the DAW manufacturer’s main manual or support team for example. However, it is always best to seek this information direct from the source i.e. if you are unable to find the specific information you seek in your own DAW’s documentation, you may well find helpful information in another document for a different DAW. Some documents are more in depth than others and it is possible that some may be cross-transferable i.e. Therefore, because we want our users to get the most out of their controllers and where possible, be able to use plug in control, control virtual instruments, use V pots/rotary controllers to control functions such as panning, use the onboard DAW EQ and Sends etc., we have produced a table of support materials users may find helpful. Given that current iCON controllers now support fifteen or so DAW’s, (if it’s Mackie Control it will run), producing and maintaining accompanying manuals for each DAW would be entirely impractical, (especially since when DAW manufacturers update their DAW’s, say from version 8 to version 9, this can change the landscape yet again). Your DAW manufacturer may be able to provide a list of these messages, although some do not publish this information to the public. You MUST have an in-depth understanding of your DAW’s MIDI messages in order to engage with this task. Please be clear it is highly inadvisable to use the iMAP to re-program switchgear, unless you intend re-programming ALL switchgear, (all faders, knobs and buttons). Remember once you have re-programmed your button, it is usually the case that the DAW controller will retain the ‘memory’ of your re-programming indefinitely, (until such time as you over-write the function). Please exercise caution with this and ensure you have researched how to do this within your DAW thoroughly, before proceeding. it does not fulfill the function you think it should, you can usually re-program that button using the MIDI learn capability of your DAW. It is worthwhile remembering that these are generic controllers and are not DAW-specific.Īnother note worth remembering is that, should your DAW send messages to a specific button, say the ‘Mixer’ button, that you find unhelpful i.e. The QCon series and the Platform series, although fantastic in their own right, cannot alter or interpret these communications. This is usually not significant, but it can lead to confusion and some frustration, because the functionality of the same machine in one DAW is not the same as in another. In other words, even though the language most used, (Mackie Control Protocol) in most cases is the same, the direction of travel of this ‘code’ can be differentiated from DAW to DAW.īecause this communication from the DAW is variable, the resulting functionality of the MIDI controller is therefore variable. In short, the answer is that the messages every DAW sends to generic control devices such as the Platform Nano or QCon Pro G2 are different. In order to help users of devices such as the controllers in the iCON QCon series, (iCON QCon Pro, iCON QCon Pro G2, iCON QCon Ex G2, iCON QCon Pro X, iCON QCon Pro XS), the Platform Series (Platform M+ and Platform X+) or single fader devices such as the iCON Platform Nano, many Digital Audio Workstation (DAW) manufacturers produce ‘Remote Control Device’ manuals, (sometimes referred to as a ‘Mackie Control’ manual). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |