Hey folks, have been using Garritan on its own at the start of a song and using CC1to give it some realism. Sounds great on playback but when I try and export it as a wave/mp3 etc the result is somewhat jumpy for the first few bars making it sound horrendous. It rights itself after a little while.I have tried fast bounce, audible bounce and every combo I can think of but it's still always wrong.
Any ideas? I'm going insane lol 

Bibs


SOLVED: 

Thanks so much guys for all of your suggestions. I tried everything you pointed out but still had no joy....However it turned out to be something as simple as increasing the midi playback buffers from 250ms to 500ms. 


Thanks again


Bibs

Just how far into your song does the CC1 appear and the Midi notes afterwards?

If everything is starting at 01:01:00 I highly recommend you move everything out to at least measure 3, this give Sonar a "breathing space" so everything can sync up properly.

Also leave a gap between the CC1 and the regular data

The instruments begin on bar 4, preceded by cc1 data set to zero the bar before. As the strings begin, there's a swell then fade to make them breathe for each chord. After four bars or so everything sounds as it should but beforehand the swell and fades are erratic to say the least. The only thing I haven't tried yet is moving the cc data at the beginning to a higher value than zero. 

Bibs

Try using CC11 instead of CC1 - it might help

Thanks Jonesy, but I thought that cc11 was expression. CC1 in garritan controls the expression and the timbre of the instruments. In its control panel the mod wheel is mapped to Cc1 so I can't see how it would work... But then again I'm no midi guru.
Having searched the forums I see I am not alone and this was a real issue in earlier versions of Sonar with no apparent fix so am surprised that it still does this in X2. Or... I have a setting wrong in prefs maybe. I've tried ticking and in ticking zero controllers on stop but that made no difference. 

In fact if I do an audible bounce it refuses to see any CC1 data throughout the whole song and just plays at a constant volume that varies in loudness with each mixdown. Strange.

Sorry Jonesy, can't edit post as im on phone but it seems you are correct and CC11 functions exactly the same as CC1 even down to the brightness filtering. Learnt something new there, thanks :-)

Hi,

I'm not having any problems with Garritan. CC levels are doing exactly as told, here. Really happy using key-switches for articulations. 
Hopefully, we'll find more information - I'll keep an eye out for strange behavior.
A trip up can be if you try automation lanes on the same CC's as in the midi track. I find you either need to stick to no automation/CC's in midi track only, or automation, but not both. It is possible to import midi track CC's into the automation lane, but for some reason you need to correct the curves to use 'jump' between CC's.

in garritan as well make surr all the ccs that you are putting in are the same misi channel as the instruments they are mapped to. also try setting snap either off totally or something really low as samples or ticks and draw them in with finer resolution it helps A LOT.

oh - i totally forgot about a similar thing when i was first using garritan.  so i had a section that started out with standard string section with crescendi then later in the project i had a keyswitch for the violin to do half step trills. i'd play the project and it would hit the trill marker... i'd stop, select all, export.... listen and all the crescendos would sound off. i was flabbergasted... i opened the project play a bit (til some other keyswitch thing... select all export same result.  took me a while to hit the duh! moment.  now, i put keyswitches ALWAYS at the beginning of the project and each section so there is a reset on export.  maybe that's a possibility.  

any progress with this?