Presonus Studio One User Manual
Agenor Ramadan
WAVAudio files in WAV format can be used where they are not visible to the user, such as within Presence XT or Impact XT instruments. Very short one-shot samples, such as single drum hits can also remain in WAV format, even if they are intended for direct use on audio tracks. Such short one-shot WAVs should not have an embedded tempo (BPM).
All other audio samples, such as loops and files with tempo-relevant content, need to be converted to the Audioloop format (see next) before finalizing your Sound Set.
MIDI loops should be in MIDI format 0 (zero). MIDI format 0 combines all 16 MIDI channels into a single track, keeping their appearance in the browser neat, and provides a better overall user experience.MusicloopThis is a Studio One exclusive format. It consists of everything required to recreate a musical performance, including the virtual instrument preset, multichannel FX chain presets and the MIDI music performance, plus an Audioloop version for sound-preview in the browser.
Musicloops can be dragged in from the Browser, just like MIDI files.To create a Musicloop, drag any Instrument Part into the Browser.
The Studio One 6 manual covers this format and its usage in greater detail.Preparing Your Folder StructureYou can freely organize the files, loops, samples and instrument presets into the folder structure you think will be the most practical for your Sound Set. However, the following important points should be considered before starting to build your Sound Set and decide on the final names and locations for your files:
Audioloops, WAVs, Musicloops, MIDI files, as well as instrument Presets must be tagged, to enable customers to quickly locate specific types of content by applying filters in the Studio One browser. To understand the purpose and importance of tagging, it is recommended to experiment with the filters found at the top of most Studio One browser tabs.
IMPORTANT: The file format, file name (case-sensitive) and location inside your Sound Set must be final before beginning the tagging process. Your tags will disappear from any sample that is moved, renamed or converted, after tags have been added. For example, do not start adding tags to WAV loops that have yet to be converted to the Audioloop format (see Section 3.2.2 for more information on Audioloops).
To open the Tag Palette, select a file within the mounted Sound Set and click on the Tags: button in the Previewer.
Documents / ResourcesPreSonus Studio One 6 Software [pdf] Owner's Manual
Studio One 6 Software, Studio One 6, SoftwareReferences
- PreSonus Wherever sound takes you.
- User Manual
- LG Sound Bar SK1 Owner's ManualLG Sound Bar SK1 Owner's Manual - Optimized PDF LG Sound Bar SK1 Owner's Manual - Original PDF
@manualsplus YouTubeManuals+,Privacy PolicyThis website is an independent publication and is neither affiliated with nor endorsed by any of the trademark owners. The "Bluetooth" word mark and logos are registered trademarks owned by Bluetooth SIG, Inc. The "Wi-Fi" word mark and logos are registered trademarks owned by the Wi-Fi Alliance. Any use of these marks on this website does not imply any affiliation with or endorsement.
Say hello to your new best friend. Metaplugin (in conjunction with jBridgeM) currently looks to be the most reliable and cost-effective way of running 32-bit plug-ins in 64-bit DAWs like Logic Pro X. Its flexible MIDI and audio routing abilities make it hugely useful in any DAW, though. Here I'm running a bunch of languishing (or defunct) 32-bit VSTs in the 64-bit version of Presonus's Studio One 2.
In last month's Apple Notes I suggested a few ways that Logic Pro X users could continue to use 32-bit plug-ins, now that the application no longer supports them. One approach involved opening virtual instrument AUs in third-party host applications. Another used the third-party utility jBridgeM to generate 64-bit 'wrapped' versions of 32-bit VST plug-ins, ready to be hosted in Plogue's Bidule application or plug-in.
Since then a few more solutions have emerged, but by far the most promising is this one, suggested by a user (thanks TreyM!) on the KVR web site. It also relies on having VST versions of your 32-bit AUs available, so it's possible you might need to do a bit of reinstalling if your setup is otherwise Audio Unit-only. Then you'll still need to splash out a few quid on jBridgeM at jstuff.wordpress.com and make 64-bit versions of those ageing VSTs. But the crucial piece of the jigsaw is the use of the $39 Metaplugin from www.ddmf.eu, an unusual plug-in that exists to host other plug-ins. And as we'll see in a moment, it's a useful thing to have for any DAW, not just Logic.
In the Metaplugin window your synth should appear represented as a green box. Click and drag a virtual cable between the orange 'pins' on the MIDI Input box and your synth. Then click and drag cables between the synth's white audio output pins and those on the Audio Output box. Virtual connections now made, you should be good to go, and if you double-click the green box representing your synth you'll bring up its user interface. The 'Load program' button in the window's title bar is there for choosing presets on synths that don't have their own preset management systems.
Hosting audio effects plug-ins in Metaplugin is a very similar process. This time you choose the straight Metaplugin plug-in in an insert slot. Right-click and choose an effect plug-in as before. And this time drag cables from the Audio Input green box to your plug-in's green box, and then from the plug-in to Audio Output. Plug-ins with many input and output pins indicate multi-channel or surround capability, so if you're wiring one for mono or stereo usage, just use the number of pins you need, working your way along from left to right.
Metaplugin works amazingly well as a 32-/64-bit problem solver. Its developer, Christian Siedschlag, knows it's being used with Logic X and has already improved it in this specific respect. It reports plug-in latency properly to your DAW and even lets its plug-ins be automated (though you'll want to hit the user manual for the low-down on that process). However, it can also let you set up things that might otherwise be difficult in any DAW: load up multiple synths and drive them from a single MIDI input, split an audio input to two or more separate, parallel processing paths, or build your own multi-band compressors from favourite broadband designs. All this and much more is possible.
All contents copyright SOS Publications Group and/or its licensors, 1985-2024. All rights reserved.
The contents of this article are subject to worldwide copyright protection and reproduction in whole or part, whether mechanical or electronic, is expressly forbidden without the prior written consent of the Publishers. Great care has been taken to ensure accuracy in the preparation of this article but neither Sound On Sound Limited nor the publishers can be held responsible for its contents. The views expressed are those of the contributors and not necessarily those of the publishers.