Mainstage 2 MULTIcore support?

Hey ladies!
Mainstage 1 only used a single CPU core which performance-wise made it less interesting for low latency live effects than Logic Pro.
How about Mainstage 2, does it use more than one CPU core?

Logic also only uses only one core for channel strips, that are in low-latency mode.
That said, MainStage makes much better use of two cores and has many more optimizations for CPU load and latency.

Similar Messages

Latency Increased or Reduced by Multicore Support? MS2 vs. Kore 2?

I'm putting together a live software synth rig that I'll be using alongside a few cherished hardware pieces. I'm a current Digital Performer user but I really need a different host for live gigs. I'm going to be running Native Instruments' Komplete 6 a lot. I'm really torn between buying Logic and Main Stage or Native Instruments' Kore 2.
They each come with a comparable assortment of great instruments and effects but definitely seem to have their own strengths and weaknesses.
I'm pretty hesitant to buy a copy of Kore 2 right now because NI really hasn't gotten Komplete 6 integrated with it yet. On the other hand, it'll be a powerful librarian for my NI software and ultimately add a significant degree of flexibility these synths as well. That being said, I'm seeing all sorts of people struggling to find workarounds for and odd solutions to what I consider to be relatively basic issues from a hardware synthesis standpoint.
Main Stage 2 definitely looks like a great program on paper. It's a lot less complicated than Kore 2 is, but at the end of the day, I don't want to invest an insane amount of time in programming my live VST/AU host. I want to be able to get my sounds on stage quickly and efficiently, I want to be able to recall them instantly when I need them in the set, and I want to avoid instance redundancies or other obnoxiously RAM-consuming situations (MIDI program change recall).
I'm running a Macbook Pro (2.4 ghz Intel Duo Core, 4 GB RAM) and I know that Main Stage 2 has multicore support while Kore 2 does not. Intuitively, one would assume that using half of your CPU processing capabilities would be inferior. However, if you're using two processors to accomplish one task, you're theoretically going to have more latency because they have to communicate with each other. So Main Stage 2's multicore support may actually prove to be a hindrance on stage.
I'm definitely very serious about not spending an eternity programming my set list into a new host, but if I had to choose between a simpler platform or lower latency, I'd undoubtedly side with low latency as it's absolutely essential to the music I play. After years of practice I'm a player first and foremost, songwriter second, synthesist third, and gear-nut fourth. I don't have the RME Fireface 800 which I know will offer the best latency of any Firewire interface, but I'd like to see if my Presonus will be usable before I invest that heavily in a first-generation FW800 unit.
So I've got a few questions for you guys...
1) What kind of latency figures are you seeing on stage with MS2? What are your laptop specs and what interface are you using? Can any of you get it down to ~5ms?
2) Have you had any experience with Kore 2 or a single-core live VST/AU host?
3) Did any of you buy Logic Studio primarily for Main Stage 2? What informed this decision?

I am getting under 4 ms with a 1st gen. MOTU Ultralite on a 2.2 Ghz MBPro.
The MOTU units are well-known for low latency. This is much better than any other interface I have used, but I have not used the FW800.
Your mileage may vary.
Thomjinx

FMLE 3.2 multicore support

Hello,
i know FMLE support multicore (up to 16 core confirmed).
Does someone know if FMLE support also 24 cores configuration ?

I have to ad that I've tried with the new version of FMLE (3.2.1_r).

MainStage 2.1.1 released

This update delivers improved compatibility and numerous fixes.
Issues addressed in MainStage 2.1.1 include:
- Improved stability of the 32-Bit Audio Unit Bridge
- Fixed problems that caused audible artifacts when using the Playback or Loopback plug-ins[/list]

MainStage 2.1.1 Update
This update improves overall performance and provides numerous fixes. This update is recommended for all users of MainStage 2. Issues addressed include but are not limited to:
64-bit Mode Issues
[*] It is now possible to run FXPansion's BFD2 plug-in in the 32-bit Audio Unit Bridge.
[*] Fixes several issues with the graphical user interface and controls of third party Audio Units running in the 32-bit Audio Unit Bridge.
Stability Issues
[*] In 64-bit mode, a 32-bit Audio Unit plug-in quitting unexpectedly no longer causes MainStage to also quit unexpectedly.
[*] Working with multiple concerts with open plug-in windows no longer causes MainStage to sometimes quit unexpectedly.
[*] MainStage no longer quits unexpectedly if a Patch increment button is assigned to a sustain pedal, and MainStage is switched from Layout mode to Edit mode while receiving continuous sustain messages.
[*] Resolves an issue that could cause MainStage to quit unexpectedly when removing or changing an audio device.
General Issues
[*] Resolves an issue that could cause loss of audio output when “Display audio engine overload” messages were enabled.
[*] Resolves an issue that could cause an unexpected sound when rapidly switching patches in a concert that contains more than one multi-output Ultrabeat instance.
[*] Duplicate MIDI events no longer sometimes lead to stuck notes.
[*] Resolves an issue that could cause MainStage to stop responding when simultaneously adjusting parameters for multiple controls.
[*] Resolves an issue where MainStage could stop responding when opening an auto-saved copy of an already open concert.
[*] Sustain pedal events with values between 1-126 no longer cause multiple triggering of mapped actions.
[*] Switching out of Layout mode while sending a note to a drum pad screen control no longer results in stuck notes.
[*] Drum pads now correctly display all parameter values.
[*] “Do not pass through” now works as expected with screen controls set to send to a specific MIDI destination.
[*] The Keyboard window now sends MIDI notes with velocity values of 100, as expected.
[*] The Layer Editor for external MIDI instruments is available again.
[*] Resolves an issue in which there could sometimes be audio "pops" when auditioning patches while notes are sustaining.
[*] Keyboard assignments are now reliably maintained for non-auto assigned keyboards when opening concerts created in MainStage 1.x.
[*] The right arrow for setting the high range in the Parameter Graph for mapped knobs now works as expected.
[*] The screen no longer flashes if a second concert is opened while a plug-in window is open, and Do Not Close is chosen for the original concert.
[*] Resolves an issue introduced in MainStage 2.1 that could lead to an accidental overlap of split points.
[*] Resolves an issue in which the left side key range of a split made no sound in some rare cases.
[*] MIDI note-off events are no longer handled as MIDI note-on events with a velocity of 0.
[*] Velocity scaling is now correctly performed with drum pads.
[*] The workspace aspect ratio now immediately updates to follow changes to the Layout mode aspect ratio.
[*] Using pitch bend on the Musical Typing Keyboard no longer causes a constant stream of erroneous pitch bend messages to be sent.
[*] The vertical scroll bar controls in the Template Chooser grid view now remain fully functional at all zoom levels.
[*] The items in the Help menu now remain available when the Template Chooser is open.
[*] If the preference for Silence Previous Patch is set to “Immediately,” MainStage no longer plays back unexpected segments of audio when switching away from and then back to a Software Instrument patch that has a plug-in with a long decay.
Screen Controls
[*] Pickup mode no longer behaves like Jump mode when assigning a hardware control that is at a higher initial value than selected screen control.
[*] Waveform screen control mappings are now reliably maintained when the sample rate is changed.
[*] The Screen Control Inspector now properly shows the status of the Mod Wheel control when reselecting it after it has been set to Block, and then another screen control has been selected.
[*] Meter screen controls now follow changes to channel strips that change between mono/stereo.
Parameter Mapping
[*] Number keys mapped to commands now reliably trigger the commands instead of patch changes in Edit mode and Performance mode.
[*] The Current Set action now reliably recalls a specific set when the min and max ranges are set to the same set name.
[*] The Current Patch action now works reliably when the Invert checkbox is selected.
[*] Range settings are reliably maintained for the Current Patch Number action.
[*] The Range pop-up for Current Patch Number mappings no longer show duplicate values.
[*] Undo after changing a mapping and then deleting a pedal from the Pedalboard now works as expected.
[*] Mappings of alias patches are now handled correctly when a plug-in on the parent patch is changed.
Playback Plug-in
[*] Resolves a rare issue where the Play button on the Loopback and Playback plug-in could remain lit with playback stopped.
[*] Resolves an issue that prevented a file that had been loaded and then removed in the Playback plug-in from being loaded again.
[*] If files containing tempo changes are imported into Playback, the following warning only appears once per session: “File contains tempo changes. One or more of the files you are importing contains tempo change markers. This version of MainStage does not support importing files with tempo changes.”
Loopback Plug-in
[*] The Position field in the Loopback GUI now reliably displays all positions at all loop lengths.
[*] After using Undo to remove previous recordings in the Loopback plug-in, recording a loop that crosses the cycle point no longer removes a portion of the loop.
[*] Using Undo to remove a take in the Loopback plug-in no longer removes crossfades at the cycle point.
[*] In the Loopback plug-in, Fade-out now works properly when applied to an overdub performed over reversed material.
[*] Resolves an issue in which enabling Reset to Saved could lead to recording in Loopback starting automatically when a concert was opened.
[*] Resolves an issue in the Loopback plug-in where immediately triggering a Software instrument after going into record could cause an unexpected sound.

MS 2.1 'Does not support importing files containing tempo changes' message

OK, so I've just loaded up the 2.1 upgrade and opened up a couple of existing concerts, and I get the following message:
+File contains tempo changes+
+One or more of the files you are importing contains tempo change markers. This version of mainstage does not support importing files with tempo changes.+
It's a bit of a problem as the dialogue box appears several times during loading, and I have to click 'OK' every time, which adds to the length of time it takes to load up the concert (something I do several times during the course of my set).
I'm not using any MIDI stuff, just acoustic and electric guitar plus vocal channel strips and playback channels.
I've tried out some of my backing tracks, which have a ralletando at the back end, and they still seem to slow down properly (which isn't surprising, as they are audio files), and I've also tried setting all the sets back to the concert tempo, which hasn't stopped the issue occurring.
Any thoughts, anyone?

Hi Blueberry
Well, if you mean I put a tempo curve at the end of some of my audio files in Logic, in order to slow down at the end of the song, then, yes, I did do that. However, that still works in MS2.1, and anyway, why would that no longer be allowed, as that is an essential musical function. Also, if the upgrade meant I had to re-do the exporting nearly 200 backing tracks, them I'm afraid it would be back to 2.01 for me.
Furthermore, I tried starting MS up in 32 bit, and that didn't make any difference either.
As it is, this problem is (so far) only an inconvenience as it takes longer for me to load a new concert. What I'd like to understand is what does it refer to? and how can I prevent it showing this message?
Thanks

Choosing architecture

Hi,
For my next project (academic, hobby), I am planning to add fine-grained multi-threading support to an existing open-source processor architecture. The OpenSPARC already includes this and I'll use it as a reference when needed. What I am thinking is to take another existing core from opencores.org and add this functionality. I have several questions to ask the experienced community.
My main decision now floats aroud selecting the core which will not only allow me to do this project, but also reuse my work in future multi-core, multi-threaded projects. That means that the open source I need to choose should be:
- an active project, so I am not the only person working on hardware/software support
- popular architecture/instruction set (mips, risc, v8, v9) to become fluent with industrially used uProcessors
- synthesizable steady code
- VHDL because that's what I know and I am short on time
With these in mind, I identified a few cores and would like to hear your opinion:
- what is the potential complexity
- how can tool availability affect this decision (leon3, openspac have lots)
- if Leon3, what's the potential to contribute to the community (it is mostly maintained by Gaisler research and not an individual after all)
Leon3
Tested, verified
Asic and FPGA-proven
VHDL
Open source, however is maintained by Gaisler Research in Sweden
Has a lot of tools, support and commercial interest (used for space missions)
Can be easily used for future projects due to above, so it is worth learning it
Plasma
FPGA-proven
VHDL
Active project started in 2001, maintained by an individual
Has success stories (complete TCP/IP stack implemented; robot control)
Potentially good processor for future projects
I am more inclined to use this core since it is not owned by any company, yet still supports tools and can be used in future
I can contribute to opensource community here
Open8 uRISC
Stable and active
VDHL
Supports v8 instructions
Comments:
I am not familiar with v8 and not sure whether it will be a better experience compared to other uPs.
OpenSPARC
Verilog--not familiar with
can use manuals and code as a reference

Hi.
From the processors that you mentioed I believe that the most complex and the most advanced is the Leon 3 processor. There is also a thesis that compares the Leon 3, the OpenRISC core and the microblaze, I think, processor cores in performance. Also Leon 3 has multicore support. During the last years I worked with Plasma core and the OpenRISC core (now with the OpenSPARC which is much more complicated) and I know both of them very well. For adding fine-grained multi-threading support, I believe that the best choises are the Leon 3 and the OpenRISC core. I can give you some usefull information about OpenRISC. OpenRISC has L1 instruction and data cache memories and a wishone interface that connects the processor core with the external memory. Wishbone interface can be configured as shared bus or a crossbar switch interconnection scheme. By default in OpenRISC is shared bus. The wishbone can gine you the opportunity to add more than one multithreaded cores at your final design. There is also a thesis in the net that creates a multicore OpenRISC (not multitreaded). Unfortunatelly I don't have the same knowlenge about Leon 3 processor and I can't help you so much but you can ask at Gaisler Research team.
Finally verilog I think that is easier than vhdl. At the beginning of my thesis I also have the same problem with you, but when I started using the verilog for the OpenSPARC core I forgot the vhdl. It is also an opportunity for you to learn more than one language.
Andreas

TestStand 4.1 Available for Download

NI TestStand 4.1 has been released and is available for download.
If your copy of NI TestStand has an active service and support contract (SSP) you will automatically receive the latest version, or you can download TestStand 4.1 from our website.
TestStand 4.1 Evaluation Software.
NI TestStand Resource Profiler : The NI TestStand resource profiler analyzes test system execution and identifies instruments bottlenecks to help optimize test sequences.
Intuitive Switch Management: With the new Switch Executive 3.0 developers can create switching code more intuitively with a graphical interface for creating new switch connections and routes.
Hierarchical View of Sequences- The hierarchical view displays a graph containing all sequence calls starting at a given sequence or sequences.
Customizable Result Collection: The new additional results step pane allows developers to add any code module parameter to the result list. A new step type facilitates adding properties and variables to the result list.
New Tcl Step Types: The new version of NI TestStand includes integration with Tcl scripts through customized step types that allow developers to call Tcl code stored in a script files or evaluate Tcl expressions. These step types are provided as examples, including source code, allowing customers to customize them for their particular Tcl implementation.
Windows Vista Compatibility: NI TestStand 4.1 supports Windows Vista by running the NI TestStand user interfaces as non-administrator users, and supporting the UI enhancements in Microsoft’s new operating system.
Multicore Support for Parallel Execution: Like LabVIEW, NI TestStand is based on a multi-threaded architecture that can take advantage of multi-core processors. Developers can use the parallel process models to test multiple units in parallel on different processor cores.
Simple Updating of LabVIEW VIs: With the new Update VI Calls tool developers can easily update the prototypes of all LabVIEW VI’s, including Express VI’s, in a sequence
Improved Advanced Step Settings Editing: Advanced step types, such as those for synchronization, now provide configurable panes that allow users to modify multiple steps at the same time and see the outcome of step properties automatically
TestStand 4.1 Evaluation Software.
Josh W.
Certified TestStand Architect
Formerly blue

Hi Thomas,
I agree. On my site there will be only 10+ Testers. This week i have received the 4.1.1. SSP paket from NI. At the monenten they were closed!
From upgrading TS2, TS3, to TS4 i dont uninstalled. I just upgraded. So all versions are present on the maschine !
With VersionSelector i switch through the versions i like and figure out if everything is working well under latest version.
Another thing NI should think about is LabViewVersions and TS:
I have TS2.0 programms that use dll from VC6,8 or CVI6,7,8 in the same file. They run under all new TS versions without any modifications!!
But it is impossible to run vis from LV6,7,8 under the same TS. Well masscompile ! but then they wont run under old stuff.
Well i am not afraid of upgrading TS. But of masscompiling a !!TESTED!! vi to new vi-version.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

TestStand 4.1 manual

Hi Ni-Guys,
Thank you for releasing TS.4.1
But before downloading and installing. I would read the Teststand Reference Manual (the big pdf one).
I am especally interested in the multicore stuff.
Please post it as an attachment here or show me a link.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

Hi Ray,
Thank you that was exactly what i need !
I also opened the Relase Notes and looked for multicore support
BUT: These documents do not deal with Multicore support.
as in http://forums.ni.com/ni/board/message?board.id=330&thread.id=19993
It seems this is an OS feature and you have no control on which
core your executions are running.
Greetings
Juergen
=s=i=g=n=a=t=u=r=e= Click on the Star and see what happens :-) =s=i=g=n=a=t=u=r=e=

How to install "NI RT Extensions for SMP"?

Hi!
I've set up an ETS realtime host on an old 2-processor machine with Pentium II 350. It is just for testing. It will be replaced by a dual core machine. How can I install the "NI RT Extensions for SMP" as described in
http://www.ni.com/pdf/manuals/371375b.pdf and
http://www.ni.com/pdf/manuals/371857d.pdf? I didn't find this software in the installation menu in MAX. Do I have to install another software packet? I searched all the CDs but didn't find it. I use LV 8.2.1.
TIA,
Christian

hello christian,
the multicore support is part of the LabVIEW 8.5. to use this feature you need version 8.5 of LabVIEW and LabVIEW Realtime.
kind regards,
robert h
NI germany

PXIe 8108 Rebooting whenever i connected to Max

Hi,
Iam Using PXIe 1082 chassis and pxie8108 controller. Pxi system having Dual Mode boot configuration (Windows/Other os boot and Labview RT Boot).If i boot with windows then no problem it is detecting in Max. If i trying to boot in Labview RT, monitor which is connected with Pxi system shows the following message
Transferring Control to user program
Can't find suitable device for drive C
LabVIEW Real - Time Boot Loader
Build Time: Oct 22 2009 11:01:12
(C) Copyright 2002 - 2007 National Instruments Corporation
Error booting hard drive boot program.
Max system identification name:Ni - PXIe8108-2F12CD1D
LabVIEW Real-Time Single-Core Kernel found '2' CPU cores.
Consider installing NI RT Extensions for SMP (Multicore Support) module from MAX
Initializing network... Link Local IP address assigned.
Device 1 - MAC address:00:80:2f:12:cd:1d: - 169.254.103.152 (primary)
System state: No software installed
if i connect Pxi with other PC MAX then Pxi system is rebooting...
in above Pxi message it is showing" Error booting hard drive boot program". This is the problem for Pxi Reboot ?
Can any one help me to solve the issue...
Vijay

Hi Vijay,
I suspect that this issue is because your system does not contain an RT compatible partition for installing LabVIEW RT.
If your system is configured for dual booting Windows and RT, then you need to have two partitions on your disk, one for Windows (typically NTFS) and a second for LabVIEW RT (either FAT32 or Reliance).
Since you already have windows on the target, you should first boot into Windows and attempt to create a second FAT32 partition for RT if you have some unpartitioned space available on your disk (depending on the version of Windows, they may require 3rd party tools). Another option is to freshly install Windows on the disk using the NI-provided OS Recovery media, which has installation options for configuring a disk to support dual-boot Windows and RT.
As to your original issue as described I have forwarded on your problem internally for further investigation - in general simply lacking a formatted partition should not cause RT safemode to reboot. In your specific situation, however, it would still be best for you to configure the paritions from within Windows anyway instead of using the tool in MAX to ensure that the Windows partition is correctly preserved.
Cheers,
JoshH

Playing MS Flight Simulator on Intel Mac

Hi,
Just like to check if anyone is playing the MS Flight Simulator on their iMac. I am asking becos I thought the spec for the iMac is not sufficient to support the game.
Rgds
TC

Hi,
I have iMac 24" 2.8GHz 2 GB ram. XP SP2 in Bootcamp. FSX runs fine. Get the latest ATI drivers for Bootcamp from the ATI site. Biggest frame hog seems to be the AA. Choose the minimum setting with the ATI utility supplied. You might want to play with Mipmapping etc as well.
From memory, I was getting around 20FPS minumum pretty consistently at mostly maxed out settings. A couple of strange things happen occasionally. Going from 3d cockpit to 2d cockpit (or vice versa) can slow down the the works. Either restarting FSX or changing some video settings and hitting OK seems to work.
One other thing, FSX SP1 is good - multicore support etc. FSX SP2 has a couple of problems - lose menu text and so on. Unless it's been fixed, stick with FSX SP1.
Lastly, I was getting strange artifacts after changing screen resolution etc, and going back into FSX. Once again, if this happens, go back into video settings (FSX that is), uncheck filtering, check it again, then click OK. Works fro me. Haven't got the foggiest idea why, and your experience may be totally different. When you feel like a change, install IL2 Sturmovik, and have some fun!

NI instruments / Logic instruments and multi processor warning

I am running an instance of FM8 and Massive and the rest of my patches are exs and evp88 , on a macbook with 2gb ram , the memory is less than 50% and mainstage has been great up untill today when i got the "mainstage does not support multi processor 's" warning and then the second time this warning came up mainstage force quitted . Anyone experienced this yet ?

Ola Ramiro,
como estas?
I'm using Atmosphere on as a normal plug-in.
However, there have been some mates that post about here in the forum.
Try to shearch about it.
If I have any news, I'll keep you post.
adieus amigo,
Jorge

Premiere 2.0 projects in CS3

I know it is not recommended but can I at least finish the editing in 2.0, then import that file into a new CS3 project to take advantage of the new multicore support aswell as improved HDV exporting?

I did with one of my projects since I wanted to try the new time remapping features.
The only thing missing, as far as I could see, was the keyframes for Motion Effects. Not bad, simple enough to redo them.
I was pleased with the transition from a project created in 2.0 and finished in CS3, so yes it can work.

EMU 0404 USB - DS driver and sample rate autoswitchng

It looks like autoswitching works well until output is going through the ASIO driver. With output switched to DS the "sample rate" option in control panel becomes grey and do not change its value to reflect source sample rate.
Assume nothing is playing via e-mu then I can switch Fs manually in audio control panel to say 96 kHz. Then I start playing some 44.1 wav via foobar + DS out. "sample rate" in audio control panel doesn't reflect 44.1 and remains greyed with Fs = 96.
Is it feature or bug?
What is going out from SPDIF in such case: bit perfect 44.1 or 96 with SRC?

Hmm... there are plenty of possible reasons for this ...here are couple of them (not mentioned in your list of suggestions given by Creative support)
- multicore support could be one culprit (I don't know if the FL has this option but if you use (IIRC) Cubase 3-> )
- on Cubase, another possible culprit is an option named as Lower latency ... disable this feature
- some background process starts after some period (E-MU USB is quite sensitive for these) ... run the DPC Latency Checker utility (just google the name to get it downloaded)
Does Coscos Reaper (google the name) give same issue?
jutapa

Pro Applications Update2008-01 1.0?

This update mentions updates to Shake but the "Release Notes" mention nothing of Shake. Does anyone know what the updates for Shake are? More specifically does it deal with 8 proc support with 10.5.2?
+"This update improves reliability for Apple's professional applications and is recommended for all users of Final Cut Studio, Final Cut Server, Logic Studio, and Shake."+
Thanks

I think they mean that it updates the common frameworks that Shake shares along with the other ProApps like Final Cut Pro. It might make Shake more stable but it is unlikely to add new features.
And as Shake is unsupported, don't expect 8-proc support. Final Cut Studio doesn't even have multicore support yet (do any of their applications?).

Mainstage 2 MULTIcore support?

Similar Messages

Maybe you are looking for