FM 8.0.3 patch RECALLED!

Anybody who has installed the 8.0.3 patch should uninstall it (use the Add/Remove Programs from your Control panel).
Here's a note from the FM product manager:
FrameMaker 8.0.3 patch is NOT available through Adobe Updater anymore.
Unfortunately, an error has crept in with this recent patch 8.0.3 (p276). This error may cause deletion of cross-reference markers when show/hide operations are performed on conditional text.
With due apologies, we wish to inform you that well provide a fix in a week for
customers who have already applied 8.0.3 (p276)
customers who are still on 8.0.2 (p273)
Thanks for your co-operation
Regards
Mahesh K Gupta
Product Manager Adobe FrameMaker

In addition to the problems with cross-reference markers, it seems that Variables are affected as well. I use WebWorks ePublisher Pro 9.2 build 10315 to convert my FM8 documents to CHM or other formats. After applying this patch, the variables now appear blank in ePublisher Pro and in the output.
I tried uninstalling the patch and that did not work. I saved my document as FM7.2 and ran it through ePublisher Pro again, and it worked, the Variables were populated.
I have put in a support request to Adobe and will share their response with the forum.

Similar Messages

Where is the patch coming from

So we have a patch recall, 14-080 as it caouse IE to become unstable. I KNOW we killed all deployments of the patch out of any group membership. However end point are picking up and installing the patch. How can I tell where they are
geting the patch, Our SCCM Envrironment VS the Internet?

39672D42-789E-43D7-8F52-DD3EBFBE66BB is the
Unique Update ID of the patch.
Go in the SCCM console, Software Library\Overview\Software Updates\All Software Updates
Right-click on one of the column and check Unique Update ID.
After,use the search function on the top and enter your ID.
Benoit Lecours | Blog: System Center Dudes

Is it time yet for Microsoft to "Recall" Office 2013 and provide anyone who has a 2013 license a replacement Office 2010 license?

The interface is terrible and can't be changed. Every application in the suite locks up/crashes nearly constantly on any machine it is used on. The activation process is terrible and wastes hours of any support/IT dept's time. From a 'privacy
standpoint', the software is seemingly criminally intrusive. It is clearly a product that should never have been released and is so far from functional that it can't be repaired by any 'service pack', 'hotfix', or 'patch'. It needs to be completely
scrapped.
The only 'redeeming quality' of this software is that the guy who was in charge of creating it is gone from Microsoft. (Unfortunately, he is now President Obama's appointee for running the attempt at repairing the 'healthcare.gov' website...
out of the frying pan... )
When the software is installed using one profile (domain or machine account) and a different profile tries to use the software, it requires 're-activation' - which often fails because the software believes it has been installed multiple times. (This is particularly
frustrating because it has to be installed by an administrative user, but most of the time, the person who 'uses' the software is not the 'administrator' - so it is almost always being 'installed' using one profile and 'used' using another profile).
The necessary intrusion into privacy created by the requirement of a "Microsoft Account" to use the software is seemingly criminal.
The tracking of, and installation of licenses is absolutely ridiculous.
An example:
Many of my clients have many users and many computers (up to 75 or so).
I could create a "Microsoft User Account" for each 'user', but these machines get moved between users, and the software license is tied to the 'machine' and not to the 'user' so as soon as that happens, the licenses and the users are no longer
in line and become impossible to track.
I could create a "Microsoft User Account" for each 'computer'... and I can't even count the ways this would be a nightmare to try to track.
I actually did that up front for one client, and created Exchange email boxes for each computer so that "prove you are really you" emails from Microsoft could be received managed, and responded to, and passed out second usernames and passwords
to all of the users so they could "log-in" to their Office 2013 software, and created a database of the 'computer usernames and passwords' so I could track this... unfortunately, this confused the users (as it rightfully should) so they would change
the passwords for their computer's 'Microsoft User Account' thus locking me out and invalidating my database, ... and... CLUSTERF#%K!!!
As a 'best - worst case', I have had to create a single 'Microsoft User Account" for each of my clients' businesses so I can install and activate Office 2013 products. This is a whole new set of "Awesome Stupidity".
Now, I can put a new computer into a client's office and install their new license key for their oem Office 2013, and it shows up in the 'business's Microsoft User Account'. Then when I give the machine to the user, I get to 're-activate' the software
(hoping that it doesn't tell me to piss-off - which happens about 40% of the time. This is a process that can only be described as a "feat of engineering created by a group of monkeys whose former jobs included 'janitor at MAD magazine headquarters'
or 'beer-pong referee').
It starts with two hours of pressing phone buttons and ultimately talking to someone who tells me "yeah, nothin' I can do about that I'm just here for product activation" (which, incidentally, is done by machine until you pass through MS's ridiculous
labyrinth of repetitious keystroking until the machine is convinced you are just too stupid to punch in the right numbers and allows you to talk to a person... who then asks you for the exact same set of numbers and repeats back the exact same responding set
of numbers and acts dumbfounded when it still doesn't work - since it didn't work the first six times you punched or said it into the phone) followed by "I need to send you to the support group... but because it's 6:30 pm (in a process you started at
3:00pm) they are gone for the day and you'll have to call back on Monday morning"
At some point in the process, you get to log into the "Microsoft user account" and 'roll the roulette wheel of stupidity' by trying to activate the right software from a list of 40 different lines that all say "Microsoft Office 2013 Home and
Business oem", but none give any indicator or differentiating factor like for instance: license key, date installed, license key last 4 digits, mother's maiden name, phase of moon when software was first activated, color or type of blood of the user's
paperboy's dog's previous owner... NOTHING... RANDOM FREAKING STAB IN THE DARK - pick one, any one, hope its the license you are trying to install onto this machine, 'cause if not, you very well may kill the product on some other machine.
So through the process, the lucky support staff person gets' to waste roughly an hour and a half on average for every Microsoft Office 2013 installation. I have actually had to start telling my clients that they are going to likely have to pay an extra
$100 or so per machine in order to get their new Microsoft Office software which comes on their new computer activated - that number tends to work out roughly accurately - except that it is a terrible way of trying to 'please a client'.
Oh,... and did I mention... "THE SOFTWARE CONSISTANTLY FAILS"!?!
A client tries to open a document that they have been using for 8 years and Excel doesn't say "Hey, I don't know how to deal with some element of the file that you put in here using Excel 2003, or Office 2010 (both products, by the way, which worked
great) - no... instead,... it crashes. Doesn't really do any damage to the file it choked on, but the work you'd been doing on three other files which you also had open,... yeah,... that work is gone.
Yeah,.... over time, I have developed a pretty consistent spiel for client's needing new computers that goes over how absolutely terrible Office 2013 is, and explains that our options are further limited by Microsoft's yanking of all Office 2010 or previous
products from market availability, and explaining the merits of both LibreOffice and OpenOffice, as well as their drawbacks. I also have a strangely static response explaining how "larger companies are not burdened by these issues because they are
able to use MOPL which allows them to downgrade their productivity software to Office 2010 so they can continue to function happily, but this is really not a cost effective solution for smaller companies who primarily buy oem Office products with their replacement
computers".
Unfortunately, many clients still decide they want to go with Office 2013 because they apparently believe "it really can't be that bad". The value in my 'presale descriptions' are only really realized when they come back to me a week, two
weeks, or up to a month after the new machine is in place and say "wow,... you were right". The place I am left open for any further problems is when I don't impress upon them beforehand just HOW BAD OFFICE 2013 REALLY IS. In that case,
they still come back to me as though I have done something wrong foe selling them this piece of $#!% software and I have to remind them of our previous discussions.
Strangely, far too few heed the warnings and buy the software anyway - but the discussion has saved many clients the costs of Microsoft Project, because the discussion of LibreOffice and OpenOffice nearly always leads to at least a small philosophical conversation
about 'Open Source Software' in general, and my absolute favorite descriptive analogy in that discussion is to compare Microsoft Project at $600 v. ProjectLibre at $0 - and then further describe the costs of licensing and implementing the associated back-end
server solutions, etc.
This is a saving grace for me, because even though the client has been saddled with Office 2013, they have also saved substantially on Project and it is a rare (but granted, not absolutely absent) occasion that ProjectLibre is lacking some feature or function
that they actually need or want to use - and on those occasions, finding out has cost them absolutely nothing in software purchases.
Its not surprising, I suppose, that clients have grown to accept Office as a required 'cost', but still choke heavily on the price-tag of Project every time they have to buy it. The interesting thing to watch over the coming couple of years will be
'how many businesses stop accepting MS Office as a 'required cost' due to the failing of the software itself and the fact that most are being burned, at least once, by purchasing the software "against technical advice" and are learning, merely by
virtue of HOW BAD Office is, that there are other options out there that both cost less and work better... I mean,... LOTS BETTER.
How many businesses that are used to accepting the cost of Microsoft Office as a cost of doing business will be moved over to open source options and satisfied by them by the time Microsoft releases its next version - which will, presumably work - such that
they will no longer justify the cost of Microsoft's offering even if it is 'superior' to the open source offerings because the open source offerings are plenty sufficient and include a price tag of $0 and an installation/implementation time that is much, much
shorter than Microsoft's offering.
If Microsoft doesn't make some dramatic reparations, and do it soon, I expect their market share will be reduced in this area by a very significant margin.
I am suggesting either a 'Complete Recall' of Office 2013 including an 'uninstall 2013/install 2010' process driven by the automatic update engine, or at the very least, a free and easy downgrade rights offering for anybody who has already purchased 2013
and anyone who purchases it between now and the time the next "functional product" is released.

I understand the inconvenience you are experiencing when working with Office 2013.
If you have any feedback about Office 2013 product, click the and submit to Microsoft.
Microsoft will decide how to fix the problem for all customers.
For the activation mechanism, it intends to protect customers of their rights and interests.
For a retail version of Office, if it was purchased with a disk, Microsoft account is not necessary during the installation.
For volume license of Office, refer to the following link to deploy Office suites can be much efficient:
http://technet.microsoft.com/en-us/library/cc178982.aspx
For the problem Office 2013 keep crashing, check the following link to check:
http://support.microsoft.com/kb/2813143/en-us
http://support.microsoft.com/kb/2758592/en-us
Thanks,
Tyor Wang
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no
help.
If you have any feedback on our support, please click
here

Patch deployment on second Primary SCCM 2007 site

Dears,
I have the following design on my SCCM infrastructure.
1 Primary Site (Parent Site code H01) - Located at HQ
1 Primary Site (Site code D01) - Located at DR and reporting to HQ primary Parent site
- clients located in DR location has the agent installed with site code ("D01")
-clients located in HQ has the agent installed with site code "HQ1")
My questions are:
I have create a deployment management in HQ site and install patches to all clients belong to HQ with site code H01 without any problem.
For clients belong to "D01" I want them to get the patches from D01 primary sccm server located in DR.
Should I create another deployment management in DR sccm server separately or I can use the existing SCCM deployment management created in HQ1?
Any suggestions are much highly appreciated.
Many thanks guyz..
MC

Yes, they will appear locked at that site. You can't edit them. If I recall correctly though you can deploy them. I always perform all administration at the top site in the hierarchy though.
Are you truly trying to use a child primary as a in a DR scenario? If so that's not a great idea.
John Marcum | http://myitforum.com/myitforumwp/author/johnmarcum/

Message recall from shared mailbox greyed out Outlook 2010

Hello,
Can anyone advise if it's possible to recall a message sent from a shared mailbox? The user has full access permissions to the shared mailbox but the 'recall this message' option is greyed out.
We have installed the hotfix below but it says the update is already installed on the system?
http://support.microsoft.com/kb/2475877/en-gb
This is using Windows 8, Outlook 2010 32bit and Exchange 2007 SP3.

Hi,
Try to remove and grant the user the permission to the shared mailbox again to see if the issue still exists.
This issue should have been fixed by kb2475877, please also make sure Office is patched up to date.
We can try with a new profile to setup the account, check if the issue persists:
http://support.microsoft.com/kb/829918/en-us
Regards,
Melon Chen
TechNet Community Support

ISE 1.2 Patch 8 Endpoint icon Missing

Hi,
Has anyone seen an issue where the Endpoint icon under Identity just disappears.
I upgraded to Patch 8 yesterday and all seemed fine but sometime this morning between adding enpoints the icon has gone.
Very strange.

I recall seeing this as a bug with Patch 8. v1.2.1 addresses and fixes this.

Another burst A1189 battery that doesn't fit within the recall

Battery model A1189, Serial No. 6N64905XW4HB. Was doing the abrupt shut offs, started about a month ago. Battery Update and all other patches were current. Now its bulged out and is now unsafe if usable at all. But I guess that's my problem, not Apple's. Sorry your power source is obviously defective, but we can't help you. Great service.
Whats scary is the new ones that are now inside the case, where will those have room to bulge out of? And will Apple say you're SOL if you don't fit what they determined to be the range of serial numbers that were bad?

Glad you got your issue sorted.
bshomb wrote:
... inferiority of Apple that they can't make a laptop battery that doesn't have issues. Can't say I blame them, the lenovos we use are pretty decent.
Apple doesn't make their own batteries. They use batteries made by Sony, SMP, etc. If your colleagues want to discuss the batteries in Lenovo laptops, which you call 'pretty decent', you might refer them to this article discussing the recall of over half a million batteries in Lenovo laptops, and the related incident at the LA International Airport in which a Lenovo T43 caught fire due to a faulty battery.
Just some food for thought...
As a side note, a brand new Lenovo T400 that my work's IT department issued to me last week died this morning - it fails to boot beyond the initial BIOS screen. That Lenovo was my fifth work-provided PC laptop in the past 3 years. My 3-year old MBP is working just perfectly...and I'm still productive at work at this very moment because I'm running an image of a corporate Windows installation via Parallels on my MBP.

FM 8.0.4 patch released

The fix to the recalled patch has been released as 8.0.4. This fixes the 8.0.3 patch if you didn't uninstall it. For those that uninstalled it or hadn't installed 8.0.3, a new patch combining both 8.0.3 and 8.0.4 will be issued shortly.

The direct link to this patch will probably not be posted as it fixes
errors in the removed 8.0.3 patch. A complete patch for those still at
8.0.2 (aka FM8.0p273) will be posted when it is ready (most likely
8.0.5). It will first be available through the Update Manager in FM
and then will eventually (I don't know why the lag, so please don't
ask) be available on the FM main downloads page.
For Windows it will be at:
http://www.adobe.com/support/downloads/product.jsp?product=22&platform=Windows

Outlook 2013 since last patch (Dec 2014) gives error: System Administrator - Undeliverable

After installing the latest round of patches from Microsoft in our environment, we have had numerous users having this issue. When sending an email, internally or externally, they get the following message.
Your message did not reach some or all of the intended recipients.
From: System Administrator
Subject: Undeliverable: Email Subject
      Subject: Email Subject
      Sent: 12/16/2014 9:21 AM
The following recipient(s) cannot be reached:
Person#1 on 12/16/2014 9:21 AM
            This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].
The problem is sporadic and sometimes just closing Outlook and reopening it will fix the problem. The problem does happen both when the users are in the office and when they are out. There isn't any pattern that we can identify. It
happened to me once and a reboot resolved it for me. We thought that maybe a specific patch that was installed just needed another reboot but we still have other users that are having the problem even after numerous reboots.
A little more about our environment:
Exchange 2010, fully patched with all service packs and updates (single server)
Running on a Windows 2008R2 server with all service packs and updates
Outlook 2013 with all updates installed
Happening on both Windows 8.1 (fully updated) and Windows 7 (fully updated)
Again this just started happening after the last patch cycle and we have never had this situation occur prior to that.
Steve Eason, MCSE FM:Systems

If you installed Exchange 2010 SP3 RU8 then you need to update to the 2nd revision of that update, as the first one had that very issue.
Update 12/12/2014:
Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package corrects the issue which impacted users connecting to Exchange from Outlook. The
issue was insulated to the MAPI RPC layer and was able to be isolated to quickly deliver the updated RU8 package. The updated RU8 package is version number 14.03.0224.002 if you need to confirm you have the updated package. The updates for Exchange Server
2013 and 2007 were not impacted by this regression and have not been updated.
Update 12/10/2014:
An issue has been identified in the Exchange Server 2010 SP3 Update Rollup 8. The update has been recalled and is no longer available on the download center pending a new RU8 release. Customers should not proceed with deployments of this update
until the new RU8 version is made available. Customers who have already started deployment of RU8 should rollback this update.
The issue impacts the ability of Outlook to connect to Exchange, thus we are taking the action to recall the RU8 to resolve this problem. We will deliver a revised RU8 package as soon as the issue can be isolated, corrected, and validated. We will
publish further updates to this blog post regarding RU8.
This issue only impacts the Exchange Server 2010 SP3 RU8 update, the other updates remain valid and customers can continue with deployment of these packages.
https://www.microsoft.com/en-us/download/details.aspx?id=45225
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

Installing Patch 9.2.0.5: Weird "Stop Running Services" Screen

Hi to all.
I found this issue in several places, including this forum, but I never saw a working proposal for a satisfying solution. Installing Oracle Patch 9.2.0.5 over a 9.2.0.1-Installation on XP Pro, I was confronted with a "Stop Running Services" screen, that listed ALL running Windows Services, even the most basic ones, which are required for a working OS and cannot/should not be stopped. Of course I had stopped the Oracle listener and instance services (including the recovery service, omtsreco.exe).
I found using TASKLIST.EXE or LISTDLLS.EXE, that many Oracle DLLs like ORAPLS9.DLL were used by a command "svchost -k netsvcs". But I could not find out, where and for what reason this command is launched and how I can prevent this launching without hazarding the system. The string "netsvcs" can not be found in the registry, for instance.
At least, somehow I managed to do the job, but I cannot exactly recall all the steps I took! At the "Stop Running Services" screen I chose "Abort current component and continue installation", and after install finished (it said something like "install finished with errors" or that like), I was left with a non-functioning Oracle client. Whopee! It told me "Bad function entry point" when I tried to start SQL*Plus. Desperately, I started the patch installation a second time. THIS time I installed OUI 10.1.0.2 as a first step (which I did NOT during the first round), and then started patch install. Strangely, this time I was presented another flow of dialogs (Sorry, but I missed to make notes about the exact titles and the dialog flow), which took MUCH MUCH longer ("Analyzing Dependencies" for example, took 1.5 hours to complete), and I really do not know, how or whether I was confronted with a "Stop Running Services" issue), but after all I really managed to complete the second try successfully, and the client functions worked again (SQL*Plus reported the correct version, 9.2.0.5).
Before I'm driven through this hell again (I have to patch several workstations running 9.2.0.1), I'd like to know,
- Whether the issue has been solved, that the "Stop Running Services Screen" lists
most basic services like "Event Manager". Could it have been caused by using the
wrong OUI version or under what circumstances will it appear?
- Secondly, what is this mysterious "svchost -k netsvcs" (netsvcs = NETSerViCeS ?)
locking many of the DLL files in the Oracle "BIN" folder. It is definitely NOT
one of the Oracle listener or instance services (all of which start with "Oracle").
How can this service be disabled or be prevented from loading the Oracle DLLs?
Sorry for the long story and partially unclear details, since I do not recall all of the long installation session. Any input is welcome.
Werner

Ok, "netsvcs" CAN be found in the registry, but I used FINDSTR.EXE to seach a UNICODE .REG file, and of course had no hits. Meanwhile, I learned more about SVCHOST.EXE and it's service groups, one of which is "netsvcs". In HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost, I found a value and a key named "netsvcs", the value contains this string (abbreviated):
"6to4
AppMgmt
AudioSrv
Browser
CryptSvc
helpsvc
xmlprov
wscsvc
WmdmPmSN".
These are the symbolic names of the services presented to me in the "Stop Running Services" screen! Now it's clear, why this screen appears, since "svchost -k netsvcs" is the process locking the Oracle DLLs.
But the question remains: WHY does "svchost -k netsvcs" need access to Oracle DLLs? Which system or application setting controls whether svchosts tries to load the DLLs?
Still puzzled. Werner.

Applying a patch

I'm having a problem setting my wireless card to monitor mode and apparently this is the solution. Unfortunately, I have no idea how to apply this patch or which files to patch. Could somebody please help me out? Thanks!

SOLVED!
Speak of the devil! I was just about to make a thread on the same subject about a patch problem I have had for a few days now.
Ok, I have read the "Patching in ABS" wiki entry, but I am still having issues with patching a custom WINE build. At the moment I am unsure of whether it is an issue with the patch or if it is an issue with my PKGBUILD. Here is the output I get from makepkg:
can't find file to patch at input line 4
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|diff -pur wine/dlls/user32/Makefile.in wine/dlls/user32/Makefile.in
|--- wine/dlls/user32/Makefile.in 2010-10-15 21:37:09.000000000 +0400
|+++ wine/dlls/user32/Makefile.in 2010-10-18 22:44:01.000000000 +0400
Instantly I'm thinking this is possibly a directory transversal issue. The way the PKGBUILD for wine works is it has a 64-bit and 32-bit install and creates them in seperate directories from the looks of things. I may be completely wrong, I am only a newb (Tread softly, please ). I have tried everything possible from copying the patch file to the source directory like the wiki mentions, copying the patch file to the actual package directory itself, and a few other iterations of changes that I can't seem to recall.
Here is the PKGBUILD and patch I am trying to use.
PKGBUILD: http://paste.pocoo.org/show/335187/
Patch: http://paste.pocoo.org/show/335188/
Yes, I realize it's using an older version of WINE. I was backtracking to see if it was just a possible issue with the patch or not. I am not extremely knowledgeable about patching (Or ABS for that matter yet!), but I am willing to learn.
EDIT: Oh also I could not figure out how to add the patch to the source array. Any help with this would be appreciated as it would probably solve the problem of having to copy the patch two times in the PKGBUILD.
EDIT2 (SOLVED): My problem was solved simply by adding the patch to sources (Figured out how to finally do that with the help of people in IRC and looking at Skype's PKGBUILD). I also removed the individual "cp ($patch)" lines and made an individual one underneath where PKBUILD renames the '$pkgbuild' directory. Also ran into to some compiling errors because I forgot to add a forward slash spacer in the configure portions of the install. Newb mistakes fixed thanks to some help, reading, and common sense (Doh, I lost mine in the /tmp/ folder apparently).
Last edited by dexxra (2011-02-09 20:17:36)

Whole root or sparse root zones and patching

Hi all,
A while back, I did some cluster patching tests on a system with only sparse root zones, and one with whole root zones...and I seem to recall that the patch time was about equal which surprised me. I had thought the sparse root model mainly is patching the global zone, and even though patchadd may need to run through the sparse NGZ's...that it isn't doing much other than updating /var/sadm info in the NGZ's.
Has anyone seen this to be true or if there are major patching improvements using a "sparse" root NGZ model over a "whole" root model?
thanks much.

My testing showed the same results and I was a bit surprised as well. As I dug into it further my understanding was that the majority of the patch application time goes into figuring out what to patch, not actually copying files around. That work must be done for the sparse zones in the same way as for the full root zones, we just save the few milliseconds of actually backing up and replacing the file.
I suspect there is a large amount of slack that could be optimized in the patching process (both with and without zones), but I don't understand it nearly well enough to say that with any authority.

Cloud 12c schedule patch plan?

Am I missing something obvious? Can't seem to figure out how to schedule the deployment of an analyzed Patch Plan in Cloud 12cR2 - only seem to have the option to deploy immediately.
I seem to recall being able to scheduled patches in previous db console/grid versions....

You are not missing anything. There is no way to schedule the deployment step in a patch plan.
Regards,
Dave

Problem in installing patch set 8.1.7.4

Hi All,
when i am installing patch set 8.1.7.4 i am getting stuck here like it is not able to file link the binaries can i know what is the reason
when i tailed install log i am getting below error.
/usr/ccs/bin/make -f ins_net_client.mk client_sharedlib ORACLE_HOME=/meta01/app/oracle/product/8.1.7
/meta01/app/oracle/product/8.1.7/bin/genclntsh
when i tailed installlog.err log
Error in deleting /meta01/app/oracle/product/8.1.7/rdbms/lib64/config.c

Error in deleting /meta01/app/oracle/product/8.1.7/rdbms/lib64/config.cIt has been so long since I worked with V8 that I can't recall whether or not a 64-bit version existed.
What OS name & version produced this error?

MainStage patches not loading Guitar Rig 4 patches

I'm trying to use Guitar Rig 4 as a channel strip plugin for live EG performance. Unfortunately Mainstage seems unable to properly recall assigned Guitar Rig patches and/or recall screen mapping for those patches. It seems like it only loads the first GR4 patch. If I open up the plugin I see the correct GR4 plugin name but when I double click it seems to then load.
I've mapped screen controls to specific editable functions within Guitar Rig 4's patch. Unfortunately after reboot Mainstage patches do not properly load Guitar Rig patches and screen control mapping breaks.
For instance within a specific Mainstage patch, I have a Guitar Rig 4 patch that has a stereo delay. I screen map to the stereo delay's controllable functions (mix, feedback, etc). I test it out and everything works properly. I save. I restart and then the screen controls lose their mappings.
So what's up? Is it a user error or a limitation between the two softwares?
Andy

Hi again,
OK so to map a MS toggle switch to activate an event in a Plug-in like Guitar Rig 4?
- You have Pedalboard as an insert in the channel strip?
- You have Guitar Rig as an insert in the channel strip?
- if so
- selecect the unassigned button in Manstage edit mode
- MS will open the screen control inspector panel below the edit view of your MS edit window
- In the third tab 'unassined' of the inspector you sohould see columns make sure you're looking at the left most col
- You will find the name of the channel strip (guitar-1) or something like that - select it
- The next col will fill with info on the channel strip including the inserts - select Guitar Rig 4- The next col will fill with all the attributes of the Guitar Rig patch you've selected as an insert
- The list will contain all the controllable attrubutes of the componants that mack up the guitar rig patch.
- Select the WAH/ON/OFF or what have you.
- Now the switch in MS will control the ON/OFF state of the WAH efect in that Guitar Rig patch.
The same process works for rotary knobs so you can have MS contol the ON/OFF function and allow you to adjust say the Gain and Tone of your choosen Guitar Rig effect. Obviously you can use for Amps/effects/Cabs/and even Tapdeck etc.
Once you have a channel strip set up and your happy with the layout of MS you can save the channel strip and use it in Logic and vise versa - so I have started a library when my guitar and bass patches are channel strips.
This is because I mix up componants of the various Plig-ins I have say - Pedelboard => Ampdesigner => Guitar Rig 4 => Amplitube 3 => and Redwirez as a single 'patch'. So playing live I use the appropriate 'patch' strip in MS and when recording the I use same 'patch' strip in Logic.
Have fun!

FM 8.0.3 patch RECALLED!

Similar Messages

Maybe you are looking for