[Rwp] Ivory?

Fri Nov 27 12:25:29 EST 2015

Chris,

Thank you for such an absolutely brilliant explanation.  What you say 
actually does make a lot of sense.  I have tried committing the Ivery 
tracks, but as you said, all that really is doing is bouncing them all down 
to an audio track, rather than to a rendered file.  I'm not sure about 
Reaper, but ProTools doesn't really per sé, have a freezing option.  It kind 
of does, with committing, but that's about the closest we have.  You 
commit/bounce to another audio track any selected tracks, then at the same 
time, you also can have it hide the original source tracks, and even make 
them inactive.  So I guess, kind of, if you wanna get really technical, it's 
a form of a freeze.

Chris.

----- Original Message ----- 
From: "Chris Belle" <cb1963 at sbcglobal.net>
To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
Sent: Friday, November 27, 2015 2:56 AM
Subject: Re: [Rwp] Ivory?

> This is relevant to theory for rendering and bouncing for any DAW so I'll 
> comment here.
>
> With sampling based instruments, especially one as heavy as ivory, there 
> is a lot of disk i/o going on.
> With that many samples
> velocity layers, round robin and such it has to slow down to render that.
> A 5400 rpm drive would really bog down a sample library,
> especially one as huge as ivory, one thing you might consider doing is to 
> freeze your trak
> which may takesome time as well,
> but then when you render your project, it should go normally at that 
> point.
>
> There are also certain synths I have used that just don't render well with 
> a fast bounce,
> and this is why in most good DAW's
> there still exists the ability to do it in real time.
> Some time certain controlers don't move just like they should,
> with a fast bounce,
> I've even had one situation and my experience is mostly with sonar but 
> this actually happened,
> I had a complex aray of stuf going on, and when I rendered with the daw,
> some of the stuf wasn't taking.
> It would play just fine, but not render with everything like it should.
>
> I ended up dumping in real time by playing and recording in to another set 
> of input tracks,
> in real time to get it perfect.
> This is a rare occurance,
> as most modern vst's and DAW's are designed to sync up together and get it 
> all right,
> but it can happen.
> So it doesn't surprise me that ivory won't go super fast in a render.
>
> On 11/26/2015 5:28 AM, Christopher-Mark Gilland wrote:
>> OK, you are *just!* the guy I need to speak with!
>>
>> I can't seem to extract your e-mail address from your message on the 
>> list, so others, please forgive me.  I have every single intention of 
>> taking this thread off list past this point.
>>
>> Firstly, here is my e-mail address, so we can converse privately.
>>
>> clgilland07 at gmail.com
>>
>> OK, so yes, I am trying to use Ivory with Reaper, however, I, too, am 
>> using ProTools on the mac.
>>
>> I'm noticing that when I pop Ivory on an insert, even if only one stereo 
>> instrument track and no more, it makes my offline bouncing go to a 
>> complete crawl!
>>
>> The only thing I can think of is, my internal drive isn't solid state, 
>> and is only 5400RPM.  I'm not getting any sort of pops, or buffer issues 
>> though when recording/monitoring in PT, nor am I getting any artifacts or 
>> latency. The only time it's slow is when offline bouncing.  The fasting I 
>> can get it to go is like maybe 1.2X.
>>
>> I just didn't know if you had this issue as well.  I mean, this is 
>> literally happening even with a session with only one track all total in 
>> the whole session, which only has one thing on insert A, which is the 
>> Ivory plug. It's totally stupid!
>>
>> Anyway, let's not clog the reaper list with this any more than already, 
>> you have my e-mail, so if you or anyone else has any ideas, I'd be very 
>> very grateful for any suggestions, short of getting an SSD.
>>
>> I can do that come next month, but I'd really rather not, if I don't have 
>> to.
>>
>> Chris.
>>
>> ----- Original Message ----- From: "onlineeagle via RWP" 
>> <rwp at bluegrasspals.com>
>> To: "Reapers Without Peepers" <rwp at bluegrasspals.com>
>> Cc: "onlineeagle" <onlineeagle at googlemail.com>
>> Sent: Thursday, November 26, 2015 5:49 AM
>> Subject: Re: [Rwp] Ivory?
>>
>>
>>> Hi Christopher, I don't have the concert grand, but I have other Ivory 
>>> pianos. They all use the same plugin, so my experience will be the same 
>>> as yours, regardless of which piano. I haven't used it on Windows with 
>>> Reaper yet. I have used it with ProTools on the mac, however, I can tell 
>>> you that all the piano options are available as parameters. Therefore 
>>> you will be able to do everything you need to do with the Shift P 
>>> parameter window in Reaper. This even includes changing the presets. I 
>>> was able to change presets this way in ProTools and then save the 
>>> preset, so that I was able to bring it up again by using the preset part 
>>> of the FX window. So, good news on the Ivory front I think.
>>> Sent from my iPhone
>>>
>>>> On 26 Nov 2015, at 09:04, Christopher-Mark Gilland 
>>>> <clgilland07 at gmail.com> wrote:
>>>>
>>>> Does anyone have any experience running Synthogy Ivory American Concert 
>>>> D on Windows with Reaper?
>>>>
>>>> If so, I am very curious to know how well it worked for you.
>>>>
>>>> Chris.
>>>>
>>>> _______________________________________________
>>>> RWP mailing list
>>>> RWP at bluegrasspals.com
>>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at bluegrasspals.com
>>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at bluegrasspals.com
>> http://bluegrasspals.com/mailman/listinfo/rwp
>>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> _______________________________________________
> RWP mailing list
> RWP at bluegrasspals.com
> http://bluegrasspals.com/mailman/listinfo/rwp 