Kareoke Style Patch in Mainstage

Hello all,
Wondering if you brainy people could help me brainstorm.
I'm wondering if there's a way to get lyrics to scroll along with the playback of an audio file when using mainstage. I'm trying to get a little kareoke game going and was hoping there would be someway to trigger text to change dynamically with an audio file being triggered by an EXS24.
Here's the catch, I can't change patches while the song plays back because I want to control fx's on a single patches tracks.
Any Ideas??????......

Here's one idea;
I used iMovie to create a Quicktime movie with a black background and scrolling white words. I made a movie clip that's roughly the same length as the song, so it kinda naturally follows as the song progresses. You may have to tweak it a bit.
I'm using it for several long (Don McLean) songs and other wordy ones. Works great. It's my teleprompter...of sorts.
You could make the movie and then assign a button in Mainstage to an Applescript that is designated to "play the next QT movie in folder X" or something like that. With two video screens, you could keep the QT movie in one, and MS in the other.
It might work. Stranger things have happened.
Good luck,
Brian

Similar Messages

Transition old-style patching for C++ and PL/SQL compilation

Please help, have u experienced the patch installation problem?
# smpatch add -i 117837-08
add patch 117837-08
Transition old-style patching
ERROR: This patch requires patch 117846-02
which has not been applied to the system
# smpatch add -i 117846-19
add patch 117837-08
Transition old-style patching
ERROR: This patch requires patch 118682-01
which has not been applied to the system
# smpatch add -i 118682-01
add patch 118682-01
Transition old-style patching
Could anyone tell me how to install it?
Thanks a lot!
Vivian

No product name.
No version number.
Only a very sketchy description of what you are doing or why.
No help is possible.
If you need help you need to provide sufficient information for us to be able to determine what you are trying to do and what you are asking for help in doing. All is unclear.

Is there a way to import Mainstage 2 patches into Mainstage 3?

Currently trying to upgrade from Mainstage 2 to Mainstage 3 on my new MBA. Haven't downloaded Omnisphere yet and have a gig coming up. Was wondering if it was possible to take built-in patches from Mainstage 2 and move them to Mainstage 3. (Most specifically Tranquil Horizon, an ambient pad)
Thanks for the help.

Drag and drop open via the gear menu, open existing concerts...

How do I set up different hardware controls for different patches in mainstage?

I'm using Mainstage 3.0.4 and a Novation Impulse.
I created a concert, with the drawbar organ as my first and most important patch. I assigned the hardware controls on the Novation exactly how I wanted them, with the sliders controlling the drawbars, and the rotary controls changing the distortion, reverb, etc. It was perfect. I was happy.
Then I added a new instrument (a new patch, not a new channel or anything like that), a Wurlitzer. Once again I assigned my hardware controllers as I wanted them, and was happy with that.
When I saved the concert, and went back to my organ patch, my settings didn't stay the same, but they still work for the Wurli.
My question is this - do I have to have a new concert for each instrument patch I want to use, if I need to assign different controllers for each patch? This would be stupid! If not, what I am doing wrong, that I can only set up one set of hardware controls per concert, instead of per patch?
Thank you in advance for the help!!!

Hi
matthewabennett wrote:
CCTM, thank you! I have a small idea what you mean, but I still can't implement it :-)
You have some fundamental choices:
A) If you want to see Drawbar Controls for organ Patches, and then have other types ( knobs/sliders etc) for other Patches, you could simply make all the screen controls you need, then assign and map them as required.
B) you could simply use drawbar screen controls only and remap them to other parameters for non-organ patches
C) You could use Smart Controls ( which will update their appearance in a 'smart' way
D) You could make your own Drawbar type controls using standard faders
The basic process in a 2 part thing:
Assign incoming MIDI messages from your controller to Screen Controls in Layout mode. This is global for concert. Per patch ( or Set or globally for the Concert) you then map the Screen Controls to parameters for each patch as needed.
Smart Control MIDI assignment is done in the Assignments and Mappings pane
CCT

Using GM and/or QT Synth patches in Mainstage?

Hi.
I'm programming keyboards for the pit, and need a music box sound. The one in the GM specs would be fine, but I can't seem to access it from Mainstage.
Anyone know how to do this?
Thanks.
-Doxster

Well, I found a very clumsy way to do it and someone may know an easier way but try this.
In edit mode, create your Software Instrument channel strip and associate it with the DLSMusicDevice instrument (It's under AU Instruments - Apple).
In layout mode (if you haven't already done this), create a knob or slider and associate it with a knob on your keyboard.
In edit mode, switch to the patch containing the DLSMusicDevice channel (if you're not already there), click on the knob (or slider). In the Screen Control Inspector, select the channel strip name in the first column, select MIDI Controller in the second column, and then select Program Change in the third column.
Now, as you turn the knob, the appropriate program change number will be sent to the DLSMusicDevice. I think the musicbox is at 10 or 11.
Having said all that, if you have Logic Studio/MainStage, then you have the Garage Band sounds. You'd be far better served by just using the Musicbox sound from Garage Band, which you'll find under Mallets. You'll find you have a lot more control over the actual sound, (i.e, you can change the decay to suit)

Auto show/hide Plug-in when switching between patches in Mainstage 2

Hi, I was wondering if there is a way to have Mainstage 2 automatically reveal a plug-in when switching between patches. For instance, when switching to a Clav patch, have it reveal the EVD6 plug-in. Then, if you switch to a Rhodes patch, it automatically closes the EVD6 and reveals the EVP88.

As far as I know, no. I haven't found a way to do this. It would be useful in certain setups.

EXS losing saved patches in Mainstage

This is weird. First off, I love Mainstage. It's working VERY well at church as our live keyboard rig. However, I'm having an odd issue. We mostly use EXS24's and every so often when we load up the concert and pick a patch from the list, the sound is the default sine wave instead of what we saved it as in the EXS. So we have to load up the sound in the EXS and save it all over again in the concert. Any ideas? Anyone experiencing this? It's like the EXS24 is losing it's memory. Weird.

I can confirm that this happens to me too... usually it happens after I do something such as pasting a patch into the current set or concert.
Seems to be a memory problem...
it's reproducable here. just open two new concerts from existing templates, then copy/paste, or drag drop a bunch of patches at one.
No error message, but going back to one of the existing patches plays back the sinewave...
if it's an existing patch, going back to the inspector and reselecting the patch brings it "back".
this is a killer problem for patch management, mix and matching between sets/concerts for me...
at least we're not alone in having this problem...

HT3989 The patch is from an older version of MainStage. Open the patch in MainStage 3 or later, export it again, then open it in Logic Pro.

this problem loading from the library.
cannot find help anywhere on the net

I'd like to see a comparison with say CS2. I tend think that your current software might run marginally faster. I warn you against going to CS6, as it seems to have higher computing overhead thus far, and there has been some issue with DV editors connecting to dv devices. I don't see where it could help your dv workflow very much.
But Dude.....,Pentium D, 3.60GHz? You could build a new PC funded solely by the electricity that you would save over 18 months. Combine that with savings from not upgrading to CS6 and join us all here in modern computing land. Editing HD natively (It will happen for you) without rendering previews, exporting to DVD and mp4 in minutes instead of hours. It is so worth it. Is this your work's or your church's system where its just not your choice to upgrade? Here at work we were finally able to upgrade to CS5 capable systems 2 years ago, and HD material had already become a big workflow issue with us, even though we were primarily working with DV. I also had to upgrade my home system to take on any freelance editing. You can rock with any modern i5 or i7 quad core, 12gb memory, and a gtx card. You could also get and AMD 6 or 8 core and maybe save a little $ there.
I just wouldn't ever consider upgrading the software before that rig.

MainStage playback plugin tempo issue

I am having problems with importing audio into a playback plugin.
I understand that the audio file needs to be exported from Logic X as a CAF file. I have done this, and then imported it into the playback plugin in Mainstage3.
I have ensured that the tempo of the song in MainStage is at the appropriate level i.e. in this case a patch, which has been set to the tempo of the original song in logic.
I have also synced the loop in the playback plugin, and set snap to beat.
The problem is, it doesn't play at the same speed as the metronome i.e. as the tempo of the patch in MainStage. The result is that it plays too fast, and pitch shifts with adjustment. I have used all the flexitime options, but ultimately this is trying to put a small plaster on a large open wound.
As a test of sanity, I have also exported as AIFF and wav. No joy there either. I have even opened the resultant AIFF file in iTunes, and it DOES play at the correct tempo.
Does anyone know a solution to this problem, or if not, of another playback plugin for MainStage that actually might work properly!!!??
Thanks

Although I still have no idea what causes this problem I do have a work around for anyone else who happens to experience this same problem.
As I am not the creator of the loops, I cannot recreate them, so my only option is to "convert" them from *.wav to *.wav using FormatFactory on my work computer (MS Windows).
For some reason, the files end up a few bytes smaller, but they play to the end with no issues.
I would love to know what changes are being made during the conversion, but at the moment, I don't have the time to "debug" the situation.
Cheers

How to use at the same time the audio sounds of a keyboard & the midi sounds with mainstage

Hello! hope you can shed some light on my problem! I want to be able to use at the same time the real sounds of korg sv-1(stage keyboard, but it could be any stage piano with USB midi) and use other sounds from mainstage. Of course i switch between patches and sets with a footpedal so i can be quick with my changes of sounds so I try to keep my hands on the keys.
My question is: Is there a way that one moment for example i have a silend patch (from mainstage) and the real sound i want passing through audio and the next moment silence from korg and the next patch a sound from mainstage? Or even combine them. I mean in general how am I able to integrate the sounds I prepared and organised in patches in mainstage with the beautiful piano & rhode sounds of my sv-1?
thanx in advance for your response!

Yes. To have a silent Mainstage patch, simply do not create any instrument channel strips. To have the SV-1 silent on a patch you should be able to set and save the volume for that patch to 0. As an alternative you could turn local off on the SV-1( this function will reset to local on after the SV-1 has been turned off). With local off you can determine with each Mainstage patch whether or not you want to transmit MIDI to the external instrument(SV-1) channel strip. If you have local on, be careful not to create a MIDI feedback/loop with the SV-1. This is a lot of info to digest at once, so take it slowly, step by step. Snapshots below are somewhat in order.
Click on the cog wheel in the upper right corner of the channel strips section to get to this menu. Select add external instrument channel strip.
The external channel instrument strip will look like this.
Click on the MIDI output box to show the display below and choose your external keyboard destination(SV-1).
In the channel strip inspector you can send patch changes to the SV-1.
Here is where you select the MIDI input for routing MIDI to the SV-1. If want no SV-1 sound for this Mainstage patch, select none.
You'll need to play with these parameters to get the desired results. Stepping through the MS patches with a footswitch can be done, too, but that can wait for now. Post another question when you master these steps.

MainStage 2.1 release (64-bit)

MainStage 2.1 Update
This update delivers improved compatibility and numerous fixes.
Issues addressed include:
Support for 64-bit native mode
Compatibility with 64-bit Audio Unit plug-ins
Improved compatibility with MainStage 1.x documents
Multiple Playback plug-ins in the same group now sync reliably
Improved recording when using the Loopback plug-in
Updated System Requirements
32-bit mode requires Mac OS X 10.5.7 or later
64-bit mode requires Mac OS X 10.6.2 or later
The update is recommended for all users of MainStage 2.
For detailed information on this update, including some restrictions when working in 64-bit mode, please visit this website: http://support.apple.com/kb/ts2566

MainStage 2.1 Update
This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2.
* An issue where Pressing Command-N to create a new concert could lead to MainStage quitting unexpectedly while the Save dialog was open for a previously loaded concert is resolved.
* An issue that sometimes led to MainStage quitting unexpectedly when closing a concert or quitting MainStage is resolved.
* An issue in which the Invert checkbox for mapping ranges could be unexpectedly enabled in a concert where the minimum mapping range was set, but the maximum was not altered is resolved.
* An issue where CPU usage was initially higher than expected when loading some concerts created in MainStage 1 is resolved.
* Importing patches from a concert whose layout contains more keyboard screen controls than the current concert no longer sometimes leads to incomplete display of settings in the Channel Strip Inspector.
* An issue that lead the the name in the Mixer to fail to update when renaming an alias of a channel strip is resolved.
* An issue where changes made to MIDI Out parameters on an external channel strip were not immediately displayed in an alias is resolved.
* The screen display of an expression pedal in an alias patch now moves correctly in response to incoming data.
* The number of sends shown on channel strips now immediately updates as expected after cut, copy, or paste of channel strips.
* An issue that prevented mapping a screen control to the mute parameter on Bus 8 is resolved.
* An issue where it was not possible to return audio from an Aux higher than Aux 8 is resolved.
* Sends no longer sometimes lose settings when patches are imported, copied, cut, and pasted.
* Polyphonic aftertouch is now sent to external instruments as expected.
* Polyphonic aftertouch sent to software instruments no longer causes unexpected parameter changes.
* Dragging an audio file into an empty patch now creates a channel strip with a Playback plug-in instantiated, as expected.
* An issue that prevented EVB3 drawbars in the workspace from correctly updating when MIDI to Preset Key was enabled, and a new preset was triggered via MIDI, is resolved.
* An issue that prevented screen controls from updating properly in response to CC7 and CC10 messages is resolved.
* Mapping to Solo now works properly with hardware buttons that send single MIDI values.
* Changing a Send All mapping from a channel strip directly to a MIDI mapping now works correctly.
* Grouped buttons now update correctly with the send level parameter.
* Mappings are no longer sometimes lost when importing layouts and patches exported from MainStage 1.x.
* Reset to Saved Value now works reliably when changing patches.
* MainStage no longer intermittently stops responding when choosing Undo after deleting patches.
* An issue that prevented Keyboard objects from sending to all channels of a multitimbral external instrument is resolved.
* Inputting notes while auditioning patches no longer sometimes causes MainStage to sometimes unexpectedly quit.
* The I/O plug-in now works correctly on channel strips with "no input" selected.
* MIDI input now works reliably with grouped keyboard controls.
* The alert dialog "The document 'Untitled Concert' could not be saved as '2'" no longer appears when saving a concert with a long file name.
* An issue that prevented Apple Remote from working as expected in Full Screen mode with Mac OS X v10.6.2 is resolved.
* Setting preferences when there is no concert open now works as expected.
* Parameter tabs now maintain a consistent order for multimapped parameters in duplicated patches.
* Changes to "send Program change" and "send Bank change" in patches are now reliably saved.
* Recordings in Loopback are now reliably maintained when Play on patch change is used while the transport is running with "Snap to:" set to "Bar/Beat."
* Count-in now starts immediately on play in the Loopback and Playback plug-ins.
* Setting a Loopback and Playback plug-in the same group and then recording to the Loopback no longer causes MainStage to quit unexpectedly.
* Issues that sometimes caused the metronome to drift out of sync with the Playback and Loopback plug-ins are resolved.
* MainStage remains responsive when making tempo adjustments in concerts that contain multiple instances of the Loopback plug-in with sync enabled.
* The "Start with Play Action" command now reliably triggers all instances of Playback and Loopback in a group.
* An issue that sometimes caused a small section of unexpected audio to sound when switching to a patch with Playback that had previously been stopped with the "instantly silence previous patch" command is resolved.
* The "Begin Finding Patch in Performance" key command now works properly with patches whose names start with numbers.
* Using the Undo command after deleting an object that is a member of a group in the workspace now correctly maintains the object's group membership.
* Control labels are now correctly displayed when switching from full screen view to layout view.
* An issue that caused the workspace in layout view to be invisible when remote connecting to a computer running MainStage with no display connected is resolved.
* An issue that caused objects to become ungrouped when dragging them from the palette to the workspace is resolved.

Patch 120335-04

Having some trouble installing this patch. Have not found anything that helps. Here is what I am getting:
Utility used to install the update failed with exit code 5.
Checking installed patches...Executing prepatch script...Verifying sufficient filesystem capacity (dry run method)...Patch 120335-04 failed to install due to a failure produced by pkgadd.See /var/sadm/patch/120335-04/log for detailsPatchadd is terminating.
Transition old-style patching.
Failed to install patch 120335-04.
ALERT: Failed to install patch 120335-04.
[rays1@kahlua ~]$ patchadd 120335-04
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
120335-04
Checking installed patches...
Executing prepatch script...
Verifying sufficient filesystem capacity (dry run method)...
Patch 120335-04 failed to install due to a failure produced by pkgadd.
See /var/sadm/patch/120335-04/log for details
Patchadd is terminating.
[rays1@kahlua ~]$ more /var/sadm/patch/120335-04/log
This appears to be an attempt to install the same architecture and
version of a package which is already installed. This installation
will attempt to overwrite this package.
pkgadd: ERROR: attempt to unset package <SUNWcbreg> version <1.0,REV=2005.07.01.10.53> package zone attribute <SUNW_PKG_HOLLOW> from <>: the package zone attribute values of installed packages that are set to <true> cannot be unset
Dryrun complete.
No changes were made to the system.
Any ideas or suggestions?
Thanks,
Ray

Hello,
i ran into the same problem: at some point the recommended cluster patchset issues warnings about not installing the patches:
The logfile
/var/sadm/install_data/Solaris_10_x86_Recommended_Patch_Cluster.log
shows the following error messages:
---------------- Begin of Logfile --------------
Installing 120720-02...
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches have packages not installed on the system Package SUNWgzipS from directory SUNWgzipS in patch 120720-02 is not installed on the system. Changes for package SUNWgzipS will not be applied to the system.
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
120720-02
Checking installed patches...
Verifying sufficent filesystem capacity (dry run method)...
Patch 120720-02 failed to install due to a failure produced by pkgadd.
See /var/sadm/patch/120720-02/log for details
Patchadd is terminating.
Installing 121297-01...
---------------- End of Logfile --------------
It seems, that at some point the patchadd process does an su to the install user if one exists, otherwise to user nobody. If the patch files and all parent directories are not readable by either install or nobody, you get the above mentioned error message.
So there are two workarounds:
1. Setting execute permission for all on /var/spool/patch so that the user nobody can read all patch files and execute a pwd in the patch directory hierarchy.
2. Add an account "install" to the system
useradd -u 0 -o -g 1 -c "Install user" -d / -s /bin/true install
The second workaround did the trick for me!!!!
tc
FAI
2.

Solaris x86 10 u1 (01/06) Update manager showing obsolete patches

I installed 10 u1 (01/06) the other day. I ran the Update Manager and I think there were 8 patches, so I attempted to install them.
Only one of them successfully installed (118966-12), six of them show up in /var/sadm/spool/disallwed_patch_list_report:
STATUS INSTALL BEGIN 119076-10
Transition old-style patching.
STATUS INSTALL END 119076-10 INSTALL.6
STATUS INSTALL BEGIN 119833-02
Transition old-style patching.
STATUS INSTALL END 119833-02 INSTALL.6
STATUS INSTALL BEGIN 120470-02
Transition old-style patching.
STATUS INSTALL END 120470-02 INSTALL.6
STATUS INSTALL BEGIN 120082-07
Transition old-style patching.
STATUS INSTALL END 120082-07 INSTALL.6
STATUS INSTALL BEGIN 120666-01
Transition old-style patching.
STATUS INSTALL END 120666-01 INSTALL.6
STATUS INSTALL BEGIN 119684-02
Transition old-style patching.
STATUS INSTALL END 119684-02 INSTALL.6
And the last one (120041-02) failed.
Anyway, I was grep'ing patchadd -p for some of these and it looks like the ones I checked have been obsoleted by other patches (I didn't check them all, maybe 3).
So, why do they still show up in Update Manager? Or am I missing something (very possible, I'm not a sysadmin, I use this machine for development).

The same problem:
smpatch analyze
119076-10 SunOS 5.10_x86: ip Patch
119833-02 SunOS 5.10_x86: gld patch
120082-07 SunOS 5.10_x86: bge patch
120666-01 SunOS 5.10_x86: busra patch
119684-02 SunOS 5.10_x86: lib/svc/bin/svc.configd Patch
120470-02 SunOS 5.10_x86: kerberos patch
120041-02 SunOS 5.10_x86: ata patch
patchadd -p | egrep "119076|119833|120082|120666|119684|120470|120041"
Patch: 118844-26 Obsoletes: 117462-04 118549-01 118552-03 118847-01 118851-02 118860-01 118993-03 119206-01 119208-01 119565-01 119830-01 119859-02 120320-01 118863-01 119590-03 119720-01 118922-07 119076-12 119946-03 119952-01 120014-02 120029-02 120132-01 120363-01 118924-03 119684-02 119833-02 119948-02 119950-02 119991-01 119995-01 120067-01 120082-07 120303-01 120470-02 120666-01 119857-01 120041-02 118886-01 Requires: 113000-01 118344-05 119255-08 Incompatibles: Packages: ...
Now look to file "patchlist.delimited" from /var/sadm/spool/cache/Database/*.zip (this file is downloaded automaticaly and used for analysis) for patch 118844:
118844<!>20<!>SunOS 5.10_x86: kernel Patch<!>i386<!>SunOS<!>5.10<!>118344-05 <!>118851-02 118860-01 118993-03 119206-01 119208-01 119565-01 119830-01 119859-02 120320-01 118863-01 119590-03 119720-01 <!><!><!><!>BaseOS.SolarisSunIEEE1394-5.10 .... <!><!>reconfigimmediate singleuser clientroot clientusr noncontract<!><!>9361303<!>20051028<!><!>
AND:
there is recorded only 118844-20 and NOT 118844-26 in the "central update" database, therefore obsolete patch path is not resolved correctly (look at 8 field).
SOLUTION:
We must wait :-)
M.C>

How to apply signed patches to Studio 11 under Solaris 10?

I'm running Solaris 10 6/06 on a Sun W2100z (x86_64) workstation. I have a long history of experience with Solaris, but I'm not terribly familiar with the things that are new or different with 10, including zones and the new patch management tools.
I want to apply the latest patches to the various components of Studio 11, e.g. 120759-08,
121018-04, etc. Since all the other patches I've applied (for other OS subsets) have been "signed" patches, I was hoping to stay consisent and apply signed patches to Studio 11 too. I've been foiled at every attempt, though, so I'm looking for some help.
- if I use /usr/bin/updatemanager to select and attempt to apply the patches, I just get error
messages saying that the patches could not be applied:
121016-03 Sun Studio 11_x86: Patch for Sun C_x86 5.8 Compiler            Failed
Utility used to install the update failed with exit code {0}.
120762-02 Sun Studio 11_x86: Patch for Performance Analyzer Tools       Failed
Install of update failed. Utility used to install the update is not able to add packages. Utility used to install the update failed with exit code 5.... and so on.
- if I try using "smpatch" to add the patch, I get this error:
$sudo smpatch add -i 120759-08
add patch 120759-08
Transition old-style patching.
Patch 120759-08 failed to install due to a failure produced by pkgadd.
pkgadd: ERROR: The package <SPROlang> is currently installed on the system in the
global zone. To install the new instance of this package in the global
zone only, you must specify the -G option. To install the new instance
of this package in all zones you must first remove the existing instance
of this package from the global zone first (via pkgrm) and then install
the new instance of this package in all zones.
pkgadd: ERROR: package <SPROlang> cannot be installed on this system/zone- if I try to use "patchadd" directly with the jar file in the current directory, I get this:
$sudo patchadd 120759-08
Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
Checking patches that you specified for installation.
Done!
Approved patches will be installed in this order:
120759-08
Verifying signed patch <120759-08>...
Verifying digital signature for signer <es-signature>
ERROR: Signature verification failed while verifying certificate <subject=Sun Microsystems Inc Root CA, issuer=GTE CyberTrust Root>:<unable to get local issuer certificate>.
ERROR: Unable to verify signature for signer <es-signature>
Signature invalid on signed patch <120759-08>.
Patchadd is terminating.That's three strikes, and I'm out of ideas. Any suggestions for how one goes about applying signed patches for Studio 11? I'll switch to unsigned if I have to, but this seems like it shouldn't be this hard.
Thanks,
Tim

I started a new thread on the updatemanager forum.
http://forum.sun.com/jive/thread.jspa?threadID=107410
I found that forum by googling for "updatemanager" and "zones", but
I couldn't find any recent information on this issue. It seems the
problem has been known about for a while now.
--chris

Kernal patch 142901-07 is not able to install with smpatch add -i command

Hi Guys,
I am using Sun Update Connection proxy in our environment to patch Solaris 10 (x86) machine. I am able to install all the other patches except 142901-07 patch. When I try to install this patch using smpatch add -i 142901-07 command, I am getting following error message
# smpatch add -i 142901-07
add patch 142901-07
Transition old-style patching.
Error: Deferred Activation Patches such as /var/tmp/patchsort.1089.0/142901-07 cannot be installed with -t.
Any idea about this error.
Thanks in advance,
Baiju B

Hi Guys,
I am using Sun Update Connection proxy in our environment to patch Solaris 10 (x86) machine. I am able to install all the other patches except 142901-07 patch. When I try to install this patch using smpatch add -i 142901-07 command, I am getting following error message
# smpatch add -i 142901-07
add patch 142901-07
Transition old-style patching.
Error: Deferred Activation Patches such as /var/tmp/patchsort.1089.0/142901-07 cannot be installed with -t.
Any idea about this error.
Thanks in advance,
Baiju B

Kareoke Style Patch in Mainstage

Similar Messages

Maybe you are looking for