FEATURE REQUEST list - what do you want from energyXT2 ?

[jonnyG]

-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)

Ahh, cables...Mebbe I'm too used to Bidule's cable handling properties but I'd really like to be able to select cables by lassoing 'em with the mouse so i can move them individually or as a bunch more quickly (unless I'm missing a hotkey somewhere - long time since I rtfm'd...). Bendy cables would be cool also.

I'm really missing half-decent level metering / control in the modular view. I know there's been a workaround suggested for this (volume modifiers in the wires), but I think that the mixer should be available in the modular view. Perhaps showing all the wires to it would be unnecessary (it would get pretty messy with big projects) but I'd like a mixer component that could be clicked to reveal a compact representation for monitoring / rough tweaking of levels. Perhaps individual channels could be quickly expanded to access the entire channel strip and of course, the entire mixer could be docked to a new page and be available there in expanded form. Nothing would need to change in the sequencer view - it would be the same mixer channels, only the view would change.
I imagine there are others like me who still use just the modular view occasionally (and without a sequencer) for chaining stuff for live performance or jamming / soundscape creation. A "create new mixer" option would be cool. Synths and whatnot could then be wired to this. But if a sequencer was subsequently added I'm not sure how the mixers would be amalgamated, but it's only an idea...

I guess I'm still missing a lot of XT 1.4's features.

[acid1]

AU/VST/UB version for Mac OSX


... so I can actually use renoise...

[gamble]

I'm really missing half-decent level metering / control in the modular view. I know there's been a workaround suggested for this (volume modifiers in the wires), but I think that the mixer should be available in the modular view. Perhaps showing all the wires to it would be unnecessary (it would get pretty messy with big projects) but I'd like a mixer component that could be clicked to reveal a compact representation for monitoring / rough tweaking of levels. Perhaps individual channels could be quickly expanded to access the entire channel strip and of course, the entire mixer could be docked to a new page and be available there in expanded form. Nothing would need to change in the sequencer view - it would be the same mixer channels, only the view would change.

you can undock the mixer so you can have mixer channels and modular view on the same page. I guess you're hinting to a visual mixer representation like podium where you have hierarchies that can be (un-)folded.
otherwise it's hard for me to imagine how your proposal might look in the actual application... are you suggesting something like the mixer strips in the sequencer for the modular view?
I think that this might become redundant if you habe level control via audio cables in modular view. as brought up earlier, with volume control like in buzz it should be possible to equip the "triangles" with the current volume level (percentage or dB)

[KenRally]

MIDI file (type 0) export, specifically MIDI file type 0 (the very simple type 0, so I can support creating Midi drum patterns, or bass lines, and then
export them to a DigiTech GNX4 Guitar workstation),
so I guess these things below.
But if I cannot select type 0 midi file, it would be pointless for my needs.

DRM1 - MIDI out from the drum track
DRM2 - .rex support for the drumtrack - drag a rex file to the drum track and it maps each slice to a seperate pad (and preferably dumps the order as MIDI into the sequencer like the slicers in FLstudio)

MID1 - MIDI export

KenRally

[gamble]

me once again ....

- in modular view: double-click / context menu->setup on "Audio In/Out" and "Midi In/Out" shall open the setup page with preferences for Audio or Midi respectivley

- it should be possible to change or delete (plus warning of deleting samples) the audio folder for a project. in this respect, one might be able to change project location / project file name. doing this, the ext2 should ask for moving/renaming the audio folder. a "change" button right next to the location might be used. also, in deeper folder structures or with longer file names the complete path isn't displayed in Setup->Project. a longer text field or scroll bar might help.

- startup settings in global setup don't seem to affect the welcome screen

- localised key-bindings in the shortcut menu would be cool. well, it's rather down the list, I guess, but it might help newbies to load short files for their keyboard

[gamble]

- localised key-bindings in the shortcut menu would be cool. well, it's rather down the list, I guess, but it might help newbies to load short files for their keyboard

FYI: I've created a raw XSD how this issue might resolved

Code: Select all

<?xml version="1.0" encoding="utf-8" ?>
<xs:schema elementFormDefault="qualified" xmlns:xs="http://www.w3.org/2001/XMLSchema">
  <xs:element name="actions">
    <xs:complexType>
      <xs:sequence>
        <xs:element name="common">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="zoom_in" type="key_binding" />
              <xs:element name="zoom_out" type="key_binding" />
              <xs:element name="left_locator" type="key_binding" />
              <xs:element name="right_locator" type="key_binding" />
              <xs:element name="play_selection" type="key_binding" />
              <xs:element name="quantize" type="key_binding" />
              <xs:element name="next_beat" type="key_binding" />
              <xs:element name="prior_beat" type="key_binding" />
              <xs:element name="mixer" type="key_binding" />
              <xs:element name="browser" type="key_binding" />
              <xs:element name="setup" type="key_binding" />
              <xs:element name="find" type="key_binding" />
              <xs:element name="edit" type="key_binding" />
              <xs:element name="edit_in-place" type="key_binding" />
              <xs:element name="rename" type="key_binding" />
              <xs:element name="export_project" type="key_binding" />
              <xs:element name="prior_page" type="key_binding" />
              <xs:element name="next_page" type="key_binding" />
              <xs:element name="prior_program" type="key_binding" />
              <xs:element name="next_program" type="key_binding" />
              <xs:element name="metronome" type="key_binding" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="file">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="new" type="key_binding" />
              <xs:element name="open" type="key_binding" />
              <xs:element name="save" type="key_binding" />
              <xs:element name="save_as" type="key_binding" />
              <xs:element name="open_last" type="key_binding" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="edit">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="undo" type="key_binding" />
              <xs:element name="redo" type="key_binding" />
              <xs:element name="repeat" type="key_binding" />
              <xs:element name="delete" type="key_binding" />
              <xs:element name="select_all" type="key_binding" />
              <xs:element name="cut" type="key_binding" />
              <xs:element name="copy" type="key_binding" />
              <xs:element name="paste" type="key_binding" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="transporter">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="play" type="key_binding" />
              <xs:element name="record" type="key_binding" />
              <xs:element name="stop" type="key_binding" />
              <xs:element name="rewind_to_start" type="key_binding" />
              <xs:element name="loop" type="key_binding" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
        <xs:element name="sequencer">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="mute" type="key_binding" />
              <xs:element name="solo" type="key_binding" />
              <xs:element name="mute_part" type="key_binding" />
              <xs:element name="show_track_comp" type="key_binding" />
              <xs:element name="split_at_cursor" type="key_binding" />
              <xs:element name="insert_bars" type="key_binding" />
              <xs:element name="remove_bars" type="key_binding" />
              <xs:element name="channel_strip" type="key_binding" />
              <xs:element name="add_track" type="key_binding" />
              <xs:element name="zoom_selection" type="key_binding" />
              <xs:element name="show_track-params" type="key_binding" />
              <xs:element name="snap" type="key_binding" />
              <xs:element name="autoscroll" type="key_binding" />
              <xs:element name="scroll_octave_up" type="key_binding" />
              <xs:element name="scroll_octave_down" type="key_binding" />
              <xs:element name="freeze" type="key_binding" />
              <xs:element name="glue" type="key_binding" />
              <xs:element name="unghost" type="key_binding" />
              <xs:element name="object_bar" type="key_binding" />
              <xs:element name="bounce_to_audio_track" type="key_binding" />
              <xs:element name="crossfade" type="key_binding" />
            </xs:sequence>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:complexType>
  </xs:element>
  <xs:complexType name="key_binding">
    <xs:sequence>
      <xs:element minOccurs="1" maxOccurs="1" name="key" type="xs:string" />
      <xs:element minOccurs="0" maxOccurs="1" name="modifier">
        <xs:complexType>
          <xs:all>
            <xs:element name="shift" type="xs:boolean" />
            <xs:element name="ctrl" type="xs:boolean" />
            <xs:element name="alt" type="xs:boolean" />
          </xs:all>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:schema>

things to do:
- adding author and keyboard (language representation: RFC1766/3066), etc information based on dublin core/RDF for metadata
- parsing in xt2 for saving/loading key binding files[/code]

[original flipper]

HI

Don't know if it has been mentioned already: loading XTV1 songs into XTV2 would be unbelievably helpful!

Flipper.

[Brittlestem]

HI

Don't know if it has been mentioned already: loading XTV1 songs into XTV2 would be unbelievably helpful!

Flipper.

Jorgen originally said this would be possible. Doubt it's ever going to happen, though.

[weltgeist]

Just to ensure that this feature request won't be forgotten, I post the link to the sticky FR thread:

7 request for a feature that allows to use external audio editors in EXT2:
http://www.kvraudio.com/forum/viewtopic.php?p=3158205

Would be great, if this would be added to the list

[xybre]

MID6 - energyXT1 style programmable arp ++

[insertpizhere]

- in modular view: double-click / context menu->setup on "Audio In/Out" and "Midi In/Out" shall open the setup page with preferences for Audio or Midi respectivley

good idea.

[gamble]

that's my middle name

[Diek]

Just bought a MIDI controller (BCR 2000) and realized of the need of feedback from XT2 to controller. I've read there are probs with the MIDI out so first is first. Anyway this FR would be more generally "Controller support"

Cheers

Diek

[gamble]

yep. same for me for years - so to say - because I can't use my beloved doepfer pocket dial in "incremental" mode

[kwerty]

MID1 - MIDI export (3 requests)

Can I add my support for this? I've just paid for the full version XT, then much to my disapointment found that I can't export compositions to the MIDI format. Had I been more aware I may have invested in MU.LAB...