Is there a way to save a return channel as a preset?

[jonljacobi]

Question is in the title. TIA

[jdd]

You could group all the effects and save the effects rack.

[Da hand]

You could group all the effects and save the effects rack.

My suggestion as well. Unless you need something more?

Question is in the title. TIA

Not clear from the title what do you need exactly - do you just need to save the chain of effects on the return track? or also some track routing options as well? if so, what?

[aklisiewicz]

the question is quite clear, and I would love to know that too.
I see no way to do this at the moment. I would love to save a Return Track with several FX as a preset to reuse it in another project.

[Da hand]

the question is quite clear, and I would love to know that too.

Please don't be that person. There is no need for macho posturing here if you are seeking help from people willing to take their time for free to help you. If it so clear, then a clear solution has been provided. If you need anything more than has been suggested so far then you can offer more clarity as to why the solution doesn't meet your needs and what you need more exactly.

[jestermgee]

Mate, he is that person all the time. Question was already answered, just make a rack and save. Done.

For obvious reasons you cannot save the whole return channel since routings would be problematic in a new set if you don't have the same track setup. You can load in any effects chain easily so you can just make a folder called "Return Channels" and save suitable chains in there for recall.

[jonljacobi]

Man. Why so contentious everyone? I rarely use more than one effect on a return channel. You can drag a regular track to create a preset, so I thought it would work with return tracks and discovered it didn’t seem to. I asked to make sure I wasn’t missing something or doing something wrong.

I understand the workaround, but I’m missing the “obvious” reasons why dragging a return preset to create a new one or alter an existing one would cause issues. Please explain.

[jestermgee]

I guess it's simply a case of there really is little need to save a whole "track" for the purpose when you can just create a rack for it since there are no clips or anything to save apart from the actual chain of effects, it would just be another file extension needed and possibly could create confusion in your library when you don't know what it is for and why it wont load onto a channel etc. At least a rack can be easily loaded onto any track or return or master so it is more universal for the job.

No need to invent another hammer when the first one does the job of hitting a nail I guess.

[Da hand]

Mate, he is that person all the time.

Good to know. Thanks man

[jonljacobi]

I guess it's simply a case of there really is little need to save a whole "track" for the purpose when you can just create a rack for it since there are no clips or anything to save apart from the actual chain of effects, it would just be another file extension needed and possibly could create confusion in your library when you don't know what it is for and why it wont load onto a channel etc. At least a rack can be easily loaded onto any track or return or master so it is more universal for the job.

No need to invent another hammer when the first one does the job of hitting a nail I guess.

Not a big deal. My only argument is that it would make for a consistent methodology. I don't know about other users, but I tend to stick with whatever method I happen to be using at the time. Mouse, keyboard, double-clicking, dragging, etc. I also try to apply the methods I learn to new situations. When they don't work, I wonder why. Easy to work around, it just takes longer to learn and isn't as convenient.