|
Subject:Tempo events
Posted by: Mus
Date:7/21/2001 5:56:38 PM
Hi, If I insert Time eg. 1 bar at the beginning of a song, Acid 3.0 does not shift all the Tempo events forward. Also the event Shift-Click and select from first to last marker doesn't seem to work for Tempo change events. Do I have to move Tempo events one by one? Thanks M |
|
Subject:RE: Tempo events
Reply by: Rockitglider
Date:7/22/2001 6:02:56 PM
Hello, I tried iserting Time at the start of the song by putting the curser at start and clicking menu>insert>Time, then I put a time value in and clicked OK and all the events shiffted, Seems to be working ok. also, If you want to select and move alot of events at once I would zoom out full, and use the selection tool it works great for moving events like that. Hope this helps See ya |
|
Subject:RE: Tempo events
Reply by: Mus
Date:7/23/2001 8:10:15 AM
Thanks. But if you try it, neither the insert or the selection stuff works on Tempo change markers. SF? Regards Murray |
|
Subject:RE: Tempo events
Reply by: Rockitglider
Date:7/23/2001 10:29:45 AM
Try not selecting any loop events before inserting the time. |
|
Subject:RE: Tempo events
Reply by: Mus
Date:7/23/2001 1:00:21 PM
Thanks No loop events are selected. When inserting time, ordinary markers move, but Tempo markers don't. Regards M |
|
Subject:RE: Tempo events
Reply by: Mus
Date:8/6/2001 12:54:14 PM
> When inserting time, ordinary markers move, but Tempo markers don't. So, SF, is this a bug that will be fixed or a feature to be worked around? Thanks M |
|
Subject:RE: Tempo events
Reply by: DaveP
Date:8/6/2001 5:19:50 PM
This is not a bug. The key and tempo markers do not move when inserting time. This is normal expected behavior in Acid 3. This has been put in several times as a feature request. Hopefully we will see this feature in a future update. |
|
Subject:RE: Tempo events
Reply by: Mus
Date:8/7/2001 2:02:33 PM
Dave, > The key and tempo markers do not move when inserting > time. This has been put in several times as a > feature request. Hopefully we will see this feature > in a future update. OK, thanks. M |