|
Post by TheatreTeacher on Nov 16, 2020 21:44:47 GMT
I am doing a project with 6 groups, and for some reason, one video from group one and one from group 2 are also appearing in group 6. Any reason why this might be happening, and can I delete the duplicates?
|
|
|
Post by lizrad on Nov 16, 2020 21:49:01 GMT
Hello,
It is only possible for videos to appear in the collaboration mode of groups if the videos were recorded in collaboration mode of that group. If videos are appearing across groups, perhaps they were accidentally recorded in reference, not collaboration mode?
We do not recommend deleting anything, but you may watch the tutorial on how to upload a previous recording to replace a recording with the one you want
|
|
|
Post by Theatre Teacher on Nov 17, 2020 12:19:45 GMT
Ok - thank you, it's so strange! Is there a way I can tell if they were recorded in reference mode?
|
|
|
Post by lizrad on Nov 17, 2020 13:48:07 GMT
Hello, The way to tell where a video was recorded is by the way it behaves. - If a recording was made in Collaboration mode, it appears only in Collaboration mode.
- If a recording was made in a group in Collaboration mode mode, it appears only in that group's Collaboration mode. CL is not capable of grabbing recordings from other groups and mixing them up. It's just not sophisticated enough to do that.
- If a recording was made in Reference mode, it will appear across ALL modes and ALL groups.
Here is another way (besides being recorded in reference mode) that a recording made in a group in Collaboration mode in, for example Group 1, could also appear in Group 2: A user with access to Group 2 uploaded the recording that was made in Group 1 (tutorial how to do this on the tutorial page of the website "How to Upload a Previous Recording")
|
|
|
Post by TheatreTeacher on Nov 17, 2020 19:55:28 GMT
I just went back in and checked group 6 in collaboration mode, and now there are two more videos from other groups in there (that were not there this morning even though they were in their original group). I'm just concerned that if I have other students record over those, they might end up someone erasing the ones that are in the correct groups. None of these singers have access to anything except their own group.
|
|
|
Post by lizrad on Nov 17, 2020 20:27:30 GMT
Hello,
Anyone may upload a recording from another group. So it may be that group 6 members may have accidentally uploaded a recording from other groups. If it is not that recordings are made in reference mode, it must be that group 6 collaborators are uploading takes from other groups (or that anyone on the project is uploading recordings to Reference mode). It's just not possible that recordings would move between groups without being explicitly told to. It is not within CL's capacity. It can't do anything that fancy.
To your concern that recordings will be deleted or 'over-written': saved recordings are never lost unless explicitly deleted from the drive. So even if something gets over-written, the appropriate recording can be uploaded ("How to Upload a Previous Recording").
Please let me know if there is another way that I can help you.
|
|
|
Post by lunchbox on Nov 17, 2020 20:44:56 GMT
Hi,
It is unclear if you have determined yet if the offending takes are reference takes or not. You can determine this by opening the project in 'Reference' mode, using any group (groups have no effect in 'Reference' mode); if the takes appear in this mode they are definitely reference takes.
Do any takes show up in your project's reference mode?
|
|
|
Post by TheatreTeacher on Nov 18, 2020 23:37:11 GMT
No recordings appear in Reference mode. Not sure how any of my students would have been able to upload from a different group, either - it's very strange and has now happened in two projects.
I will tell students that were supposed to be in that group to record over that video and hope that it doesn't also cross groups!
|
|
|
Post by lizrad on Nov 19, 2020 0:14:26 GMT
Hello,
To proceed with troubleshooting, the next steps would require involved investigation. This would require you to share the project folder with us at cyborg.llama.app@gmail.com. If you are comfortable, you may do so. We would greatly appreciate if you could possibly verify with your students in group 6 (before we do the investigation) if they may have accidentally uploaded recordings from another group, as this is the most likely explanation, program-wise.
|
|
|
Post by lizrad on Nov 19, 2020 3:20:22 GMT
Hello,
We reviewed the project that was shared with us and found that the part and recording information matches exactly what we would expect if a user was uploading recordings to group 6 from another group. We were not able to find any information that suggested a recording had been duplicated without CL being explicitly directed to do so. The code shows that takes were uploaded to group 6. This is an extremely labor-intensive investigation, so we have limited our investigation to one example. We will illustrate our findings below, using anonymized ID information:
person w/headset part 4 Group 6 [ID#1](part) [ID#2](recording) { "kind": "drive#file", "id": "[ID#2]", "name": "@ __type__= part=[ID#1] type=normal group=Group6 user=[ID#3] recorded_latency=0.07383333333333404 effective_duration=253.73333333331533 initial_volume=1 initial_nudge=0 data=[ID#6]", "mimeType": "application/octet-stream" }
person w/headset part 2 Group Faulty [ID#4](part) [ID#5](take) { "kind": "drive#file", "id": "[ID#5]", "name": "@ __type__= part=[ID#4] type=normal group=FacultyGroup user=[ID#3] recorded_latency=0.07383333333333404 effective_duration=253.73333333331533 initial_volume=1 initial_nudge=0 data=[ID#6]", "mimeType": "application/octet-stream" }
If a single take was bleeding into other groups, the 'recording ID' would be the same. In the above example, we would need to see that ID#2 appeared in place of ID#5. Because these IDs were not identical, this shows us that there were TWO separate recording creation events, ie, the same recording was explicitly (as in, directed by a user) uploaded a second time to Group 6. Please note also that the recording that was made in the Faculty Group was made for part '2', but the identical recording that appears in Group 6 appears in part '4'. There is pseudo-cryptographic and unique meta-data attached to each 'part' and their associated recordings. In other words, a recording cannot be associated with more than one 'part' (for example here, a recording cannot be associated with both part '2' and part '4'). Computers will obviously mess up sometimes and not do what you want them to do, but this kind of error has a virtually 0% chance of happening.
It seems like there is a fundamental misunderstanding about how to interact with the program among your collaborators. We are 100% sure that someone said 'open' in a project. We cannot be sure how this happened, as we do not have intimate details about the group assignments, and how, for example, links might have been passed around between collaborators. For example, although the collaborator in the example above was ONLY assigned to the Faculty Group, it is possible that they somehow obtained a link to Group 6 and accidentally uploaded their recording there. OR, the reverse could have happened: perhaps the above collaborator obtained a link to Group 6, recorded in part '2', then went back to the project through their CL homepage (not through the link), opened the project, saw their recording wasn't there, then uploaded their take from Group 6 to the correct group. There are other possibilities for how the collaborators interacted with the program, but the program was told to 'open' and a previous recording was uploaded to another group.
|
|
|
Post by TheatreTeacher on Nov 19, 2020 12:25:49 GMT
Thank you - when I asked the group members, they insisted no one uploaded a video, but it seems somehow it must have happened!
I will tell the other group members to record over the uploaded recordings.
|
|
|
Post by lizrad on Nov 19, 2020 13:58:48 GMT
Hello,
If I may, we are recommending that you make sure ALL your collaborators know about the problems the 'open' issue has caused, not just the members of group 6, in order to avoid the problem happening again and to avoid future confusion.
|
|