Become a member
Become a member

or
Log in
Log in

or
News

Outsim Updates SynthMaker

Enlarge
Add this product to
  • My former gear
  • My current gear
  • My wishlist
Outsim SynthMaker
Images
1/1

Outsim has updated SynthMaker to v1.1.7: This release contains a number of bug fixes and improves compatibility with hosts like Cubase.

Exe export also sees a number of improvements in this release.

There is one new component called System Folders. This will give you the App Data and Documents folders on the host PC so that you can use them for storing user data or settings. It’s particularly important that you use these folders on Vista and Windows 7 as these are assured to be accessible and don’t require admin permissions for writing to them.

Additions and Fixes:
  • Fixed a problem where using the Format String to display an automated parameter in an exported plugin can cause the host to freeze.
  • Fixed a bug in the Wave Array component which would cause stereo 24bit files loaded into a mono array to be incorrectly converted.
  • Fixed a possible crash situation in the Wave Read Hop when changing the hop length.
  • Exported exes made to run in full screen now do so immediately instead of showing the window frame first.
  • Exported exes running in full screen do not now prevent other popup windows from appearing above them.
  • Shell Execute now uses the working folder of target application.
  • All the Wave Read components were susceptible to crashing during copy and paste or other operations when used with an analyser.
  • Fixed a problem with mouse over tracking getting stuck sometimes when more than one Mouse Move component is being used.
  • Added protection for cvtdq2ps and cvtps2dq assembler commands when used on SSE only machines to prevent crashing.
  • Fixed a bug in the Graph to Point Array primitive that would cause a crash if no float array was fed into it.
  • Poly to Mono doesn’t use a fixed size buffer any more and now copes with much larger code sizes.
  • DirectSoundOut and ASIOut no longer used fixed size buffers and now cope with much larger code sizes.
  • You can now have more than 256 components in a module, up to 32767 in total.
  • Fixed the problem of blurring of module front panels at certain zoom and pan settings.
  • Fixed a problem that was causing crashes with effects in Cubase that had more than 2 mono inputs.
  • Made a small tweak to the Shell Execute component to prevent potential delays after execution.
  • The Preset Manager and Preset Save components have a new options input so that advanced users can switch off muting, process kills and audio recompiles after a preset change or load.
  • Fixed a problem where MIDI devices were being reset when the schematic window loses and then regains the input focus.
  • Fixed a problem in the Sine primitive that can cause unpredictable crashes due to incorrect SSE2 optimisations.
  • Fixed a bug in the String to Sysex component that was causing incorrect sysex messages to be sent on random occasions.
  • Audio is now stopped during loading of exported exes.
  • New System Folders primitive gives you access to App Data and Documents folders for storing settings and user data.

New Components:
  • System Folders.

Be the first to post a comment about this news item

    Viewers of this article also read...

    cookies
    We are using cookies!

    Yes, Audiofanzine is using cookies. Since the last thing that we want is disturbing your diet with too much fat or too much sugar, you'll be glad to learn that we made them ourselves with fresh, organic and fair ingredients, and with a perfect nutritional balance. What this means is that the data we store in them is used to enhance your use of our website as well as improve your user experience on our pages and show you personalised ads (learn more). To configure your cookie preferences, click here.

    We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

    Our cookies
    Cookies not subject to consent
    These are cookies that guarantee the proper functioning of Audiofanzine and allow its optimization. The website cannot function properly without these cookies. Example: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).
    Google Analytics
    We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it.
    Advertising
    This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.

    We did not wait for a law to make us respect our members and visitors' privacy. The cookies that we use are only meant to improve your experience on our website.

    Our cookies
    Cookies not subject to consent

    These are cookies that guarantee the proper functioning of Audiofanzine. The website cannot function properly without these cookies. Examples: cookies that help you stay logged in from page to page or that help customizing your usage of the website (dark mode or filters).

    Google Analytics

    We are using Google Analytics in order to better understand the use that our visitors make of our website in an attempt to improve it. When this parameter is activated, no personal information is sent to Google and the IP addresses are anonymized.

    Advertising

    This information allows us to show you personalized advertisements thanks to which Audiofanzine is financed. By unchecking this box you will still have advertisements but they may be less interesting :) We are using Google Ad Manager to display part of our ads, or tools integrated to our own CMS for the rest. We are likely to display advertisements from our own platform, from Google Advertising Products or from Adform.


    You can find more details on data protection in our privacy policy.
    You can also find information about how Google uses personal data by following this link.