Paul, I'm still a bit curious: has the loading time speeded up with this update, or is my pc just in a particularly good mood today?
Thanks,
Alex
Thanks,
Alex
-
@Paul said:
Hi Alex,
if it feels faster, it IS faster [:)], thatĀ“s why I like old cars [:)]
Seriously, weĀ“re always improving the loading time, thatĀ“s an ongoing process. But we didnĀ“t particularily focus on this aspect with this update.
Best,
Paul
Alex and Paul - might be a little of a 'placebo effect' but it does feel a tad faster [:D]
Rob
-
Seriously, weĀ“re always improving the loading time, thatĀ“s an ongoing process. But we didnĀ“t particularily focus on this aspect with this update.
Wow, in that case I'd better put on me rocket suit to be ready for the time you Do focus on this aspect[:)]
One more thing if you please: how the ... do you get these nice frames around your quotes? I always seem to be doing it wrong...
Cheers,
Alex
-
just a little tutorial *how to quote* (not in the sense how it is meant in usegroups, althoght sometimes ... anyway)
BB-code disabled here to display:somthing without referring to the poster
and remember: only a CRAY can run an endless loop in just three seconds. -
certain characters allow formatting using *BB code* [b] bold [i] italic, ect ... see the buttons above the edit-region - pointing with the mouse on the buttons shows the syntax, every opening command has to be followed by an ending command eg. [/b] ... more or less similar to HTML
http://myserver.com/mypic.png"> (picture)
nice link-text (link)
but we will loose this soon - the new forum software has a *real* editor ...
and remember: only a CRAY can run an endless loop in just three seconds. -
On Logic 7.1.1., for a file with many EXS instruments and some -- but not too many -- VI instruments, the new software loaded:six seconds faster, going from 3:40 to 3:34. The difference probably would have been greater with more VI's. We are certainly going in the right direction.
Personally, I think the functioning velocity switcher is huge.
-
@JWL said:
Thanks, Herb.
One question about the "upfront window bug". I'm not 100% sure what was an actual bug and what was part of the window's intended function. I know there was some discussion as to how this window *might have* worked from users, but it's not clear just what the bug is... can you explain a little bit more about this? Thanks again.
Hey JWL,
The "Upfront window bug" refers to a rare problem, that occurred when more than 2 VIĀ“s instances were opened and moved to the background. After clicking "Show GUI" of a certain instance, a wrong instance (the last one that went to the background) did show up instead of the right one.
When closing VI instances this did not happen.
Best,
Maya
-
@Jerome said:
Hey there...
what's the "Note On Velocity" ?
You probably found this out already, but it's the 1-127 midi value that indicates how hard you hit the key. It's the most basic dynamic indication midi can give. I'm glad they put this feature in, as we can now use it for an "old school" velocity x-fade, where the key velocity controls not only the dynamic layer of the sample selected, but also the mix of dynamic layers, whenever velocity x-fade is enabled. This will be best for tutti strings, and other ensemble patches, where it will allow for more subtle dynamic transitions in live playback (*without* using any continuous controller). It will, of course, work for solo instruments too, but with those you'll hear the phasing between different dynamic layers more clearly, so it might not be as good to use for solos. But it also allows for other types of velocity-based effects. For example, I could imagine switching to my "harsh" solo string articulations only for velocity > 124, and that sort of thing...
Nice addition! Thanks guys.
J.
