Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

1.0.0 - Automation Editor can't copy #515

Closed
ahogen opened this issue Mar 27, 2014 · 8 comments
Closed

1.0.0 - Automation Editor can't copy #515

ahogen opened this issue Mar 27, 2014 · 8 comments
Labels

Comments

@ahogen
Copy link

ahogen commented Mar 27, 2014

So I've noticed since the intro duction of the new pattern shaping features (dot, line, and curve) that I can't copy and paste the pattern. LMMS will do it, but the new pattern will not have all the points moved to the top instead of the original locations.

So, looks like there's a bug when copying the Automation pattern.

Original pattern:
1

New pattern:
capture

@musikBear
Copy link

Its because you have to think logically. You have an automation-track (AT) that you bind to a controller. Then you make a pattern. You now like to -copy- this pattern to a new -empty- track -right?
What should lmms se as limits forn this AT? There are non! So what you need to do is to drag a controller int the new AT, hence establishing the limits, and -then- copy the existing AT-pattern into -that- AT - ive tested (win32) and it works like butter on popcorn. (One thing that no longer works, is ctrl-a/v -inside- the AT editor. Only context menu works now.) not a bug
Buut.. the best way is actually to only use ONE AT!
You can bind several similar controller to the SAME AT, so you do not need to copy it at all! What you CANT do is bind very different controllers to -one- AT -and ofcause you cant! The logic limits are very different. PAN for instance span over -1->1 VOL form 1-200%. Only bind identical controllers to a single AT, and all works.

@ahogen
Copy link
Author

ahogen commented Mar 27, 2014

Right. I knew about the limits and all that. In versions past, I was able to copy and paste a pattern (say, down the timeline, later in the song) and route the same control to the AT and the limits would then be set and everything would be just fine.

I didn't know you'd have to route a controller before copying the pattern. In versions past (before the new AT Editor features) you could connect the controller AFTER copying and it would work just fine. That functionality is gone. Maybe it's just me whining, but it was super nice to be able to work either way.

@diizy
Copy link
Contributor

diizy commented Mar 27, 2014

On 03/27/2014 07:18 PM, darkscrap wrote:

Right. I knew about the limits and all that. In versions past, I was
able to copy and paste a pattern (say, down the timeline, later in the
song) and route the same control to the AT and the limits would then
be set and everything would be just fine.

I didn't know you'd have to route a controller before copying the
pattern. In versions past (before the new AT Editor features) you
could connect the controller AFTER copying and it would work just
fine. That functionality is gone. Maybe it's just me whining, but it
was super nice to be able to work either way.

No yeah, that definitely sounds like a bug.

But I can't seem to reproduce it. Can you list the exact steps to
replicate this bug in LMMS 1.0.0?

Do you copy the pattern by copy-paste buttons, or the ctrl-drag feature?
Ctrl-drag at least seems to work fine.

@musikBear
Copy link

Q
Ctrl-drag at least seems to work fine.
q
Not in win32 version. ctrl+lm-drag, adds a new point in all 3 edit-forms, this point then moves with the mouse, as its dragged

@diizy
Copy link
Contributor

diizy commented Mar 27, 2014

On 03/27/2014 08:17 PM, musikBear wrote:

Q
Ctrl-drag at least seems to work fine.
q
Not in win32 version. ctrl+lm-drag, adds a new point in all 3
edit-forms, this point then moves with the mouse, as its dragged

In the song editor. Ctrl-drag in the song editor.

@musikBear
Copy link

Q
In the song editor. Ctrl-drag in the song editor.
q
sounds like oop want to reuse the pattern for a different controller, in a different auto-track.
If you want to see the 'bug'
Open 2 new autotracks
bind VOL to 1. track
draw a pattern
close auto-editor
right-click track-container -chose copy
point to second auto-track and click it
right-click track-container -chose paste
all ctrl-points are now on max, as in his screenie
(You actually also get that result if you only use one auto-track, but two seperate containers.)
But imo its not a bug, its just a different way to work, and its more intuitive, to first bind the controller, and then shape a pattern.

@diizy
Copy link
Contributor

diizy commented Mar 28, 2014

On 03/28/2014 12:54 PM, musikBear wrote:

Q
In the song editor. Ctrl-drag in the song editor.
q
sounds like oop want to reuse the pattern for a different controller,
in a different auto-track.
If you want to see the 'bug'
Open 2 new autotracks
bind VOL to 1. track
draw a pattern
close auto-editor
right-click track-container -chose copy
point to second auto-track and click it
right-click track-container -chose paste
all ctrl-points are now on max, as in his screenie
(You actually also get that result if you only use one auto-track, but
two seperate containers.)
But imo its not a bug, its just a different way to work, and its more
intuitive, to first bind the controller, and then shape a pattern.

No, it is a bug. Particularly since it used to work before. You should
be able to do it both ways, so this should be fixed.

In the meanwhile, ctrl-drag still works even between tracks. You just
have to edit the connections in the copied pattern.

@PhysSong
Copy link
Member

Closing because there were no conversations for 4 years and I can't find any reliable way to reproduce this now. Please feel free to request reopening if the bug still exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants