MetaTrader 5 Platform Beta Build 5770: OpenBLAS Enhancements and Improved Operations with CSV in MetaEditor

New comment
 

On Thursday, April 9, 2026, a new beta version of the MetaTrader 5 platform will be released.

In this update, we have further enhanced integration with the OpenBLAS linear algebra library, by introducing new methods for L1 trend filtering and improvements to the component update system.

MetaEditor now also offers a more convenient way to work with CSV files. The editor automatically displays them in a table format, allowing you to filter data, sort by columns, and delete rows via the context menu.

In addition, we have improved the stability of the Strategy Tester and the web version of the platform.

MetaTrader 5 Platform Beta Build 5770: OpenBLAS Enhancements and Improved Operations with CSV in MetaEditor

We invite traders to join the testing of the new platform version, to evaluate its features and to help developers fix errors. To update to the new MetaTrader 5 beta build, navigate to Help \ Check Desktop Updates \ Latest Beta Version:

Update to beta and join testing

The final build of the new MetaTrader 5 platform will be released after the public beta test.

The update provides the following changes:


MetaTrader 5 Client Terminal

  1. Terminal: Fixed updates for ONNX and OpenBLAS libraries. Platform updates now correctly verify and download required component versions when needed.
  2. Terminal: Fixed display of the chart position fixing marker.
  3. Terminal: Fixed balance drawdown calculation in trading reports. Previously, withdrawals could be incorrectly included.
  4. Terminal: Improved the dark theme. We have adjusted some colors for better contrast.
  5. Terminal: Fixed saving the settings for connection via a proxy server. Expanded the connection logging: the first time a proxy is used in a current session, a message like this is logged:
    connecting through HTTP proxy [server]:[port]
  6. MQL5: Added new OpenBLAS methods for L1 trend filtering, enabling fast and reproducible extraction of trend components from time series.

    Where to use
    • Piecewise linear trends instead of smooth averaging: the L1 filter reduces noise and short-term fluctuations without blurring regime changes, representing trends as linear segments.
    • Automatic detection of turning points: changes in trend slope are identified naturally due to sparsity in second differences—particularly useful for financial time series.
    • Normalized regularization parameter via λmax: the λ parameter can now be defined in relative terms (as a fraction of λmax). This makes it easier to transfer settings across symbols, timeframes, and history dataset with different lengths.

    New methods

    • L1TrendFilterLambdaMax — calculates the maximum regularization value (λmax) at which the solution becomes strictly linear (global trend). Returns true/false, with λmax provided via an output parameter.
    • L1TrendFilter — computes the L1 trend for a given λ. Supports relative=true, where λ is defined within the range [0…1] as a fraction of λmax.

  7. MQL5: Fixed data requests via CopyRates. Requests outside available history now correctly return error code -1.
  8. MQL5: Expanded CUDA support for ONNX models. Currently, the following architectures can be used:

    • Turing: Nvidia 1660, RTX 2080/2070/2060, T4, Quadro RTX
    • Ampere: A100, RTX 3090/3080/3070
    • Ada Lovelace: RTX 4090/4080/4070, L40, L4
    • Hopper: H100, H200
    • Blackwell: B100, B200, B20, RTX 5090/5080/5070

  9. MQL5: Improved WebRequest performance for long-running requests with Keep-Alive header.
  10. MetaEditor: Added table view for CSV files.

    When opening CSV files, the editor now automatically displays them in a structured table format. You can filter data, sort by columns, and delete rows using the context menu.

    Any character can be used as a delimiter, including commas, semicolons, tabs, and spaces. If automatic detection is incorrect, the delimiter can be set manually.


    CSV table view feature added


  11. MetaEditor: Improved default compilation mode setting. If your CPU supports the AVX2 instruction set, the editor automatically installs the corresponding compilation mode of MQL5 applications. This allows for automatically obtaining the best execution speed.
  12. MetaEditor: Updated the default source code file writing format. The editor now saves files in UTF-8 without the BOM header. This is necessary for the correct display of files in MQL5 Algo Forge.
  13. MetaEditor: Fixed the 'repository not owned by current user' error that could occur when using MQL5 Algo Forge cloud storage.
  14. Signals: Fixed delays in signal copying when the subscriber account lacks the exchange rate required for calculating the copy ratio.

    When determining trade volumes, the system considers the balance ratio between subscriber and provider accounts. If deposit currencies differ, a corresponding conversion rate is required. If the needed conversion rate is unavailable, the system assumes equal balances and logs the warning:
    no conversion rate for the deposit currency of provider and subscriber
    Previously, after this warning, users could experience delays in trade copying. This issue has now been resolved.

  15. Tester: Fixed CopyTicksRange behavior. Requests for symbols other than the main testing symbol previously returned error 4401.
  16. Tester: Fixed import of custom trading settings. These settings can now be edited after import.
  17. Updated Uzbek localization — now it uses the Latin script.

MetaTrader 5 Web Terminal

  1. Fixed positioning of the indicator adding dialog. It could previously appear at the edge of the screen for some users.
  2. Fixed display of trading start in instrument specifications.
  3. Fixed double-click behavior on objects and the vertical scale. It now opens properties and resets zoom to default.


The update will be available through the Live Update system.

 

Hello,

a) Thank you for the continued improvement :) 

b) Regarding MetaEditor, I noticed that the behavior of the "Find Dialog" has changed recently, where when pressing "Find Next", the focus leaves the dialog window and goes inside the text editor; is this on purpose, because I may say I find it somehow inconvenient (?)

Greetings

New comment