# Alpha Release 5 **URL:** \ **Category:** Downloads / Releases\ **Created:** [June 3, 2019, 2:20am UTC](https://discuss.saleae.com/t/alpha-release-5/59 "2019-06-03T02:20:20Z")\ **Posts on this page:** 10\ **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:** [June 3, 2019, 2:20am UTC](https://discuss.saleae.com/t/alpha-release-5/59/1 "2019-06-03T02:20:20Z")
**I would love to hear from you! Any feedback is helpful – please reply to this thread or start a new one!** Hi All, This is an interim release that shows what we’re working on for Timing Markers. I had hoped to have Protocol Analyzers and Electron in here but we’re not quite there yet. Timing Markers also needs more love in terms of making “pairs”, so I won’t post a video this time. **Low expectations please:** This alpha is rough, unstable, and lacks crucial functionality. [https://downloads.saleae.com/betas/2.0.2/Logic-2.0.2-win64.zip](https://downloads.saleae.com/betas/2.0.2/Logic-2.0.2-win64.zip) [https://downloads.saleae.com/betas/2.0.2/Logic-2.0.2-MacOS.dmg](https://downloads.saleae.com/betas/2.0.2/Logic-2.0.2-MacOS.dmg) [https://downloads.saleae.com/betas/2.0.2/Logic-2.0.2.AppImage](https://downloads.saleae.com/betas/2.0.2/Logic-2.0.2.AppImage) Note: It is our goal to have the alpha software stable enough to use for real work by July 1. Join the [Alpha Users Mailing List](https://saleae-support.typeform.com/to/dnapk5) to be notified about the next release! ---
**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:** [June 11, 2019, 9:17am UTC](https://discuss.saleae.com/t/alpha-release-5/59/2 "2019-06-11T09:17:10Z")
I’ve just gave Alpha 5 a try. I haven’t tested it in real case: I’ve only played with the demo generated signals. Here are some comments / suggestions: - I really like the interface: it is clean and easy to read, with high contrast. - Everything is displayed with large fonts and takes much space. Screen real-estate is a constrained resource, so I would suggest to optimise how it is used. - Make the colour mark of the signal larger. It is early visible. ![43](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/fb3753fda172adee721a1a06847da0a735c0f989.png) _The post is split as I am only authorised to include one picture._ ---
**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:** [June 11, 2019, 9:17am UTC](https://discuss.saleae.com/t/alpha-release-5/59/3 "2019-06-11T09:17:41Z")
- I’m not a big fan of collapsable panes as they require rather elaborate mouse gestures. Could a double-click be used instead to open and close the pane? ![48](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/06fa5f6ea1e87983fa6497af2bc660dbe7751233.png) ---
**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:** [June 11, 2019, 9:18am UTC](https://discuss.saleae.com/t/alpha-release-5/59/4 "2019-06-11T09:18:21Z")
- Similar remark for sub-sub-pane, here for trigger configuration? Sticking with two levels (first displayed, second asked for) would be better. ![33](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/afc8014dc36803245d511142b9c79b15e5e8fe5b.png) _Please answer this post so I could continue posting the remaining parts._ ---
**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:** [June 11, 2019, 5:37pm UTC](https://discuss.saleae.com/t/alpha-release-5/59/5 "2019-06-11T17:37:55Z")
> [@rei\_vilo](#): > > Everything is displayed with large fonts and takes much space. Screen real-estate is a constrained resource, so I would suggest to optimise how it is used. We’ll make it happen! Both the channels ‘sidebar’ on the left and the sidebar on the right will be easily collapsible and adjustable. > [@rei\_vilo](#): > > Make the colour mark of the signal larger. It is early visible. Will do. > [@rei\_vilo](#): > > The post is split as I am only authorised to include one picture. Sorry about that, I’ve removed the default limitations for new users. > [@rei\_vilo](#): > > I’m not a big fan of collapsable panes as they require rather elaborate mouse gestures. Could a double-click be used instead to open and close the pane? Absolutely. We will replace with some sort of open/close button most likely. > [@rei\_vilo](#): > > Similar remark for sub-sub-pane, here for trigger configuration? Sticking with two levels (first displayed, second asked for) would be better. I don’t quite follow – very interested in what you mean though – could you elaborate? Hey, thank you for the help rei\_vilo! Super appreciated. ---
**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:** [June 11, 2019, 5:50pm UTC](https://discuss.saleae.com/t/alpha-release-5/59/6 "2019-06-11T17:50:36Z")
First, the other comments and suggestions: - Please make the analog line stronger as it is difficult to read on a MacBook Retina. ![07](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/cb35293a2c2552d0f4437ed1bf804384311a904f.png) I remember some suggestions I made earlier: - Provide a QuickTime-like selection of the trace to extract a part of it, in yellow below. ![40](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/7b3bcc5f6792fa149373ccc739d47afcddd9e35f.jpeg) - Leverage the RGB LED of the Saleae logic analyser to signal different states: _e.g._ yellow while waiting for trigger, red when recording, white for memory overflow, green for inactive, … ![53](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/f511b4e2eab09cccb12e70457a608e67987f9e70.png) Good luck with the development! ---
**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:** [June 11, 2019, 6:01pm UTC](https://discuss.saleae.com/t/alpha-release-5/59/7 "2019-06-11T18:01:35Z")
> [@joe\_garrison](#): > > > Similar remark for sub-sub-pane, here for trigger configuration? Sticking with two levels (first displayed, second asked for) would be better. > > I don’t quite follow – very interested in what you mean though – could you elaborate? Currently, the interface shows 3 levels: ![Levels](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/e1ebc846f98bd94275227a8f011f256b3bb2731f.jpeg) - Level 1: list of channels - Level 2: (?), shown when swiping **1-swipe-2**. - Level 3: I guess it is about defining the trigger, shown when clicking on **2-click-3**. About Level 2, sorry, I don’t understand what it corresponds to. ![21](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/30febc6215714b94e014710b5dda8cd6803834e1.png) For an optimised GUI, sticking with two levels (_i.e._ Level 1 and Level 2) is recommended. In that case, the button **2-click-3** would appear in Level 1, close to the name of the channel as in the current version 1.2.29. ![43](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/bbf66d63a672ab1940749d7c4b255b4e72c373de.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:** [June 11, 2019, 6:32pm UTC](https://discuss.saleae.com/t/alpha-release-5/59/8 "2019-06-11T18:32:45Z")
> [@rei\_vilo](#): > > - Please make the analog line stronger as it is difficult to read on a MacBook Retina. > > ![Capture 2019-06-11 à 11.06.07.png](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/cb35293a2c2552d0f4437ed1bf804384311a904f.png) 👍 Will do. > [@rei\_vilo](#): > > - Provide a QuickTime-like selection of the trace to extract a part of it, in yellow below. > > ![Capture 2019-06-11 à 11.11.40.jpg](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/7b3bcc5f6792fa149373ccc739d47afcddd9e35f.jpeg) 👍 It’s on the board, tentatively slated for Q4 this year. What I have in mind is where whatever is in the current view is simply exported, by itself, into a new tab. There could be other methods too, will explore more when we’re ready to start working on it. ![board](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/b2a38f6de4446e3c366b136c46a493a510097847.jpeg) > [@rei\_vilo](#): > > - Leverage the RGB LED of the Saleae logic analyser to signal different states: _e.g._ yellow while waiting for trigger, red when recording, white for memory overflow, green for inactive, … > > ![Capture 2019-06-11 à 11.03.53.png](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/f511b4e2eab09cccb12e70457a608e67987f9e70.png) 👍 It’s on the board, tentatively slated for Q4 this year. > [@rei\_vilo](#): > > Good luck with the development! Thanks! We’re excited about it! > [@rei\_vilo](#): > > For an optimised GUI, sticking with two levels ( _i.e._ Level 1 and Level 2) is recommended. > > In that case, the button **2-click-3** would appear in Level 1, close to the name of the channel as in the current version 1.2.29. Thanks for the clarification! It’s not obvious - because there is a lot of clean up that needs to happen, but the “level 2” you describe is what we call the “Scope View” i.e. Oscilloscope View. See the video here: [Alpha Release 4](https://discuss.saleae.com/t/alpha-release-4/46) . The “trigger settings button” is specific to the Scope View, that’s why it’s on that panel. “Capture start triggering” like in the old software has moved here: ![image](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/48a5b8eba5e19bbf84621f045d6cb137de78a765.png) That said, it does feel like a step backwards in some respects (decoupling the trigger settings from the Channel Labels that is) but will def. be revisited over time. ---
**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:** [June 11, 2019, 6:58pm UTC](https://discuss.saleae.com/t/alpha-release-5/59/9 "2019-06-11T18:58:27Z")
Thanks, it looks like I missed an episode! So now, I understand the scope view better. ![30febc6215714b94e014710b5dda8cd6803834e1_2_1380x156](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/4ed45bad0bf1dd2296691cb0e5a34a554998734b.png) ---
**Author:** ![alank2](https://avatars.discourse-cdn.com/v4/letter/a/ecd19e/32.png) [@alank2](https://discuss.saleae.com/u/alank2)\ **Post date:** [June 28, 2020, 2:23am UTC](https://discuss.saleae.com/t/alpha-release-5/59/10 "2020-06-28T02:23:12Z")
Something that would have been useful to me the other day is the ability to specify the time on a measurement. I was trying to count the positive pulses in a 60 second period and I could zoom in at each end and carefully click drag the measurement, but if we could have a properties dialog that actually has the start and end positions in seconds that I could have just put in a 0 and 60, that would have been much easier.