You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 8, 2022. It is now read-only.
This issue is a result of having one dash tree per node. Each channel is modifying the same dash tree according to their own view. We tried with multiple nodes (means multiple dash trees) and it is working with "Dynamic2D" config.
The solution is to have a dash context per channel. In current architecture this is possible using multiple connections from/to dash processors but in this case the triggering of the right input/right output should be tracked.
If we are going to switch from dash ( where I will vote for that ) to boost::future, boost::async and threadpool based pipeline implementation, this is not necessary for now.
Some bricks are missing for one frame when the load_eq changes the tiling, even though they should be on GPU memory.
The text was updated successfully, but these errors were encountered: