Beats Bars not returning to 1.1.1

Post Reply
tracy
Posts: 54
Joined: Mon Jan 19, 2009 2:11 am

Beats Bars not returning to 1.1.1

Post by tracy » Fri Feb 20, 2009 4:16 am

Beats-bars-16ths display not returning to 1.1.1 when stop is pressed or clicked twice. Subsequent playback begins at 1.1.1, but readout does not reset until play is pressed.

Nokatus
Posts: 1068
Joined: Fri Jul 01, 2005 7:06 am

Post by Nokatus » Fri Feb 20, 2009 4:48 am

Confirmed. It's pretty serious, as it effects position dependent VST plugins as well.

One way to test: place a marker on 1.1.1, load a syncable VST plugin, let the project play and hit stop. Activate the marker. Start playback, and the project starts at 1.1.1 BUT as the playback position didn't update, any plugin which reads the playback position at the exact moment of initiating playback can be thrown off.

This happens for example with Image Line Gross Beat, which stays in sync with Live 7.0.14 but loses its playback position in 8b12, starting to play where it left off because the 8b12 song position doesn't update properly when hitting the marker.

And yeah, I know, I was supposed to go to sleep something like two hours ago :D ... It's an hour till sunrise. Shit.

Szwagier
Posts: 64
Joined: Sun Feb 15, 2009 10:15 am

Post by Szwagier » Fri Feb 20, 2009 7:24 am

+1. Same here.
HP Omen | 12GB RAM | Windows 10 Home| Presonus Audiobox iOne USB | NI Kontrol A49| Behringer BCR 2000 | Korg nanoPAD2

scientist
Posts: 1338
Joined: Sun Aug 10, 2003 2:06 am
Location: seattle

Post by scientist » Fri Feb 20, 2009 7:38 am


Nokatus
Posts: 1068
Joined: Fri Jul 01, 2005 7:06 am

Post by Nokatus » Fri Feb 20, 2009 10:01 am

scientist wrote:http://forum.ableton.com/viewtopic.php?t=107187

they're working on it.
Thanks for linking that, as that thread seems to show this is currently considered to be a "cosmetic" bug instead of a seriously playback effecting one. However, this seems to be able to effect plugins which depend on the position info. (Either that, or there's another bug causing the behavior I described in my previous post, and the position readout not updating is a coincidence :) - in any case there's a song position bug which needs addressing.)

Post Reply