Simple multi thread example

Hello I am still confused as to how to run parallel processes. I am looking for something very simple so that I can understand better. If possible I would like to see an example that basically starts a vi that writes to a file. For example the vi has a for loop that runs 10 times each time it generates a new instance of a program that writes the number associated with the for loop to the file 2 times. So basically after the program is run the file will read.1122334455667788991010...or have some numbers mixed up depending on how fast each thread ran. I guess the vi would have some controls on the front to adjust the number of times so that the user could get the idea of how the threads would end up writing of order...This is a common example similar to "hello world" of multi threading programs in most languages so I figured that there would be something like this somewhere...but I can't find it. If anyone can point me in the right direction I would appreciate it thanks.

Hmmm. I cannot locate a good example for you, but I know it's possible.
So I created my own example (I THINK I saved it in 8.5 format)
YOU NEED TO HANDLE ERRORS - this example doesn't.
But it does do what you asked.
It spawns any number of subVIs, all of which run independently.
Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com
Blog for (mostly LabVIEW) programmers: Tips And Tricks
Attachments:
Spawning.llb ‏39 KB

Similar Messages

Example multi-thread program

Hi,
Can anybody tell me where can I find a multi-thread (THREADED_MUTEXED) occi example?
Thanks in advance,
Jose LUIs.

Hi,
Can anybody tell me where can I find a multi-thread (THREADED_MUTEXED) occi example?
Thanks in advance,
Jose LUIs.

Enterprise User and Multi Thread Server

Hi,
We are going to build a system which uses a configuration:
10g2
Enterprise User
Multi Thread Server
Client apps accesses db over JDBC/SSL
Could some please share experience about issues regarding
using Enterprise User and Multi Thread Server ?
Is MTS transparant for Enterprise User authentication ?
Regards,
Cezary

If you build simpserv with -t, and set MIN and MAXDISPATCHTHREADS, you
should have an example of a multithreaded server.
Scott
Johan Philippe wrote:
>
We have been going to the documentation on multi-threading and contexting in servers
on Tuxedo 7.1.
And the impression so far is that apart from the function definitions there is
not much information around.
Didn't even find a simple example of a multi-threaded server in the Bea refs yet.
Does anyone know/have such an example?
And is anyone using multi-contexting in a server, because the limitation that
only server-dispatched
thread get a context puts quite a limitation on its usefullness.

Writing a multi-threaded server

Hi. I'm working in a starting project here at my company and, as a requirement, I must implement a multithreaded server using SSL connections (SSL over Socket). The secure connection is no longer a concern (after a lot of struggle, I build a simple client/server over SSLSockets that actually works), but I still need to build all the multithreaded code... I'm needing some guidelines and design ideas. Any ideas? Can someone post some interesting links about this subject?
Thanks in advance!

>
For example why must it be multi-threaded in thefirst
place?Because it will serve a few tens of people
concurrently.
tens? Like 50 people or 500 people?
And how many threads? 3 or 60,000?I do not know yet, but I'm assuming it will be one
thread per socket connection and possibly another few
threads doing housekeeping stuff (managing files,
etc)
And how long will a thread last? What sort of
processing will it do?Ain't got all requirements yet!! But basically (at
least what I understood) it's going to receive lots of
data, process it and re-route the data to a mainframe
So 5O (or 500) people are going to connect...
1. Once a week and deliver 10 giga bytes of data?
2. Once a minute and deliber 10 giga bytes of data?
3. Once a week and deliver 1,000 bytes of data?
4. Once a minute and deliber 1,000 bytes of data?
And then the general questions for any 'server'...
-What happens when the server (box or application)fails
Well, nothing has been said about that matter yet, but
I guess the server got to resume (or discard)
unfinished stuff (depending on the status of the
received data before the connection was lost)
And how is it going to do that on the 'mainframe'?
Two easy paths.
1. The mainframe has a database interface AND the data volume is low enough then you can use transactions.
2. The data does not have to be committed at once. This could be because it just doesn't always need to go, or because it is 'sequential' (which still requires code but not much.)
Really hard paths.
1. 'Lots' of data and it all must be committed at 'once'.
2. There is no database interface and data must be committed.
-What is the expected scaling requirements?No clustering involved - it will run on a single
machine, during a limited time. The system in question
is a 'contingency control' (not sure about this term
in English), so it will run when (and if) our client
get screwed in any way - their buildings destroyed,
that kind of stuff...
-How will it be maintained?Sorry, I didn't understood, could you clarify?
Someone has to make sure the box and application is running. Who is going to do that? What tools will they need to do this?
If it is you and the users call you directly if it doesn't work then it is easy (code wise.) If it is someone else then you will need to provide tools to ease that. And if someone expects it to work in an automated management system (like with SNMP) it is going to be even more complicated.

Multiple Containers read/write access in multi-threaded environment

I'm been reading the Berkeley DB XML Transaction Processing document and have a few questions. I have a multi-threaded environment (not multi-process).
1) In the "Summary and Examples" section, there is an example of several worker threads that perform many writes to a shared container. The one container is passed to all the worker threads, rather them having their own instance of the container. In my application, I could potentially have multiple worker threads acting on the same container, is it better to provide some type of connection pool, so each thread has access to the same container? Is their a problem with each thread creating a new instance of the container and writing to that? Is their pros and cons to each approach?
2) In some specific web applications, they only require read-access and have no intention of writing to the database. If the environment was created with transactions, can these applications open the environment in read-only mode, so as to not suffer the performance penalty of using transactions? Or do they still require transaction support since other threads in other applications might be writing to it. Is it better in this case to
3) Is there any decent connection pooling framework that work well with BDB XML? If transactions are involved, it seems pretty important to always close the container once you are finished with it, which kind of defeats the purpose of pooling. I see a container somewhat analogous to a JDBC transaction, where in connection pooling these transactions remain open, but in BDB XML, it doesn't seem like this is good practice. So clarification here would be appreciated.
Thanks in advance...
Chris

Chris,
I'd be careful about trying to draw too many analogies with other sorts of systems. In many ways BDB XML is simpler -- it's just a library, no server process.
An open container is analogous to an open file handle/descriptor in your operating system. It can safely be shared by all threads within a given process. In fact, you should not create more than one -- while that works, it can just be confusing, and a source of errors (for example, if you use a different path to open the container each time, you'll have problems). So by all means share them. Most Java applications just point them in a class that is accessible to all threads.
Other objects that can, and should be shared among threads include:
Environment
XmlManager
XmlQueryExpression
Most others should not. You also mention closing your containers -- there is no reason to close your active container objects until your application needs to shut down. A long-running application will want to use db_checkpoint (or equivalent) to ensure that modified pages are flushed from the transaction log to the database files, but that's about it.
As for concurrency, you obviously need transactions for concurrent write operations. If you want concurrent read access to the same containers, they should use transactions as well. Even if you don't explicitly use transactions, locks are always taken on pages in transactional containers. You cannot open the same container transactionally and not transactionally at the same time -- bad things could happen.
Depending on your performance needs, you could using snapshot concurrency, and see how it works for you. While locking does incur some overhead, it may be acceptable.
You mention creating your own "snapshot" of a container and running read-only on that copy. That's possible to do, but you have to be careful of how you create the snapshot (following hot backup procedures). Also, if you intend to open that "new" container in the same environment or application as the old one, you need to run a program on it to change its internal identification so Berkeley DB won't think it's the same file. That is, you can't just copy a container file to a new name and just open it like it's a new container if it's still in the vicinity of the original. See the -r option for the db_load program.
Now that you are probably really confused, good luck!
Regards,
George

Multi threading under single file channel

Hi,
We have File-Proxy scenario .
We are using fCC sender channel and using
recordset sequence as varaibale
recordsets per message was 250.
When large size file like 2GB was processed, PI is taking 45-50 min to process the file and from proxy end its taking 8 hrs to process this file.
we are using one channel and 250 recordsets per message by chunking file and process to target. We are following EOIO for sequence for these chunk files.
with this approach in PI target system proxy is taking huge time to process.
experts suggested using multi threading and multiple channels are the ideal solution for this issue.
am expecting with multiple channels and multi threading will cause issue for receiver proxy because of more objects and current approach is fine.
Please suggest any other alternatives we can acheive in PI with respect to this issue?
Note: I checked blog for file chunk option under Adv parameters and I cant use that here as FCC and Mapping is there .
Rgds,
aman

Hi Aman,
We had file to proxy interface and the XML payload of the proxy was around 400mb...to reduce the time taken in PI in mapping step we reduced the XML payload of the proxy by cutting the XML tagnames.
for example an xml field <firstname>Anand</firstname> was converted to <f>Anand</f>
with this we were able to achieve about 40-50% reduction in XML payload the file and a good improvement in the time taken by PI mapping to process the file.
Hope it helps,
Thanks,
Anand

Multi-Thread application and common data

I try to make a multi-Thread application. All the Threads will update some common data.
How could I access the variable �VALUE� with the Thread in the following code:
public class Demo {
private static long VALUE;
public Demo(long SvId) {
VALUE = 0;
public static class makeThread extends Thread {
public void run() {
VALUE++;
public static long getVALUE() {
return VALUE;
The goal is to get the �VALUE� updated by the Thread with �getVALUE()�
Thanks for your reply
Benoit

That code is so wrong in so many ways......
I know you're just experimenting here, learning what can and can't be done with Threads, but bad habits start early, and get harder to kick as time goes on. I am going to give a little explanation here about what's wrong, and what's right.. If you're going to do anything serious though, please, read some books, and don't pick up bad habits.
Alright, The "answer" code. You don't use Thread.sleep() to wait for Threads to finish. That's just silly, use the join() method. It blocks until the threads execution is done. So if you have a whole bunch of threads in an array, and you want to start them up, and then do something once they finish. Do this.
for(int k=0; k<threads.length; k++) {
threads[k].start();
for(int k=0; k<threads.length; k++) {
threads[k].join();
System.out.println("All Threads Done");Now that's the simple problem. No tears there.
On to the java memory model. Here where the eye water starts flowing. The program you have written is not guarenteed to do what you expect it to do, that is, increment VALUE some amount of time and then print it out. The program is not "Thread Safe".
Problem 1) - Atomic Operations and Synchronization
Incrementing a 'long' is not an atomic operation via the JVM spec, icrementing an int is, so if you change the type of VALUE to an int you don't have to worry about corruption here. If a long is required, or any method with more then one operation that must complete without another thread entering. Then you must learn how to use the synchronized keyword.
Problem 2) - Visiblity
To get at this problem you have to understand low level computing terms. The variable VALUE will NOT be written out to main memory every time you increment it. It will be stored in the CPUs cache. If you have more then one CPU, and different CPUs get those threads you are starting up, one CPU won't know what the other is doing. You get memory overwrites, and nothing you expect. If you solve problem 1 by using a synchronized block, you also solve problem 2, because updating a variable under a lock will cause full visiblity of the change. However, there is another keyword in java.. "volatile".. A field modified with this keyword will always have it's changes visible.
This is a very short explaination, barely scratching the surface. I won't even go into performance issues here. If you want to know more. Here's the resources.
Doug Lea's book
http://java.sun.com/docs/books/cp/
Doug Lea's Site
http://g.cs.oswego.edu
-Spinoza

Using multi threading to access 2 RS232 ports

Hi,
I'm a beginner in multi threading, so this question may be a very basic one....
I'm Using TS3.5 + CVI 8.01 to communicate withs 2 RS232 ports. I thought to use mult threading so I can process 2 steps in parallel rather than in series.
This is what I do:
1) I defined 2 subsequences, each of them call the same CVI function. I use the sub sequence parameters to transfer the com number.
2) My CVI application includes one dll for this specific project and another one, a general dll to handle RS232 functions. The RS232 dll uses one global buffer than collects all the traffic on the com.
QUESTIONS:
1) What happens when 2 seperate threads run the same function in the RS232 dll? (in terms of memory etc...). Does each one use a different buffer (in terms of memory allocation), or, both of them writes to the same buffer? Obviously, if they writes to the same buffer, then, my function will not operate properly.
2) What happens in TestStand after the 2 steps in new threads have finished their execution? does the next step run back in the same threads the sequence run before?
Thanks
Rafi

Rafi,
Glad to hear you were able to make some ground on your application. As for all of your questions, I'll try to answer as many as I can.
First, when you are talking about your global buffer, is it created in TestStand or in the DLL itself? When you use DLLs, global variables or global structures are shared between all threads that call your DLL. On the other hand, if your buffer is declared inside of the DLL it is global for the DLL but not shared and would be a separate buffer for each call.
With your run-time error in TS, it would definitely be helpful to have more information about the error. From what you explained (executing fine on the first call, but failing on future executions), it sounds like the resource is not being released after the first execution.
As far as a specific example for TestStand Multithreading, you'll want to look at the TestStand Development Library and, specifically, Multithreading in TestStand. If you look and browse through the Application Notes and Tutorials section, as well as the Technical Presentations section, you will learn a great deal about multithreading and what options you have in TestStand. For a specific example, you may want to look at This Example. You could also look in the <TestStand>\Examples (where <TestStand> is the directory where TS is installed) at the MultiUUT example for an example of multithreading in TS. These examples may not be exactly what you need, but they should give you a jump start.
As far as making your DLL multithread safe, it is definitely not necessary; however, there are some significant advantages described in this article: Designing Thread-Safe DLLs. It is an MSDN article that focuses on Visual Basic, but it has some helpful information that can apply to C as well.
Hopefully this can help you move further. I have attached a list of links at the end of this post with other helpful links for you as well. Keep us posted with your progress.
Matt Mueller
NI
Links:
General Information on Multithreading for C Programmers
Building Multithreading Applications with LabWindows/CVI
Multithreading in LabWindows/CVI
Easy Multithreading Programming in LabWindows/CVI
Multithreading for Rookies

Analysis for Office support multi thread?

Does Analysis for Office support multi thread/core? If so, what verison? I tried searching around this site as well as note 1466118 - Hardware & Software requirements for Analysis, edition for MS Office but was unable to find an answer.
I am on an Intel dual cpu with hyper threading turned on so it essentially looks like 4 cores. When I execute an Analysis View, I rarely see the EXCEL.EXE process go above 25% CPU utilization. I have plenty of RAM and hard drive space.
64bit Windows 7
32bit Office 2010
AAO 1.3.5.2288
Thanks

I found the following info at:
Excel 2010 Performance: Performance and Limit Improvements
Large Data Sets and 64-bit Excel
The 64-bit version of Excel 2010 is not constrained to 2 GB of RAM like 32-bit applications. Therefore, 64-bit Excel 2010 enables users to create much larger workbooks. 64-bit Windows enables a larger addressable memory capacity, and 64-bit Excel is designed to take advantage of that capacity. For example, users are able to fill more of the grid with data than was possible in previous versions of Excel. As more RAM is added to the computer, Excel uses that additional memory, allows larger and larger workbooks, and scales with the amount of RAM available.
In addition, because 64-bit Excel enables larger data sets, both 32-bit and 64-bit Excel 2010 introduce improvements to common large data set tasks such as entering and filling down data, sorting, filtering, and copying and pasting data. Memory usage is also optimized to be more efficient, in both the 32-bit and 64-bit versions of Excel.
Multi-Core Processing
Additional investments were made to take advantage of multi-core processors and increase performance for routine tasks. Starting in Excel 2010, the following features use multi-core processors: saving a file, opening a file, refreshing a PivotTable (for external data sources, except OLAP and SharePoint), sorting a cell table, sorting a PivotTable, and auto-sizing a column.
For operations that involve reading and loading or writing data, such as opening a file, saving a file or refreshing data, splitting the operation into two processes increases performance speed. The first process gets the data, and the second process loads the data into the appropriate structure in memory or writes the data to a file. In this way, as soon as the first process beings reading a portion of data, the second process can immediately start loading or writing that data, while the first process continues to read the next portion of data. Previously, the first process had to finish reading all the data in a certain section before the second process could load that section of the data into memory or write the data to a file.

MUlti-threading concept

Hi All,
Want to know how we can multi-thread a program for a particular PLSQL code in Oracle EBS for which the child thread doesn't consume any thread in the front-end even though it executes with user-specified threads?

Hi;
Please review below notes which could gives you some idea:
How Does iPayment Use Multi Threading? [ID 983478.1]
http://orabiz.blogspot.com/2010/06/ebs-plsql-multithreading-example.html
Can I have multi-thread program in EBS
Regard
Helios

Multi threaded programming

I am quite new to multi threaded programming.
The problem I am facing in my code is as follows:
I can instantiate 1-10 threads from my controller class. For example if my controller class generates 10 threads, 5 threads
finish the task they are assigned to do(i.e send SMS and Update the Database) and the other 5 threads eventhough send SMS but
get stuck when they are supposed to update the Database (this is inferred from the logs).
Due to this problem my controller class remains in a wait state as I am using the join() method and some of the threads never
join.
Another interesting observation is that it always happens that the thread numbered 0-5 always get stuck at the exact point
where database has to be updated and thread number 6-10 complete their task. Same is the case when i instantiate 2 threads, i
thread completes its task and another thread gets stuck, again at the same point.
I am using Connection Pooling to connect to the database.
I am sure that the problem is with the query
int j=dbObject.execute_pst("UPDATE table SET flag='true' WHERE message IN("+trueFlag+")",con);
where true flag is a comma seperated string containing some ID's.
What i cannot understand is why some of the threads (almost 50% of them), work fine with this query and the others get stuck
(i.e. just wait at this query during runtime)

The problem must lie in the connection, as the SQL statement is to basic to cause an endless loop inside the DBMS. If you are in doubt, try the setMaxRows() method of the Statement interface, I'm using Sybase and it also limits the number of rows processed in update and delete statements (which I'm pretty sure is buggy, but you can still try it).
Which DBMS are you using by the way?

Is ABAP multi-threading safe?

When implementing the Singleton design pattern in Java, we must use keyword <b>synchronized</b> with <b>getInstance()</b> method to ensure multi-threading safety, so that we can get the one and only instance.
What shall I do in ABAP? or just leave it alone? Would you help me find a example?
thanks and regards,
Davin,WANG

Hi Davin,
I do not understand fully what you are going to do in ABAP terms so I hope my comment will be of any value.
Multithreading may be achieved in ABAB by calling a function with the addition STARTING NEW TASK IN GROUP.... See my sample program for <a href="https://wiki.sdn.sap.com/wiki/display/Snippets/Easilyimplementparallelprocessinginonlineandbatchprocessing">Easily implement parallel processing in online and batch processing</a>
The second question may be solved by help of SAP lock concept. This is used primarily to secure a consistent database by not allowing two processes to change data at the same time. Chose a lock object of your choice and set at start of first instance. At end, remove the lock. Before creating the second instance, try so set the same lock. If you get a foreign lock error, you know the process is running.
See documentation on lock objects on how to lock/unlock.
Regards,
Clemens
Hope your internet connection is broken no longer so you can read this.

Clarification of the handle/body idiom in multi threaded applications

Hello
As some DBXML classes use the handle-body idiom (handle/body idiom in some docs), could someone please clarify the consequences of that in a multi threaded application like a web container?
For 100% Java people, like me, this is known in the Java world as 'programming towards interfaces', or as the Bridge pattern; which is seen as good practice.
Let's take an example. The class XmlQueryContext is not thread safe, but it has a copy constructor. Imagine that your web application has one XmlQueryContext, that we never use in a query, but that we prepare only to be copied in new threads. Is it thus safe to instantiate various new XmlQueryContexts using that copy constructor in various new threads and use them simultaneously?
Thank you
Koen
PS What I am really asking here is if somebody could please translate the following to Java parlé:
A copy constructor is provided for this class. The class is implemented using a handle-body idiom. When a handle is copied both handles maintain a reference to the same body.

As a Java user you do not have to worry about how the C++ copy constructors behave. In the Java API if a copy constructor exists for the object, then the copy constructor will copy all of the original object's data into a new object (XmlContainer is the one exception to this rule, generally one should not use that copy constructor at all). So in short, what you plan to do will work.
Lauren Foutz

Some general questions about multi-threading

Hey Everybody,
I have a dilemma with a multi-threaded program that I have written.
Well to be truthful I actually wrote the program with no consideration whatsoever for multithreading.
As a result of this complete lack of concern I get a completely hung user interface.
My program performs a lot of network communications over URL��s and also writes information from URL��s to disk. The combination of networking and I/O in my program and the fact that I have not built multi-threading into the program has lead to complete failure of the user interface. When I say complete failure I mean complete failure. If it were only button��s not responding then I wouldn��t be all that worried, however the entire drawing area of my programs ��Frame�� completely freezes. It��s cool if nothing is maximized or minimized over the frame but as soon as this happens my programs drawing area has a ��serious hang over!��.
I have begun learning about threads, in principle they sound wicked however in practice they have proven to be a brain tease (oops �K.. honesty).
The difficulty of threads should not be all that daunting to me, however I have a couple of very simple questions that I would love to have answered�K..anybody out there!!!!!!!!!
This is the normal basic method of running a thread that I have been attempting to incorporate into my program:
1). Extend the thread class,
2). Override the run() method in the subclass (created from step 1),
3). Create an instance of the subclass,
4). Call the start() method on the instance (from step 3).
I have read that every statement the thread will execute is contained within it��s run() method.
Question 1). This being the case is it possible to have member variables or methods inside a class that extends thread? Please explain!
Question 2). Can a class that extends thread contain a constructor? Please explain!
Question 3). If a subclass of thread cannot contain a constructor as I assume to be the case then how can code executing within the newly spawned thread reference information from the object that spawned it?
If anybody out there on the great net can answer even half of one of these questions I will be more than grateful. Thanks for your time, and rock on Java!
David

Thread t = new Thread(MyRunnableDerivedClass);
t.start();I hope it is understood that MyRunnableDerivedClass is actually an object of the MyRunnableDerivedClass. sorry for the confusion.
so here's a thread that reads from a file using constructors, member variables, other funcs. It's not optimal but shows use of all of the above. I just typed this in so there are probably syntax errors, but you should get the point.
public class ThreadedFileReader implements Runnable
    private File m_File;
    byte[] contents = new byte[0];
    public ThreadedFileReader( File f )
       m_File = f;
    public void run()
        BufferedInputStream bis = null;
        try
            bis = new BufferedInputStream( new FileInputStream( m_File ));
            int avail = bis.available();
            while (avail > 0)
                int oldLen = contents.length();
                contents = expand( contents, avail );
                bis.read( contents, oldLen, avail );
                avail = bis.available();
        catch (Exception e)
        { //do something witty
        finally
            try{ if (bis != null) bis.close(); } catch (Exception e){}
   private byte[] expand( byte[] oldBuf, int addedLen )
      byte[] newBuf = new char[oldBuf.length + addedLen];
      System.arrayCopy( newBuf, 0, oldBuf, 0, oldBuf.length );
      return newBuf;
   public byte[] getContents()
       return contents;
//here's where we use it
File f = new File( "c:\myfile" );
ThreadedFileReader tfr = new ThreadedFileReader( f );
Thread t = new Thread( tfr );
t.start();
t.join();
// At this point the thread has died, but the thread object still exists
byte [] data = tfr.getContents();

Multi-Instrument + Multi-Thread problem found

Right.....I have done a lot of research on why logic was not multi-threading correctly and have narrowed it down to one problem...using Kontakt as a multi instrument.
My Mac is a 2 x 2.26 GHz Quad-Core Intel Xeon. This means that it is capable of distributing work loads over the multiple cores of the CPU to prevent core audio overloads from happening.
If I run any plug ins in stereo or mono mode, the CPU acts as it should; I will load up a program, add processing and when the load is becoming a strain for the CPU, I use a bus send and work on that, then the workload is redistributed across more of the cores by logic, allowing me to continue working.
However, I need to use Kontakt as a multi instrument. I usually have 3 instances of Kontakt open and on each one of these, I usually have a minimum of 10 outputs being sent to the aux channels of logic. Therefore using Kontakt as a stereo instrument is not an option, as I would have to open around 30 instances!
Here is the problem; say for example, in Kontakt I send a kick drum out of Kontakt into AUX 3 + 4. The AUX channel in logic will being to show output. I can now EQ this single kick drum seperate from any other sound in logic.
If I began to add processor heavy plug ins to this AUX output, rather than share the workload across the cores as it should and does with stereo instruments, logic now only uses a single core and it will core audio overload very quickly.
As I said, this only happens when I set up Kontakt as a multi instrument. The main problem is when I begin to have many different outputs from my 3 instances of Kontakt, as by this stage, many different sounds will have processing. All 3 multi instruments and their processing are then controlled by the single processor and the other 7 are almost inactive! It therefore becomes impossible to use Kontakt and I have to switch to stereo instances. This happens for all multi-instruments not just Kontakt.
I have just purchased Kontakt 4, I am upgrading to OSX 10.6 (Snow Leopard) and am updating Logic to v9.1. (From v9.0) Will this help at all? Is there an answer to this problem or will I just have to open 30 stereo and mono instances of Kontakt to continue working!
I have included a link to a ZIP file with two photos of the problem. In the photo named MASSIVE. I have one instance of massive running as a stereo instrument. It is sent to a BUS where I applied the WAVES L316 Limiter. I did this multiple times and if you can see on the system performance (Top right) Logic is sharing the workload over the processors as it should.
In the second picture named KONTAKT MULTI - I have done the same thing, but I have opened Kontakt as a multi instrument, sent a kick drum to AUX 2 and then forwarded this to a send where I applied the same WAVES L316. You can see on the system performance meter (Top Right) that Logic now does not re-distribute the workload, it is using one core and anymore plug ins applied to the AUX or bus channels relating to Kontakt will now make it core audio over load, even though now I am using far less processing.
PHOTOS: http://www.sendspace.com/file/og8a94

Ditto
Using Pro 8 Studio, I had this problem after installing Snow Leopard.
Invested £159 in Pro 9 update, same problem.
This has stopped most of my work since my external WK4 sounds are superior to the included software sounds.
As suggested, will now report since since it obviously seems to be a general problem.

Simple multi thread example

Similar Messages

Maybe you are looking for