DO backup your project templates before applying this update…
UPDATE: Today is the day of the new releases. The updates are available now. See also:
- Is it possible to have one consistent zoom between all the marketplaces? One page comes in at 100%, the other at 150% zoom, the other at 120%, etc. This is probably due to my own manual actions sometime before, possibly the browser remember it – at least I suppose so. I don’t know if this can be arranged site-based or whether it’s a pure browser-side thing. Either way, it nullifies the “one site”-aspect of things.
- Is it possible for a user (or at least an marketplace-specific author) to remove the bar with marketsite-links (or perhaps move them as icons to the top bar, next to Envato)? Not to discredit your work, but for my personal preferences I dislike having this huge middle-row around and would prefer to only have 2 main menu rows like it was, which is already plenty as it is. When there’s some item-action/bundle, a blue bar appears on top of the screen, there’s even 4 bars then, but at least you can hide the blue bar (site-per-site, rather than once for all sites). Besides I personally find it messy and counter-intuitive, I already have hotlinks to the sites of interest to me on my browser’s hotlink bar. It’s faster to click there then to first open some random Envato-page and then click in there to visit the desired marketplace. Not to mention the wasted traffic-overhead.
Never mind, got it. Permanently converting one CC controller type to another CC type is indeed done through Logical Functions, but you’ll have to freeze them. I forgot about the “Freeze MIDI Modifiers” command.
As far as I’m concerned this topic can be locked/removed. It sucks to be wrestling with something for quite a while, then ask for help on some forum, only to then suddently realize what you’ve been doing wrong.
Does anyone know of a way to permanently convert the type of a given MIDI CC to another type? Here’s the casus:
A while ago I created some string related stuff, which uses various CCs for controlling expression (i.e. CC1 modulation, CC11 Expression). I did this for a specific lib. I now want to ‘port’ this to another lib, but the different controllers have different functions there. So I need to transform existing CC-data to another CC-type. Seeing there’s a lot of curves going on, doing all this manual would be time consuming. Seeing it’s just byte data, I figured there should be a way to do this in an automated way. For example: I’d like to permantly change all CC1 (Modulation) values to CC11 (Expression Values). Permanently. I don’t want to “live remap” them, no just permanent data conversion in the MIDI-data.
Now I’ve looked into MIDI Logical Functions but I cannot really get it to work. My idea for there was to “transform” the first parameter to 11, if it equalled 1. Does anyone have a clue?
ADDENDUM: upgrade cost will be EUR 49,- (unless you activated October 15th 2013 or later, in which case it’s free). Sounds like a fair deal to me, especially seeing you not only get alot of improvements but also some extra goodies like the comeback of Magento, and more.
I am very, very happy with this update making the upgrade a total no-brainer. Why? Well: apart from many other improvements and additions this one is killer:
Instrument (t)rack 2.0Implementation of this feature has been long awaited and can drastically improve the way we set up our projects. Aside from many other features, another nice thing is the further upgrade of VST Connection – it now supports MIDI-messaging, enabling MIDI-data transfers over the wire further enabling networked collaboration, or client-server (slave/master) signal flows. This is a jolly day for my hardworking slaves.
By fusing the VST Instruments Rack with the instrument track concept, Cubase 7.5 makes working with instruments easier, quicker and more transparent than ever before. Instrument tracks now boast multiple audio outputs for any instrument, and can also be fed by any MIDI track on any channel. Inserting a new instrument into the rack is reflected within the Project window by creating the corresponding instrument track automatically and vice versa. The new Instrument Rack introduces VST Quick Controls for each instrument, letting you modify instruments and sounds even quicker — without even opening their GUI. Best of all, you can now assign each instrument a meaningful name for better identification of its MIDI ports and audio return channels.
Thank you very much for your review.
I’m holding off as well. Gotta be picky due to financial position, and well, the demos haven’t impressed me at all. I had the idea of just another percussion lib, something I don’t really need.