Appmuse

Maintenance update version 1.9 - There was a fairly gritty sound caused by a wrong optimization. This has been fixed. - A new global option can switch between different render modi, which affects performance. The UI has got new controls for this. LQ is a low quality rendering mode, especially for performance reasons. But also the sound is slightly different (muddier) with that. HQ is the better (not the best possible yet) rendering quality. It uses clearly more CPU cycles. PASS will completely bypass the convolution engine for testing and temporary suspending purposes. It is useful to free the CPU from overload instantly. - There is an inbuilt reverberation detection algorithm now, which auto-suspends the engine if very quiet (inaudible) levels occur. It does not make any sense to continuously convolute milliards of samples that are inaudible. Most audio units actually have such issues. - The preset loading and parameter recall with IR load should now work as expected. Please note, that this is a quite difficult thing, because Audio Units are limited in doing allocations and file operations while operation. It is also complicated because AU parameters do not support raw data or strings but merely floating point values. - An offline rendering bug was corrected. Many users reported problems with rendering 'offline'. This problem was specific to some host applications, doing offline rendering in a questionable way. Maintenance update version 1.95 - We have changed the Dry/Wet scheme. The reverberated signal can now be completely isolated from the input signal. Previous versions had a max. 50/50% percent "Mix" of the input and its convolution result. So if you want to recreate the 100% dry/wet of the previous versions, please set the dry/wet parameter to 50% now. Complete isolation (100% now) enables to cut out the input signal completely (this is thought for supporting send busses). - We got advices that some (long) user loaded IR files will produce very quiet results of reverberation. The problem here is most likely, that these files are not properly normalized. Convolutors expect normalized levels. This effect of reduced loudness will accumulate, if very long IRs are not normalized, because the larger the convolution tail is, the more pre-calculated internal loudness reduction must be applied for a correctly leveled convolution result. You may correct loudness with the reverb gain parameter up to a certain amount manually. - Better use quality produced IRs or preprocess such files prior importing. Such IRs will most probably be files, where the dynamic and the stereo field has been optimized. IRs with low dynamics tend to become quiet and weak. You also may become creative, if you feed some sort of stereo noise with rich frequency content into JAX Convolutor PRO. Some IRs, optimized for certain commercial convolution engines may not be automatically optimal for JAX Convolutor without editing or some preparation. - Note: JAX Convolutor PRO will NOT normalize IRs on import, nor will they normalize cut parts of an IR when editing, even if the display always displays normalized waveforms for better visual control. - JAX Convolutor PRO expects IR files with the sample rate of the current processing sample rate. These will not be stretched on import but you always have the possibility to stretch them with the IR stretch parameter manually. Some last words to BUGS: Bugs are everywhere and in-avoidable. Please support your developers actively by switching on sending automated anonymous crash reports to the apple servers. This is secure and no personal data is transmitted. Such reports are essential for identifying device specific problems and mistakes inside the code. And it will enable the developers to fix them in a short period of time, as you may expect.