Log in
Log in

or
News

Abeem Rack Performer 0.98-beta2

Enlarge
Add this product to
  • My former gear
  • My current gear
  • My wishlist
Abeem Rack Performer
Images
1/25
News Abeem Rack Performer

Virtual Rack/Host for Plug-in from Abeem

Write a user review or Ask for a user review
Reviews
Price engine
Classified Ads
Forums

Abeem Live Technologies has updated Rack Performer to version 0.98-beta2, its last public beta version.

This is the last opportunity to join the beta test program, as registrations will be closed soon, and the application transitioned to closed beta phase.

 

Several new features have been added in this release, including the Live Synopsis, Presets Links, Quick keyboard mapping and VST-Shell support (ex: Waves plugins)

 

New features:

  • The new “live synopsis” is a centralized interface to manage all document mappings
  • New “mappings” module context menu entry displays the live synopsis for the selected module only
  • Patcher operations are no longer disabled when patch is powered, but remain locked when perform mode is enabled
  • Perform mode semantic has changed: it can be enabled or disabled independently of the main mode (patch or edit)
  • VST Shell plugins (ex: Waves) are now fully supported
  • Presets links allow to link module preset numbers together such that changing any link member also changes the others
  • Quick keyboard map allows to create control focus key mappings
  • Implemented “free-wheeling” synchro config option (default: on)
  • In full slave mode with free-wheeling off, application stops and re-locate when timecode or clock signal stops (not requiring transport control commands)
  • In live synch mode with free-wheeling enabled, stoping and restarting the master makes the application properly re-lock synch
  • Patcher copy, cut and paste operations are now functional
  • Modules can now be renamed (new entry in patcher module context menu)


Minor modifications:

  • Current monitor group is now properly updated when modified via the monitor groups dialog while engaged
  • Ticker size is now dynamic and adapts to displayed content
  • Ticker events to display can now be filtered by type, in the general configuration tab
  • Refactored the (rather useless) “flat plugin listing” option to “automatically create sub directories when lists are too large”
  • Slightly optimized VST plugin scanner (again)
  • Added a “clear cache” button to the VST configuration tab (force a full deep scan)
  • Added new hidden compatibility option (default: on) to support some faulty VST plugins (ex: Model-E, VB-1)
  • New hidden advanced option to set the synchro-lost duration before triggering free-wheeling (default: 300ms)
  • Local module latencies are displayed in patcher when doing manual patch delay compensation
  • Application now properly installs for non-admin user accounts (some support files and shortcuts were missing)
  • Added hidden advanced config option to change user data directory location
  • Required fonts are now loaded dynamically to prevent accidental user deletion
  • Now reverting back to default system MMCSS profiles when custom ones are not available
  • Added a new “carbon fiber” screen background


Bug fixes:

  • Resolved some edge cases around “CRC check” and “name check” plugin listing options
  • Some recent VST plugins (ex: Model-E re-edition) were not properly listed during scan
  • OpenGL patcher surface could be corrupted when using some VST plugins built with the same technology
  • Corrected an edge case around audio output channels offset (when monitoring dedicated channels are in use)
  • “Edit” menu items were re-enabled after a right-click on a locked patcher object
  • Fixed a rare race condition that could happen on mono-core machines with some ASIO drivers
  • Resolved a crash that could happen when creating VST modules with special GUIs (ex: Mobius2)
  • Corrected some button refreshing problems in transport bar when changing synchro engine settings
  • Metronome in MIDI mode could sometimes retrigger the first down beat when tempo was zero
  • Swapping master modules did not clear scene snapshot data properly
  • Error appearing in log when using the custom MMCSS profiles right after installation
  • Angular modes for knob controls have been fixed and re-enabled
  • Minor error appearing in log sometimes when closing some documents


Check out www.abeem.eu for more.

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.