FEATURE REQUEST list - what do you want from energyXT2 ?

[Branis]

Oh, and while I'm at it...

This won't be a biggie for anyone else but I'd like the delay in the multi-fx to spit out a single delayed signal when the feedback is set to 0%. Currently it does nothing. Turn up the f/b a little and... multiple echoes. Aaaaaargh! It's driving me mad!

Sorry.

I'd love that too. It would be useful for setting pre-delay time for the reverb.

[siegfried]

Diek: yeah, the possibility of change levels in the cords (like in Buzz) instead of new built-in effects!

[Igro]

Please add Copy/Paste action into menu shell.

[tomg]

Diek: yeah, the possibility of change levels in the cords (like in Buzz) instead of new built-in effects!

-1

Personally, I do not want this at all and would whine if it gets put in. If you really want it I'll make you a vst level control and you can use that.

[Mighty Pea]

And you'd whine why exactly? It'd be easy enough to ignore, and it's been requested many times over already

[D-Fusion]

+ Multicore support
+ Note entry from midi keyboard which XT1 already have (Step recording)
+ Deleted vst instrument and effects should be removed from memory
+ Save midi mapping as a preset
+ Kill all the bad bugs that has been in v2 since the beginning before adding more things

[Kyran]

And you'd whine why exactly? It'd be easy enough to ignore, and it's been requested many times over already

Because it doesn't really make sense from a design point of view:
wires route the data, the blocks modify it. Once you start modifying data in the blocks you lose some form of clarity.
Why not use a vst gain plugin or something?

[robenestobenz]

And you'd whine why exactly? It'd be easy enough to ignore, and it's been requested many times over already

Because it doesn't really make sense from a design point of view:
wires route the data, the blocks modify it. Once you start modifying data in the blocks you lose some form of clarity.
Why not use a vst gain plugin or something?

It lacks immediacy, both to set up and to work with. I see your point - a legitimate one from a structural point of view - but for those who use the modular view for improvised sound manipulation I think the benefits of the feature justify its exception from the pattern.

[gamble]

my 2 cents for FR (may have been aroused before but I repeat them here):

- preview in browser with options of auto-play, level (gain of preview) and additional information (length, bit rate, sampling rate, file type)

- midi comp, similar to the built-in audio fx so you can stack several midi fx (plus support of vst-midi) for one or more midi channels

- live mode (yeah boyyyy )

- project clipboard with audio and midi files and a snapshot function for improvising (sort of "rec all" even if you're not recording anything)

- cpu meter that is adjustable - like in buzz or other tools for accurate measurement of cpu consumption per plugin

- show grid always ... and not just when a part is selected

- don't stack inserted plugins in modular view! insert them next to each other

- auto-bypass plugins if cpu consumptions extents a specific limit for a reasonable amount of time

I guess that's it for the moment
cheers

[Diek]

And you'd whine why exactly? It'd be easy enough to ignore, and it's been requested many times over already

Because it doesn't really make sense from a design point of view:
wires route the data, the blocks modify it. Once you start modifying data in the blocks you lose some form of clarity.

If that's the point you could also control the I/O gain right clicking the block. Would be useful also level meters specially when the Live mode come, as gamble and robenestobenz said.

[umd]

- Midi functionalities from ext1.
- No memory deallocation issues / disable undo option.
- Better stability (at least better than V1)

I still (and only) use v1.

[gamble]

- dedicated tempo/meter track
- MMC (midi machine control) as option for sequencer buttons instead of midi CCs
- implementation of MTS (midi tuning standard) for midi tracks in ext2
- inconsistency: right click in sequencer or sequencer quick button offers internal fx/instruments or vst/i respectivley. to add an empty midi, audio, drum or folder track you have right-click on an existing track in the sequencer. it might be more intuitive to move the "Add New ..." function to the quick button and sequencer context menu
- regarding per-track CCs it is not really clear why there's an distinction between the usage of bars and envelopes. it should help streamlining the two behaviours into one. then, the users can decide via an option; either in the object bar (which hasn't much use for CC sub-tracks whatsoever because there are no real "options") or in the CC track itself.
-- inconsistency: a) you can mute enveleopes which you can't do with bar-based CC tracks and you have a display with the repective values --except for the pitch wheel envelope. b) changing values in the beforesaid "display" doesn't affect the envelope values but rather the global value for a midi track, eg volume. if you select a point in an envelope and change the value, the value of the selected point isn't affected. this needs to be corrected. the current value shall be displayed in CC track and shall be altered there as well. same goes for bar-based CC tracks. take a program change, where you have to adjust a value very accurately, which is right now quite tricky.
- for CC tracks (bars and envelopes) there shall be an option to switch between 0-64+65-127 and 0-127. the latter is used at the moment (and was used in ext1 too). for some parameters like pitch-bend, phase, dry/wet-mix the former parameter representation (where 64/65 is in the "middle") is more appropriate.

cheers

[fas1piano]

- 1.4 midi features

- freeing up ram when istrument is unloaded

- stability

plus

- live mode

- no controllers zeroed on scene change in brainspawn forte (neither in other hosts when ext patches are recalled in projects)

- midi channel definition for midi cc (when midi learning)

- scrolling for parameter names in midi learn so we can see long names

fab

(1.4 vst user here, too)

[gamble]

- inconsistency: manually typing values for envelope tracks in CC sub-track view. for volume, values for dB are displayed but the entry of those is made by midi CC values from 0 to 127. in envelopes, for other CC messages you have to enter values per cent (0-1). again, the user should decide which method to use. either the type sent by the sequencer (dB makes sense here for volume), or midi messages, or per cent (either 0-1 or 0-100%).
this representation of values should accompany the properties of the CC sub track (as in former post, where you decide from 0-127 oder 0-64+65-127; in case of percentages it might be (-50%)-0-(+50%) ... well it's arguable if -1 till +1 is approriate also ...)

[Morrog]

-flexible modular cables: wouldn't it be cool if you could bend audio/midi cables, so the modular view wouldn't get cluttered up with a lot of straight cables on top of each other and crossing the whole thing (take a look at applied acoustics tassman)