How to make Kontakt player 5 work with Logic Pro X ?

I tried adding a library but it keeps showing desired file couldnt be loaded ! Is it something to do with 64 bit or 32 bit may be ? Someone knows how to get me out of it and successfully use kontakt libraries here in PRO X ?

No problems with Kontakt 5.3.0 here.. All works as normal with LPX. Both the Player and the Full versions of K5 are available as a 64bit AU plugin so no issues with that and LPX
So...
Make sure you are using the latest version of the K5 Player... thiough the fact you can access it within LPX tells me that's not the problem
Therefore note:
Not all libraries will work with the Player version however but that is by design...
Also not all libraries can be loaded in as a Library to the Library list but instead must be loaded via the K5 file manager...
So, what libraries are you trying to use with the Player version of K5?
What is the exact error msg you are getting when to attempt to add a library to K5

Similar Messages

How would Kirk Hunter EXS24 instruments work with Logic Pro 9

I understand that Kirk Hunter strings are quite good. Does anyone know how the EXS24 version would work in logic pro 9? Is it just a question of putting files in the correct directory so they show up in the media library, or is something else involved?
Thanks
(Note : The orchestral strings that come bundled with logic are disappointing. For a quantitative example, playing C1 (2 Cs below middle C) of the cello, there is no contribution at the fundamental frequency of ~65 Hz, as can be seen from an EQ analyzer.)

Kirk Hunter's EXS24 instruments work very well in Logic 9.
Drag the instruments folder here: User>>Library>Application Support>Logic>Sampler Instruments. (Or place an Alias of the KH instruments folder at the above location if you have your instruments stored on another drive.)
I placed the instruments in the above location but have the samples on an external drive when using my MPB, and on a separate internal HD in my MP.
Click on Options in the upper right of the EXS24 GUI to access Preferences. Make sure that Search samples on... is set to All Volumes.
The Diamond library is big bang for the buck when buying the EXS24 version. I also have the EXS 24 version of Concert Strings ll. But, it looks like KH is only going to release Kontakt versions of new products. I ended up also buying the Kontakt version of Diamond.

01v96i Yamaha...will it work with logic pro X

I bought the new Yamaha 01v96i Mixer but I can't make it works with Logic pro, in the list of available DAW I only find the 01v96 which is not the same and in-fact it does not work with the 01v96i.
Does anyone have an idea on how to set Logic for it or at least does anyone know if the new Logic Pro X has the new 01v96i in the list?

Lyford,
Again, in regards to hardware... it is not about LPX compatibility.. It is about compatibility with the OS X version and it's CoreAudio... Once you 'get' that point then everything else makes sense...
Tascam are notorious about leaving owners of "End of Line" products 'high and dry' when OS X is updated... and as you have found... the 1884 is not compatible with Mountain Lion 10.8.4 and likely will never be so... because Tascam will not be releasing Mountain Lion drivers for it.. so, it is not something you can use with LPX, which requires Mountain Lion 10.8.4 as a minimum requirement.
As an aside, Apple have acknowledged they make an error in simply using the LP9 Hardware compatibility chart for LPX (as LP9 could be used with earlier OS X versions for which there were drivers for the 1884 for example) and have said they will be issuing an updated version "in the near future"......

Will the Tascam FW-1884 work with Logic Pro X?

Hello,
I notice that the new Logic is 64 bit only and yet the Tascam FW-1884 is specifically listed as a supported control surface.
Tascam has not released 64 bit drivers for this device! Can anyone shed any light on this? Will it work only as a control surface and not an audio interface? Is the documentation in error? Anyone have this working with Logic Pro X?
Thanks,
Lyford Rome

Lyford,
Again, in regards to hardware... it is not about LPX compatibility.. It is about compatibility with the OS X version and it's CoreAudio... Once you 'get' that point then everything else makes sense...
Tascam are notorious about leaving owners of "End of Line" products 'high and dry' when OS X is updated... and as you have found... the 1884 is not compatible with Mountain Lion 10.8.4 and likely will never be so... because Tascam will not be releasing Mountain Lion drivers for it.. so, it is not something you can use with LPX, which requires Mountain Lion 10.8.4 as a minimum requirement.
As an aside, Apple have acknowledged they make an error in simply using the LP9 Hardware compatibility chart for LPX (as LP9 could be used with earlier OS X versions for which there were drivers for the 1884 for example) and have said they will be issuing an updated version "in the near future"......

Which MIDI keyboards work with Logic Pro x and Yosimite?

can anyone suggest some midi keyboards that work with Logic Pro x and yosimite

Hi Jacub,
I have a 2i4 running Mavericks 10.9.2 on a Mac Book Pro, and my unit works properly, please make sure your run the unit with the class compliant mode app (click the link below):
http://us.focusrite.com/downloads?product=iTrack+Solo
Please contact Focusrite support if you have any more concerns.
Best Regards,

Do you know if the Digidesign 192 will work with Logic Pro X?

Hi everybody! The question is simple, maube the answer too... Do anyone know if the Digidesign 192 I/O will (completely) work with Logic Pro X or if it needs other devices (such as controllers, internal or external card, etc.)? Thank you all.

Hi Jacub,
I have a 2i4 running Mavericks 10.9.2 on a Mac Book Pro, and my unit works properly, please make sure your run the unit with the class compliant mode app (click the link below):
http://us.focusrite.com/downloads?product=iTrack+Solo
Please contact Focusrite support if you have any more concerns.
Best Regards,

Will a Mackie Control Universal V.2.1.2 work with Logic Pro 9?

Will a Mackie Universal Controller V. 1.2.1 work with Logic Pro 9?

Mine does. There was something If I can remember how to do it about after the update selecting the controller to mackie controller. You have the option within the controller itself to be mackie controller or logic controller. If it powers up and says mackie controller, You should be fine. If you have a problem get back to me, Ill look for the link that tells you how to change it.

Wha wha pedal work well with GarageBand but don't want to work with logic pro 9.1.8 on my MBPro end 2011

Install on MacBook Pro end of 2011 with logic Pro 9.1.8 and Apogee GIO interface guitar
The wha wha pedal work well with GarageBand but not working with Logic Pro
Only the red light turning on and off at the screnn of the MBPro and on my Apogee GIO (Guitar Interface Midi) switch button but the effect wha wha won't work.
HOPE YOU UNDERSTAND MY ENGLISH

Pancenter...
Yes... but I have come across some setups that came with a native SL (and even one Lion!) installation.. that somehow had a corrupted or older Prokit installed for some unknown reason... and given it's a quick fix to try.. I thought I'd mention it..
I frankly don't think it is entirely a Prokit issue itself, but it wouldn't do any harm to try and install v7 just in case it is part of the problem...
+1 on the UAD stuff....
Also, at the time it crashed... according to the logs...the OP was running Ableton Live at the same time, presumably rewired with Logic... so add all that together with UAD plugins... and that's quite a load on the system...
Finally in thread 32 there is a weird exception msg relating to the Trash2 plugin.. that I haven't seen before...
Thread 32:
0   libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1   libSystem.B.dylib
0x94c2a267 mach_msg + 68
2   ...tope.audioplugins.AU.Trash2
0x667bd57a catch_exception_raise + 250
3   libSystem.B.dylib
0x94c57259 _pthread_start + 345
4   libSystem.B.dylib
0x94c570de thread_start + 34
That might be nothing... but as i said, I haven't seen that one before and given what else is going on.. it might be involved too... or nothing to do with that at all!

HT5812 Will East West Quantum Leap SILVER work with Logic Pro X ?

I wonder if EWQLSO SILVER edition will work with Logic Pro X. I can't think of any reason that it should NOT but if anyone tested please let me know. The software is quite old..
Thanks

it's worthwhile considering the VSL Special Edition, but check whether anyone else is running it on macbook, my iMac (also 4GB) is very happy with it, and some of the sounds are wonderful.
Best
Steve

YES! How to make PRINT QUOTAS WORK with 10.4

How to make PRINT QUOTAS WORK in 10.4
After struggling for quite some time, I finally found a pretty simple way to make print quotas work.
First, I’ll tell you our setup. We have 3 different computer centers with a variety of eMacs and new Intel iMacs, all clients are running 10.4.8, and each of those 3 centers has its own HP Laserjet 4200 printer. Our dual G5 server is running Server v.10.4.8. Client computers and printers have static IP addresses. All clients are bound to the server with the standard WorkGroup Manager/ LDAPv3 Directory Access scheme - such that all students login to the clients with their network username/password to mount their home directory on the client.
Next, I’ll tell you what does not work. IF YOU WANT PRINT QUOTAS TO WORK, you cannot use Workgroup Manager to assign a printer to any managed user account, user group, or computer group. Why? Because when you go to a client, and Show Info on the printer that is being pushed by Workgroup Manager, you’ll see that the queue name is not the queue that you’ve setup in Server Admin. Instead, you’ll see the queue name is “MCX” or something along those lines. Even if you manually edit the Workgroup print preference file that is being pushed to clients, it still will not work.
Drawbacks of my technique: In my case, students will see all 3 printers (1 from each lab) available to them no matter which lab they are in. Not the best, but for now I think it’ll be worth it to be able to control wasteful printing. Students may be able to move/delete the preference file (see below), but they’ll only be hurting themselves, as they won’t have any printers at all then.
Okay, here’s how I did it:
1. If you have setup any printers to be pushed out via Workgroup Manager’s preference enforcement to individual users, usergroups, or computer groups, turn those preferences off and leave them off.
2. Delete any existing printers in your Printer Setup Utility and/or Server Admin. Add and setup a new printer queue using the Server Admin> Print service. I added the printer through the Server Admin application, not Printer Setup Utility (may not matter). However, I did go into that latter utility to set the model of the printer. Now, back in Server Admin, edit the printer queue to turn on these services IPP, LPR (bonjour off), and of course check off the enforce quotas box. (No student Windows clients, so I didn’t tinker with SMB print service). I went ahead and specified the standard cover sheet – it will be handy while troubleshooting.
3. In Workgroup Manager, select the users that you want to enforce quotas upon, go to the Printer Quota tab (not the preference pane) and, in my case, I selected All Queues and specified a quota, and clicked Save.
4. Delete all printers that appear in the Printer Setup Utility from each client computer (I know, UGH).
5. For all network users, you need to edit a preference file and put it into each user’s home directory. That file is “com.apple.print.favorites.plist” and as you guessed, it needs to go into the Library> Preferences folder of every one of your network users’ home directories. Now, the content of that file is crucial… what it should show is the name of the queue(s) you created in Server Admin above, and be immediately followed by an “@” and the address of the server that is hosting that queue. For example, my queue’s name is TCStudentQ and the server’s address is student.mydomain.org… so my preference file has this entry: [email protected]. If you have more than one queue, you’ll have more entries. Be sure that the network user has at least Read level access under Group or Others. I’d recommend making the server System account the Owner of the file, and be sure to lock the file so the users can’t easily trash it. If you don’t know how to create this file in the first place, what you can do is go to a client computer, and log into the client with a dummy network account. Then open Printer Setup Utility, and you should see the queue you created in step 2. Add that printer, and then the file will be created in your dummy account’s home directory under Library> Preferences. Now you can use that file to distribute to other user’s folders… but don’t forget that each user needs Read level access.
6. That’s it. Works for me. When they exceed the quota, all that spits out is the cover page. It’d be nice if there was a quota monitor utility on the client side so users can see how many pages they have remaining and when the quota will automatically reset. I plan to start the quota on a Monday morning and go on a weekly duration. Not sure what a good starting point is… perhaps 25 pages every school week.
7. Hey Apple Computer, Inc. Server Developers & Project Managers, I truly hope you’re reading this and can explain why print quotas don’t function as you have documented and advertised. I don’t mean to toot my own horn, but I’ve spent way too much time discovering this workaround, and I know it will help thousands of others with the same problem. I can see where your Print Quota system breaks down, and I think you need to fix these issues or at least document them. Don’t forget to fix serious 10.4 Server bugs before leaving it behind for 10.5 Server – many of us will continue using 10.4 Server for at least another year or two.

David,
Your assumption that I didn't read the documentation is incorrect. I read that 10.4 documentation over and over - followed it to the letter to no avail. Perhaps it was updated in the last few weeks? So, do you have a fully operable printer quota system in conjunction with a managed computer or user group that has a managed printer pushed to the group via Workgroup Manager? I can push a managed printer to a managed group without a problem, but the quotas won't be enforced unless I use the workaround above and cut Workgroup Manager's managed/pushed printer out of the picture.
I know this is a user-to-user forum - however, I'm also aware that Apple tech support often chime in here, so it doesn't hurt to post a message to them in the context of a larger posting about a 'known issue'. I have used the server feedback form... hasn't seemed to me to be very helpful in the past.

USB Interface Not Working With Logic Pro 9

Hello,
I've had a Tascam US-1641 for several years now with absolutely zero issues on my old PC. Ever since I upgraded to Mac (early 2011 17 inch Macbook Pro running Snow Leopard) I've had nothing but problems with the US-1641. No matter how many times I uninstall-reinstall the drivers and what USB port I plug it into, whenever I turn on the device and it's connected to my Macbook, it crashes my operating system and it freezes everything I was doing. Logic Pro doesn't load and when it sometimes does (10 minutes later), it immediately crashes when I click anything.
I've tried several tips to fix it and nothing worked. The most popular choice was select the default input/output in Logic to the system audio, then quit Logic, turn on the interface, then restart Logic. No such luck. I have to reboot my machine at least 5 times, uninstall/reinstall the driver and hope it works to use the interface. I thought it was the operating system, so I upgraded to Mountain Lion and installed the new driver for Mountain Lion, after of course deleting the other drivers and removing all previous data, and it is still giving me the same problems.
I don't have the money to afford a replacement model or a different interface from a different company, so I'm hoping you guys can help me figure out what exactly it is that's causing the interface to freeze my operating system and crashing my Mac whenever I try to use it. I am getting extremely frustrated at this and as much as I love OSX and Logic, what good is this piece of software if I can't use it? I need help.
Thank you.

The problem lies with Tascam and their inability to write stable drivers for OS X... and isn't anything to do with Logic Pro ..
As you know, you are not the only person to have had this issue and the reality is, while the 1641 might work fine with Windows, when it comes to OS X Macs.. it's an entirely different story... depending on the version of OS XS you are running.
The one tip I have read, that seemed to fix it for most people.. (Though not all) is as follows;
(Thanks to Paulypaulpaul for this)
-uninstall your tascam driver 2.10
-restart
-install driver 1.03
-restart
-plug in your tascam
-goto where you download your drivers (http://tascam.com/product/us-1641/downloads/), scroll down to the bottom where it says firmware, Download the firmware 1.02 (3rd from top under firmware), install it. your control panal should now read 1.03 for your drivers and 1.02 for your firmware.
-install drivers 2.10
-restart
Follow each of the steps exactly.. including all restarts when indicated..
...and good luck...

Which 61 key midi keyboards work with Logic Pro X (10)? M-Audio, Novation, Akai, Roland???

Hi. I'm new to this community but would really appreciate some help.
I'm struggling to find a 61 key midi keyboard which works properly with Logic Pro X.
I was looking into getting either the M-Audio Axiom 61 or Novation Impulse 61 but all I can find on google etc. is people saying they don't work properly.
Has anybody got a 61 key which works seamlessly with Pro X?
Any help would be much appreciated.
Thanks.

To "The Art Of Sound"
Hi. I doing next.
1. I create new project
2. I select Yamaha Grand Piano
3. I play something in "live" mode. All is ok
4. I play something in "Rec" mode. All is ok
5. I record second track with the same instrument, with Yamaha Grand Piano. All is ok
6. I record third track with Yamaha Grand Piano. All is ok again.
7. Now I muting first or second track and... third track plays wrong notes! I unmute first track, but third track still to play wrong notes! Why???
Ok. I continue experiment with created project. I have three Yamaha grand Piano tracks and I creating new software instrument and assing Hovering Machine to it. I try to play in "live" mode something. And I get interesting effect. If I play short notes (sixteens, for example), I can play for one minute without problem. And Logic Pro X starts to play wrong notes after this time delay.
If I start to press chord notes without breaking, Logic Pro X plays for 15-30 secounds normally and starts to play wrong notes them.
Well. I turn off all plugins and effects from instruments. But Logic Pro X countinues to play wrong notes!
I experimented with NI Kontakt 5. Kontakt plays wrong notes!
I experimented with LUSH-101 plugin and minimoog. This two instruments play correct notes always!!! WHY????
Why some instruments play wrong notes and other instruments play correct notes in the same project?
I wrote wrong in my previous post. I got this problem with Logic Pro X 10.0.3 update.
Actually I have serious problem now. I opened projects created in Logic Pro X early and I have this problem in ALL projects. This's commercial projects and my partners asked me already about release date... What must I answer?

Novation Remote 25SL Not Working with Logic Pro (Logic Automap)

Hi,
I can't seem to get my new Novation Remote 25 SL to work in Logic Automap mode.
I have the Remote SL in Logic AutoMap (template #39). When I launch Logic Pro 7, The Remote SL shows : "Logic AutoMap" on the Left LCD display, and nothing else happens, it seems to be frozen at this state. The Up/Down arrows on the Left side don't change anything.
Any clues why this is happening ?
I have read many posts on this and other forums of user issues in setting the Remote up properly, and have it work in Logic Automode. Tried many configurations, and settings, re-installed sw, OS 1.0.13, but no luck so far.
I would like to hear from Logic Pro 7 users who have successfully setup their Remote SL with Logic Pro 7.2.1 in Logic Automode, and are working with this system without any issues.
This will be very helpful in figuring out if there is something wrong in my settings, or if the unit itself is defective, or I am doing something wrong during the installation of the software ? I have been trying to get this thing to work for the past two days, with no success so far.
The Remote SL should be a wonderful controller for Logic Pro 7 (once it works !) so, I'm being as patient as I can with this thing.
I'm using Logic pro 7.2.1 on a Mac G5 2.5 Quad, Mac OSX 10.4.6
Thanks.

Hi Blaze,
I tried your settings, but no change, the Remote SL is still frozen showing :
"Logic Automap" on the left LCD .
You mention setting "Mixer View 64" well the parameter I see is called :
"Mixer View Fader" which I guess is the same one you are referring to. I set it to 64, it was set to 8, but has not changed anything. Still having the same problem. This problem is dragging into Day 3, what a bummer.
Thanks.

Preamps/comp working with logic pro 7

Ther is so much to choose from in the preamp/comp world.I have looked at focusrite,and joemeek.My spending limit is around $700.Im looking for a all in one unit(preamp/comp,with an optical out.Im welcome to any ideas,Im getting a G5,with logic pro 7.Right now i have a G4 laptop,with a firewire 410 from m-audio,Thanks Derek
powerbook g4/powermac G4 dual 1.25Ghz Mac OS 9.2.x Logic audio platinum 4.8.1/Logic pro 6

your preamp/comp has nothing to do with logic pro 7, they will all work, there are probably better places to ask for help with this kind of question, such as gearslutz.com

Nexus 1.4.1 stopped working with Logic Pro X

Hello Guys! I am currently using Logic Pro X on Mavericks 10.9.4. I have been using refx Nexus 1.4.1 with Logic Pro X with the help of another application called 32 lives that allows 32 bit apps to be used with 64 bit apps but all of sudden it stopped working and I get " validation result: couldn't be opened". I also tried uninstalling and reinstalling the app to no avail. I'm attaching a screenshot. I hope this helps. What can I do to resolve this issue. Thanks.

Then... either you have a problem with your system... Permissions issue maybe...
or you are using an out of date version of 32Lives... (Update to v1.4)
or you are using the pirated version of Nexus 1 (Buy the legal version..as v1.4.1 cracked is known to have issues under the latest OS X versions..)
Because I just tested a legal Nexus v1.4.1 with 32Lives v1.4 (I had an old copy that I reinstalled on one of my testbed Macs here as i use Nexus 2 these days..) and with both Mavericks and LPX (10.9.4 and 10.0.7) it all works fine here without issue....

Will my Kurzweil PC3 work with Logic Pro 9?

I spent months looking for the right keyboard--what I mean by 'right' is one that I felt sounded best. I ended up with a Kurzweil PC3.
Before I purchase Logic Pro 9, does anyone know if I can use the sounds on board (Kurzweil objects) with Logic Pro 9, instead of using the built-in sounds (objects) in Logic Pro 9? If so, how does one do it? I don't want to use this beautiful keyboard as just a MIDI controller.

My own setup is similar to your discussion. I use a Native Instrument Komplete 6 audio unit as the interface for both midi and audio into and out of Logic Pro 9.1.8. You can set up a Multi-channel instrument in the Logic environment, or use the External Instrument plug-in. In any case, there is a fair learning curve to get this right, but the multi-instrument in the environment is completely capable of controlling the PC3 if you set up the correct Bank change and program change messages. There is one major problem that I am having and that is using PC3 Setup mode. If you set the PC3 into Setup mode and hit some notes, it produces a midi-feedback loop between Logic and the synth, causing the PC3 to go insane if you are connected using the USB port. This is because the midi out from the PC3 is sent thru the Logic track and back out to the PC3 causing a midi feedback loop. In program mode it isn't as bad but does cause a small amount of delay echo. The only way I have got around this so far is to connect using midi cables instead of USB then when recording I disconnect the cable from the Komplete 6 to the PC3 midi in, leaving only the midi cable from the PC3 out to the Komplete for recording to Logic (while monitoring what I am playing via the PC3 audio outputs). Then when I want Logic Pro to drive the PC3, I disconnect the midi in to Komplete and reconnect the midi out to the PC3. Playing the recorded Logic track now drives the PC3 without any feedback. But, there has got to be a better way! Any ideas would be appreciated.
I think this result is because Logic always sends midi notes thru to midi output. Is there some way of preventing this?

How to make Kontakt player 5 work with Logic Pro X ?

Similar Messages

Maybe you are looking for