Bug in Automation List Editor Position

Just watch the video, this happens in several songs too. You input a bar number, for example 68, and the value is set to some random number close to 68 but not 68, for example it can be 67.4.3 or 67.4.4 …. after several attempts it eventually sets on 68.1.1 , I have the feeling it get closer and closer as I try several times.

I tried using 68.1.1, but the same issue. Just watch the video.

I am using version 2.2.60.437

My songs use different tempos and time signatures. Also it takes a lot of effort to compress a screen capture video to 4 megabytes, which makes reporting issues very hard

Hi @BalticoX,

Could you please click on your Tempo Track ? Your tempo events will then be displayed in the left Inspector. Please create a screenshot and add it here. With that information, we can re-create your project and analyze why the automation events are ending up at the wrong time position.

Thank you,
Michael.

Hello @Spork thanks for looking into this. Here is an image of the tempo track for the same song on the video. this song does not have time signature changes, only tempo changes. The issue happens in other songs too.

Thank you, @BalticoX

I’ve tested it with the latest Pre-Release 2.2.68 - all is working fine.

Can you please update to the latest version and try again? You can download it here.

Keep us in the loop,
Michael.

Hello @Spork , I just updated to version 2.2.69.474 and the problem persists.

On the songs that I don’t have tempo changes I don’t see the issue. On the songs that I have tempo changes, I see the issue after the tempo changes, so if for example yo created some kind of automation between bars 1 and 11, you won’t notice the issue, but I if you create an automation after let’s say, at bar 17, they you will see the issue (I hope).

I have Windows 11

Have a great weekend

Hello happy weekend. I just updated to 2.2.71 but the bug persists. Please @Spork when you have time, try to replicate again, but create automation sections towards the end after tempo changes had happened. For me it’s easy to replicate as seen on the video.

All the best,

BalticoX

Hi @BalticoX,

Could you please create a simple test project and share it here?

  1. Start VL, New Project
  2. Select TRACKS, Add Tempo Track
  3. Add Tempo Events
  4. File / Save Archive …, Select empty folder
  5. Zip folder and drop it here

Then please remind me what I need to do afterward — I think I might have missed an important detail.

Thank you,
Michael.

Hello @Spork Michael! thanks for the reply

The short version:

Open the project, edit the automation events that are between bars 48 and 52. Try changing the 3rd event from 51 to 47. It will change to a value different to 47. It will require several attempts. Try changing the other events to start on some other measure, most likely it won’t work at the first attempt, it will get closer and closer as you try more and more. Try to add an event by using the + symbol.

Here is the file:

AutomationBug.zip (15.9 KB)

The long version:

I am just trying to create automation. It gets very difficult.

I created new project, created Tempo track, add values as shown in previous post image. Then created an automation track, I created an automation section between bars 47 and 52. The first problem happens when I try to create an automation event. I position the transport at measure 50, open “Automation List Editor…” and click on the + button to add an automation. It does not work, I get the message, “No event at the current time”. Here is an image

If I try to create an on a section on first few bars, I don’t get the error, but events are not created either.

So how can I create an automation event? Well, the only option available for me seems to be using the drawing pencil. So I go ahead and Create some events, that I will need to edit afterwards.

So I open the “Automation List Editor…”

I click on the 3rd event with a value of 48.3.1, a message box opens, I enter 51

The value changes to something different, in this case 50.4.3

If I try again with the value 51

It gets closer but not yet 51, in this example it changed to 50.4.4

I tried twice more, and in the fourth attempt it finally changed to 51

And the + sign does not work, so having to use the pencil a later edit the events, its really painful since the pencil is not precise and basically you end up with a lot of random events that you need to later edit. The minus do work.

1 Like

I’ll add that I checked and got the same result as the thread’s author.
Also, if we trim the automation track by a beat, for some reason it leaves a tail that extends into another beat, but the audio track trims without any problems.

And also, if at the beginning of the automation track the pencil works without problems, then already at the 57th measure drawing something with a pencil is already a problem

1 Like

Hello @Spork I this going to be addressed? I want to program DMX but the problem also happens there, not just in Automation, so its very very hard (practically impossible) to program DMX if I cannot control the event times. I prepared a project (see above) and other people have reported the same issue since then. Thanks in advance.

2 Likes

Just create an automation path, grab a pencil, and try drawing something after bar 49. You’ll be exhausted. How many times do you have to write that it’s not working? I understand. You couldn’t fix bugs in one version before, and now you have to fix them in two versions, which is probably a huge undertaking.

3 Likes