When I add amplitube3 as a plug-in to a Realband (DAW) file, it works perfectly.
But when I come back to the file (after exiting RB), my Amplitude plug-in does not load and I have to choose it again.
Can anybody help? Thanks

Which version of RealBand are you using? Are you running RealBand as administrator (which is different than logging into your computer with administrative rights)?

When you look at your list of available plugins, is Amplitube still in the list or do you have to go find it again?

What format are you saving the file to? If it is anything other than the .SEQ format, things like VST/VSTi settings won't save.

Thanks John.
I'm using Realband 2016, running as administrator.
Yes, Amplitube 3 is always on the list of available plug-ins and, yes, i am saving it as an SEQ file.
When i load Kontakt 5 or Guitar Rig, I have no problems; they are there as set when I reopen the file.
Mike

Unfortunately, I don't have 2016 on my computer anymore. It's odd that the Native Instrument plugins "stick", but the IK-Multimedia ones don't. The only other things I can think of to try is to 1) save the file to a different name, or 2) make sure you are running the latest patch for RealBand 2016 (which is Build 10).

If none of those, you might want to contact PGMusic support either by phone or live chat and see if they can shed some light on the problem.

If the plugin is availble in the list and loads with the song, but wrong settings, you can try using the Save Preset (or Save Group if you have multiple plugins on that track).
Sometimes this helps RB remember settings for some plugins that do not play nice.

At the very least it saves time tinkering with the plugin again and again; if it doesn't automatically load you can quickly retrieve the settings using Load Preset (or Group).

Good point from RHarv. Definitely worth trying (takes all of two seconds to do).

Hi Mkg50,

When I add Amplitube to a track in RealBand 2016 and save, it's definitely still there the next time I open the song file.

Are you updated to build 10?

Also, has this happened with more than one SEQ file?

Thanks
Kent
PG Music

Following everyone's helpful suggestions I have figured out:
1. When I load my midi track using Coyote WT, then load Amplitude 3 and save the file, Amplitude will NOT be loaded when I reopen the SEQ file
2. When I load my midi track using Forte DXi, then load Amplitude 3 and save the file, Amplitude IS loaded when I reopen the SEQ file
3. If convert my Coyote WT midi track to audio, then load Amplitude 3 and then save, Amplitude IS loaded with the audio track when I reopen the SEQ file
I know I could simply convert the midi track to audio and all would be fine but I like to keep the tracks editable for as long as possible before attempting mixing/mastering.
I could also use Forte DXi instead of Coyote WT but the jazz guitar with Coyote and Amplitude's Ensemble Chorus preset is the sound I like for this track.
I'm curious if anyone elese has had this problem with Coyote, which I have as my default synth.
Should I use Forte DXi as my default synth instead?
Thanks again everyone for you prompt help.
Mike
PS I am using Build 10 and it does happen with other SEQ files

So, given what you have found out, have you tried using Coyote Forte as your default synth, but then over-ride it on that one track with Coyote WT and then see if Amplitube sticks when you re-open it?

Remember, Coyote WT is just a wrapper for the default MIDI sounds you get with all copies of Windows. While you may like certain sounds for specific situations, in general, they're not that good and the WT just gives you something to work with lacking anything else. But that's just my opinion. Yours may vary.

Hi,

When you add Amplitube to a MIDI track that's using the Coyote WT, are you assigning that track to its own MIDI port? If you don't, then you likely assigning Amplitube to the Default Synth channel, and it'll be applied to all MIDI tracks.

I'd still expect it to save, but try assigning it to a new port and see if that helps.

When you assign the Forte to a MIDI track when using the Coyote WT as the default, that track is automatically going to its own port, which would be why there's no problem.

Thanks
Kent
PG Music

No, I didn't assign the Coyote track to its own midi port. And, yes, Amplitude would appear on all Coyote tracks (so I only used Coyote on that one track).
What's the best way to assign a given track to its own midi port? Should it be a number from 1-16 or from 17-32?
Thanks everyone for your help. I haven't used this forum before and have spent countless hours over the last couple of years trying to figure stuff out. I have learnt so much just this week.

Hi MKG50,

Right-click on the MIDI track, go to Port, and select one of the "DXi/VSTi Synth" options. The 16th one is the Default Synth slot, so use any of the others.

Cheers
Kent
PG Music