# Alpha Release 6 **URL:** \ **Category:** Downloads / Releases\ **Created:** [July 17, 2019, 7:17pm UTC](https://discuss.saleae.com/t/alpha-release-6/89 "2019-07-17T19:17:26Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 17, 2019, 7:17pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/1 "2019-07-17T19:17:26Z")
**I would love to hear from you! Any feedback is helpful – please reply to this thread or start a new one!** Finally! - Electron! (no more Chrome) - Severed all ties with the old codebase - Crash reporting - Considerable re-architecture under the hood. - Timing Markers - Export **Protocol analyzers** did not make the cut - more issues were uncovered. Also, **Save/Load** didn’t make it in - barely. There is a **known USB problem** causing captures to ‘abort’ when lots of bandwidth is used. **Mark’s** working on that. **Rani & Anthony** will have Analyzers ready in a few more days, maybe a week. There’s also about ~10 high priority issues in work. There also a lot of pending UI updates, including improving the colors that will make it in shortly. **Low expectations please:** This alpha is rough, unstable, and lacks crucial functionality. MacOS: [http://logic-io.s3.amazonaws.com/test-builds/logic-darwin-x64-2.0.3-rc-alpha-6.zip](http://logic-io.s3.amazonaws.com/test-builds/logic-darwin-x64-2.0.3-rc-alpha-6.zip) Windows: [http://logic-io.s3.amazonaws.com/test-builds/squirrel.windows/x64/logic-2.0.3-rc-alpha-6%20Setup.exe](http://logic-io.s3.amazonaws.com/test-builds/squirrel.windows/x64/logic-2.0.3-rc-alpha-6%20Setup.exe) Linux: [http://logic-io.s3.amazonaws.com/test-builds/logic\_2.0.3-rc-alpha-6\_amd64.deb](http://logic-io.s3.amazonaws.com/test-builds/logic_2.0.3-rc-alpha-6_amd64.deb) Note: It is our goal to have the alpha software stable enough to use for real work by `J̶u̶l̶y̶ ̶1̶` **August 1**. Join the [Alpha Users Mailing List](https://saleae-support.typeform.com/to/dnapk5) to be notified about the next release! ## Coming up - 90+% done - Protocol analyzers - Save/load - High priority issue fixes ## Planned for this Quarter (Q3) - Analyzer Search - Analyzer Sequence Search - Analyzer Results Export - Improved capture configuration UI/UX - Proper settings persistence - Context-sensitive help - Proper shortcuts - Delete channels - Trim capture - Wall-clock time display - analog/digital proper alignment - Analog channel v2 - App performance metrics - Sidebar resize and collapse - Auto-update - Digital Scope-View - Trigger-on-Analog - Scope-View v2 - Performance improvements - Comprehensive USB reliability testing (internal) - Themes - Art updates / polish ---
**Author:** ![Brian](https://avatars.discourse-cdn.com/v4/letter/b/97f17d/32.png) [@Brian](https://discuss.saleae.com/u/Brian)\ **Post date:** [July 17, 2019, 8:01pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/2 "2019-07-17T20:01:13Z")
Wow! Alpha 6 is looking great. However, one thing that’s really bugged me about the previous versions as well as this new Alpha set off release is the way that the right and left side of the thing I’m really interested in (the horizontal traces) is taken up with stuff I don’t really care about that much (the “Start” button on the right and the Channel names on the left). A big usability improvement would be to allow both of these things to be minimized when I don’t need them so that as the capture is progressing and I’m doing my manual analysis of the resulting data traces they’re not taking up super-precious space. The more horizontal space that I can see my traces, the better. In fact, with the existing Logic (1.2.29 Beta) I’ll commonly stretch the Logic window horizontally across my three monitors so I can get more trace pixels in front of my eyeballs. \*Brian ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 17, 2019, 8:54pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/3 "2019-07-17T20:54:44Z")
Hey, thanks Brian! Agreed. Collapsible and resizable sidebars are coming this quarter (probably within a month I would guess). Here’s a UI mockup in the meantime. What do you think? ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/f37b5e79d9f0fe152c009682785bb67d5e2f03da.png) ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/f4225231fb1d6c497836288f7d9e6e19eae3c1fe.png) ---
**Author:** ![Collin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/collin/32/53_2.png) [@Collin](https://discuss.saleae.com/u/Collin)\ **Post date:** [July 17, 2019, 11:35pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/4 "2019-07-17T23:35:29Z")
Alpha6 nearly instantly crashes on me with Ubuntu 19.04 (linux obviously). I tried twice and told it to go ahead and send the crash report both times. Hopefully that helps to narrow it down. This is all I see on the console when trying to run it: (logic:9842): Gtk-WARNING \*\*: 19:32:57.413: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn’t be used anymore. It will be removed in a future version (logic:9842): Gtk-WARNING \*\*: 19:32:57.413: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn’t be used anymore. It will be removed in a future version (logic:9842): Gtk-WARNING \*\*: 19:32:57.413: Theme parsing error: gtk.css:73:46: The style property GtkScrolledWindow:scrollbars-within-bevel is deprecated and shouldn’t be used anymore. It will be removed in a future version ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 17, 2019, 11:54pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/5 "2019-07-17T23:54:17Z")
> [@Collin](#): > > Alpha6 nearly instantly crashes on me with Ubuntu 19.04 (linux obviously). Ouch! We’re on it – thank you Collin! The crash reports should be super useful (first real test of this). Will update soon. ---
**Author:** ![luisfhm007](https://avatars.discourse-cdn.com/v4/letter/l/ecb155/32.png) [@luisfhm007](https://discuss.saleae.com/u/luisfhm007)\ **Post date:** [July 18, 2019, 3:28am UTC](https://discuss.saleae.com/t/alpha-release-6/89/6 "2019-07-18T03:28:11Z")
> [@Collin](#): > > Alpha6 nearly instantly crashes on me with Ubuntu 19.04 Same thing on Debian 10, just after click it crashes (not even able to see the interface) same console message as Collin and it kept running on the background And on Windows 7 home (virtual machine) I was met with this ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/6a579c072c2f6443c18f80a9fb8e966cbbdf7b69.png) ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 18, 2019, 1:28pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/7 "2019-07-18T13:28:25Z")
> [@luisfhm007](#): > > Same thing on Debian 10, just after click it crashes (not even able to see the interface) same console message as Collin and it kept running on the background > > And on Windows 7 home (virtual machine) I was met with this > ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/6a579c072c2f6443c18f80a9fb8e966cbbdf7b69.png) We’re on it – thanks Luis! Will update soon. ---
**Author:** ![Brian](https://avatars.discourse-cdn.com/v4/letter/b/97f17d/32.png) [@Brian](https://discuss.saleae.com/u/Brian)\ **Post date:** [July 18, 2019, 1:45pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/8 "2019-07-18T13:45:45Z")
Joe - those mockups look AWESOME! Yes, that will work just fine and will be a huge help. Thanks! ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 18, 2019, 2:16pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/9 "2019-07-18T14:16:29Z")
> [@Brian](#): > > Joe - those mockups look AWESOME! Yes, that will work just fine and will be a huge help. Thanks! Woo! Thanks Brian, we’ll make it happen! ---
**Author:** ![rei\_vilo](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@rei\_vilo](https://discuss.saleae.com/u/rei_vilo)\ **Post date:** [July 18, 2019, 2:31pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/10 "2019-07-18T14:31:54Z")
Bonjour! Getting rid of separate Google Chrome for Electron is a great improvement. Please find below my comments: ![35](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4b25cfbc0016c478019a5ddabd7fa1d8c2c23037.jpeg) - Screen real estate is limited, and **Alpha Release 6** still consume a lot of it. - Grey on black labels are almost impossible to read. - Same for the very thick colour bands for the channels. Please make them larger! - I am still not convinced by the click-and-drag mode to get the oscilloscope view. Please allow double-clicking of the three points to open and close the view! - Please ensure menues offer only two levels, not three. ![18](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/b262ec5a972dd3c1983467e9f066c0f8d2a5c542.jpeg) - On the Export panel, does light grey mention a selected channel? Most suggestions done [Jun 11](https://discuss.saleae.com/t/alpha-release-5/59/6) on **Alpha Release 5** remain valid. Does the **Analyzer Search** planned for Q3 allow search on multiple bytes, _e.g._ `0x20 0x10` on I²C with `0x20` as I²C address and `0x10` for register? Good luck with the developement! ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 18, 2019, 3:56pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/11 "2019-07-18T15:56:37Z")
Thank you Rei! > [@rei\_vilo](#): > > Screen real estate is limited, and **Alpha Release 6** still consume a lot of it. Does the collapsing of the left and right panels (and resizing them) solve this do you think? (See UI mockup further up) > [@rei\_vilo](#): > > Grey on black labels are almost impossible to read. How’s this looking? ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/85b888bcaa3964f551f5a1673982aa547b510289.png) > [@rei\_vilo](#): > > Same for the very thick colour bands for the channels. Please make them larger! Better? ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4f7e0678f794939f0c22686382cf5cd86de5f14f.png) > [@rei\_vilo](#): > > I am still not convinced by the click-and-drag mode to get the oscilloscope view. Please allow double-clicking of the three points to open and close the view! How about this? ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/d142e6b23abd65088f71c6a29748aba315ea3f3c.png) > [@rei\_vilo](#): > > Please ensure menues offer only two levels, not three. In work. > [@rei\_vilo](#): > > On the Export panel, does light grey mention a selected channel? Will fix, thanks! > [@rei\_vilo](#): > > Most suggestions done [Jun 11](https://discuss.saleae.com/t/alpha-release-5/59/6) on **Alpha Release 5** remain valid. Agreed. > [@rei\_vilo](#): > > Does the **Analyzer Search** planned for Q3 allow search on multiple bytes, _e.g._ `0x20 0x10` on I²C with `0x20` as I²C address and `0x10` for register? Yes. > [@rei\_vilo](#): > > Good luck with the development! Thanks for the detailed feedback! Sorry this latest release has so many rough edges still. We focused on the most critical issues at the exclusion of all else just to get it out the door. But not to worry, we’re on top of the rest of it. ---
**Author:** ![rei\_vilo](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@rei\_vilo](https://discuss.saleae.com/u/rei_vilo)\ **Post date:** [July 18, 2019, 4:24pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/12 "2019-07-18T16:24:56Z")
> [@joe\_garrison](#): > > Thank you Rei! You’re welcome! > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > Screen real estate is limited, and **Alpha Release 6** still consume a lot of it. > > Does the collapsing of the left and right panels (and resizing them) solve this do you think? (See UI mockup further up) It’s promising. I’ll have a closer look when the collapsable panels are implemented. > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > Grey on black labels are almost impossible to read. > > How’s this looking? > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/85b888bcaa3964f551f5a1673982aa547b510289.png) Not enough readable: please use full white and possibly bold fonts. > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > Same for the very thick colour bands for the channels. Please make them larger! > > Better? > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4f7e0678f794939f0c22686382cf5cd86de5f14f.png) How many pixels? On a Retina display, I would need twice as much. > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > I am still not convinced by the click-and-drag mode to get the oscilloscope view. Please allow double-clicking of the three points to open and close the view! > > How about this? > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/d142e6b23abd65088f71c6a29748aba315ea3f3c.png) That’s much better. > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > Please ensure menues offer only two levels, not three. > > In work. > > > [@rei\_vilo](#): > > > > On the Export panel, does light grey mention a selected channel? > > Will fix, thanks! > > > [@rei\_vilo](#): > > > > Most suggestions done [Jun 11](https://discuss.saleae.com/t/alpha-release-5/59/6) on **Alpha Release 5** remain valid. > > Agreed. Especially saving a portion of the trace, but it looks like **Time Range to Export** has an option **Between ? and ?**. > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > Does the **Analyzer Search** planned for Q3 allow search on multiple bytes, _e.g._ `0x20 0x10` on I²C with `0x20` as I²C address and `0x10` for register? > > Yes. That’s great news! > [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > Good luck with the development! > > Thanks for the detailed feedback! Sorry this latest release has so many rough edges still. We focused on the most critical issues at the exclusion of all else just to get it out the door. But not to worry, we’re on top of the rest of it. No problem, I understand the iteration process with each release fixing targeted issues or implementing new features. ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 18, 2019, 8:31pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/13 "2019-07-18T20:31:43Z")
> [@rei\_vilo](#): > > Not enough readable: please use full white and possibly bold fonts. We’ll improve the readability further, thanks! ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 18, 2019, 8:34pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/14 "2019-07-18T20:34:38Z")
> [@rei\_vilo](#): > > > Better? > > > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4f7e0678f794939f0c22686382cf5cd86de5f14f.png) > > How many pixels? On a Retina display, I would need twice as much. Looks to be 2px on low dpi, 4 px on retina. ---
**Author:** ![rei\_vilo](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@rei\_vilo](https://discuss.saleae.com/u/rei_vilo)\ **Post date:** [July 19, 2019, 7:07am UTC](https://discuss.saleae.com/t/alpha-release-6/89/15 "2019-07-19T07:07:42Z")
> [@joe\_garrison](#): > > > [@rei\_vilo](#): > > > > > Better? > > > > > > ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4f7e0678f794939f0c22686382cf5cd86de5f14f.png) > > > > How many pixels? On a Retina display, I would need twice as much. > > Looks to be 2px on low dpi, 4 px on retina. I would suggest twice as many pixels: 4 on low dpi, 8 on retina. ---
**Author:** ![joe\_garrison](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/joe_garrison/32/12_2.png) [@joe\_garrison](https://discuss.saleae.com/u/joe_garrison)\ **Post date:** [July 19, 2019, 5:15pm UTC](https://discuss.saleae.com/t/alpha-release-6/89/16 "2019-07-19T17:15:44Z")
> [@rei\_vilo](#): > > I would suggest twice as many pixels: 4 on low dpi, 8 on retina. Well noted, thank you. We’ll should have a release by the end of the data, let me know what you think if it. It’s not 8px (high dpi) yet but is better.