Vienna Symphonic Library Forum
Forum Statistics

194,408 users have contributed to 42,920 threads and 257,965 posts.

In the past 24 hours, we have 4 new thread(s), 10 new post(s) and 80 new user(s).

  1. Home
  2. Sample Libraries
  3. Vienna Instruments Libraries
  4. VI Console Vanished!!

  • VI Console Vanished!!

    J
    J
    Hello-- it's me again.

    New issue here--

    While moving a keyswitch note in the MIDI editor window (DP 4.61) the VI Console just vanished. I mean, I stop short of saying it crashed, but that's pretty much what happened. The AU-GUI Interface remained open, so I clicked to open the Vi console again and got the dreaded eternal spinning beachball.

    Knowing that sounds have been taking more than 10 minutes to load, I just let it spin for abut 15 minutes-- I gave up and did a 'force quit'.

    Really frustrating.

    My System:
    G5 2.5 Dual, 4.5 GB RAM, OS 10.4.5
    7 VI instances, about 500 MB total
    No other plugins loaded

    Any thoughts? Anyone?

    Will run Disk Warrior in a little while, but a day of sequencing has just come to a sad end.
  • D
    D
    I had something similar happen today for the first time. Some sort of syncrosoft error which said to move the dongle. Everything vanished and on came the beach ball. Also DP 4.61. Forced quit restarted and all was well.

    Do you have the latest version? It takes about 4x's the amount of time to load than the previous it seems.
  • J
    J
    last edited
    last edited

    @dpcon said:

    I had something similar happen today for the first time. Some sort of syncrosoft error which said to move the dongle. Everything vanished and on came the beach ball. Also DP 4.61. Forced quit restarted and all was well.

    Do you have the latest version? It takes about 4x's the amount of time to load than the previous it seems.


    Ohhhhhhhhhh! So it's not just me?

    I swear I was feeling totally stupid, totally unlucky, and totally SOL with all of this.

    I got no warning window, and I am running 5.0.2.0. Time to try 4.9.7.7 since that's the only one I haven't tried.

    --- What version are you running?

    At the moment, I'm running DiskWarrior, which means I can go watch all three extended editions of Lord of the Rings and make it back just about when it finishes up.
  • D
    D
    I'm running the latest version of the VI (there's only two correct: 1.03 and 1.04?)

    My license is 1.9.4.0 according to the program. It's worked from the start so I left it alone. Does upgrading the license help with load times?
  • J
    J
    Dave--

    LCC 1.9.4.2 was installed with the Syncrosoft package 5.0.2.0, which is what was running at the time the consoles were disappearing. I am using VI 1.04 as well. Both are the latest versions.

    I noticed substantial improvement (much faster load times) with VI 1.04 over 1.03, but LCC 4.9.7.6 was the fastest Syncrosoft I'd used to date in combination with VI 1.04-- until it glitched the other day-- prompting me to try the latest LCC update as a possible solution.

    The odd thing about this latest experience was that even though the load times were considerably longer with the latest LCC, everything loaded eventually and seemed to be fine. I'd put in 3 measures of a violin part and was dotting in keyswitches to change matrices when the console disappeared.

    The first time the console disappeared, I clicked on the AU-GUI prompt to "display GUI". The result was the spinning beach ball. The next time I tried it, I didn't try to reopen the GUI, but instead I tried to close the little AU-GUI Interface window that remained. Instead of closing, it just froze.

    The most frustrating part about this is that I'd spent 3 hours auditioning sounds and loading them up into the various consoles, about 15 seconds playing in a few notes, and another 5 hours troubleshooting. That's not a lot of productivity for 8 hours.
  • D
    D
    JWL,

    I feel your pain. It still seems to me that DP is the most stabile platform with this new program, particularly if there are no other dongles (which I think is what's causing the headaches with Logic users.)

    Let's hope we are in for no more surprises or vanishing acts. I have Strings I+II with Woodwinds I arriving today. I'm hoping I can run both collections on my Dual 2.7 but we'll see. My 5 instances of strings each have 4 large matrixes so I will either cut back or ram save I guess.
  • J
    J
    Dave--

    One interesting thing I've found is that in DP's settings, I can only set the buffers to 1024. All other higher buffer settings are grayed out, unless I'm in a different session. Lower buffers than 1024 are resulting in serious cracks and pops. When not using VI, I can access buffers higher than 1024. Hmmm. Could VI be taking over DP so much that it puts a brick wall on my normal settings and options?

    I haven't yet dared VI with Logic-- and didn't even consider the headache of the extra dongle!! In fact, my USB hub is SO loaded right now that I had to remove my Logic XSKey just to get my iLok, Vienna Key, and other essential USB items connected at once.

    But back to the issue at hand, here's what I suspect is happening:

    Since VI's floating windows fight for domination, I think that whenever I change a keyswitch manually in the MIDI edit window, the VI console wants to be on top again, but because I'm clicking constantly inside DP's MIDI edit window, it fights against VI's floating priority and eventually crashes. I can see the different matrices being highlighted as I move a MIDI note keyswitch. Because the matrix keyswitches work better at C0-B0 (being off the keyboard), they must be changed in the MIDI window.

    I've also written to the VSL Team about another issue which they can't sort out. It just so happens to deal with odd keyswitch behavior-- some keyswitches cause a new attack to be triggered during a sustained note, even though the keyswitch is out of range of the instrument.

    This brings me to the thought of another feature for VI-- to be able to set some sort of transpostion +/- 1 octave right on the console in an effort to assign keyswitches which are above or below the range of the 88-key controller.

    Lastly, for the moment, I've also been wondering if having 2 consoles with 2 matrices each is better than having one console with 4 matrices (being of the same instrument such as a violin). Since so many of the PERFORM controls are global this may also offer some additional flexibility. I'm not getting any sort of CPU spikes at all in with VI in DP as I do with other sample libraries. The one caveat is that if VI maxes out at 24 instances, it seems to be a bit of a waste of resources to just add more instances for the sake of convenience. What shall we do with the entire Cube loaded?
  • D
    D
    JWL,

    Very interesting report. I've thought of 2 instances for each part as well. That brings up the multiple midi track scenario but maybe 2 will prove to be the best way to go. Let me know how you find that working for you.

    I get crackles when lots of things are going so I have to check my buffer settings.

    I think the interface displays (and definitely the DP Mixer - hog) should be closed whenever you're not addressing them.

    Why do the matrix keyswitches work any better off the keyboard? Incidently I always record in keyswitches and hadn't thought of penciling which is a good idea.

    It seems that DP doesn't chase note on. So if I'm on a staccato matrix and roll back midway to a legato matrix: even though I have the keyswitch note dragged accross the legato section there matrix doesn't switch. Am I missing something?

    How much ram do you have to load 24 instances and how much ram do you have in say the 1st viloins.

    Sorry for too many questions.
  • J
    J
    Hey Dave--

    For 24 instances, I took my cue from the initial stress tests for Mac. Granted, these tests were done with Logic as the host app. I've heard nothing about other test results done on other hosts, but if I recall VSL was "working on it".

    It's very odd that the PC results are still pegged at the top of the forum, but I was hard pressed to find the Mac results. Forunately, I saved them on my HD. Looks like 4GB RAM is the magic number, but different buffer settings impact on the number of instances and samples which can be loaded at once, regardless of how much RAM

    TEST COMPUTER 1

    Processor: G5, 2 x 2.5 GHz,
    Ram: 4 GB
    OS 10.4.2
    Data storage: Firewire 800
    Host application: Logic 7.1.1
    Soundcard: RME HDSP MADI with 648 MADI Interface

    Latency at 512 Samples (12ms) / 2.5 GB Ram usage
    Maximum Vienna Instrument instances: 24 (CPU 90%)
    Maximum Samples loaded: 45000
    Maximum polyphony: 300 stereo voices / (CPU 70%)

    Latency at 256 Samples (6 ms) / 1.74 GB Ram usage
    Maximum Vienna Instrument instances: 23 (CPU 70%)
    Maximum polyphony: 200 stereo voices / (CPU 75%)

    TEST COMPUTER 2

    Processor: iMac G5 single, 1.8 GHz,
    Ram: 2 GB
    OS 10.4.5
    Data storage: Firewire 400
    Host application: Logic 7.1
    Soundcard: Built in Audio

    Latency at 512 Samples (12ms) / 1.08 GB Ram usage
    Maximum Vienna Instrument instances: 11 (CPU 85%)
    Maximum Samples loaded: 17400
    Maximum polyphony: 250 stereo voices / (CPU 80%)

    Latency at 256 Samples (6 ms) / 1 GB Ram usage
    Maximum Vienna Instrument instances: 9 (CPU 85%)
    Maximum polyphony: 160 stereo voices / (CPU 80%)
    -------

    I've not dared 24 instances because I've had so much trouble with Syncrosoft. The most I've ever attempted were 10 instances. Since yesterday's troubles, that went down to 5, and most recently down to 1 instance.

    There have been other issues which have prevented me from attempted larger projects so far. For one, I'm getting drop outs-- or drop offs, meaning that the same MIDI notes on the same patch or matrix are now dropping off the highest notes where they once played without incident. I mean, the notes just stopped playing about D7 (with C4 as Middle-C). They played just fine earlier-- and I'm no longer convinced that I've gone insanse.

    Keyswitches:

    The one reason why I've elected to do certain keyswitches off the keyboard is because the "suggested' first keyswitch for the matrices is preset to C0. Keyswithces for patch cells are pre-prgrammed to begin at C1. Some A/B layer keyswitches (for example, cresc and decresc 2 Layer patches) are set to A0 and B0. So that's at least 9 (or 10) available keyswitches for changing matrices between C0 and G#0, plus A#0.

    I had sent an mp3 to the VSL team showing how my assigned keyswitches which were within the 88-keyboard range (yet OUTSIDE in the range of the instruments) casued a "hiccup" on any note playing as the scroll bar crossed its loaction.... a long sustained note was playing, during which time the keyswitch note was entered to allow for a different articulation on the forthcoming note. Instead of a smooth switch, the sustained note "burped" right at the location of the keyswitch.

    Backward chase!! YES!! Man, I've never used markers more liberally than I have with VI. Depending upon which track and how many keyswitches have been entered, it's almost necessary to start from the beginning. Sort of a waste of time, especially if things don't catch up after a couple of bars.

    So, the latest news is that I CANNOT LOAD ANY INSTANCES AT ALL WHATSOEVER. I tried to remove all of the Syncrosoft components to reinstall 4.9.7.6. I manually removed the Synsopos, Synoacc, & Synsonos folders and their contents, plus LCC (restart-reboot-) but the installer wouldn't let me reinstall anything except for 5.0.2.0. That means I'm stuck. I opened a "clean" DP project and tried to add just one instance of VI. It took about 30 seconds to the license scan, and then there was the eternal beachball--- JUST FOR ONE EMPTY CONSOLE which never loaded!!

    5 PM now. I've been picking at these issues for days and days. It just seems that with every step forward there are two more steps backwards. I love the sound of VI, but I'm really starting to wonder if I shouldn't have invested in a new car since I've only been able to overcome the hurdles for short periods of time.

    To be quite honest, I've all but given up.
  • D
    D
    JWL,

    Just had a bunch of problems after installing Woodwinds I. Syncrosoft error of not finding licenses. So I moved the dongle from the back of the G5 to the front (I read to do that somewhere) and everything came back online. Give it a try.

    Other sequencers apply the note on as long as any part of the note is sounding where the cursor is. DP chases controller obviously but I guess that's it unless there's a preference somewhere, but I haven't found one.
  • J
    J
    Hey Dave,

    thanks for the dongle suggestion, but trust me-- the Vienna Key has made the rounds to just about every available USB port I have-- front and back of my G5. I even tried the back of my monitor to the same results.

    It's a strange thing with Mac and DP in general. Athough it happens less now than it once did, sometimes in OSX things just don't work at first for no reason. You reboot, fix permissions, you get up the next day and try again-- still nothing.

    Then all of a sudden one day it just happens.

    I've even noticed that some of the aliases in the Dock just stop working and have to be replaced, regardless of whether permissions were repaired or directories rebuilt.

    But one of these days, I'd like to finish my self designed tutorials with VI. I was working on the Barber Adagio for a while, but I got lost in a sea of legatos, whose variants began to number by the dozens. There are limitations to how many gradations of legato one can get out of this thing. it got fatiguing, so I starting in on an excerpt from the opera Salome by R. Strauss. It's not the 'Dance', but the final scene when the orchestra has that wonderful polytonal explosion. Again, I'm stumped by the extended ranges of the violin and cello, which means that I cannot compete the exercise. My cellos are only playing as high as D5, but Strauss' parts have them going a half octave higher in places.

    But at least for the moment, I'm going to head out to find a six-pack of a good beer, the biggest prime steaks I can find and a good DVD I've not seen.

    Tomorrow is another day.

    And another month....
  • D
    D
    Excellent post. Firstly I will pull out my score to Salome and have a look at that section which I vaguely recall since it's been a while. Secondly I will repair permissions since I'm having some problems (everytime I try to change buffer settings I crash: just opening the menu.) A yes the sea of legatos which is akin to the sea of articulations which is where I swim alot.

    Lastly beer: one of the most important elements in computer maintenance and realizations of music, so drink up.
  • J
    J
    Dave--

    LOL!! Yes-- beer is at least an occasional must.

    You know, I'd gotten so aggrivated earlier that I closed shop entirely. Curiosity-- and the cost of VI hanging over my head-- got the best of me. I came back and started dinking around some more. It finally loaded, although there are more strange behaviors going on. Having closed one of the VI consoles, I actually had the matrix pulldown menu sitting alone in the middle of DP's MIDI Edit Window. I tried to get a screen grab, but that involved hitting the space bar. Of course, when I'm in the matrix Control Edit window on VI, the space bar open and closes this menu. Also, when taking a screen window snapshot (Apple+Shift+4+Space Bar) it all went away. I really wanted to save that shot for a momento.

    In any case, I'm wading through other stupid glitches, but I've gotten the striings parts I intended to reproduce all done, save for the contrabass. Music at last!! Now, I really want to go further and then use PE for the rest of the orchesra parts for this.

    The score I'm using is the Fürstner reprint by Dover. If you have that, the section I'm doing starts at rehearsal #314 (page 302).

    If this is a good time to continue with musical discoveries, there are several things I've discovered and have tried to work around....

    1. Not all violin patches go up to F7, which is a drag. I did find one non-Vib patch that did and slotted that in, but it sounds a little funky to me. Will look for others.

    2. The cello range in VI is also a little shy on top by Strauss' standards. I got around this by slotting in a viola matrix in the cello console to get the part up to A5 (the last note before rehearsal #315). Doesn't sound like a cello, nor should it, but hopefully the rest of the orchestra will provide enough noise to draw a score reader's attention away from this.

    3. Divisis!! Two issues here: The first is the usual problem of creating violin 1 and violin 2 parts without phase cancellation. I think I got lucky and was able to find another set of legato patches, wandering back and forth between Universal and ALL matrices. Doesn't seemt to conflict, especially when parts of the X-fade can be manipulated at crucial points.

    The second issue is the 4-part divisi trems in the violas and cellos. Divide a VI viola patch in to four-note chords and you have 40 violas playing-- and it sounds like it!! I'm not sure if I should use the Chamber String patches in cases like these or if I should take advantage of the more epic sound for the sake of the mix to come...

    All-in-all, doing these sorts of exercises every once in a while really offers tremendous insight to what VSL sounds can do. So far, I've not had to cheat with the parts, except where the cello range fell short. With other orchestra libraries, I usually have to "pad" certain parts and eliminate others for various reasons..

    The MOST enjoyable thing about doing this is that your are working with great music-- and in this case a brilliantly orchestrated masterpiece by one of the greatest orchestrators of the Late Romantic era.

    It may be a while, but I hope to post a mix and some files (at the risk of having my efforts torn apart by more astute users of VSL-VI.

    Time for a brew!!
  • D
    D
    JWL,

    Another great post. I have the Dover and have looked at the section which looks like some splendid music. Would love to hear your results. I know what you mean about using appropriate number of strings in divisi as well as ulimately using what sounds best. I would try the chamber and see if they actually sound more accurate and then go with whatever sounds best in the end: the first law of midi.

    Speaking of patches not quite fullfilling expectations, I thought that all legato samples were now looped but find the oboes quitting on sustained notes (just bought the winds to get around this!) so maybe I have to switch to a sustain note but that means another matrix which I don't have room for. Maybe if I load more than my 4.5 gig of ram I'll be okay (I've heard people are able to access it - can you confirm?)

    I'm working on a Classical style overture I wrote ages ago just to test things out. Still trying to figure what's best workflow-wise. I agree that between downtime and loading time one could end up consuming a little to much drink for obvious reasons.
  • J
    J
    Hey Dave:

    Didn't get to work too much more tonight, but I at least got the contrabasses in for the few bars I was working on today. For as much as I would love to go further, I can already see an eternity of expression editing with just the little bit I've done so far.

    For the moment, I'm going to stick with the 40 violas and 32 cellos for the div.a4 passages for now,and just turn them down a little. I'm sure that I'll swap them out for the chamber tremolos, but I may retain 1 note of the orchestral 10-vla /8-vc for this just to see what happens. These adjustments won't be made until the rest of the orchestra has been programmed. One thing I've been hearing and reading about VSL is the challenge of creating more cinematic string sounds. It may help fill out the middle a bit to keep the tremolos full. It's not authentic, but as you say: rule 1 of MIDI is do what sounds best. I may even try tucking in some violins from "another sample library" to give some of the altissimo passages a touch more substance without losing VI's sparkle, but that will be a last resort.

    I am discovering that there are a lot of patches of the same instrument that don't share the same range extremities. The violins are one example, tapering off for the most part at D7, while other patches go higher. Similarly, the legato contrabass patches I've tried drop off after C1 (and the notes don't sustain in the Unversal patches the way they do in the other string parts). But, one of the 'long note' bass patches does play B0. It's not legato, but perhaps a non-legato patch will help keep things clean on the bottom (so to speak).

    It may be necessary to take a day (or two) to go through the matrices to take note of which patches drop off at the extremes. I wonder if this was intentional? Doesn't make sense to force the user into an undesired articulation for a note just because it plays a certain note when the patch you want is missing that note. I also noticed that some of my contrabass notes crop off around D4 or E4. Lots of large Romantic era scores will send the contrabasses up a bit higher. But maybe the VSL Team didn't deem these occurrences necessary.

    Oh, yeah: there's the concept of mixing in some solo strings. Ducking them in the mix can emulate those players who are closer to the mic's (or closer to the front of the stage, as the case may be).

    So many thoughts at once... (so late, too!)...

    I've read Beat Kaufmann's site, and one thing that struck me was the notion of adding the sub-bass, meaning some sort of harmonizer that doubles the bass to some small degree an octave lower as a matter of virtaul resonance rather than of the actual sound. Not sure the best way to go about doing this just yet, but lots of people have been talking about this. Gladly, I have a a sub to handle LFE info. This will help for more accurate monitoring of extreme low end.

    Workflow!!

    I was thinking about this today, more accurately, I was re-thinking this. I took time to load in several matrices into different consoles to save the trouble of having to fish through the folders, wait for load times every time, dump the matrix or patch, then load another and another and another until the most desired one is found. It did save time to be able to just load an '.aupreset' and to get started with a variety of articulations on hand.

    For a while, I would just start playing with one sound until I needed another. Then I'd stop, go hunting for the right sound, add to the matrix and play some more until such time a new articulation was needed. It's probably best for the CPU to work that way, but it wreaks havoc on efficiency and momentum. You can spend 45 minutes just getting 2 notes to sound right.

    I can't complain about the matrix and patch list. It's well organized, but it's not the fastest way to work. Having a set of 'mega-consoles' puts most everything commonly used on the table at once. Dumping unused samples aftewards may be more of a habit rather than an option.

    Currently, I've got 5 consoles, each with 9 matrices loaded-- pretty hefty. Oddly enough, CPU is hitting at less than 10%. Things are look a lot more promising for loading in more consoles for a full orchestra.

    One other thought I had was if the VSL Team could give us one or two sizable percussion matrices with no keyswitches, but with the most common orchestral percussion instruments mapped across the entire range of the keyboard. Dunno-- might be a tall order, but it would be a lot easier to deal with in a pinch. Of course, we would have whatever key mapping method VSL chooses.

    LOL!! All of this idle thought was inspired by sequencing 10 measures of music! Such is the plight of the April fool. [:D]
  • D
    D
    JWL,

    Couldn't load this page for a while so I don't know what was up with that: tried to respond long ago.

    By all means, whatever works for divisi go for it. It could be argued (and has) that a very tight sample of a string section as with VSL is not the real world with various attacks and vibrato etc., so it's hardly cheating to do what sounds best. Strauss loves multiple divis's as in the opening section of Zarathustra. I was thinking of the chamber strings to get that particular sound. I am trying to see how complete I can make my piece sound with VSL only, than as you said maybe layer else in there.

    Haven't checked out ranges of VSL VI but I'll take your word for it and imagine that's a little troublesome. Yes the Universal patches don't sustain it seems - I ran into that with the Woodwinds.

    You have solo strings? True lot's of folks layer them in for more bite and deliniation of the parts.

    Also wanting my lows to sound bigger as well. Let me know if you find out what software people are using for harmonizing .

    How much ram does your G5 have? I crashed after loading in some winds and maxing out mu ram. I'm thinking I should add a couple more gigs to reach 6.5? Any thoughts on this.

    The old Perc 1 + 2 had mappings of various percussion as a single instrument but you're talking about a lot ,ore. I really wonder how they are going to solve that. A multi tambral VI is probably not far off.
  • J
    J
    Hey Dave:

    Yeah, the site was down from this end, too.

    One other little trick with solo strings is to pull the filter down a bit. It's nice to have a little "bite", but for that less obvious "rougue" player or two, a good low pass works wonders on solo strings tucked into the section. If you wanted to get complicated, have two solo instruments per section-- one to add a little "point" where needed, and the other to represent the 7th stand player who didn't do so well in the concert master audition.

    My G5 2.5 dual has 4.5 GB RAM. DP doesn't see anything over 4 GB, but I'm not maxing out DP just yet. I really don't know how the Mac actually uses additional RAM-- if having 8 GB will help the performance or not. Clearly, if one is running VI as both a plugin concurrently with VI Standalone, the benefits are clear. You've got 4 GB for each processor with some consideration for the OS to take up some of that. I'm still suffering from the OS9 mindest, and my first instinct for years has always been to max out the RAM. The one benefit is that RAM for older Macs is cheaper than it was. Maybe going full wack is not a bad thing, but the few people I know with max RAM are experiencing other problems which RAM hasn't solved. My Quad friends are asking the most questions about this, although they are experiencing other benefits not RAM related.

    I just read that MIR has to process offline because computers are just not fast enough yet to do everything in real time. This is frustrating. I'm tired of buying new computers which can't keep up, only to see a newer computer released weeks later that don't solve the problem either.

    I'm seeing a few more "helper boxes" like these:

    Native Instruments KORE
    http://www.native-instruments.com/index.php?kore_us

    Waves Nutshell
    http://www.sweetwater.com/store/detail/APA44/

    Muse Receptor
    http://www.sweetwater.com/store/detail/Receptor/

    Focusrite Liquid Mix
    http://messe.harmony-central.com/Musikmesse06/Content/Focusrite/PR/Focusrite-Liquid-Mix.html

    Virtual instruments in general reduced studio clutter, but continues to easily overwhelm computers. I'm still not convinced that AU is as efficient as it might be. I think the VI team has made the best use of AU I've ever seen. But these "helper boxes" might take considerable load off our current CPU's-- moreso than with UAD-1 or TC Powercore. While some are touting forthcoming brilliance with Intel Macs, I've always seen Apple's improvements as being in small increments, however innovative... 1.8-2.0, 2.5-2.7. My favorite was 867 "up" to dual 800!!

    Sub-bass:

    Beat Kaufmann works on a PC, but posted this on his site regarding cinema bass:

    http://www.beat-kaufmann.com/tipspcmusic/vslacoustics/index.php#53248296fa00f2a1e

    I'm still not clear on how this is done, but it seems that it's added synthetically. Some type of harmonizer might work best for this instead of pitch shifting an audio track or needlessly boosting EQ on the low in where it doesn't belong. One might make a copy of the contrabass and manipulate it, but that doesn't address the overall low end of other instruments-- tuba, contrabassoon, perc, etc. Not sure what the best way might be, but if I sort this out I'll let you know!

    In any case, Beat's tutorials are brilliant-- there are mp3's demonstrating "before and after" effects. You may want to go through all of his tut's because he gets into some serious basics and more with mixing sampled orchestras-- specifically VSL. I love his comments about how something like Altiverb can take the "point" off of the timp when it's placed further back in the orchestra-- and how to compensate for transients lost for the sake of stage placement.

    Back OT-- I was surprised to have had a pretty good day, technically speaking. Granted, I was doing projects with Vitous Philharmonik, but I was able to load in a few instances of VI. DP reconciled the bit depths quite smoothly without anything special needing to be done.

    No crashes to report, knock wood!!
  • D
    D
    JWL,

    Good ideas on solo string layering. I'll get them at some point but I don't have the processing or cpu's to handle them now.

    VI actually runs outside of DP doesn't it? I saw someone post early on that they loaded way beyond 4 gigs with a DP G5 setup. Don't know if that was an inside/outside set up or not. It will be interesting to see what the future holds with quads for processing and RAM.


    How will one work with MIR if you can't use it in real time? Wonder what they've come up with reference prior to offline rendering.

    I've read a little about Kore and will check out the others. I think hardware solutions may indeed be what's coming for sharing processing. Then again that's what Gigastudio was supposed to be in a sense: a dedicated processor for handling streaming samples. Yeah it's never enough.

    My current solution on the piece I'm doing is going to be to finish the strings with VI then Ram save then load the winds and get those working. Can't load hardly anything beyond my 5 string instances so not much choice. I could use my Giga 1st edition winds but that would mean multiple midi tracks and no real repitition since the repitition tool is so unwieldy. Plus searching for patches or presets in VI is so clear and easy.

    Yes I studied Beat Kaufmen's tutorials regarding articulations but haven't really looked at the mixing stuff so I will check that out.

    Glad you made some progress - same here.
  • H
    H
    JWL and Dave,

    I've been following this discussion with interest, and learnt a lot, which i'll carefully put away for the future.

    Thank you to you both.

    Regards,

    Alex.
  • D
    D
    Always nice to get a visit from the kind soul Alex.