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
Just to let you know, haven't checked if you already identified and fixed any such rendering issues:
In Cyberbeing/xy-VSFilter#18 Cyberbeing mentioned there are differences between upstream’s xy_sub_filter_rc* XySubFilter branches and the ones intended for xy-VSFilter and xy-VSFilter binaries based on the XySubFilter branches might be buggy. See Cyberbeing/xy-VSFilter#18 (comment) and follow-ups.
On a cursory glance it appears like you are using the XySubFilter branch for both XySubFilter and xy-VSFilter builds. At least your builds are not containing upstream’s CSRI name change from 2014 which was only committed to the xy-VSFilter branch: Cyberbeing/xy-VSFilter@0d64ad7 (released in 3.0.0.306)
The text was updated successfully, but these errors were encountered:
There are supposedly more differences between Cyberbeing’s master (xy-VSFilter) and xy_sub_filter_rc* (XySubFilter) branches. Whether pinterf already merged all other fixes I do no know. If not, pulling in just the name change is a start but not a full solution.
Yeah, I agree... I guess the solution is either waiting for pinterf to check and merge the missing patches, or going yourself and checking the differences, and finding what changes weren't merged...
Just to let you know, haven't checked if you already identified and fixed any such rendering issues:
In Cyberbeing/xy-VSFilter#18 Cyberbeing mentioned there are differences between upstream’s
xy_sub_filter_rc*
XySubFilter branches and the ones intended for xy-VSFilter and xy-VSFilter binaries based on the XySubFilter branches might be buggy. See Cyberbeing/xy-VSFilter#18 (comment) and follow-ups.On a cursory glance it appears like you are using the XySubFilter branch for both XySubFilter and xy-VSFilter builds. At least your builds are not containing upstream’s CSRI name change from 2014 which was only committed to the xy-VSFilter branch: Cyberbeing/xy-VSFilter@0d64ad7 (released in 3.0.0.306)
The text was updated successfully, but these errors were encountered: