Showing posts with label bug. Show all posts
Showing posts with label bug. Show all posts
Monday, 14 November 2011
Sequent demo critical bug notice
Just a quick heads up to make everyone aware that there is a critical bug in the Sequent evaluation: since earlier today, the demo will no longer load factory presets. Since being informed of the bug (thanks Emmanuel!), we've fixed it, but building and testing the eleven or so architectures and plug-in formats that Sequent supports will take a little while. ETA for bug fix: early tomorrow morning.
I apologise for the inconvinience, and will update this thread when the new evaluation is available.
Note that registered copies of Sequent aren't affected by this.
Thanks!
Sunday, 21 August 2011
Mac OS X plug-in interface resizing issues
It would appear that, with the most recent 1.6.0 releases, there is a problem with certain Mac OS X hosts, such as Digital Performer 7, and Resound's and Manifold's interface resizing, which occurs when the preset browser is open.
We are looking into this, but in the intermin, those affected by this bug can work-around it by switching the preset browser to a modal type dialog. To do this:
- Open the corresponding configuration file, which will usually be placed at ~/Library/Preferences/Loomer/Resound.xml or ~/Library/Preferences/Loomer/Manifold.xml .
- Add the following line to the file: <value name="ModalPresetBrowser" val="1">
- Save and close the configuration file.
All new instances of the plug-in will now use the modal (pop-up) version of the browser.
We apologize for the inconvenience, and hope to have a fix out as soon as possible. I would be interested to hear if this problems also occurs in any other hosts, so by all means post details here of any resizing incompatibilities.
Thanks!
Thursday, 10 March 2011
Upgrade notice for Cubase users
Just a quick heads-up for Cubase users regarding an issue which can cause Loomer plug-ins saved in Cubase projects to reset to their default after upgrading said plug-in.
Other hosts are not affected. Presets saved externally are not affected.
This issue will only crop up if you:
And this is the new integrated preset browser:
To clarify, if you've updated from a version before any of these, to these versions or later, your plug-in configuration saved in the Cubase project will reset to default:
Due to the nature of the bug, there is no workaround that we can implement in our code. The bug is with Cubase, and the ball is very much in Steinberg's court in terms of a fix. In the interim, we suggest:
We apologize for any inconvenience this may have caused.
Other hosts are not affected. Presets saved externally are not affected.
This issue will only crop up if you:
- Save a project using a plug-in that used the old, flat preset system.
- Upgrade the plug-in to a version that users the new integrated preset browser.

And this is the new integrated preset browser:

To clarify, if you've updated from a version before any of these, to these versions or later, your plug-in configuration saved in the Cubase project will reset to default:
- Aspect 1.6.0
- Manifold 1.5.0
- Shift 2.0.0
- Resound 1.5.0
- Sequent 1.1.0
- String 1.2.3
Due to the nature of the bug, there is no workaround that we can implement in our code. The bug is with Cubase, and the ball is very much in Steinberg's court in terms of a fix. In the interim, we suggest:
- Before you upgrade, save your presets out to native .xml or .fxp files.
- Upgrade the plug-in(s).
- Open your Cubase projects, load your saved presets into the affected plugins, save the projects, and never concern yourself about this bug again.
We apologize for any inconvenience this may have caused.
Subscribe to:
Posts (Atom)