Watch out switching between your Cab-2 and DCS app with regard to lashups. If you build a lashup using the DCS app, and subsequently build the same lashup using your Cab-2, the lashup will no longer function when you return to the DCS app. Likewise, the opposite is true if you build a lashup with your Cab-2 and then move to the DCS app.
The big difference is what happens next. When your Cab-2 forgets a lashup, the configuration details for the lashup are retained, and you only need to press the “build” button to bring it back to life. However, with the DCS app, you are required to start over and rebuild the entire lashup right from the beginning. It’s a royal PITA, particularly if you have some complex arrangement that has taken a lot of time to set up via trial and error with regard to lead engines, orientations etc.
My preferred solution is using the DCS app to run only an engine or group of engines as the lashup, excluding sound cars. Then I just use a Cab-1 or Cab-2, to directly address any cars with sounds. I do this with station sounds dining cars and it works very well.