Sorry, this is unavoidably verbose.
I was discussing a YouTube video by an approved Producer showing incorrect logic in the Logical Editor, and found what appears to be a similar error in the Cubase 11 manual.
The processing is quoted for the Project Logical Editor, but similar Boolean logic applies to the track Logical Editor.
It’s the old problem of mixing ANDs and ORs in the same condition.
The first example on Page 1017 has accompanying text “You can set up the Project Logical Editor to find all audio parts and events whose name contains perc as well as other MIDI parts and events whose name contains drums. ” In fact, the condition as shown in the graphic will find everything containing drums, and will include Audio as well as MIDI parts.
I just tried it on one of my own Projects and that’s what happens.
The second example is correct. If you mix ANDs and ORs you MUST bracket them properly or you get unexpected results.
It is notable that the similar mixed AND and OR examples on Page 1002 are both CORRECT.
The first example makes it clear that the last condition “Channel Equal (to) 1” will select “all events (regardless of their type) set to MIDI Channel 1.”
It’s basic Boolean logic. The difficulties in mixing ORs and ANDs are encountered by new programmers in any programming language.
Both of the Cubase Logical Editors appear to conform to the rules of Boolean logic – that’s why double and triple brackets are available in the “(“ and “)” columns.
Wouldn’t the example on Page 1014 pick up all Parts?
The first line “Container Type Equals Part OR” would select all Parts irrespective of further conditions. I think that the “Length Less than 200 Samples” is disconnected from the first line.
I haven’t tested it, but would if you like.
It would help if the chapter were to mention that texts are available which explain how Boolean logic works.
The 4th example on Page 1011 is correct, but a non-IT-savvy person would likely just zone out at the sight of all the brackets.
I don’t think that the overarching start and end brackets are actually necessary; a structure
((Media type Equals MIDI AND Container Type Equals Part) OR (Media type Equals Audio and Container Type Equals Event)) AND Property … Event is Muted
would have been slightly less opaque. Thanks for your attention. Trevor