Pulseview question

[Back2Volts]

I am trying to look at some signals in a project.   I connect to the device and get busy tagging and color coding the eight signals.    Is there a way to save the signal tags and colors, so I do not have to do it every time I start the tool again?    I have tried saving but told me there was no data to save. 

[Nominal Animal]

If you record just a short piece of data first (just click on record and immediately stop), you can then save the session (into an .sr session file).  When you load the session, you get the signal tags and colors back.  Do remember to choose your logic analyzer device in PulseView first, before customizing the tags and colors; the capture device is part of the session.

Sigrok folks did add the session-setup save/restore support to .pvs files a couple of weeks ago, making this easier/more intuitive in future versions of PulseView.

[Back2Volts]

Thank you NA.   I have got to a somehow similar conclusion, but there seem to be some quirks that cause it to permanently disconnect the configuration from the device.   This happens if you mess around disconnecting and reconnecting the USB cable.    I got to a point where if I open the saved file, it uses as device name the file name, and recovers the line tags, but if I try then to select the real device, it drops the line tags.

Lets hope that the new save function solves the problem.   I wonder how good are the nightly builds and if it is possible to have the nightly coexisting with the stable and using the same sigrok

[Nominal Animal]

This happens if you mess around disconnecting and reconnecting the USB cable.

At least my Saleae Logic clone works that way, because of how Sigrok needs to upload the (open!) firmware (fx2lafw) on each connection.  For best results, avoid disconnecting the USB cable, and restart PulseView after reconnecting.

As I mentioned, always verify you have the correct device selected, before customizing the display. The session files include a reference to the specific hardware used, and if you change the hardware, PulseView tries to revert to the last session stored for that other hardware.  Yeah, it is a bit funky.

I wonder how good are the nightly builds and if it is possible to have the nightly coexisting with the stable and using the same sigrok

My "feel" is that the nightly builds are usually OK.  You can take a look at the PulseView git log to see what kind of changes are involved.  They seem pretty conservative to me.

If you run Linux, you can use the nightly AppImage binary (on x86 or x86-64 only though), without affecting a stable/installed sigrok in any way.  It is basically a self-contained archived executable and libraries it depends on; it is run directly, it does not "install" anything.  See appimage.org for details.

[dirtcooker]

I have used this script a few times to download, compile and install sigrok and pulseview on linux mint (tested on 18.3, 19.1 and 19.2 so far, which corresponds to Xenial 16.04 and Bionic 18.04 versions of ubuntu).
https://www.onetransistor.eu/2017/11/script-to-compile-and-install-pulseview.html

The script does everything including build environment setup, drivers, udev rules, etc. You might need to add plugdev group and add yourself to it as follows:
sudo groupadd plugdev
sudo usermod -a -G plugdev <your login name>

I just ran the script again today. This is from the pulseview about dialog:

Versions, libraries and features: PulseView 0.5.0-git-476ca5f

libsigrok 0.6.0-git-ef62ab6c/4:0:0 (rt: 0.6.0-git-ef62ab6c/4:0:0)

libsigrokdecode 0.6.0-git-3f6cc6d/4:0:0 (rt: 0.6.0-git-3f6cc6d/4:0:0)