Post crusher-X feature requests here

[freq]

Hi,

Please feel free to post any suggestions or feature requests for crusher-X here. We are very interested in your opinion and will do our best to include your feature request in the backlog for future updates or upgrades.

Thanks!
accSone

[guyd2]

On the risk of sounding pretentious/arrogant as a beginning user, or threading into unknown territory, here's a few requests springing to mind, in no particular order :

1. File (Program) management :
- Adding a way to categorize & annotate Presets, and enabling filtering on these.
E.g. with Author/Bank (instead of using the underscore in its name)/Attributes (soundscape, atmospheric, FX, ...)/Features (ext.input, sidechained,...), and a Notes/Annotation field (handy for e.g. performance hints).
All this preferably in a combination of preset parameters and user-definable ones.

- Using a more common file management system: New, Save, Save As..., Save a Copy As..., Duplicate..., Import..., Export..., Revert.
(Save does not use a file dialog, which obviously is a lot quicker than Export...)
Ideally accompanied by a History List, the Undo/Redo buttons' big brother.

- Adding a INIT button (with confirmation) to make it easy to start from really-scratch.
(I'm aware of the factory start-presets)

- Making the factory presets & samples easier to access (Mac OS only, I suppose); see my other post.

2. DCO & Player editor panel :
- Unless I've missed a major chapter, I'm a bit surprised that the In/Out loop Markers {for the sample} aren't under voltage control ? Likewise for the Frequency... Aren't these major basic requirements for a granular system ? Hmm, I must be overlooking something.

- Displaying the sample's file size and length could be useful.

3. Trigger & Glitcher panel:
- In the same vein as above: making the Low/High freq markers voltage-controllable, with control over both their levels and frequencies.
- Adding a Link button (*), similar to the DCO's markers, and also enabling voltage control over the center frequency. Nice with Formant- and BP filters.
(*)I'm aware of the "click-in-the-middle-to drag-both" feature, but that's a bit of a hit-and-miss thing in some cases.

4. Making the PM field somewhat more useful by adding pre-set trajectories ? E.g. Bouncing ball, spiralling, etc... In best case, user-definable (drawing).

5. More and elaborate control over individual channels' panning [behaviour].

6. Non-MIDI-driven, internal triggerable Envelopes as a new modulation source [for about everything]. For example, when applied to the Output(s) or VOL, one could simply fade-in/fade-out a complete patch, at will.

7. A "Disable all GUI Animation" thingy. To save some CPU cycles (quite a few, I reckon).
The animations are obviously a very important part of the ability to see what you're creating, but I'm thinking that once you're done creating your patch, and you got familiar with its workings and e.g. defined your controllers, the animations are kinda redundant and are just gobbling up cycles and memory. I think. Especially in a live performance where there's likely a lot more things going on than only Crusher-X, this might be a life saver.


Apologies if there's too much nonsense and/or wishful thinking in my post !

Cheers,
_Guy

[freq]

Thanks for the suggestions Guy! Very thoughtful suggestions!
We will study them carefully and let you know (here) when they made it to a release!
Best
accSone

[CrystalWizard]

Newby myself (demoing and haven't had time to dig too deeply) but i think these are great ideas. As is Crusher X.
BTW, it;s treading into unknown territory.

On the risk of sounding pretentious/arrogant as a beginning user, or threading into unknown territory, here's a few requests springing to mind, in no particular order :

1. File (Program) management : ...

2. DCO & Player editor panel :...

3. Trigger & Glitcher panel: ...


4. Making the PM field somewhat more useful by adding pre-set trajectories ? E.g. Bouncing ball, spiralling, etc... In best case, user-definable (drawing).

5. More and elaborate control over individual channels' panning [behaviour].

6. Non-MIDI-driven, internal triggerable Envelopes as a new modulation source [for about everything]. For example, when applied to the Output(s) or VOL, one could simply fade-in/fade-out a complete patch, at will.

7. A "Disable all GUI Animation" thingy. To save some CPU cycles (quite a few, I reckon).
...

[guyd2]

BTW, it;s treading into unknown territory.

It's "it's".

[CrystalWizard]

BTW, it;s treading into unknown territory.

It's "it's".

Ah yes, i'm aware of that, i obviously hit the wrong key ; instead of '...
Between the cognitive impairment, over self medicating, and a crap keyboard with poor lighting, and poor eyesight, i end up editing just about every post, even after i preview them, hence my sig.

[neverbefore]

BTW, it;s treading into unknown territory.

It's "it's".

Ah yes, i'm aware of that, i obviously hit the wrong key ; instead of '...
Between the cognitive impairment, over self medicating, and a crap keyboard with poor lighting, and poor eyesight, i end up editing just about every post, even after i preview them, hence my sig.

and yet, by recognising the meaning of 'it;s' guyd2 demonstrates that 'it;s' is a functionally valid contraction of 'it is'

[safetyscissors]

I'd love to see more that 10 channels of output possible. 7.1.2 is great but I have been working in 7.1.4. Having the higher height channel count adds a lot of space, and there are Atmos based workflows that incorporate higher than 2 heights using composites (even with 9.1.6) and it would be amazing if crusher-x could work with these.

[freq]

Hi,

some of above mentioned features wishes related to a more flexible program management were implemented in free crusher-X 10.43 feature update:

viewtopic.php?t=606569&sid=d8143e784741 ... da04e5bdd4

Thanks for your input! Very appreciated!

Enjoy!
accSone

[morphex]

Since I first started using this plug-in, I’ve been letting my colleagues and other sound designers know about my experiences with it. I have a reputation for always seeking out the most unique and exotic effects that I can find. And crusher-X fits that description like a glove.

This isn’t really a feature suggestion, but one about versions that are available to choose from. Clearly, the sound designer crowd and experimental musicians are the people who are most likely to purchase crusher-X. They’re also more likely to pay a premium for such a deep VST.

Unfortunately, that means that crusher-X remains out of reach for many hobbyists and other curious minds. I received 3 emails from friends asking if you have sales or if you offer a “lite version” that isn’t such a large investment.

Offering a slimmed down version that would be eligible for upgrades to the full version seems like an interesting idea. And it’s one that’s been suggested to me several times now. So I thought that I would share that with you.

Certainly there are a lot of logistics involved that I don’t claim to know about or understand. But I would be curious to know if that’s something that you would ever consider. Cheers!

[Penguin Classics]

I totally get why there are no sales and I'm fine with the high price - you can demo it no problem for as long as you like I think so I don't think a lite version would bring many sales personally - if you really want to explore granular and like the demo you will probably stump up for the full version anyway - hobbyists also tend to have way more money to spend usually - when I worked on music full time I was counting the pennies but now I have money but no time like most people unfortunately.
It is an interesting idea though if a cheaper version would get people to buy it but I think Crusher-X is so specialised you either will or won't buy it at the end of the day.
What I think does hurt sales is not having a discount for people who own the current version to upgrade to the newest version.. I have skipped 10 but if it was 25% discount or whatever for version 9 owners I would probably have upgraded to 10 then upgraded to 11 etc so they have actually lost money from me with the upgrade price as it is. If you don't upgrade straight away you might as well just wait for another version - there is no point me buying 10 now as 11 might be out in a few months and I would have to pay the full price again.

Also there was a private chat room a few years ago ( I don't know if it is still going ) to discuss new features etc which I thought was a bad idea as for people interested in granular and checking out Crusher-X on KVR it makes it seem a bit dead - gets people excited to buy something when they see it is actively being discussed and developed.

[freq]

you above for all the great suggestions! Sorry, we were a bit quite in the past but all your suggestions were put in the product backlog and are prioritized due to feasibility and its value for the community. We intensively worked together with well known sound designers and music producers (e.g. this time with the Grammy nominated Hans-Martin Buff) to validate the backlog and most of your suggestions made it into the new crusher-X 11 release.

Please continue posting your feature requests here - It's a pleasure and honor to stay in contact with you creatives and get your valuable inputs and ideas!

Best
accSone

[andreTSV]

The DCO & Player Editor in version 11 doesn't react in the same way as in version 10 for the FX plugin.
Here's the problem: I've created presets for various acoustic instruments, and what I like about version 10 is that you can save a preset with the DCO Player wave. So, I created a bank of 200 presets with a preset 01 for a piano with a piano wave in the Player, a preset 02 for a trumpet with a trumpet sound in the Player, and so on. For each preset, I pressed the Start/Stop button on the DCO Player and saved the bank, so that when I opened the bank, I could immediately listen to the different presets without having to press the Start/Stop button again for each preset. This is no longer possible with version 11. If I open this bank from version 10, I still have to press the Start/Stop button for each preset, and on the other hand, if I save a bank in the same way as I did for version 10, I still get the same result.
Is there a way of solving this problem?
It works in the crusher-X11 instrument and in the Standalone version, but more importantly it should work in the FX plugin.

[freq]

Hi,

interesting - unless the "Global DCO" switch in the Setting Tab is not active - an import of a patch in version 11 should set the DCO player status the same as exported in version 10. Are you using the crusher-X import/export functionality or do you using a patch/bank save from the host DAW (in case which DAW)? Would be great if you could provide a short screenshot video that illustrates the wrong behavior.

Thanks
accSone

[andreTSV]

For both versions, everything I did was inside the plugin and with the Global DCO deactivated.

Playback of the bank (saved by version 10) with version 11:
If the Global DCO is ON (lit in blue), you always have to press Start/Stop and, what's more, the wave in the DCO always remains the same regardless of the preset chosen.
If the Global DCO is OFF, Start/Stop must always be pressed for each preset, but the wave changes with the preset, as it should.

Indeed, a preset saved with version 10 opens correctly with version 11.....but not the bank!

Hi,

Would be great if you could provide a short screenshot video that illustrates the wrong behavior.

Thanks
accSone

I suppose you're thinking of a smartphone. I don't have one. If you think it would be useful, I could take screenshots. If so, can I send them directly to you at: email@accsone.com?

BTW is it normal, for morphing time, to have to enter a desired value twice if it's greater than 60s?