Re: [Bluemusic-users] Freeze-rendering vs. rendering in realtime
Brought to you by:
kunstmusik
From: Jan J. H. <jj...@so...> - 2014-04-13 06:37:46
|
Dear Steven, I tried the new version 2.5.12 yesterday. Changinging the freezing to disk render settings certainly looks right to me, it was obvious, that it freezing now uses disk-render settings. With my disk render settings of ksmps= 1 it took much longer to render than before and the resulting sound seems definitely cleaner to me. However the noise/ artefacts after every sound event have not vanished. The strange thing is that they do not occur while rendering in real-time. Maybe it has to do with the nature of freezing, taking maybe not every instrument into account, which is described in the manual: > The freezing system does *not* work for all graph toplogies. If > you're using soundObjects with instruments used as control signals, > this won't work unless the notes for the instruments they are > controlling are alsoin the same soundObject. I.e. I have one > soundObject that has only notes that affect global variables, while > I have one instrument thatuses those global variables. This could > work though if you repackage the set of soundObjects into a > polyObject. Probably best to generalize as: > > Your soundObject must be self-contained > > All sound output from instruments go directly out or piped through > always-on instruments, that most likely should take advantage of the > <total_dur> variable, as well as the new <processing_start> variable > (more about this when I release, but together with freezing, this > lets you set the start time of always-on instruments to the first > time where non-frozen soundObjects occur, so if the first half of > your piece is frozen and you're unfrozen stuff is in the second > half, you don't need always on instruments to be turned on until the > second half as the first half is routed to out > I am not sure if it has to do with that. I will investigate this further to make sure, it is not a bug in my code and maybe to get a clue, what might be the origin of these unwanted sounds. Still I am courious to find out the reason for that phenomenon. All the best, Jan Jacob sound | movement | object | space sonic architecture | site: http://www.sonicarchitecture.de spatial electronic composition | higher order ambisonic music Am 11.04.2014 um 18:06 schrieb Steven Yi: > Hi Jan Jacob, > > Could you try this release: > > http://www.kunstmusik.com/blue_OSX_2.5.12.zip > > I tested here and freezing used the disk render settings here. > > Thanks! > steven > > On Fri, Apr 11, 2014 at 11:21 AM, Steven Yi <ste...@gm...> > wrote: >> Hi Jan Jacob, >> >> I think there is a bug. It looks like when I redid the render service >> code, I had the freezing code use the realtime settings instead of >> the >> disk settings. Let me create another hotfix branch and do a fix. I'll >> post a build for you to test shortly. >> >> Thanks! >> steven >> >> On Fri, Apr 11, 2014 at 10:55 AM, Jan Jacob Hofmann >> <jj...@so...> wrote: >>> Dear Steven, dear list, >>> >>> being now able to render much more in realtime, I noticed a strange >>> phenomenon on which I have no explanation so far: >>> >>> Listeneng carefully to frozen sound objects of mine reveals textures >>> of unwanted noise after every single short sound event. The sound >>> quality is somehow not so clean, there are also some artefacts in my >>> sounds. The noise persists about 1 sec. after every note event, then >>> it is silent until the next sound starts. >>> >>> First I thought, there is something wrong with my instrument but >>> then >>> I found out, that the sound is clean as can be if listened to in >>> realtime. >>> The strange thing is that I do render with ksmps= 10 in realtime and >>> ksmps=1 to disk. I would therefore expect the rendering to disk >>> having >>> the better sound quality in general. >>> >>> So I wonder, which settings Freezing uses, the ones for realtime- >>> rendering, disk rendering (as I would expect) or something else, >>> taylor-made for Freezing. >>> >>> Partly I am asking just out of curiosity, I would like to know >>> what is >>> behind things, partly I wonder, if maybe something else is wrong >>> with >>> my code. Actually I am not minding the quality, it is allright for >>> freezing, as long as it sounds clean at the end. But I wonder >>> where It >>> might come from. >>> >>> Best, >>> >>> Jan Jacob >>> >>> >>> >>> sound | movement | object >>> | space >>> sonic architecture | site: http://www.sonicarchitecture.de >>> spatial electronic composition | higher order ambisonic music >>> >>> >>> ------------------------------------------------------------------------------ >>> Put Bad Developers to Shame >>> Dominate Development with Jenkins Continuous Integration >>> Continuously Automate Build, Test & Deployment >>> Start a new project now. Try Jenkins in the cloud. >>> http://p.sf.net/sfu/13600_Cloudbees >>> _______________________________________________ >>> Bluemusic-users mailing list >>> Blu...@li... >>> https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |