Re: [Bluemusic-users] Something's wrong with the mixer
Brought to you by:
kunstmusik
From: r.30 <r.3...@te...> - 2010-02-24 20:59:55
|
Many thanks Steven, yes that helped. I thought that the formula "isustain = p3 -iattack -irelease" has a p3 as result when I give 3 parameters to the linsegr-instruction, but obviously it isn't. The signal extends p3. The problem with vst4cs.dll still exists, but I think this is a problem of CSound. I tried to pass the output to one (two) ga-rated variable(s) and then to a simple instrument only with an outs-instruction -> no sound occurs. I tested it with winxsound too. I forgot to say that I use Csound 5.11. Does anyone has new experiences with 5.12 in that matter? Steven Yi wrote: > > I just tested and I think I understand the problem. Because blue > creates a mixer instrument, it creates a single note for that > instrument to run. It uses the value of the generated score and sets > the duration of the mixer instrument to that value. However, because > the note instance is extending itself 5 seconds for the irelease, that > value is not added in as part of the calculation of how long the mixer > note should play. This case occurs too for when reverbs have a long > tail. The solution is to add "Extra Render Time" on the mixer to a > value you would like to add. I tested with adding "5.0" and it plays > the full sound correctly. You can add extra time here too to add > silence at the end of your piece. > > For myself, I normally use at least 5.0 seconds extra to account for > the effects I use plus to have a little bit of silence at the end of > the rendered piece. > > Hope that helps! > steven > > > On Tue, Feb 23, 2010 at 3:52 PM, r.30 <r.3...@te...> wrote: >> Steve, It seems that Blue does not accept optional parameters when the >> mixer >> is enabled. I uploaded a simple file, in which the signal is damped with >> the >> "linsegr" instruction. If the mixer is disabled it works well, but if it >> is >> enabled, it ignores the optional values. I uploaded a test file. Vary the >> value behind iattack to 0.0 and behind irelease to 1.0. Hear the >> differences >> when the mixer is disabled and then enabled. I detected also the problem >> with the mixer, when using vst4cs.dll. It works well, when the mixer is >> disabled, but blue makes no sound even if it is enabled. Test.blue FYI: I >> use a Toshiba Satellite Laptop with Pentium Dual CPU T2730 1.63GHz, 2GB >> RAM, >> Windows Vista incl. Service Pack 2 (forgive my sin!) and Blue 2.0.3, but >> I >> don't think that it is a problem of hardware, isn't it? >> ________________________________ >> View this message in context: Something's wrong with the mixer >> Sent from the Csound - Blue - User mailing list archive at Nabble.com. >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Bluemusic-users mailing list >> Blu...@li... >> https://lists.sourceforge.net/lists/listinfo/bluemusic-users >> >> > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > -- View this message in context: http://old.nabble.com/Something%27s-wrong-with-the-mixer-tp27710285p27714297.html Sent from the Csound - Blue - User mailing list archive at Nabble.com. |