I am also aware that this behavior shouldn't really be happening and it's possible that my hardware configuration is to blame, but every other aspect of the VC and Virus works just fine. I can only think of this enforced limitation as protection of hardware sales,but there must be some way of using the virus as a super dongle in non-real time export mode. The best solution for me would be that VC dealt with export as a true VSTi and did the DSP calculations in non-real time, either on the host CPU or on the virus hardware. Is there any way around this? (apart from recording the live outs, which isn't going to happen as this is just a work around rather than a solution) If you do hear glitches in an exported audio, then its a plugin behaving badly. It takes hours to get a track to the state where I can export it when the Virus is involved - I have no issues when it isn't involved. CPU overload is quite obvious as you will see the FL Studio CPU meter. This is extremely frustrating and means I have little motivation to finish songs as I know the export is going to be a nightmare. I generally have to thin the part down and export in two takes. Usually I have to solo out virus tracks and export them to a wav file before I have any hope of exporting correctly and even then, If I've pushed a sound past the polyphony limit (or at least towards it) I constantly get cpu overload errors which stop the export. My issue is that I'm happy with the occasional note being lost, and in fact sometimes my arrangements make use of it, but when it comes to export the virus just messes up my workflow. The tracks tend to play back fine in real-time although I am certain that there are a few notes being lost due to the lack of polyphony when playing complex sounds (it really can get down to being about three notes at once if you have complex sounds) I have this problem a lot with the virus - I'm doing a real-time export and the sounds I use are heavy on the DSP.
0 Comments
Leave a Reply. |