Sooooo....
Over the last year we have transitioned all of our Turbosound rigs over to PLM amps and mostly it has gone very well. Very powerful, sound great, factory presets, Lake control, etc etc.
But I can't seem to lick one part. Any PLM pros on here?
We have three flavors of mains and two types of subwoofers, which we occasionally use in various combinations. Add in the convenience of using a PLM, and the Lake, for a front fill or a stray wedge, and we are talking about 50 or 60 presets.
Using a tablet, I can make the amp be any of our combinations of speaker boxes. But I obviously want to save the configurations, including the amplifier routing, to the amp to be able to make front panel selection for use without a tablet.
I know how to save a FRAME PRESET to the amp, which is exactly what I need to do. I also know how to use the PRESET MANAGER to copy the saved presets from one amplifier to the other 16 amplifiers.
Here is the problem I am having. When I open a FRAME PRESET on an amplifier, the FRAME NAME of the amplifier I am loading it on changes to the FRAME NAME of the amplifier that I created it on.
It is crucial that the FRAME NAMES remain static so I know which physical amplifier I am working with on the tablet. All of our FRAME NAMES indicate the exact amplifier in the exact amp rack so you also know which amp you are working with.
Obviously I am missing something. They can't expect you to write new presets for every single amplifier only on the amplifier that you will be saving it to. That's what the PRESET MANAGER is for, right? I know on the PRESET MANAGER you can rename the frame, but that only lasts until you reload another preset. It doesn't modify it in all the presets.
Or maybe the FRAME NAME is not supposed to be the unique identifier for each amp? If not, what IS, and how do I see it when I am looking at a normal layout, and adjusting things, etc?
Also, is there a way to write a FRAME PRESET using a virtual amplifier module, so it doesn't take the FRAME NAME of an amplifier? This would be helpful for other reasons. I looked around and it did not seem to be the case.
Thanks for your help!
Jason
Over the last year we have transitioned all of our Turbosound rigs over to PLM amps and mostly it has gone very well. Very powerful, sound great, factory presets, Lake control, etc etc.
But I can't seem to lick one part. Any PLM pros on here?
We have three flavors of mains and two types of subwoofers, which we occasionally use in various combinations. Add in the convenience of using a PLM, and the Lake, for a front fill or a stray wedge, and we are talking about 50 or 60 presets.
Using a tablet, I can make the amp be any of our combinations of speaker boxes. But I obviously want to save the configurations, including the amplifier routing, to the amp to be able to make front panel selection for use without a tablet.
I know how to save a FRAME PRESET to the amp, which is exactly what I need to do. I also know how to use the PRESET MANAGER to copy the saved presets from one amplifier to the other 16 amplifiers.
Here is the problem I am having. When I open a FRAME PRESET on an amplifier, the FRAME NAME of the amplifier I am loading it on changes to the FRAME NAME of the amplifier that I created it on.
It is crucial that the FRAME NAMES remain static so I know which physical amplifier I am working with on the tablet. All of our FRAME NAMES indicate the exact amplifier in the exact amp rack so you also know which amp you are working with.
Obviously I am missing something. They can't expect you to write new presets for every single amplifier only on the amplifier that you will be saving it to. That's what the PRESET MANAGER is for, right? I know on the PRESET MANAGER you can rename the frame, but that only lasts until you reload another preset. It doesn't modify it in all the presets.
Or maybe the FRAME NAME is not supposed to be the unique identifier for each amp? If not, what IS, and how do I see it when I am looking at a normal layout, and adjusting things, etc?
Also, is there a way to write a FRAME PRESET using a virtual amplifier module, so it doesn't take the FRAME NAME of an amplifier? This would be helpful for other reasons. I looked around and it did not seem to be the case.
Thanks for your help!
Jason