Problems with tempo track

[GhostsonAcid]

@paul

Combining grid mode and an existing tempo map with hundreds of tempo changes is not the use case I had in mind.

Well then, this returns us back to your and @Mariano_Cardillo_Fot 's comments.
Namely:

@paul

Ardour can do all of that.

In this case, if someone already has a large tempo map with dozens or hundreds of tempo markers, ramps, etc., then Grid Mode seems like it would be Ardour’s best weapon for handling tweaks to that already-existing grid. But if Grid Mode is super slow in these situations, then I suppose you’re just left with a more manual approach, i.e. double-clicking on each tempo marker and adjusting tempos/ramps accordingly.

And yes, after deleting 143 tracks, the slowness remains. So it definitely has to just do with tempo map recalculation.

So yes, ‘Ardour can do it’ in these cases, but not with speed it seems…

Any obvious reason why tempo map calculation should/would/has to take so long in these cases? -Can’t all tempos/bars/beats outside the scope of what’s being adjusted simply be ignored by whatever processing mechanism is in place for this?

(I’m reminded of FreeCAD’s “Skip recomputes”/“Allow partial recomputes” options. -If you don’t engage those, with every tiny change you make in the model FreeCAD will attempt to freshly recompute literally everything in the model. Thus, when the model gets quite large, this becomes a slow nightmare.)

[Mariano_Cardillo_Fot (Mariano Cardillo Fotografo)]

Nei commenti precedenti parlavo dello gestire diverse decine di tracce viruali e strumenti sintetici, se poi ci aggiungi la traccia video, il tutto si complica.
immagina di dover scrivere musica sincronizzata e doverla consegnare l’altro ieri (la fretta dei committenti) XD. la visione della traccia tempo, tra l’altro, ti aiuta a capire quale musica/frammento di musica sta arrivando e ti prepara a pensare alla migliore soluzione audio

[GhostsonAcid]

Update:

After deleting all midi regions from my test snapshot, the problem resolved! -Editing a complicated tempo map is reasonably (actually very) responsive. Thus, it would seem that restructuring midi note and midi region lengths is the (truer) culprit here.

Hmm…

[GhostsonAcid]

@paul, Is this intended behavior?:

When this symbol is placed directly over a tempo marker’s vertical line, clicking and dragging moves the marker accordingly, as expected:

However, if I click slightly to the left (-left only, in this case), it generates a new tempo marker that I can then move around.

[Lost_Highway]

I believe so – I’ve certainly used it that way when there’s been a large, non-linear slow down over the course of a single bar

[paul (Paul Davis)]

Yes, absolutely. Near the bar lines, we ramp the tempo change; away from the bar lines, we let you add new tempo markers and move them around.

[Mariano_Cardillo_Fot (Mariano Cardillo Fotografo)]

a me compaiono simboli diversi. per spostare il marker di battuta ho una chiave inglese in obliquo e per il tempo intermendio compare una chiave inglese orizzontale @paul . windows 10 64 bit

[GhostsonAcid]

Okay, thanks for the info.

Although in further working with Grid Mode today, here’s a few related requests I have, which I should probably move over to Mantis, although the forum here is more visually engaging… : P

1.

In this situation where I had just one bar, but wished to ramp its final few beats only, I had used a Tempo Marker in-between like so:

However, in Grid Mode you are unable to grab those markers, and this is the resulting behavior:

This takes us back to the mention of Rubato.

Thus, I think Grid Mode reposition-ability should be available to at least all Tempo Markers, whether they correspond to the start of a bar or not.

2.

The specificity of cursor placement is way too exact.
Here’s an example of it being difficult:

Beyond that, and this ties into #1: what is the point of being able to manifest a new Tempo Marker a beat to the left of one that already exists if you are then unable to further grab and move that new Tempo Marker?

3.

And related to #2, after (successfully) grabbing a Tempo Marker to attempt to move it, any ramp that came before or after it is immediately destroyed or altered. It would be nice if those ramps and the initial placement of the now-movable Tempo Marker was preserved.

For example, see here how the previous 122 → 100BPM ramp was replaced with 100 → 100BPM as a starting point, and thus the vertical line suddenly jumps:

---

At this point, I’m all in favor of what Ardour has to offer in terms of Grid Mode and grid adjust-ability.
I just want the tools ‘she’ does have to be more polished!

@paul Thanks for reading/considering!
-J

[GhostsonAcid]

Goddamn Mantis…

-___-

I guess better for the devs, to prevent spammers like me from flooding their inbox with reminders about how terrible their software is.

-J

[Mariano_Cardillo_Fot (Mariano Cardillo Fotografo)]

Esiste un modo più fluido di gestire la tempo track, non capisco perché gli sviluppatori non vogliano guardare a questa problematica e incrementare le funzioni di scrittura del tempo.

Idea.
Potremmo pensare di avere due funzioni per la tempo track:

1. lasciare la possibilità che Ardour si comporti nella maniera standard per la gioia degli utenti amanti del vecchio sistema,

2. avere la possibilità di cambiare gestione della tempo track con sistemi potenziati e simili alle altre (tutte le altre) daw.

@paul che ne pensi?

[GhostsonAcid]

@Mariano_Cardillo_Fot

Esiste un modo più fluido di gestire la tempo track, non capisco perché gli sviluppatori non vogliano guardare a questa problematica e incrementare le funzioni di scrittura del tempo.

Things take time.
They probably have 1000 other things to do even if they’re considering.
Don’t worry, your point/push has been made.

Besides, Grid Mode would be a powerful feature (for you, me, or anyone) if it could be polished and get a massive speed boost, despite you not being used to it. –They should probably start there first, before adding-to or reinventing the way tempo maps are handled. -Polish what already exists, then maybe move forward with potential developments.

…
That makes sense to me at least.

[GhostsonAcid]

FYI, on Mantis now:

0010530: Allow any Tempo Marker to be grab-able and reposition-able by Grid Mode

0010531: The specificity of cursor placement in Grid Mode is way too demanding

0010533: Initial Tempo Ramps before and after a Tempo Marker are destroyed/reset when clicking using Grid Mode

Thankzzz Youzzz…

-J

[Mariano_Cardillo_Fot (Mariano Cardillo Fotografo)]

nel video di mixibus, Harrison usa i tracciati di guardia. pilastri che vengono messi per evitare che si sposi la griglia prima e dopo una variazione