System exclusive?

Hello!
I have a whole ton of patches saved on a Yamaha CP300, and I need to find a way to back them up. I sent in an e-mail to Yamaha to find out how to do this. Here is the message that I got back:
"Yes, you can save the data of CP-300 by performing a bulk dump. Check if your version of Garage Band can record the bulk dump. GB must be able to record system exclusive. Just start recording a Midi track with sequencer software and start the BULK DUMP on CP-300. When the BULK DUMP is finished, save the song. Your Midi data is saved in the song. Use the setting example at page 93 of manual."
Is this something that I can do using GarageBand? If so, can someone please tell me how? Thanks.
-Steven

It must be the Hyper draw, I' am learning how to use
it, does LE have an automation button so I can do the
changes manually?
Yes,
Select the track or tracks that are giving you the problem, then go to the "View" menu and select "Hyperdraw". When you select it a submenu opens and in that list you will see "Volume". You can reset the volume in hyperdraw by dragging the line to the bottom. Hope this helps. Phil

Similar Messages

Is there a way of stopping the battery from charging?

Dear Apple Community,
Recently I installed iStat Menus and found that, over the course of this year, my Macbook's charging capacity has dropped 5%. I know this isn't a massive number, but battery performance has become a concern for me. I use my Macbook as a desktop replacement, on the main. It's sitting on a mStand, connected to a large monitor on my desk. I use my Macbook to play games, surf the internet, do work and all that good stuff - basically, I use it for everything. I rarely use the Macbook without it being plugged in. I read on the Apple website that they do not recommend leaving the Macbook on charge permanently and that I should use it on battery at least one a month. As I use my Macbook as a desktop replacement, I don't actually have a lot of opportunity to do this.
My question to you, the community, is: is there a way of stopping the battery from charging, either with the use of an app or a physical device? Ideally, I would love to have my power plugged in BUT only used when the battery drops below 10%. Is this possible with an app?
On the other hand, am I just worrying about nothing? Will my battery be damaged further if I leave the Macbook charging permanently?
Thanks for your help!
Jeremy Reid

Ideally, I would love to have my power plugged in BUT only used when the battery drops below 10%. Is this possible with an app?
The charging characteristics are handled in firmware. There is no app that would be able to do this. You actually would not want to do this anyway. Regularly discharging your battery to 10% will greatly decrease the life of your battery. While it is true that you should not use your system exclusively plugged in, allowing it to run on battery a few hours a week should be fine. Letting the battery regularly run down to (or below) 10% will cause you to use up cycles more quickly than is necessary (thereby reducing the life of your battery). It's really a only a matter of disconnecting your Magsafe connector once in a while.
Leaving it plugged in does not result in it being charged "permanently". It will charge until it is full and then charging will stop. It will only begin recharging when it reaches about 95%.

Ram for G3 RevA Mini-Tower

Hello all again. Next ussue: want to upgrade from 320ram to 512 or more. I once a while ago installed a 256mb stick to upgrade to 320mb, recently got another from the local mac guy, PC100, 256mb, and the Mac only reads it as 128mb. What's up with that? And what do I need? And where do I find it?
Thanks in advance.

Hi James,
I wager the chip that shows up at 1/2 its rated size in a hi-density module, with eight devices only on one side. A 256MB module for the Beige needs low-density or 8 devices on EACH side.
I've used one company, Data Memory Systems, exclusively for RAM for over three years and can't complain a bit. I get PC100 RAM by choosing the Blue & White G3 from their selector:
http://www.datamemorysystems.com/memory-information/256MB_SDRAM_PC100_CL2_DIMM_Apple555.asp
This works great in my Beige G3 and the price is pretty good.
(I have no relation with the mentioned form other than as a happy customer)

Assign MIDI Keyboard Pedal to control Record?

I can't seem to get it to work, I used MIDI learn but it didn't assign the Pedal, a simple 0-127 cc64 VFP 1/25, to control the transport record button. Could the problem be that the box the pedal came in mentions most makes of keyboards but not my M-Audio 49e?

I see. the pedal must send CC64 to Logic to be able to control the software instruments sustain ect.
One of the reasons that the CC64 can be "blocked" is if there are any previous Controller Assignments or Keycommand assignments of that message i.e CC64. In this scenario the Logic Physical Input blocks the original message. There is a little trick to split that message using IAC but for now you must be sure where is the problem. Try to trash (and make a backup) the Logic Preferences file which will reset/delete all previous assignments. Open Logic and operate the pedal just to see if there is any CC64 shown in the Transport midi monitor or in the Input View monitor in Click & Ports environment layer. If that works then you can try to learn a keycommand again.
Those asignment numbers mean little to me, they are"F0 7E 7F 06 02 00 20 08 4D 14 10 01 20 31 32 32 F7:learned
This is System Exclusive message.
A.G
www.audiogrocery.com
Author of: Logic GUI Deluxe (Free),
Vox De Bulgaria - s.a.g.e vocal pack for RMX,
Logic Snapshot Console,
RMX Power CTRL - Logic Environment Midi editor for Stylus etc.

Remote Function Call

Hi,
I am very much new to RFC, Can anyone help me to suggest some ideas for the following scenario.
1. For the created PA30 screen using webdynpro, i have to create RFC.
2. BAsed on the input from the system and the screen i have to write RFC.
3. Through the RFC i have to update the Tables.
Thanks ,
Vijay
Moderator message : Spec dumping is not allowed, search for available information. Thread locked.
Edited by: Vinod Kumar on Aug 9, 2011 10:28 AM

Hi..,
CALL FUNCTION - RFC
Syntax Forms
Synchroner RFC
1. CALL FUNCTION func DESTINATION dest
                     parameter_list.
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
                [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
                parameter_list
                [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Transaktionaler RFC
3. CALL FUNCTION func IN BACKGROUND TASK
                     [DESTINATION dest]
                     parameter_list
                     [AS SEPARATE UNIT].
<b>The destination contains the connection parameters for remote function calls. It contains the connection type, the target system and the partner program. Connections that affect SAP systems exclusively can be agreed as trustedsystems. RFC destinations are managed using transaction code SM59. </b>
regards,
sai ramesh

Consuming Webservice runtime

Hi All,
I have a doubt regarding the usage of webservice runtime.
I have a scenario where we have a webdynpro ABAP program which displays all the messages for a particular interface. In our scenario we have only an Integration server of PI 7.1. In this server we have developed the web dynpro ABAP program. Now in this program we need to display the adapter status of the message also.
For getting the adapter status from the Java Stack we developed a webservice. but now the problem is that we cannot consume the webserive using a proxy runtime from the inntegration server.
I have heared that it can be done if we are using webservice runntime instead of the proxy runtime, but i dont have a clue in how to use the web service runtime.
so please somebody help me understand the concept of using the webservice runtime, and how to create and use the webservice runntime to achieve my requirement.
Thanks in advance.
AjithV

Vijay,
I've to make a call to External (non-sap) system --> pass some values --> (and then) get the returning parameters/values from the exernal system. The webservice is created in external system and here SAP will act as a client.
The system is SRM5.0, is it possible to use the RFC - XI soap approach in SRM 5.0 by maintaining the necessay configuration w/o involving XI system exclusively ? or XI is a MUST for this type of scenario ?

Consuming Web Service from ABAP: ERROR_WEBSERVICE_RUNTIME_INIT

Hi fellows,
I have to make a call from SAP (CRM) to external system (via webservice) for this purpose I've setup a new Proxy-Object, uploaded the WSDL file (locally) and Created a Logical port.
In the Logical Port under the tab Call Parameter I've defined the URL of the web-service. I am also not able to upload the WSDL by selecting the option URL/HTTP due to error message "HTTP error (return code 400, message "ICM_HTTP_CONNECTION_FAILED")
Message no. SPRX090" so uploaded the file locally.
However, when testing the service, I didn't received a sucess message but:
<CX_AI_SYSTEM_FAULT>
<CODECONTEXT>Local</CODECONTEXT>
<CODE> ERROR_WEBSERVICE_RUNTIME_INIT </CODE>
<ERRORTEXT> Error when instantiating the Web service runtime (Error when initializing SOAP client application: ' error_text' ) </ERRORTEXT>
<LANGUAGE />
</CX_AI_SYSTEM_FAULT>
</cls:CX_AI_SYSTEM_FAULT>
What might be the Problem ?
/Manik

Vijay,
I've to make a call to External (non-sap) system --> pass some values --> (and then) get the returning parameters/values from the exernal system. The webservice is created in external system and here SAP will act as a client.
The system is SRM5.0, is it possible to use the RFC - XI soap approach in SRM 5.0 by maintaining the necessay configuration w/o involving XI system exclusively ? or XI is a MUST for this type of scenario ?

Every time I think I will switch to Lightroom...

I do something in Ap that just blows my mind. Today was a day for building a new client album, selecting a group of shots from across several projects in different years.....the incredible power of the Ap database design and search/collating tools made this a piecacake...and I did this, wirelessly, on my laptop while on another floor of my home studio, with the main Library on the desktop downstairs..and I even did some last minute editing on a couple of several year-old images, without +a thought+ for which exact file I was changing, where it was stored or if I needed to dupe it for backup (I use the Vault system exclusively)...
Yeah, I'm still desperate for 2.0...but this is a strong reminder to me why I am so impatient to see this awesome software design be fully and well-implemented.
thanks for listening to the cheers!
david

I have to say...I gave LR a spin this weekend and I am trying to justify waiting a little longer and seeing what happens with AP, knowing that a 2.0 of LR is probably just as close. I've been an AP user for over a year and a half. I've amassed tens of thousands of images in by library.
I always told myself that I needed the dual monitor support of Aperture, etc...and when I started playing with LR, I didn't. What I found was that I was moving through images at a much more rapid pace, and that IMO, the RAW conversions from LR (ACR 4.3) are much more pleasing than AP. I still like the Aperture UI better, but there are aesthetics, and a program that works well. At the end of the day, I'll go with the application that is the best tool for my business...emotions aside.
For instance, I was able to sort through 800 images (from three different shoots), do some low level post, create three very elegant flash web galleries, and ftp them to production in just under 3 hours. I've never worked that quickly and been satisfied with presentation for the time. That same work in AP would have taken 5+ hours.
This isn't a dig on AP...but improvements have been a long time coming. I feel that if Apple is serious about this application, they need to be much more aggressive in development, and committed to over delivering a better product. I think LR has a lot of momentum right now. With each day they are losing the small percentage of photographers using AP to LR. It's a shame, because they had the lead "out of the gates". They knew they were taking on a 900 lb gorilla, and I can't help feel that they lazily brought a knife to a gunfight.

ProRes 422 & Premiere Pro CS5.5.2 Playback

I am a long-term user of CS5
Recently started using ProRes 422 footage, (LT in order to keep file size a little smaller). The footage is taken from a Ninja2 via the HDMI of a Sony HVR Z5.
I do a lot of post work on my projects and the native mpeg2 8 bit from the HVR would not hold out too well. Apart from that, I had no previous performance issues using mpeg 2 files.
Now the ProRes 422 footage in the preview window and in the timeline of PremPro is stuttering and won't play smoothly for more than a couple of seconds at a time. This has become progressively worse as the timeline has grown.
I use a single video track (I don't stack or nest) and often use 4-5 audio tracks ( 24bit .WAV) plus a stereo channel from the Ninja2. Audio settings within the project are 32 bit floating.
Average Data Rate of the ProRes (LT) Video File is 8.9 MB/s. Source Audio is 48KHz 16 Bit.
Edit Workstation system (exclusive, no other use):
Triple Channel 24GB 1600 RAM
i7 970 (Hex) 3.2GHz
Nvidia GeForce GTX 580
MB Gigabyte X58 (No Overclocking)
SSD OS & Programs
4 x 500 GB Sata2 Caviar Black RAID 0 media scratch disk and cache (Software RAID - no hardware controller). The RAID is striped at 128Kb.
1 x 1TB Sata2 Caviar Black project files
CPU Temps 44-46 C
System Temps 41 C
Graphics Temps 58-60 C
Disk Temps 30-40 C
The disk access times during playback are often less than 5 ms. Quick Bench (8MB zone) test gives RAID 0 Average Read Time of 642 MB/s, Random Access Time of 14 ms, and Burst Speed of 3411MB/s. CPU Utilisation is 2%. CPU system usage is fairly low as is the RAM demand with 50% often unused. 18Gb of RAM is allocated to Adobe programs (After Effects & Prem Pro) with 6GB available for other things.
I am using no external monitor interfaces.
The ProRes footage is imported into Prem Pro and the sequence setting is automatically created by dragging the ProRes file into the New Item folder.
The project sequence created by Premiere Pro is AVCHD 1080i Square Pixels 1920 x 1080, Upper Field First 25 fps (PAL) which is correct for me in the UK.
This works out fine as I have additional footage from a Sony NX5 which is AVCHD and happy with those sequence settings - I get smooth playback from the NX5 in both the preview window and the timeline. The resulting timeline bar colour is Yellow for both footage. If the Pro Res footage is rendered on the timeline (green bar) playback is fine. The render codec is by default I-Frame Only MPEG.
At the start of the project, the playback seemed fine, but now I am about 35 minutes in and the whole thing has ground to a stuttery conclusion.
The footage in the preview window scrubs and jogs fine, but plays for about a second or two then stutters, as does the timeline. I would expect my system to easily handle the Pros Res footage - but it doesn't.
Any similar experiences out there?

1. With that much footage, I might set previews to render to my output size, so as to cut down on final render time.
2. 112gb! Holy Crap! I hope you're on a fast RAID drive with that! Otherwise saying you're headed up $*it creek without a paddle doesn't quite cover it... ...more like drowning in the $*it ocean.
With that much information you're almost always better off utilizing a rendered file rather than relying on your dynamic link. If playback is choppy, you need to be able to render to a drive that isn't "Busy" while you're playing from it. I've found that using separate RAID for my main project file, and my original or AE assets allows me to render out the previews to a non-busy drive, making the output faster, and the playback faster when reading it.
Dynamic linkage is great... ...if you're going to be making more changes to that piece, leave it as is and play it back, if not, RENDER THE EFFECT, or RENDER A WORK AREA set to the clip you're editing. If you're done for the day, render the whole damned thing and leave it until you come back. Rendered effects will play back faster than active process effects (renders are already in the video, set into it as if native to it; active process edits aren't in the video, they are applied as it is played back, and require more processing so they slow things down), and when you come back from lunch or from home, you'll have a freshly rendered slate to preview. This means you'll be able to show off for the client by morning. Need a Web-capable rendering for a status update you're sending to a client, DUPE the sequence, change the preview on the DUPE to match some web capable settings with smaller frame height\width resolution and compress the hell out of it. Youtube can play it back pretty well, and vimeo also, and you'll be able to upload it in 2-4 hours (if your system is archaic like mine, smaller video outputs great). Personally, I've found comps with AE to be a pain when trying to link and playback. Render a work area around the comp if you're going to play it back. IF you want to preview a whole section, Dupe the Sequence and use the Dupe to NEST the SECTION (create a trim or edit mark at the beginning and end of the section you wish to preview, select everything between the markers, right click and select nest), and you can use AME to render a small preview file, so you don't interrupt the rest of your work.
I work with more sound quality constraint than video, and the sound quality has to be real, while the video does not need to be perfect (doesn't mean I don't damn well try; I've really just begun my journey into this world, and have only begun to use prores, but found some pitfalls to experiment and solve). I start with whatever I'm given, go to prores, edit with a prores proxy preview at ¼ the input size, and render out once just to get started. The effects values are applied to the preview in playback, easing the playback stutter, and allowing me to work fluidly on a laptop mac with an intel core2 2.16ghz with a geforce gfx card at 256mbvram and 4gb of system ram, with (hardware hack) 2 internal drives each at 1tb, one for main use, and one for housing my project files. Using an old esata express card raid box, I get great speed from the playback by storing the previews on RAID, while all the other files are housed on my secondary internal drive. With multi cam AV, you need to be able to store the main clips on different drives, or on a raid store (ideally on separate RAID stores) in order to play them back while cutting them together. However, once cut, you should render out the preview in it's entirety, and start your other edits from that point. Then you can render just the effects and still get great playback.
If you don't see Prores in your preview box, get the AME prores presets from the adobe site, and you can place them by hand into your app (the folder should be the EncoderPresets folder in the program files on windows, on mac open the .app by right click and select show package contents>contents folder>settings>EncoderPresets and paste the .epr files there by hand). Then open up premiere and you should be able to use prores proxy for your previews and export. I like to export to prores and then use handbrake to export to x264 with --fake-interlaced set up so I can use it as a transcode for Encore. Just keep your blu-ray data rates under 35mbps and you should be fine.

Call library with struct as parameter - several problems

Hi everyone,
I'm trying to send a MIDI sysex message to a midi device through winmm.dll using MidiOutLongMsg. I have trouble figuring out how to pass the parameters right.
I need to call three functions (midiOutPrepareHeader, midiOutLongMsg, midiOutUnprepareHeader), all of them having the same form
MMRESULT midiOutPrepareHeader(
HMIDIOUT hmo,
LPMIDIHDR lpMidiOutHdr,
UINT cbMidiOutHdr
where HMIDIOUT hmo is a handle that I have already. Troubling me are the other two parameters. cbMidiOutHdr is the size (in bytes) of the struct lpMidiOutHdr. This is a struct of the form
typedef struct {
LPSTR lpData;
DWORD dwBufferLength;
DWORD dwBytesRecorded;
DWORD_PTR dwUser;
DWORD dwFlags;
struct midihdr_tag far * lpNext;
DWORD_PTR reserved;
DWORD dwOffset;
DWORD_PTR dwReserved[4];
} MIDIHDR;
(Struct: http://msdn2.microsoft.com/en-us/library/ms711592.aspx
PrepareHeader http://msdn2.microsoft.com/en-us/library/ms711634.aspx
SendMessage http://msdn2.microsoft.com/en-us/library/ms711629.aspx
UnprepareHeader http://msdn2.microsoft.com/en-us/library/ms711641.aspx)
[Note: The full code for what I want to do can be found here http://www.borg.com/~jglatt/tech/lowmidi.htm (section "outputting system exclusive MIDI messages) - basically I need a translation of this code to LabView.]
The following are my problems:
a) How do I emulate a struct in LabView? (other threads suggest that this is done by clusters)
b) How do I pass a pointer to a struct (cluster?) to a DLL?
c) If I can use a cluster for this struct, how do I represent the LPSTR lpData in the cluster, i.e., a pointer to my data?
d) how do I get the struct size for cbMidiOutHdr?
This is how far I got, lots of it with the help of several threads in this forum:
a) use a LabView cluster
b) use "adapt to type" in the dll call (couldn't get this to work)
c) I use a type cast on my string in the hope that what it returns is the register address (and I'm probably superwrong here)
d) my cluster consists of 9 elements of 4 byte datatypes, so I just use 36 for cbMidiOutHdr
The dll seems to be happy with the way I pass the cluster - I get error codes of 0 in both the PrepareHeader and UnprepareHeader functions. However, sending doesn't work (error code 7). Guessing that the type cast returns a pointer, I have also cast the cluster to an Int32 and passed that parameter as pointer to numeric value. Interestingly, the PrepareHeader and UnprepareHeader functions are still happy, but I get a different error code from the sending (code 11)
Most of what I've done so far is guesswork, and I'm out of guesses now. I've attached the code to this post (it uses VIs from the NI MIDI example library ftp://ftp.ni.com/pub/devzone/epd/midi-example.llb ). I'd appreciate any help with this. Thanks!
Attachments:
Write MIDI SysEx Message.vi ‏21 KB

First off, this problem doesn't have anything to do with control references; those have meaning only inside of the LabView environment.
My first suggestion is to look for a higher-level library that will do whatever MIDI function you are trying to call. If you can find an ActiveX or .NET object that will control the MIDI subsystem, I recommend that you use it instead since it will be a lot easier.
If calling the DLL directly is the best option (and calling DLLs is absolutely the way to go when you need high performance) then you need to understand how LabView passes data to library functions. That is described here:
http://zone.ni.com/reference/en-XX/help/371361D-01/lvexcodeconcepts/configuring_the_clf_node/
As you can see there are a lot of ways to pass data, but they boil down to this: LabView can pass, via various levels of dereferencing, a pointer to some [mostly] flat data. Things are easiest when your DLL mimics LabView's own data storage methods. For example, wiring a cluster into a node set with Adapt to Type passes a handle (struct**, pointer to pointer to [mostly] flat data). So if you are writing your own DLL, it's pretty easy to write something that works nicely with LabView data (e.g., strings with 4-byte length headers, self-describing arrays) and in fact the result is cleaner looking than its "pure C" variant because of the self-describing arrays and string length prefixes. (I say "mostly" flat because LabView clusters with variable-length elements aren't stored in a flat format.)
When it comes to matching someone else's API things get harder, and in this case you are out of luck; you are going to have to write a LabView-callable wrapper function in C because LabView can't mimic the exact data structure needed. The problem is not the struct; there is a sneaky way to pass a pointer (vs a handle) to a struct, which is to do this:
Generate a cluster in LabView representing the struct (atomic numeric data only! no strings arrays etc!)
Flatten to string using native byte order.
Convert string to byte array.
Configure the call library function note to accept a pointer to an unsigned byte array. (NOT a C-string as suggested at the bottom of the page in the link above; your data may have internal 0x00s, and it certainly doesn't need an extra 0x00 at the end!)
The reason this works is that a pointer is just an address; as long as all the right bytes are in memory in the right order starting at that address, all is well. The DLL doesn't know that LabView thinks it is passing a pointer to an array of bytes, it just gets the pointer to the first byte and it reads and interprets those bytes according to its own struct def. Reverse the process cooming back from the DLL (convert byte array to string, unflatten from string against the LV cluster.) This method will work for any flat struct.
In LabView 8.5 there may be a less bogus way of doing this, which is to pass the cluster in with Adapt to Type and select "Array Data Pointer" as the format. This is new and I haven't tried it.
But in your case, you want to point to a struct that contains a pointer to a string plus some numeric data and another pointer, and this you can't do directly. LabView does not expose the location of a string to you anywhere outside the Call Library Function node, so there's no way to "find the pointer" to a LabView string from outside the DLL. What you need to do in this case is write a wrapper function in C that takes your LabView data. Only then will LabView "tell you where the bytes are" and promise not to fiddle with them until the library call is complete. Once you are in C-land, you can throw pointers around to your heart's content. As long as you do it all perfectly, all will be well. (If you write one byte too many on output, boom! :-)
There are a few ways to do this. You could make a cluster that has meaning in LabView, e.g. replace lpData with a LabView string, then pass the cluster in to your wrapper function set to "Adapt to Type"; that will pass a handle to the cluster. You can generate the .c file from the Call Lib Fuction, and it will outline where the data is.
Complications: In this case it's your job to convert the handle to the labview string (which has 4 bytes of length as a prefix and no trailing 0x00) to a C-string by malloc()'ing a new buffer and memcopying the string out. There might be something in the LV CIN tools that does this, I'm not sure. Make sure you release the new string after the MIDI call.
The lazy route (which is what I would do) is pass the string as the first arg and all of the numeric stuff as the second arg, leaving the space for lpData as you have now. (I don't know what struct "midihdr_tag" is, but if that's not something you were passed in a previous call, you'll need to add a third argument for that cluster and treat it similarly.) Then you can tell LabView that it should pass the string arg as a C-string pointer. Inside your wrapper, extract the pointers and stuff them into the data structure as needed. Dereference once (to go from handle to pointer) and make the MIDI call. To be clean, put everything back where it was before in the cluster; in particular don't believe you can pass out lpData* and do whatever you want with it in LabView; LabView will release/change that address as soon as you leave the output string unwired or do anything to it (e.g. concatenate.) You'll be creating a new string buffer and a new pointer on your next MIDI call.
All of this complication is a result of a) LabView's hiding the details of memory allocation/deallocation from you and b) LabView's internal data structures being a bit different from C conventions (e.g. LabView strings vs. C strings). The second means that even when LabView is using non-flat data structures (e.g. cluster containing an array), you can't just blindly pass them along to a C function and expect it to work right. It would be nice if NI would write a little mini-compiler into the Call Library Function that would do what our wrapper function is going to do, but that's probably a fairly significant project.
Still, each function wrapper is only going to have about 10 lines of C. You can put wrappers for all the MIDI functions you want to call into a single DLL, then ship that DLL with your app.
(Now you see why I suggested you look for an ActiveX MIDI control!)
-Rob Calhoun

Is it possible to use the UC-33e (surface control) with FCP ?

If it's the case, how can you do it ?
Thanks

No, FCP has no MIDI implementation to support generic assignable fader boxes. It's pretty much stick to devices that support the Logic/Mackie Control protocol. Unless FCP gets the proper System Exclusive handshake, it will ignore continuous controller messages.

About transaction logs

Can you tell me about transaction log space? how does it gets full? How is it related to performance?

Hi,
Monitoring the SAP Log Disk
Use
The size of the transaction log must be checked regularly to work out how much free space is available on the log disk. There should always be enough free space to allow the next file extension. When the SAP system has been installed the autogrow increment is set. At least the size of this increment should be available on the log disk to permit the next file extension. If less space is available and the transaction log file fills up, the SAP system will come to a standstill.
Ideally, the transaction log should never be filled to more than 60-70%. If the transaction log regularly exceeds this level between 2 transaction log backups, the transaction log must be saved at more frequent time intervals.
The size of the log can be assessed on the basis of information given for completed backups in the SAP transaction for Backup and Restore Information.
Procedure:
       1.      To access the transaction for Backup Restore Information choose CCMS ® DB Administration ® Backup logs.
Alternatively, enter the transaction code DB12.
The initial screen of the monitor CCMS Monitoring Tool u2013 DB12 (Backup Restore Information) appears.
       2.      Choose Backup history and then Logs Backup.
       3.      A result list appears. Find the largest transaction log backup of the past week. Select a row and then History info to find out the number of pages that were processed during the backup. To work out the amount of space used in the transaction log, multiply the number of dumped pages by 8 KB. You can then work out how much free space is left on the transaction log disk.
If you use a RAID1 disk system exclusively for the SAP transaction log and create hourly log backups, you will rarely encounter space problems. The SAP log file is initially created with a size of 1 GB. The smallest disk normally has 9 GB space and the log file can therefore grow to 9 GB.
Hope it Helps
Srini

Changing patches on an external keyboard in the middle of a track

I just figured out how to switch banks and patches on my external keyboard, which is a Kawai MP8II, from within Logic Pro. I would like to know if it is possible to switch patches in the middle of a track. How do I send a system control message that would accomplish this?

I presume by 'system control' you mean a sysex (system exclusive) message which isn't really necessary at all.
If you want the patch to change, locate the position where you want it to change, press 'pause' and then hit the record button. If you make the change to the program number while its in record mode, then turn off record, even though the transport hasn't moved, the change has been recorded.
Hope that's what you mean!

Any one know where I can download logic environments?

I have been trying to build an environment for my Novation Bass Station and found that most of the controls on it are only controllable via system exclusive commands. Only the two envelopes and the filter have been assigned controller numbers. Although I have had a small amount of success, it seems like it would be a lot easier to download an environment that some one has already built.
So...
my questions are:
1 - Does any one know of some good links to websites with free Logic environments.
2 - Does anyone have a logic environment for the Novation BassStation that
includes all of the System Exclusive controls.
Thanks, I'd be grateful for your support, I have been searching for ages and I cant seem to find what I'm looking for.
Future Mowgli #=O)

AirPort Utility 5.5.3 for Windows

Help, can someone help me debug? Read the crash log? Suggest a fix?

Hi,
I'm using an app called Unisyn. It's purpose to is to catalogue synthesizer configurations. The editor/librarian communicates using System Exclusive code, in hex, based on the MIDI protocol developed years ago. Manufacturers all have specific ID's built into the header files.
It works fine with my present day synths, however I recently purchased an older product which has been buggy at best. It has documentation and per the user manual it is supported. I've managed to create a profile successfully, but when I attempt to edit the parameters my Unisyn 2.1.1 crashes, consistently. Below I have pasted the crash log.
Host Name: Music-1
Date/Time: 2009-07-13 13:56:59.276 -0600
OS Version: 10.4.11 (Build 8S165)
Report Version: 4
Command: Unisyn 2 OSX
Path: /Applications/Unisyn 2.1 Folder/Unisyn 2 OSX.app/Contents/MacOS/Unisyn 2 OSX
Parent: WindowServer [57]
Version: 2.1.1 (2.1.1)
PID: 357
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 com.motu.unisyn 0x00041b08 TUProfile::RunProgram(short, TXORCLCaller&) + 576
1 com.motu.unisyn 0x00041818 TUProfile::DoStdXORCLMessage(short, TXORCLCaller&, bool, bool, bool) + 240
2 com.motu.unisyn 0x000781b4 TBankModule::Download(bool) + 804
3 com.motu.unisyn 0x00077d80 TBankModule::DoUpdate(bool) + 148
4 com.motu.unisyn 0x00038b70 TUDevice::DoUpdate(bool) + 164
5 com.motu.unisyn 0x000899f8 TUDevSet::DoUpdate() const + 148
6 com.motu.unisyn 0x00088030 TUDevSet::CmAuditionItem(TPatchContainer*, long) + 124
7 com.motu.unisyn 0x00082574 TLibraryFile::EvItemRepeatClick(long, unsigned short, short) + 60
8 com.motu.unisyn 0x00017d98 TLibraryWindow::EvItemMultiClick(short, long, unsigned short, TPoint&, short) + 52
9 com.motu.unisyn 0x0001f85c TMatrixListWindow::DispatchCellMultiClick(unsigned short, TPoint&, short) + 280
10 com.motu.unisyn 0x0001f69c TMatrixListWindow::EvLButtonDblClk(unsigned short, TPoint&) + 56
11 com.motu.unisyn 0x00093bc4 TWindow::EvContentClicked(EventRecord*, short) + 216
12 com.motu.unisyn 0x000552d8 UMacApplication::EvLButtonDown(EventRecord*) + 800
13 com.motu.unisyn 0x00054dc0 UMacApplication::DispatchEvent(EventRecord*) + 116
14 com.motu.unisyn 0x00054ca0 UMacApplication::Process1Event() + 96
15 com.motu.unisyn 0x000548dc UMacApplication::DoRun() + 244
16 com.motu.unisyn 0x000547d8 UMacApplication::HandleForeignExceptions() + 36
17 com.motu.unisyn 0x00054794 UMacApplication::Run() + 40
18 com.motu.unisyn 0x0004e5a0 main + 44
19 com.motu.unisyn 0x00003c88 _start + 460
20 com.motu.unisyn 0x00003ab8 _code_start_ + 48
Thread 1:
0 libSystem.B.dylib 0x9000af48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000ae9c mach_msg + 60
2 com.apple.audio.midi.CoreMIDI 0x97026ac8 XServerMachPort::ReceiveMessage(int&, void*, int&) + 84
3 com.apple.audio.midi.CoreMIDI 0x97019c80 MIDIInPortThread::Run() + 64
4 com.apple.audio.midi.CoreMIDI 0x9701df44 XThread::RunHelper(void*) + 28
5 com.apple.audio.midi.CoreMIDI 0x9702787c CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x9002b908 pthreadbody + 96
Thread 2:
0 libSystem.B.dylib 0x9000af48 machmsgtrap + 8
1 libSystem.B.dylib 0x9000ae9c mach_msg + 60
2 com.unsanity.ape 0xc0002afc _apeinternal + 3300 (icplusplus.c:28)
3 com.unsanity.ape 0xc0001910 _apeagent + 64 (icplusplus.c:28)
4 libSystem.B.dylib 0x9002b908 pthreadbody + 96
Thread 3:
0 libSystem.B.dylib 0x9002ec8c kevent + 12
1 com.apple.DesktopServices 0x92af9e50 TFSNotificationTask::FSNotificationTaskProc(void*) + 56
2 ...ple.CoreServices.CarbonCore 0x903ec794 PrivateMPEntryPoint + 76
3 libSystem.B.dylib 0x9002b908 pthreadbody + 96
Thread 4:
0 libSystem.B.dylib 0x9002bfc8 semaphorewait_signaltrap + 8
1 libSystem.B.dylib 0x90030aac pthreadcondwait + 480
2 ...ple.CoreServices.CarbonCore 0x903ec984 MPWaitOnQueue + 224
3 com.apple.DesktopServices 0x92afa4cc TNodeSyncTask::SyncTaskProc(void*) + 116
4 ...ple.CoreServices.CarbonCore 0x903ec794 PrivateMPEntryPoint + 76
5 libSystem.B.dylib 0x9002b908 pthreadbody + 96
Thread 5:
0 libSystem.B.dylib 0x90053f88 semaphoretimedwait_signaltrap + 8
1 libSystem.B.dylib 0x900707e8 pthreadcond_timedwait_relativenp + 556
2 ...ple.CoreServices.CarbonCore 0x903ec984 MPWaitOnQueue + 224
3 com.apple.DesktopServices 0x92b24b48 TPropertyTask::PropertyTaskProc(void*) + 72
4 ...ple.CoreServices.CarbonCore 0x903ec794 PrivateMPEntryPoint + 76
5 libSystem.B.dylib 0x9002b908 pthreadbody + 96
Thread 0 crashed with PPC Thread State 64:
srr0: 0x0000000000041b08 srr1: 0x100000000000f030 vrsave: 0x0000000000000000
cr: 0x84800482 xer: 0x0000000020000000 lr: 0x0000000000041f0c ctr: 0x0000000000041af4
r0: 0x0000000000000014 r1: 0x00000000bffff040 r2: 0x0000000000000000 r3: 0x0000000000000010
r4: 0x0000000000000030 r5: 0x0000000000000000 r6: 0x0000000000000000 r7: 0x000000000000a000
r8: 0x0000000000000000 r9: 0x0000000000000000 r10: 0x0000000000000000 r11: 0x00000000a32a6888
r12: 0x00000000000f5538 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000
r16: 0x0000000000000001 r17: 0x0000000000000003 r18: 0x0000000005d8da60 r19: 0x0000000005d30cf0
r20: 0x0000000000000000 r21: 0x000000000000000a r22: 0x0000000000000011 r23: 0x00000000001aff50
r24: 0x0000000000000000 r25: 0x00000000060f00b6 r26: 0x00000000001afe34 r27: 0x00000000bffff258
r28: 0x00000000060f008e r29: 0x0000000000000000 r30: 0x0000000000000001 r31: 0x00000000000418e8
Binary Images Description:
0x1000 - 0x177fff com.motu.unisyn 2.1.1 /Applications/Unisyn 2.1 Folder/Unisyn 2 OSX.app/Contents/MacOS/Unisyn 2 OSX
0x6ad000 - 0x6affff com.apple.textencoding.unicode 2.0 /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
0x8fe00000 - 0x8fe52fff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x901bcfff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90214000 - 0x90219fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x9028e000 - 0x90367fff com.apple.CoreFoundation 6.4.8 (368.31) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x903b1000 - 0x90688fff com.apple.CoreServices.CarbonCore 681.17 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x9077c000 - 0x907fcfff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x908de000 - 0x908defff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x908e0000 - 0x909e2fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x90a3c000 - 0x90ac0fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x90aea000 - 0x90b5cfff IOKit /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90b72000 - 0x90b84fff libauto.dylib /usr/lib/libauto.dylib
0x90fe9000 - 0x91001fff com.apple.WebServices 1.1.2 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x910d8000 - 0x91101fff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x91112000 - 0x91120fff libz.1.dylib /usr/lib/libz.1.dylib
0x91123000 - 0x912defff com.apple.security 4.6 (29770) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x913dd000 - 0x913e6fff com.apple.DiskArbitration 2.1.2 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x913ed000 - 0x913f5fff libbsm.dylib /usr/lib/libbsm.dylib
0x913f9000 - 0x91421fff com.apple.SystemConfiguration 1.8.3 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x91434000 - 0x9143ffff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x914fc000 - 0x914fcfff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x914fe000 - 0x91536fff com.apple.AE 312.2 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x91551000 - 0x91623fff com.apple.ColorSync 4.4.11 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x91676000 - 0x91707fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x9174e000 - 0x91805fff com.apple.QD 3.10.28 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x91842000 - 0x918a0fff com.apple.HIServices 1.5.3 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x918cf000 - 0x918f0fff com.apple.LangAnalysis 1.6.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x91904000 - 0x91929fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x9193c000 - 0x9197efff com.apple.LaunchServices 183.1 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x9199a000 - 0x919aefff com.apple.speech.synthesis.framework 3.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x919bc000 - 0x91a02fff com.apple.ImageIO.framework 1.5.8 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x91a19000 - 0x91ae0fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x91b2e000 - 0x91b43fff libcups.2.dylib /usr/lib/libcups.2.dylib
0x91b48000 - 0x91b66fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x91b6c000 - 0x91c23fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x91c72000 - 0x91c76fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x91c78000 - 0x91ce2fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x91ce7000 - 0x91d01fff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x91d06000 - 0x91d09fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x91d0b000 - 0x91de9fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x91e09000 - 0x91e47fff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x91e4e000 - 0x91e4efff com.apple.Accelerate 1.2.2 (Accelerate 1.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x91e50000 - 0x91f35fff com.apple.vImage 2.4 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x91f3d000 - 0x91f5cfff com.apple.Accelerate.vecLib 3.2.2 (vecLib 3.2.2) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x91fc8000 - 0x92036fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x92041000 - 0x920d6fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x920f0000 - 0x92678fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x926ab000 - 0x929d6fff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x92a06000 - 0x92af4fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x92af7000 - 0x92b7ffff com.apple.DesktopServices 1.3.7 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x92bc0000 - 0x92df3fff com.apple.Foundation 6.4.12 (567.42) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x92fc7000 - 0x92fc7fff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x92fc9000 - 0x92fddfff com.apple.ImageCapture 3.0 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x92ff5000 - 0x93005fff com.apple.speech.recognition.framework 3.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x93011000 - 0x93026fff com.apple.securityhi 2.0 (203) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x93038000 - 0x930bffff com.apple.ink.framework 101.2 (69) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x930d3000 - 0x930defff com.apple.help 1.0.3 (32) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x930e8000 - 0x93116fff com.apple.openscripting 1.2.7 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x93130000 - 0x9313ffff com.apple.print.framework.Print 5.2 (192.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x9314b000 - 0x931b1fff com.apple.htmlrendering 1.1.2 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x931e2000 - 0x93231fff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x9325f000 - 0x9327cfff com.apple.audio.SoundManager 3.9 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x9328e000 - 0x9329bfff com.apple.CommonPanels 1.2.2 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x932a4000 - 0x935b2fff com.apple.HIToolbox 1.4.10 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x93a58000 - 0x93ad9fff com.apple.SearchKit 1.0.7 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x947a5000 - 0x947b4fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x947bc000 - 0x947c9fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x9480f000 - 0x94828fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x96515000 - 0x96557fff com.apple.CFNetwork 129.22 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x97019000 - 0x97058fff com.apple.audio.midi.CoreMIDI 1.5 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x9f9a8000 - 0x9f9f5fff com.apple.CoreText 1.0.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x9fa20000 - 0x9fddbfff com.apple.CoreGraphics 1.258.77 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x9fe68000 - 0x9ff19fff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x9ff48000 - 0x9ffc3fff com.apple.audio.CoreAudio 3.0.5 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0xc0000000 - 0xc000ffff com.unsanity.ape 1.5.1 /Library/Frameworks/ApplicationEnhancer.framework/Versions/A/ApplicationEnhance r

In the Utilities folder (see GO in finder, choose Utilities item) you
can see Console and launch it from the folder; note it does have
some information on how to troubleshoot or decipher the crash
logs in various parts of the System.
And it doesn't look too complicated; except for the parts where
it tries to explain the meanings of those odd words in the logs.
Since I haven't gotten into using it for anything, that's all I know.
Good luck & happy computing!
PS: Was the application you were using built with this OS X
version in mind, or for one a bit older than Tiger 10.4.11?

System exclusive?

Similar Messages

Maybe you are looking for