Lock Tracks (esp. for EDU admin/teachers)
There are some tracks I don't want my students to change. I'm including verbal instructions for students in a track and don't want students to be able to edit the instructions track - I'm constantly having to go back and fix it because students will accidentally click it, and it moves out of sync (region snaps to next measure marker).
Would love to be able to set editing permissions on certain tracks. Would be awesome to at least be able to "Lock" tracks that don't need to be edited, even if it just gives you a warning of "This wasn't meant to be edited, are you sure?".
Appreciate all your time and energy!!
-
Another instructor here: Yes, PLEASE add a feature allowing us to lock tracks.
This feature is very much needed for classes and instruction; it would save sooo much (wasted) time and frustration and would greatly support educational use.
Ideally, track(s) would be (un)lockable by instructor only. Info message upon edit attempts would say something like: "This track is locked by the instructor. Mute track if you do not wish to hear it."
Thank you Soundtrap! :)
-
There is a related issue (to track locking... https://support.soundtrap.com/hc/en-us/community/posts/360007806560-How-to-lock-a-track- ) please vote to have this resolved by clicking on the "up arrow" after going to the link.
Depending on your perspective, there is either a significant bug, or dramatic design flaw, that makes this whole track locking problem severe. For example, when I use Reaper with its superior Midi Editor etc. to create backing tracks (and then import them into Soundtrap)... if I mark a track for "Record" the record selection can not "move" from track to track. Unfortunately, this is not the case in Soundtrap. If you identify a track for "Record" and click on another track, and then click on a third track, the high-lighted red "Record" icon "jumps" to the third track!
I share your passion for "user-focused software" and this behavior violates a number of usability guidelines. Specifically, it is unpredictable behavior that leads to a "destructive" outcome. (For others, the term "destructive" in software design is often used to designate when data gets "trashed" in a manner that may be unrealized by the user of the software. This category of "bug" is considered the most egregious by professional software engineers.)
So, after periodically spending evenings being called by users that had NO IDEA how they possibly recorded over someone else's track... at least we now have a handle on the systemic flaw that has damaged our team efficiency.
_Marvin
-
It has been two years and this issue has not been resolved. A new UI is scheduled for release on January 10th. 2022 and the preview does not support access to "Previous Versions"... which makes recovery seemingly not possible??? (Note: The absence of "Previous Versions" is one of several missing functions.)
Any ideas how we are going to recover?
Please sign in to leave a comment.
Comments
12 comments