Our teams are fully committed & invested into continuing this modernization with the rest of the product to bring it to the place that serves the needs of today’s music maker. The powerful new Browser is the first major example of this and based upon extensive user research and testing. Thus, we’ve chosen to approach this incrementally and improve the underlying workflows as we go. Given KONTAKT's role as a professional tool for many music makers, we’d like to avoid major disruptions to workflows, ensure stability, and deliver benefits early. In order to modernize KONTAKT's look and feel, and support high-DPI monitors, we’ve needed to transition KONTAKT to a new graphics rendering technology. In the Preferences dialog ( VSTPlug-ins page), you can specify what happens when you load a VST instrument. The output of the MIDI track is routed to the instrument. Why is only KONTAKT's browser Hi-DPI? What about the rest of the application? If you chose Add Rack Instrument, the instrument control panel opens, and the following tracks are added to the track list: A MIDI track with the name of the instrument. For now, the KONTAKT Factory Library 2 and CHOIR: OMNIA are the only products built on this technology but the number of instruments will quickly grow. This language is currently within closed-alpha and will be made available to developers over time as the language stabilizes. To enable developers to create modern, high-definition instrument user interfaces in KONTAKT, we’re introducing a new user-interface language for products called the Native UI. As a sampling-platform, over its 20-years history, there is a portfolio of literally thousands of KONTAKT instruments - the vast majority created by third-party developers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |