Forte and EHCo
We welcome your ideas on how to make Forte a more valuable tool. Please enter wish-list ideas or vote on existing ones here.
-
Multi-Output support for Instruments
Instrument should be able to route to multiple insert chains with independent mixes
191 votes -
187 votes
-
Customize Scene View
Waiting since years for 2.0 and there is still a fixed scene view: The scene view has to be custumizable (bigger fonts, put buttons somewhere on screen etc) - Necessairy for users with small touchscreens on stage.
182 votes -
Left - Right Panning On Each Instrument
There should be a left right panning button on each instrument. You have to load a separate panning plugin inside the instrument chain to get panning accomplished now or hope the plugin you loaded has it already. "But not always".
108 votes -
97 votes
-
OS-X Version
If there would be a native Mac-OSX Version, there will be no reason any more to buy a pc. Think about it: Musicans love Macbooks - there are not thouthands of compatibility issues etc. Just create an OS-X Forte and you will be my hero!
95 votes -
Save Instrument Console Layouts With Scenes
It would be great if the instrument consoles (which ones are open or not, their placement, etc) could be saved with each scene. There was very old post about this and the response was that it was a good idea and that implementing it would be very easy to do. I'm a little disappointed it has not made it yet into 2.0
The #1 request is scene customizaion and I think this goes along with that.... but to whatever degree you can customize the scene display, it should be saved per scene. This would be awesome.
76 votes -
69 votes
-
Global Transpose
I would like to see a global transpose feature. This would simplify setups with multiple keyboards and the need to set each keyborads transpose settings. One of my keyboards is in fact limited in that although it allows transpose it doesn't transmit the tranposed notes thru MIDI.
Forte is great - keep up the good work!
64 votes -
Double PC System
Possibility to sync 2 PCs - one as master the other as slave (muted) and controlling each other (f.e. via Ethernet). In case of a crash the PC still running can restart the other one. Additionally operations to copy any changes on the rack to the passive system. Result: expensive but very save live operation.
44 votes -
Supporting Novation Automap
I suggests that Forte 2.0 recognizes and works with the "automap" plugins created by Novation Automap,
In few words Novation Automap creates a copy of a selected VST instrument or effect adding after its name the suffix "automap": e.g. "B4II (automap).vst"
If you load the vst so created in your host the Novation device (e.g. Nocturn) automatically creates and loads the relevant template so you can manage all the vst parameters from the Novation hardware.
The problem is that Forte 2 seems not to recognize the "twin" vst created by AutoMap and loads only the original version.
Many other hosts… more43 votes -
40 votes
-
Click and learn/assigned performance on screen control buttons
I would like the ability to automatically map/learn a physical control to an onscreen control which then is assigned to any parameter I choose. I would also like to have those mapped controls display on the performance page in a grouped or individual fashion in any location. This would mean that the control does all of the midi routing and assigning based on the learned function and final button assignment to the internal or external instrument or plug-in.
39 votes -
audio (+video) player
Integrated audio multi-out player would be killer function! Even better video player... Can you imagine just one person on stage changing on one click from midi keyboard a background playback with all the settings and computer sounds at one computer?
35 votes -
30 votes
-
Manually assign CPU to a module on multicore CPUs
Now we are able to assign a seperate CPU core for known CPU hogs like Sytrus or Ominsphere, whereas all other modules and plug-ins are assignedto a second CPU core.
27 votes -
Allow Midi Program Changes to change to songs not only to scenes
In a typical live situation songs are skipped or inserted on the fly (e.g. in a coverband to adapt to the audience). To achieve this, it would be nice to jump to a specific song in the setlist, by simply sending the Midi ProgramChange for this song. It can be discussed if the current song order in the setlist should have influence on the ProgramChange-Number or if the numbers are really "user-given". However the number of scenes used in the songs should NOT have any influence on the program-number. Right now for jumping to a specific song you exactly need… more
27 votes -
Midi volume meter
This would be a plugin which is also optionally integrated into the Scene View screen. The input data would be xx controller on xx midi channel. The readout would be the value of that particular controller as defined by (for example) the position of a volume pedal connected to a midi keyboard. It would be displayed as a number as well as on a digital meter-style display. This would enable the musician to know what volume the pedal is sending before a cold entrance. Very useful for live performance.
24 votes -
Close scene view button in scene view mode
For us using touchscreens, a close button in the full screen scene view would totally avoid the need for a mouse/keyboard. Simulating a right-click on a touchscreen isn't easy to achieve.
21 votes -
Remapping of channel pressure/aftertouch to MIDI CC
Lots of instruments don't implement these, but do allow you to automate parameters with CCs. What's so nice about chan pressure / AT is that you can fire off the controller without taking your hands off the keys.
21 votes