# Exporting? **URL:** \ **Category:** Logic 2 Software\ **Created:** [December 25, 2021, 9:37pm UTC](https://discuss.saleae.com/t/exporting/1330 "2021-12-25T21:37:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![easfreitas](https://avatars.discourse-cdn.com/v4/letter/e/5daacb/32.png) [@easfreitas](https://discuss.saleae.com/u/easfreitas)\ **Post date:** [December 25, 2021, 9:37pm UTC](https://discuss.saleae.com/t/exporting/1330/1 "2021-12-25T21:37:36Z")
I don’t have too much knowledge and maybe is not necessary, but, It seems that the quantity of decoder on sigrok is way bigger than on the Saleae. I have 16 PRO which works really good for capturing but when going to decode seems very limited the options If I go to sigrok , it show much more decoder but, the capture don’t seems so good, and even using on MacOS is a nightmare (no signature on the app, hangs, etc). So I tried to capture on Saleae export and import on sigrok, but I didn’t found how if exported as .csv , sigrok import as one sample per line, what is not true, because the export is as “saved each change” what means each line is generated once the change happens and not in the sample if exported as .bin it generate on file per signal (D0, D1, D2, etc), and sigrok expect 1 single file for all signals … in this case on the import sigrok has the option to choose “saved at changed” … it works. I imported one Signal and it was OK, but of course when I go to the other file it overwrite the first signal, so only import one signal per file Like I said I don’t have too much knowledge and maybe it simplest than that and I’m missing something I appreciate any suggestion ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [December 28, 2021, 3:51am UTC](https://discuss.saleae.com/t/exporting/1330/2 "2021-12-28T03:51:05Z")
@easfreitas We don’t design our export files to import natively into Sigrok, but hopefully we can help out with getting something working from within our Logic 2 app. Can you let me know a little more about the decoding options that you require? ---
**Author:** ![easfreitas](https://avatars.discourse-cdn.com/v4/letter/e/5daacb/32.png) [@easfreitas](https://discuss.saleae.com/u/easfreitas)\ **Post date:** [December 28, 2021, 11:36am UTC](https://discuss.saleae.com/t/exporting/1330/3 "2021-12-28T11:36:16Z")
Thanks Tim. As always you helping, I appreciate that For this case I’m decoding IR NEC. I shows like this on sigrok ![Capture](https://canada1.discourse-cdn.com/flex030/uploads/saleae/original/1X/f8a9b0f2d9e87893392cc981ed9779552e643961.png) One feature that existed on the logic1 long time ago (but was removed) that can helps is when exporting to csv, put the check box “save on sample”, because today it don’t have anymore, so always export as “save on change” “save on sample” = 1 line on the csv per sample “save on change” = 1 line on the csv per changed logic (the only one existing now a days) ---
**Author:** ![timreyes](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.saleae.com/timreyes/32/108_2.png) [@timreyes](https://discuss.saleae.com/u/timreyes)\ **Post date:** [December 29, 2021, 8:36pm UTC](https://discuss.saleae.com/t/exporting/1330/4 "2021-12-29T20:36:07Z")
@easfreitas Thanks for describing that for us. One way we’re introducing decoding of multiple layers is via high level analyzer extensions below: > **[Software Extensions](https://support.saleae.com/extensions)** High level analyzers essentially act as a “translator” for decoded messages from our built in low-level analyzers. Here is a great example extension that a user has submitted to our extensions marketplace. Their extension allows further traslating of data output from our Async Serial Analyzer. They utilize multiple rows of decoded bubble tracks, similar to how you’ve shown in your screenshot. > **[GitHub - RallySmith/logic2-ext-armdebug: ARM debug/trace HLA extension for...](https://github.com/RallySmith/logic2-ext-armdebug)** > > ARM debug/trace HLA extension for Saleae Logic2. Contribute to RallySmith/logic2-ext-armdebug development by creating an account on GitHub. Unfortunately, our high level analyzers are currently limited to working with a few pre-installed analyzers listed below: > **[HLA - Analyzer Frame Format](https://support.saleae.com/extensions/analyzer-frame-types)** > > Documentation for output produced by Saleae's built-in Analyzers Currently, high level analyzers cannot work for custom analyzers such as the NEC IR analyzer that another user submitted below: > **[Community Shared Analyzers](https://support.saleae.com/protocol-analyzers/community-shared-protocols)** I added a vote and comment for you below so we can track your need for this: > **[Add HLA Support for Custom Analyzers - Logic 2 - Ideas and Feature Requests -...](https://ideas.saleae.com/b/feature-requests/add-hla-support-for-custom-analyzers/)** > > This is a request to add HLA support for custom analyzers (LLAs or Low Level Analyzers) built using our protocol analyzer sdk below: > support.saleae.com/saleae-api-and-sdk/protocol-analyzer-sdk Also, I see what you mean with regards to “row per sample” vs “row per change.” We did in fact remove the “row per sample” export option in the latest Logic 2 app. Similar to the above request, I added a comment and vote for you below: > **[Export Raw Data - export every sample - Logic 2 - Ideas and Feature Requests...](https://ideas.saleae.com/b/feature-requests/export-raw-data-export-every-sample/)** > > Currently, digital channel entries are only recorded in the export file when data changes (not on every sample). Therefore, the number of entries in the resulting export file are dependent on the number of transitions that occur and not on the number... Thanks again for detailing your use case and feature request for us! ---
**Author:** ![easfreitas](https://avatars.discourse-cdn.com/v4/letter/e/5daacb/32.png) [@easfreitas](https://discuss.saleae.com/u/easfreitas)\ **Post date:** [December 29, 2021, 9:43pm UTC](https://discuss.saleae.com/t/exporting/1330/5 "2021-12-29T21:43:03Z")
Correct, having the option to export “row per sample” for .csv file would help