Welcome to %s forums

BrainModular Users Forum

Login Register

Bar beat sync info

General Discussion about whatever fits..
Post Reply
seamus
Member
Posts: 484
Contact:

Unread post by seamus » 11 Feb 2015, 11:28

In the latest version of hollyhock I can't get the vst möbius to receive bar and beat timing info. It WILL receive tempo info.
The plug in is not getting host bar and beat info. I tried in ableton and it works perfectly. It also works in an earlier version of hollyhock (before the 1.1 version). Tried in both 32 and 64 bit versions. Seems to be a bug. Anyone else not getting bar and beat clock info into their plug ins?

drakh
Member
Posts: 198
Location: Bratislava, SK
Contact:

Unread post by drakh » 11 Feb 2015, 13:38

yep i have problem with livecut and kirnu1 arp. (reported as bug about a year ago... and nothing happened :/)

seamus
Member
Posts: 484
Contact:

Unread post by seamus » 11 Feb 2015, 19:41

There is definitely an issue that is preventing vsts from receive bars and beats although bpm gets through. Even stranger is once in a great while it seems to get through! A pity because I want to use möbius to play along with pre made loops.
Earlier versions of hollyhock I had it working!

shawnb
Member
Posts: 190
Location: San Francisco
Contact:

Unread post by shawnb » 11 Feb 2015, 21:03

Thinking aloud here...

There is a difference between MIDI Time Code (MTC) and the MIDI Clock (aka Midi Sync). MTC would sync your bar/beat, and allow you to set position across all your software, e.g., immediately jump to the 17th bar. MIDI clock would only sync tempo, start, pause, continue & stop. Sometimes you might get lucky with a MIDI clock and have it appear to be in sync, because everything started on time & the tempo was constant.

I know HH sends MIDI clock; I'm not sure if it does MTC. Interesting, though, it has an option to display smpte, which is similar to MTC.

The Create Midi Message module lets you set position pointer & create MTC messages. You might be able to write a patch to send MTCs based on the synchro, if that is what your VST needs.

http://en.wikipedia.org/wiki/MIDI_timecode
http://en.wikipedia.org/wiki/MIDI_beat_clock
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp

seamus
Member
Posts: 484
Contact:

Unread post by seamus » 11 Feb 2015, 22:14

Unfortunately möbius has no inlet for that. It says in the manual
Host Sync can be used to record Mobius loops that are in sync with something being played by the plugin host application. Typically this is used when you want the host to play pre-recorded background tracks or drum patterns that are then combined with Mobius loops created in real-time. This option is only available when Mobius is running as a plugin in a host that supports the concept of a "transport". Transports usually have buttons like "start", "stop", and "pause", they have a place where you can enter a tempo and a time signature, and while they are running they count off beats and bars. All hosts do this differently.
NOTE: Mobius currently does not support host sync in the Audio Units plugin, host sync is only available in the VST plugin. This will be fixed soon.
When the host transport is running, it will notify the plugins whenever a the start of a beat or bar is reached. Mobius calls these notifications "pulses". If the transport is not running, Mobius will not be receiving any pulses and it will not be able to record loops. You may need to manually click a "start" button to get the transport started.
To use host sync, set the Sync Source parameter to Host, then set the parameter MIDI/Host Sync Unit to either Beat or Bar.


Seems to me this function isn't working perfectly in HH

shawnb
Member
Posts: 190
Location: San Francisco
Contact:

Unread post by shawnb » 11 Feb 2015, 22:43

Yes, I just did some reading & it looks like the VST host (HH) communicates tempo & song position directly to the VST via API, not via MIDI. It would appear HH is communicating tempo but not position.
Address the process rather than the outcome. Then, the outcome becomes more likely. - Fripp

seamus
Member
Posts: 484
Contact:

Unread post by seamus » 11 Feb 2015, 23:36

thanks Shawn! I was tearing my hair out trying to figure out what i was doing wrong!

CREDO
Member
Posts: 39
Contact:

Unread post by CREDO » 12 Feb 2015, 23:17

Yeah, I think it's called the "VstTransport Event" function. I submitted a query (#58) last week but haven't heard anything. There is other serious (and possibly related?) midi flow issues that appeared in v1.1.009 also (#36).

Not to nag... I appreciate the complications and pressure Senso et al. endure to develop this AMAZING! software - But a 2.0 (or intermediate bug fix release) in the very near future (like 'before Christmas'? :)) would really be nice... Unfortunately for me, much of my workspace is dependent on these and other "fixed" or "implemented in 2.0" related issues.


Post Reply

Who is online

Users browsing this forum: Google [Bot] and 23 guests