# Adding details about publicly shared captures should be mandatory

**URL:** <https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666>\
**Category:** Feature Requests\
**Created:** [March 17, 2024, 11:09am UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666 "2024-03-17T11:09:44Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![747](https://avatars.discourse-cdn.com/v4/letter/7/e99b99/32.png) [@747](https://unity.neuraldsp.com/u/747)\
**Post date:** [March 17, 2024, 11:09am UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/1 "2024-03-17T11:09:44Z")

</div>

Problem:  
Right now there are a ton of captures on the cloud which have little to no information. Which can be really annyoing. Some steps have already been taken to better this issue, like the addition of gain structure and filtering by instrument. But the problem still remains.

Solution / Feature request:  
When sharing a capture publicly(!), it should be mandatory(!) to fill in all predetermined spaces of details about it. The only exception would be if a picture is uploaded.  
In addition to what is already in place (like author, name, preferred instrument, etc.) I would like to see added:

- Name of the actual device
- Type of the actual device
- Settings

---

<div class="post-metadata">

**Author:** ![DiffractionCircuit](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/diffractioncircuit/32/3793_2.png) [@DiffractionCircuit](https://unity.neuraldsp.com/u/DiffractionCircuit)\
**Post date:** [March 17, 2024, 1:56pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/2 "2024-03-17T13:56:22Z")

</div>

There have been discussions about this before.

The majority of users will behave the same way they always have–putting in the _bare amount_ of effort just to get their captures loaded on their Quad Cortex or up on the cloud.

- Instead of typing “Mesa Boogie Mark VII Head” in the amp device field they will type “…”

- Instead of methodically listing out their settings, they will put “Bass 1 Mid 1 Treble 1 Gain 1”, etc., whatever is the _fastest_ way to just get through the prompt and upload

- If a photo is allowed in the place of filling out the settings fields, then users will upload literally anything just to get the capture up

Adding more fields for users to fill out is fine. The users who care will use them to everyone’s benefit.

But I definitely don’t think it should be mandatory, as aggravating as that can be for the people searching for captures. It won’t solve the problem of user-generated content; it will only result in more roadblocks for everyone.

---

<div class="post-metadata">

**Author:** ![JLantz](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/jlantz/32/3610_2.png) [@JLantz](https://unity.neuraldsp.com/u/JLantz)\
**Post date:** [March 17, 2024, 3:11pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/3 "2024-03-17T15:11:02Z")

</div>

Even if they do fill out the info there is no way on the “file tree” to access those details.

Here are 13 Benson preamp captures I downloaded yesterday…I can sort by author, but it doesn’t say who the author is LOL WTF

 ![Screenshot 2024-03-17 at 9.02.36 PM](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/9/91a496798d653a497ad111e5010a1ff52b3eebf1.png)

---

<div class="post-metadata">

**Author:** ![747](https://avatars.discourse-cdn.com/v4/letter/7/e99b99/32.png) [@747](https://unity.neuraldsp.com/u/747)\
**Post date:** [March 17, 2024, 7:43pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/4 "2024-03-17T19:43:24Z")

</div>

You wouldn’t have to put in any more effort then right now if you upload for yourself. Just when sharing publicly.  
And even if what you described would happen, which I don’t think would be the norm, it would help. Because if someone won’t even spend like 20 seconds to add some much needed information and just types in random stuff, you can at least see that.  
Say I upload a capture of my setup and name it VMT 50 M15. It makes perfect sense for me. But you most likely wouldn’t know what it even is. Is it an amp? Amp with cab? Pedal?  
At the end of the day NDSP has the last word on what is being shared publicly and how it is being shared. And I think everyone would win if we would all use the same system. As long as there is no official system, everyone will use their own.

---

<div class="post-metadata">

**Author:** ![747](https://avatars.discourse-cdn.com/v4/letter/7/e99b99/32.png) [@747](https://unity.neuraldsp.com/u/747)\
**Post date:** [March 17, 2024, 7:44pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/5 "2024-03-17T19:44:20Z")

</div>

True, but a different topic. You could open a bug report for this issue.

---

<div class="post-metadata">

**Author:** ![Dorkmaster33](https://avatars.discourse-cdn.com/v4/letter/d/f04885/32.png) [@Dorkmaster33](https://unity.neuraldsp.com/u/Dorkmaster33)\
**Post date:** [March 22, 2024, 7:43pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/6 "2024-03-22T19:43:36Z")

</div>

Yeah it would be nice if people would add more info about their captures. Even a simple sound description would be enough.

---

<div class="post-metadata">

**Author:** ![LCW](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/lcw/32/6670_2.png) [@LCW](https://unity.neuraldsp.com/u/LCW)\
**Post date:** [March 22, 2024, 11:08pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/7 "2024-03-22T23:08:39Z")

</div>

If a capture in the cloud doesn’t have anything in the description I don’t even bother downloading. Not even to try. I just pass them over.

My take is they are shit if the uploader couldn’t be bothered to fill in some info.

---

<div class="post-metadata">

**Author:** ![747](https://avatars.discourse-cdn.com/v4/letter/7/e99b99/32.png) [@747](https://unity.neuraldsp.com/u/747)\
**Post date:** [March 23, 2024, 6:48am UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/8 "2024-03-23T06:48:22Z")

</div>

![IMG_1232](https://us1.discourse-cdn.com/flex020/uploads/neuraldsp/original/2X/c/ca389502db9baa79e39115af53637b529a8a419f.jpeg)  
Sadly the most popular ones don’t even have any description.

---

<div class="post-metadata">

**Author:** ![DiffractionCircuit](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/diffractioncircuit/32/3793_2.png) [@DiffractionCircuit](https://unity.neuraldsp.com/u/DiffractionCircuit)\
**Post date:** [March 23, 2024, 4:38pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/9 "2024-03-23T16:38:17Z")

</div>

✅ Adding new fields for capture settings

❌ Adding more roadblocks; requiring users to fill out the fields

---

<div class="post-metadata">

**Author:** ![rinkydinky](https://avatars.discourse-cdn.com/v4/letter/r/5daacb/32.png) [@rinkydinky](https://unity.neuraldsp.com/u/rinkydinky)\
**Post date:** [March 24, 2024, 2:37pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/10 "2024-03-24T14:37:38Z")

</div>

At what point will the company start to clean the system of junk ? It’s a minefield of junk and really I can’t be bothered with most of it , imo they need to implement a system which would benefit everyone otherwise you’d be better off just buying the ones you like from a different company.

---

<div class="post-metadata">

**Author:** ![anartist](https://avatars.discourse-cdn.com/v4/letter/a/41988e/32.png) [@anartist](https://unity.neuraldsp.com/u/anartist)\
**Post date:** [September 26, 2026, 8:29am UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/11 "2026-09-26T08:29:36Z")

</div>

No need to make it mandatory, but maybe there could be a show/hide button for captures that don’t have the details filled out.

I was looking for a V2 capture of one of my pedals since I can only create V1 captures on Linux. There were plenty of captures of the pedal, but none had any info on the settings used.

I already knew the settings I wanted, so I thought it would be pretty easy to find a capture with those settings. Instead, it would have been a whole project to go through all the captures and try to find one with the settings in mind. No thanks.

---

<div class="post-metadata">

**Author:** ![sliberty](https://avatars.discourse-cdn.com/v4/letter/s/90db22/32.png) [@sliberty](https://unity.neuraldsp.com/u/sliberty)\
**Post date:** [September 27, 2026, 12:21am UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/12 "2026-09-27T00:21:36Z")

</div>

I’d be happy if they just all said whether there was a cab included in an amp capture and what cab/speakers they are.

---

<div class="post-metadata">

**Author:** ![OceanCamp](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/oceancamp/32/10307_2.png) [@OceanCamp](https://unity.neuraldsp.com/u/OceanCamp)\
**Post date:** [October 4, 2026, 2:33pm UTC](https://unity.neuraldsp.com/t/adding-details-about-publicly-shared-captures-should-be-mandatory/13666/13 "2026-10-04T14:33:12Z")

</div>

I made a feature request some time ago addressing exactly this and other issues with the cloud captures management. Specifically comparing to the Tone3000 quite strict (and honestly better working) system.

> [@Device Profiles / Group Folders for Cloud Captures](https://unity.neuraldsp.com/t/device-profiles-group-folders-for-cloud-captures/21988):
>
> Hi everyone, here’s something I’ve been meaning to ask for since I got my Quad Mini: Currently, the Cortex Cloud upload process requires users to manually upload a photo, select tags, and write a description for every single capture. When capturing a single amplifier at various gain stages or with different cabinets, this creates a massive amount of repetitive manual labor. Because of this friction: Creators are less likely to share large, high-quality packs. Browsers see a cluttered “Ne…

I’ve seen other requests and posts regarding related topics. It would be great if we could manage to make a single Feature Request collectively, somehow. The way it is now there’s a few votes here and there and I can’t see this gaining much traction.
