Log in
Log in

or
Create an account

or
News

DirectWave Updated To v1.4.3

Enlarge
Add this product to
  • My former gear
  • My current gear
  • My wishlist
Image Line DirectWave
Images
1/1
News Image Line DirectWave

Image Line has updated DirectWave to v1.4.3.


New features and changes since v1.4.1:
  • Updated import dll.
  • Now uses modeless downloader window.
  • Click on empty area in scrollbar(s) to go to that position.
  • Set max polyphony to 256.
  • Added browser preview volume knob.
  • Added “home” button to go back to the content library.
  • Shortened browser path that’s shown (when it’s in the content library path).
  • Added option to copy imported dwp and (temp) samples to the content library.
  • Re-arranged config dialog.
  • Now shows “monolithic format” warning if an external bank is imported without reference to wave files.
  • Now searches its own library folder for missing samples as well.
  • The user can now choose between demo and player mode, to try all features before buying.
  • Allow link and move drag&drop operations, not just copy.
  • FL version now stores samples in zipped flp file, if total recall is off.
  • FL version now shows selected program’s name as the “short name” for the channel.
  • FL version now asks FL to find missing samples.
  • FL version: added popup menu for automatable parameters.

Bug fixes:
  • Overwrite existing wave files when sampling a VST (but only .wav files).
  • Make sure the sample rate is sent to the plugin before processing a VST plugin.
  • DW no longer steals keyboard focus, except for edit controls.
  • Loading a DWB file now tries to load a sample from file if it’s not in the DWB.
  • DWB files now save a reference to the file instead of the sample data when total recall is off.
  • Fixed acm import – sample length wasn’t adjusted after conversion (was sometimes less than predicted).
  • Fixed mouse position inaccuracy for pitch bend and mod sliders (multi tab).
  • Prevent crash when previewing samples in some cases.
  • Time stretch knobs are now also automatable.
  • Fixed crash when showing long program names in progress.
  • Fixed stack corruption around filename buffer when loading downloader dll.
  • Fixed crash when canceling"Browse" window in browser.
  • Fixed loading wave files by absolute filename.
  • Avoid “no disk in drive” error message when loading samples.
  • Fixed event handling for hosted VST plugin, it used a fixed size event buffer.
  • Fixed browser update after using “Browse” button.
  • Fixed PeekMessage loop on dll unload, to prevent crash in Podium.
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).
    Audience analysis (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 (Google Ads)
    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.
    Marketing (Meta Pixel)

    On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

    We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

    For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

    Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


    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).

    Audience analysis (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 (Google Ads)

    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.

    Marketing (Meta Pixel)

    On our websites, we use the Meta Pixel. The Meta Pixel is a remarketing pixel implemented on our websites that allows us to target you directly via the Meta Network by serving ads to visitors of our websites when they visit the social networks Facebook and Instagram. The meta pixel are code snippets which are able to identify your browser type via the browser ID - the individual fingerprint of your browser - and to recognise that you have visited our websites and what exactly you have looked at on our websites. When you visit our websites, the pixel establishes a direct connection to Meta's servers. Meta is able to identify you by your browser ID, as this is linked to other data about you stored by Meta on your Facebook or Instagram user account. Meta then delivers individualised ads from us on Facebook or on Instagram that are tailored to your needs.

    We ourselves are not in a position to identify you personally via the meta pixel, as apart from your browser ID no other data is stored with us via the pixel.

    For more information about the Meta Pixel, the details of data processing via this service and Meta's privacy policy, please visit Meta Privacy Policy - How Meta collects and uses user data for Facebook and Meta Privacy Policy - How Meta collects and uses user data for Instagram.

    Meta Platforms Ireland Ltd. is a subsidiary of Meta Platforms, Inc. based in the USA. It cannot be ruled out that your data collected by Facebook will also be transmitted to the USA.


    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.