When rendering a LOT of data, around 1gb or more of .wavs podium seems to eventually crash at a point. Usually these are split into 200 to a 1000 seperate wav files. Other times you can split the bouncing into segments, but eventually it seems to crash at a certian segment after you ahve done a few renders. It seems to crash randomly (but consistantly) during the rendering process, although it has also crashed when saving. I have had this happen on both my PCs, one of them has 3gb of ram and plenty of swapspace. Is this due to some sort of numerical limit in the way data is handled in podium or something? I would like this resolved so that I can leave podium rendering audio whilst I go out or to work etc – one of the reasons I am doing so many at a time is to use a vst to batch dither audio i need converting. Although I have worked out that it is certianly not due to any one plugin – i have tried just synths on their own etc. At the mo I have to split it into chunks, and restart podium every now and then to resume my work. I will try and make an example with just Z plugs and an audio file when i get back from work, and some initially blank wavs for the output so you can investigate it.
.
