Studio One Transport Bug
May 25, 2020
1
By maddsoul
The transport jumps to measures waaaaay down the timeline for NO reason. Please help. See attached video.
Installation, configuration and sound setup
The transport jumps to measures waaaaay down the timeline for NO reason. Please help. See attached video.
When somehow your global rack got messed up, chord palettes, progressions and phrases sometimes don't generate any sound anymore when clicked on.
This has been fixed with Synfire 1.10 and HN 2.8.1
There's an issue on Windows 8 only, where the installers for HN2 2.8 or Synfire 1.9 would take a minute or so to start, but ultimately fail to do so. An error message pops up saying:
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected.
If you are experiencing issues with MIDI output not being sent to an external MIDI port (MIDI interface hardware), please check the following:
As more and more plug-in manufacturers are dropping support for 32 bit, in the forseeable future Synfire will make the 64 bit Audio Engine its system default. That is, new installations and racks will use the 64 bit engine, while the 32 bit engine remains as an optional choice (currently it's the other way around). This article outlines how to migrate your existing projects and (global) racks to 64 bit.
How to export rendered MIDI phrases from HN2 to a DAW with drag & drop (Example shown: Propellerhead Reason, works similar with any music software that accepts MIDI files dropped on it)
This is an alternative version of the previous tutorial, this time showing the global instrument setup with Propellerhead Reason.
This video shows how to setup sounds hosted in a DAW for use as HN2 global instruments. As a prerequisite, you need to setup a loopback MIDI driver first, as shown in the previous tutorial.
Learn how to setup a Loopback MIDI Driver for sending MIDI data from HN2 to other software running on your computer.
