Gig Performer is not Forte 
1 Like
Do you need all 88 notes of those samples? If not, why not use the Purge feature in Kontakt to remove the ones you don’t need on a per song basis?
Also, Kontakt supports Direct From Disk playback and so it doesn’t actually need to load samples in their entirety.
I am only going by my experience, not just with Forte, but with every DAW I have ever worked with…
To load a very large sample set takes a moment…or 2…or 10.
Why would one load and unload these samples during a show (at times when you need them within 1 beat of music in the middle of a song), when you can just have them already all loaded up ready to go whenever called upon? If RAM is not an issue (it’s not),
Again, I understand I am talking/acting/writing like a dinosaur here. I appreciate all of your comments…and more importantly…your patience! LOL!!!
Nobody talked about loading/unloading samples - there must be a misunderstanding.
A rackspace contains plugins.
The plugin could be a sampler like Kontakt.
The Sampler loads the samples - in case of Kontakt you can optimize the amount of samples loaded.
In a different rackspace you have different plugins or again Kontakt.
In this rackspace Kontakt loads the needed samples.
All rackspaces (when you do not use “predictive load” in the Gig Performer options) are loaded when you load the gig file.
Now you can seemless switch between rackspaces and no samples are loaded or unloaded.
Gig Performer is not every DAW —
Sigh
OK — let me try once more
Stop focusing on trying to optimize everything and focus on what you need for each song.
For example, if you need a piano, some strings (over two octaves, say) and a moog in one song, then go ahead and create that and stop thinking about crap like “I don’t want to have to load and unload samples” all the time.
Then move to the next song and decide what you need there and then go ahead and create that in a new rackspace (say)
Then keep going.
Also… Have you seen the Rosanna video?
When doing a song with quick changes, this is a great approach for working within a single rackspace using variations. When doing something completely different, like a new song or very different part of the same song, build a new local rackspace. And stuff that is always (or nearly always) used, like a vocal chain, mixer, favorite piano, master volume, or limiter, can go in the global rackspace.
In my experience with new tools and programming languages, it requires three attempts. In attempt one, we try it out without much organization. In attempt two, we try to architect the system, but make mistakes. By attempt three, we have enough context to make a good foundation. Now, we can build and refine without needing to start from scratch. Even though Gig Performer aligns well with how I think, I still needed three attempts to really get going. Once the approach is worked out, the fun begins. 
2 Likes
It’s starting to sink in, gang!
I may be old (53), but I ain’t dead.
I will post a status update soon!
Many, many thanks…
Joey
3 Likes
In my opinion, “old” equals = “no will to learn or move forward!” 
You’d be surprised to see our brilliant community members that are 50+ and with VERY, very sharp minds
So, welcome to the community and see you around 
5 Likes
Hey Joey. I’m 76.
Please, persevere with GP. I was like you three years ago. When Mike announced that he was ending support for Forte, I was devastated. I read the announcement on the Forte forum and went through the various postings. Someone mentioned what host to switch to, and Gig Performer was suggested. I’d never heard of it. I went straight to the GP site and downloaded the demo (V2 at that time). When I opened the GP wiring window for the first time, I was totally shell shocked! I did not know what to do! Then I found a YT video (can’t remember what it was called sorry), and in an instant, while I was watching and before the video had ended, I “got it.” GP is amazing, intuitive and so easy to use. When you “get it” too, you may even think as I did - gosh Forte was so hard to use! Truely!!
For your info, here is how I use GP. I am a solo performer using guitar software and a guitar hero controller, along with drums and auto bass vst’s. I sing using a harmonizer. I perform at rest homes, Farmer’s Markets and (now and then), private home functions. All my music is based around one hour sets comprising 19 songs in a set. I use a Surface Pro 6 with 16gig ram and an i7 processor. When editing at home, I turn predictive on set to three. When gigging, I turn predictive off. The differences for me are as follows (based on 19 songs per set):
- Predictive on = set loads in 20 seconds, but song switching takes three to six seconds (ideal for
editing at home when you have plenty of time) - Predictive off = Set loads in 4 minutes or so, but song switching is instant i.e. a split second
(perfect for live performance when people want the next song RIGHT NOW!)
Keep with it mate. This forum is fantastic. All the people posting here are amazing with great understanding of GP. I am a real dodo (really), but the patience and understanding that folk here have with newbies is superlative. Be encouraged and keep it up. All the best!
6 Likes
Thank you @bigalminal …very kind of you to write out such a passionate and courteous response!
I did “get it”…earlier than I expected actually. I just didn’t want to accept that certain things that previously I looked at as “wrong” would now be considered “right.”
I think that you will likely agree that there are 1 or 2 things that Forte handled better, but overall, GP is a superior design. I look forward to further learning and experimenting before actually going “live” with it. Probably 2 or 3 months. It will take that long to re-program everything (at least) and no doubt I will be revising as I learn more.
Best wishes to you…and keep on rockin’!
Joey
Not exactly, you were more like 73 years old 
Never was particularly good at Maths.
1 Like
Not really. I found it particularly difficult in Forte to get midi out working to drive strings and organs etc. The only thing I miss with Forte was the performance page where I used pictures that filled the screen making it more attractive to look at.
It will take you a while to recreate your GP files. I was months I seem to remember. Now I’m well on the way to 500 songs. Being retired, I spend most mornings creating new songs or fixing up ones that I mucked up. Fils in my days very pleasantly. I reserve the afternoons for gigging.
1 Like
For example?
-
A “Scene view” with really large fonts for the present and the next upcomming song. With options what items of the view to show, and what not. The setlist view of GP is cluttered with many small details.
-
“Hardware profiles” with Midi AND audio bindings.
Anything else is much better in GP than in Forte. Let alone the much smaller latency and jitter of GP compared to Forte at same buffer settings of the audio driver:
I’ve been a hardcore Forte fan, user, active forum member and beta tester for over 16 years. This eventually brought me in contact with Mark Kelly from Marillion, a former Forte user, too, finally meeting him with a backstage pass for some expert talk on Forte during his sound check, before a Marillion gig in Munich, Germany back in 2009:
But this all is history. Forte is dead. It still works on my backup laptop. But the future is GP, as for many former Forte users here in the forum.
It took me a while and a steep learning curve, to adopt to the GP work flow. Some trial and error testing and messing around with features, some RTFM, and much help from the forum.
Because my GP is midi driven from an iPad Pro using a BT pedal, I have no use for the set list view at all. All my songs remain in the panel view with the song title (font set at 100) expanded to fill across the screen. To improve the look marginally, I have coloured the backgrounds whilst leaving the font white. It is quite boring and I really do miss Forte’s performance page.
As an example, for a song called “Highwayman” in Forte, I found a jpg showing a 17th century highway man galloping along a country road brandishing a pistol. I imported that picture and it filled the entire screen. And because the screen faced the audience, they had something cool to look at.
However, I am probably just one of very few people using GP like this. I am guessing that most users require hands on control of widgets synched to their controller keyboards, whereas, I stand out the front with my guitar hero controller and work every thing from my pedal board there.
If your background is boring, simply hide it, such that the crowd can look at you. You are cool too
1 Like
I prefer the MIDI mapping, which may be less flexible than GP, but (to me) flows easier.
For instance, with Forte, you have an instrument that you want to map to multiple keyboards in multiple regions. Everything is in one window pane…you select the controller(s), you select the range(s) of notes, MIDI channel, everything is in 1 spot.
In GP, you have to create a separate MIDI input for each controller and range you want. At least that’s how I understand it. It’s backwards from Forte. In Forte, it’s the instrument first. In GP, it’s the controller. The cumbersome part of that (for me) is that if I need 3 controller points for an instrument I need to create 3 instances to start. In Forte, you start with one instance and branch out.
Most likely because you’re used to it.
What do you do in Forte when, after you’ve set those up, you now want to map two other instruments (by “instrument”, I assume you mean software synth) to those exact same ranges? And what do you do, if you want to be able to change those ranges on the fly, as you switch to different parts of your song, for example?
2 Likes
I have never had the need to do that…nor could I see it in the future.
With my band, we do NOTHING on the fly, LOL!
5 Likes