Ohm Studio ... Basic Concepts, Features, and Tips

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

Ohm Studio ... Basic Concepts, Features, and Tips

  • Welcome to Ohmstudio !
    If you are interested in creating songs with other musicians from all over the world from the comfort of your home (or wherever you are) over the Internet and never losing your songs/tracks due to your own PC or MAC having a failure , you’ve come to the right place !.

    What Ohmstudio is:   
    An internet cloud based digital audio workstation (DAW) application for creating/recording songs with multiple tracks and collaborating with others from all over the world in real time.  It is designed to be used by musicians and audio engineers of all skill levels from beginners to professionals for the purpose of collaborating together to make songs.  It can also be used by yourself alone without collaborating with others.  In either case, you get the advantage of having your songs stored in the "cloud" on the internet where you can access them at any time from any location or machine (PC, MAC)  where you connect to the internet.

    What Ohmstudio is not:

    An internet game
    A place to find free music samples and software instruments

    You're new ?    Read/watch this first

    Really Great Video Tutorials and Demonstrations !

    Manual/Documentation page

    Keyboard short cuts

    And feel free to ask questions in the chat !

    Happy Ωhming !



    •    Projects and Snapshots - quick overview/summary

    •    End-User Roles - Two Roles:  Admins and Contributors

    •    Projects - Public and Private

    •    Racks and Tracks - Public and Private

    •    Using Project Attributes/Tags 
         (public, private, hidden, open, closed, cloneable)

    •    Project Versioning Techniques - Snapshots and Cloning

    •    Snapshots:  (version of the project at a point in time) 
          -  Making/Restoring Snaps

    •    Shared Mixer

    •    64 bit vst's, vsti's, vst3's - How to use your 64 bit plugs in Ohmstudio

    Projects and Snapshots - Quick Summary
    All projects are songs created by yourself and/or with others. 

    If you are new to Ohmstudio, one of the fist things you realize is that in
    stand alone DAWS  (Cubase, Protools, Reaper, Ableton, Audacity, Sonar,
    etc.) songs or projects that you do there are stored as files locally on
    your computer.   With Ohmstudio, your projects are stored in the
    "cloud" in an Ohmstudio hosted Amazon server farm.  You don't have to do
    a "file save" operation - in fact you can't so don't go looking for it
    :) ,
    Everything is automatically saved as you make changes to your
    projects.  When you exit your project and re-enter it, everything will
    have been saved just as you left it when you closed the project.   The
    System makes automatic snapshots of your project roughly every 15
    minutes.  You can also explicitly make  "snapshots" yourself and label
    them to be easily located later. 

    End-User Roles - Two Roles:  Admins and Contributors

    When you create a project, you are an AdminWhen others join, by default,  they are contributors. 

    Contributors can contribute, edit, add, delete any content, change mixer settings, etc.  in a project from their own tracks as well as anyone else's tracks
    (private tracks cannot be modified by anyone else except the creator, however, they can be deleted by anyone else)
    Admins can do anything a contributor can do with respect to content and shared editing functions in a project, but have additional administrative privileges/powers such as:
    • Ability to invite others to projects
    • Elevate contributors to admin
    • Kick contributors out of projects
    • Export project to master page
    • Restore snapshots
    • Change project attributes.

    CAUTION:  If you elevate someone to Admin, you cannot later kick them from your project nor can you demote them back to contributor
    - so be very selective as to whom you trust to make them an Admin.  They will have the same power as you do in a project - no less no more.

    Projects - Public and Private

    There are essentially two types of projects you can create in Ohmstudio - Public and Private. 
    Public projects are as they sound - public.
    There is no need to invite people to public projects -  as anyone can join them,
    however, as an Admin, you can invite someone to a public project.
    Some users like to look at the list of public projects in ohmstudio,
    play/preview them and then possibly choose to join them and contribute.
    Some users do not bother to look at the public project list and prefer to
    generally work on private projects.   So if you want to make other users
    who are logged on at the time aware of a project you have put in
    public, you should post a link to the project in the general chat or
    just tell them the name of the project in public, etc.   -  You can also
    invite others - whether they are online or offline - to your projects
    as you see fit.

    Public projects have often be referred to as "The Wild Wild West"  - low to no rules and anything can happen.  That has both good and bad implications. Public projects are where you can easily join something in progress and meet people on ohmstudio to
    establish relationships with for collaborating. As a result, they have loose controls - Anyone can join - no invite required, anyone can
    change anything in the project -  it was designed to be that way to make
    it easy and not complicated to meet people and start collaborating and
    learn ohmstudio and shared real time editing in a DAW

    This is
    where using snapshots help to protect projects from accidental or
    intentional loss/damage - the snapshot feature allows admins to restore
    projects to a prior state in the advent that something bad -
    unintentional or otherwise -  has happened to a project. 

    are automatically made by the system roughly every 15 minutes and also
    upon exiting a project, however, these can be cumbersome to look through
    and determine which snap to restore to.  It is therefore recommended to make explicit snaps yourself.

    TIP:   A best practice is to explicitly make a snap upon entering a project and before you leave
              and label it with your name as follows:

    1.   "Name - before adds/changes - date, time"
    2.    Do your changes, adds to the project and then before exiting the project, make another snap
    3.   "Name - after adds/changes - feel free to provide details on what you added or changed - date, time"

    Private Projects
    Private projects require you to invite others
    and is the default setting (attribute or tag) when you create a
    project.    When you create one you are an Admin of the project, You
    control who can join.  You invite others.   This is the type of project
    one should create to do more serious collaborations with others here on
    Ohmstudio.   You should invite people whom you trust to your private
    projects, especially with regard to them not doing damage to the project
    nor exporting your tracks and using them without your
    knowledge/approval for their own purposes.   

    Anyone who is a member (admin or contributor) of any type of project
    can export the tracks outside of ohmstudio without anyone knowing about
    it and there are no controls in place to prevent this.  Hence it
    is essential to form trusted relationships for doing anything on
    Ohmstudio which might be something you wish to sell one day.

    Project Versioning Techniques - Snapshots and Cloning

    Snapshots allow you save a project at a certain point in time and Admins of projects can restore snapshots.  Anyone can make a snapshot, but only admins can restore them.  This allows for versioning. When you are an admin, you have the power to make snapshots, restore snapshots and clone projects, hence it is relatively easy to use these feature to create multiple versions of the same project. 

    When you clone a projects, it makes an exact duplicate of the project, however, only you will be a member of it and you will be the Admin.   As an Admin, you will be able to restore snapshots and the clone will retain all the snapshots made from the original project.
    The clone will also allow you to display who else was in the original project and what their role was via inspector and the check box to display past members.

    Tracks  - Public and  Private
    Private Tracks are a safeguard within Ohmstudio against having your content modified, copied, or even heard.  No one but you can see, hear, alter, nor export your private tracks - even if you have the project as public and cloneable, those private tracks remain private. 

    The catch is that no-one can hear them either except yourself.  In order to allow someone to hear a private track, you have to copy it to a public track and then it is subject to all the bad things that can happen to a public track from others who are either unscrupulous or inadvertently make mistakes using the product.  

    You can create both audio and midi private tracks

    CAUTION:  Even though no-one can copy or modify your content in a private track, anyone can delete any type of track in any project, as a result, you are repeatedly encouraged within this documentation to utilize snaps and clones.

    Using Project Attributes and ability to find projects
    When you create a project, you will see project attributes and tags you can pick
    The attributes allow you to control whether or not the project you are creating is to be

    • public or private
    • open or closed
    • hidden or visible
    • cloneable or not.
    TIP:  Tightest control (private projects, private tracks, project marked private, closed, hidden)
    TIP:  Loosest control (public projects, public tracks, projects marked public, open, cloneable)

    The most secure project is one which is marked private, hidden and closed.
    (Private, Hidden, Open projects are also secure and cannot be seen nor messed with unless you invite someone to it.)

    Hidden means that it will not display nor be searchable in the main interface or the web interface in order for someone to hear or join the project, you would need to invite them explicitly or share the link to the web project page with them explicitly.

    A private project which is open or closed will be visible via search in the web interface. 

    The Ohmstudio main application interface does not have a private projects tab and hence the only projects you can see,  or others can see,  in the main app interface are their own projects  (My Projects tab),  Cloneable projects  (based on the attribute of the project being set to cloneable)  and the Public projects.

    As mentioned earlier, there is no File Save operation in Ohmstudio - as it is a
    cloud based DAW and the implementation is that as soon as you have recorded
    something or changed something, it is saved instantly.  There are automatic snapshots made  by the system approximately every fifteen
    minutes and you can make a snapshot yourself at any point in time.   Snapshots are like versions of a document,
    you can go back in time to the way a project was at the point of the
    snapshot.   They are always there,
    snapshots do not got deleted, when you clone a project the snapshots are there
    too.   Only an Admin can restore a
    snapshot whereas anyone -Admin or Contributor – can make one.   This provides a very good safeguard in
    general against malicious or inadvertent changes to projects and ensures
    against loss.

    Shared Mixer
    The Mixer in Ohmstudio is a "shared" mixer, 
    which means when one person mixes the project to their liking,  they have mixed the project for everyone.

    Volume sliders, panning, usage of vsts fx - etc impact the project for all who are members.   In addition to mixing, Ohmstudio has a unique feature of a shared
    vst, vsti model.  If two or more users have the same vst, vsti, vst3, etc  - they will all be able to edit the settings/patch selections, etc of that vst, vsti, vst3 -  you can each change settings, hit the manual sync button at the top of the vst window, and the other person who has the same vst etc as you do will be able to see your changed settings. This can
    be a very cool way to work together as audio engineers/editors with respect to you vst settings and features with ability to save and exchange presets for vsts, vsti, vst3 in this manner – must have the same
    vsts, vsti, vst3's and more often than not same versions/release to do this.

    This automatically works for the ohmstudio built-in vsts and works with 3rd party vsts as well

    Mutes and Solos in the mixer
    • Muting or soloing a track within a rack will affect all those who are in the
    • Muting or soloing an entire rack will only be for your ears

    So you can mute individual track(s) or solo
    track(s) and it does not impact other users in the project, however, changing
    levels of active tracks impacts everyone, so don’t crank up the master or other
    non soloed/muted tracks and be surprised if others yell  “Hey,you blew my ears out, or you just woke
    up my wife and kids”.

    64 bit vst's, vsti;s, vst3's - How to use your 64 bit plugs in Ohmstudio
    Ohmstudio is a 32 bit application and as a result only supports 32 bit vsts, vsti's vst3's natively. There is however a solution available to allow you to utilize your 64 bit vsts, vsti's, vst3's with Ohmstudio.

    There is a piece of software called "Jbridge", not free, but relatively inexpensive - ~$20 US.

    Jbridge allows you to make a 32 bit "wrapper" which goes around your 64 bit plugs and makes them accessible and usable within Ohmstudio.

    You can find out more information, download a free demo version to try it out, or purchase Jbridge here


    Note:  There is a MAC version separate from the PC version and you will find the appropriate links for those on the web site.

    Many users on ohmstudio utilize jbridge with great success !!

    Another useful plugin to look at is something called "Metaplugin".  ~50 US to purchase,  free fully functional demo version (just does not save settings)


    If you have a large number of 64 bit vsts, vsti's, vst3's - you can use jbridge in conjunction with metaplugin and save yourself a lot of "Jbridging"
    Just use jbridge to make a 32 bit wrapper for the the 64 bit metaplugin vst - then use metaplugin to load all your 64 bit plugs
    - special thanks to AndyMCProducer for this tip !

    Excerpt from metaplugin page: 
    Another favourite use case for Metaplugin is to load VST plugins in Pro
    Tools (or to load AudioUnits in Pro Tools if you’re on a Mac). Hence,
    you can use it as a VST to AAX wrapper or an AU to AAX wrapper. While
    we’re at it: you can also use Metaplugin to load VST plugins in
    Logic/LogicX (VST to AU wrapper), or AU plugins in Cubase (AU to VST

    That's it for now.    Hope you have found some of this information helpful

    Best Regards,  Make great music together, Music soothes the soul - Happy Ωhming everyone !  Rocky

  • Feel free to provide feedback or ask questions