<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Vasiliy, <div><br></div><div>I think you could’ve checked that possibility by selecting the “1-receiver” option on the stitching menu to see if doing so improves the mRX program performance. Thanks for the report!</div><div><br></div><div>73, Joe K5SO</div><div><br><div><div>On Jun 23, 2013, at 8:12 PM, k3it wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="font-family: arial, sans-serif; font-size: 12.727272033691406px; ">I wonder if the difference was due to mRx processing a much bigger data stream for stitched receivers. (there was one receiver enabled in CuSDR plus the wide bandscope)<br></div></span><br class="Apple-interchange-newline"></blockquote></div><br></div></body></html>