-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Automatic adding and linking of mixer strips to tracks #6407
base: master
Are you sure you want to change the base?
Conversation
3b015f6
to
199deb3
Compare
Task list
Possible options structure
|
🤖 Hey, I'm @LmmsBot from github.com/lmms/bot and I made downloads for this pull request, click me to make them magically appear! 🎩
Windows
Linux
macOS🤖{"platform_name_to_artifacts": {"Windows": [{"artifact": {"title": {"title": "32-bit", "platform_name": "Windows"}, "link": {"link": "https://output.circle-artifacts.com/output/job/eb797dfa-6c97-4993-ba49-6c21a6bdcf27/artifacts/0/lmms-1.3.0-alpha.1.240+g3bff810fc-mingw-win32.exe"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/17805?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}, {"artifact": {"title": {"title": "64-bit", "platform_name": "Windows"}, "link": {"link": "https://output.circle-artifacts.com/output/job/7086d0cf-d1b0-4a5a-a163-05f9deddca4a/artifacts/0/lmms-1.3.0-alpha.1.240+g3bff810fc-mingw-win64.exe"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/17804?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}, {"artifact": {"title": {"title": "32-bit", "platform_name": "Windows"}, "link": {"link": "https://ci.appveyor.com/api/buildjobs/vdfrq538awt7lvdk/artifacts/build/lmms-1.3.0-alpha-msvc2017-win32.exe"}}, "build_link": "https://ci.appveyor.com/project/Lukas-W/lmms/builds/44193685"}, {"artifact": {"title": {"title": "64-bit", "platform_name": "Windows"}, "link": {"link": "https://ci.appveyor.com/api/buildjobs/9knplb9j6fl9eftu/artifacts/build/lmms-1.3.0-alpha-msvc2017-win64.exe"}}, "build_link": "https://ci.appveyor.com/project/Lukas-W/lmms/builds/44193685"}], "Linux": [{"artifact": {"title": {"title": "(AppImage)", "platform_name": "Linux"}, "link": {"link": "https://output.circle-artifacts.com/output/job/207364ec-6281-4f9f-80e4-a55a5803e9ca/artifacts/0/lmms-1.3.0-alpha.1.240+g3bff810fc-linux-x86_64.AppImage"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/17801?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}], "macOS": [{"artifact": {"title": {"title": "", "platform_name": "macOS"}, "link": {"link": "https://output.circle-artifacts.com/output/job/55737401-b513-4337-99cb-aae4b855fa05/artifacts/0/lmms-1.3.0-alpha.1.240+g3bff810fc-mac10.14.dmg"}}, "build_link": "https://circleci.com/gh/LMMS/lmms/17802?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link"}]}, "commit_sha": "477a4337f4dd0f45fc611a5dd53119e3506ca034"} |
It would also be possible in the course of this PR to provide some additional information directly inside the mixer as it is proposed by #1214 because this PR is collecting this information anyway. Like e.g.
Auto linked channels are currently identified by changing the text color to green. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few changes and a quick review from me. I had some questions as to what certain lines were doing, especially the (void) track
and (void) channel
ones.
I noticed a few things, could you clarify these?
Thanks! |
Yes, of course - thank you for your thoughts and remarks.
I will look into this - I have added your point to my task list above
I think this is a good idea - we should only consider that it may not be used very often because of the automatic adding and assigning of mixer channels - so maybe it is enough to provide only the second option?
I was somehow focused on the idea that the track should control the mixer line (@unfa's original suggestion was to disable the auto link if the mixer name changes) but because it is in fact a management of a 1:1 relationship there is no real reason to not enable this from both sides - so, yes I think this is also a good idea.
Principally yes (beside sorting according to the track list) - I was just thinking to display some information on the mixer lines because it is collected anyway (as I mentiond above) - like if the line is used at all, how many tracks are linked or if this is linked to a pattern or a song track.
I have the whole sorting issue not really finished yet and just prepared the lock of the move operations and concentrated on the auto link updating. So it is very plausible that there are still flaws but thank you for giving me more detailed feedback about this.
|
I was thinking that with this functionality enabled it maybe makes sense to always auto link channels by default when assigning them and if they are free. Because the link would anyway automatically removed if more than one gets assigned. And it could automatically link again if there would be only one instrument left. And it would use the track text/color by default because it is initiated from there. |
@allejok96: also thought about multiple tracks linked to a fx line but I found not really a good solution for it regarding the naming. But maybe it is a solution to link only the color as you suggested. If there would be a good way to bring both approaches together - of course it could behave different depending on the count of linked tracks (1 = link name & color, n= link only color) but I am not sure if this is a good idea especially if the count changes only temporary during reorganizing. Regarding multiple options I would probably add a sort button there because I think it is better to have it not in an automatic fashion. And also an options button where you can set up e.g. if and how the pattern editor should be auto linked and which sorting should be applied when pressing the sort button. If the sorting is manual I will add the move menu entries again and yes you are absolutely right: it is normally better to grey them out instead of hiding them (don't know why I did it this way 😵) |
3a6c15c
to
888d4e0
Compare
rebasing/resolved conflicts
…ck naming and track delete
804dded
to
b6e6e7a
Compare
Because I got the impression that there are different needs regarding the auto linking it is now possible to define different settings like:
I am not sure if this is the right approach or if it would be better to define two or three named sets of settings which correspond to different ways of working - but maybe this is unrealistic. Another way would be to reduce the options and split them - e.g. while the sorting currently considers only auto track linked tracks it could be extracted by allowing sorting of all (normal and linked) assigned tracks. (If there are multiple assigned tracks the last would determine the sort order). But anyway: with the settings it should now be possible to play around with the various approaches. |
Still some issues with the pattern editor. |
A very first draft of an automatic mixer strip management as proposed by @unfa in #1215 which allows an automatic linking of tracks to fx mixer strips.
See "Task List" below for the current state and existing bugs.
Related Issues/PRs: