BUNDLE WORKSPACE
156 views
Skip to first unread message
Raul Ribeiro
Jul 9, 2021, 6:12:32 AM7/9/21
to QLab
Hi all,
I have 7 Mac's with 7 different shows on the road with QLab workspace of video, multitrack audio, timecode and network. I design the master workspace in "master"Mac and when finished version 1.0 I make a bundle workspace for the same internal drive . Only after the bundle is created I transfer the folder(with workspace) Show A to another Mac.
The folder Show A before the bundle have inside a folder called audio and another video.In audio folder every song is another folder with several audio files(multitrack) .
Every song is a group Cue with Childs playing at same time.
After Bundle workspace all the individual folders inside the audio folder are lost.
Of course all files are still there.
What am I doing wrong?
Qlab full paid license , version 4.6.9 MAC's with macOS Big Sur 11.4
Is important to me keep the organization by folder/song the same way I create.
Why the bundle isn't a perfect copy?
Thank you in advance
Raul
micpool
Jul 9, 2021, 6:29:11 AM7/9/21
to QLab
I'm afraid that's the way bundling works.
If this is unsuitable, then the only way of preserving your folder structures, when copying to other machines is to have a rigorous disciplined approach to how you build your workspace. The most important thing is never to target a file that isn't in the same folder as your workspace. A lot of users have adopted this method and never bundle shows.
If you do this then you can just copy the show folder to the new computer, check it by removing the drive you transferred it from and turning the network off and checking that all the target files are referenced from the folder on the new computer.
This also has the advantage that you can include other files that you might want an operator to swap out in the workspace, which would be lost in a bundle operation.
It might be the case that your master show folders are organised this way anyway as the way you describe how your folders are organised suggests you are targeting only from the show folder.
Bundling is only really useful for folks that like to target files from all over their storage. A few sound effects from a Sound FX Library removable, some music tracks from their downloads folder, files copied from the directors USB stick to their desktop etc. etc. Users who work this way are rarely concerned with folder structure in the bundled workspace, and attempting to preserve some sort of folder hierarchy from their working method would probably be highly counterproductive.
Mic
micpool
Jul 9, 2021, 6:40:22 AM7/9/21
to QLab
The other advantage of using the 'being organised' approach, as opposed to bundling is that it makes maintaining identical copies of the show across all the computers that might be used to work on it, or make safety copies. , e.g Main Computer, Backup Computer, Designers Laptop, Off site Network copy, USB stick Backup, so much quicker and easier. . You can just use standard file comparison and backup software to ensure that all your working copies and backups are identical by only copying a few modified files, instead of bundling and copying Gigabytes of data on a daily basis.
If you do this, another great rule is to always duplicate the show workspace file before you copy. That way if you accidentally copy in the wrong direction, you don't lose your days (or sessions) work! It also ensures you have a regular incremental backup to roll back to if you have a catastrophic workspace problem.
Mic
Raul Ribeiro
Jul 9, 2021, 8:55:41 AM7/9/21
to ql...@googlegroups.com
Thank you all.
That's the way it is, all good.
I will keep redoing the folders after the bundle.
My organization with subfolders for audio is paramount in my operation. If a bass line has to be changed from one song after 100 shows/presentations that will be version 2.0 and so on and with subFolders is easier to give remote help.
I understood the workspace rules were very important since day 1 on Qlab.
Again, thank you.
--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to a topic in the Google Groups "QLab" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qlab/uLM6nF9HkWs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/80b466f7-c77d-4f43-a3b7-64337220713bn%40googlegroups.com.
Chris Ashworth
Jul 9, 2021, 12:29:34 PM7/9/21
to Raul Ribeiro, ql...@googlegroups.com
Hi Raul,
I may be misunderstanding your situation, but it sounds like maybe you don’t need to use the bundle operation at all?
As Mic said, if you are already organizing your own files within a folder structure “beneath” the workspace file, the bundling is only de-organizing your files, and offering no benefit.
Best,
Chris
Richard Sillitto
Jul 9, 2021, 5:26:43 PM7/9/21
to QLab
FWIW, and I’ll probably get shot down in flames, but I’ve designed several shows working out of dropbox.
Whilst this takes some discipline from both the designer and the operators, it does mean you can have a shared folder structure on the edit machines as well as the playback machines.
It also means, changes on any of them are reflected everywhere else.
This has made it immensely powerful for me for tech rehearsals for shows that aren’t funded well enough for me to be sat in the rehearsal room continuously, but I can attend to edits modifications in the evening after a days rehearsal from the luxury of my home studio (with full resources to bear), and the updates are ready for the rehearsals on site the following day.
Once the show is up and running, there is automatically a backup path between main and reserve machines, and off site. Typically, the machines wouldn’t be running at “show time” connected to the internet and syncing, naturally, for fear of inheriting changes at an inconvenient time, or because of the processing hit.
But machines can be sync’d up periodically or when changes are made so that they are kept in track with each other.
Just some thoughts.
Best wishes,
Richard x
Whilst this takes some discipline from both the designer and the operators, it does mean you can have a shared folder structure on the edit machines as well as the playback machines.
It also means, changes on any of them are reflected everywhere else.
This has made it immensely powerful for me for tech rehearsals for shows that aren’t funded well enough for me to be sat in the rehearsal room continuously, but I can attend to edits modifications in the evening after a days rehearsal from the luxury of my home studio (with full resources to bear), and the updates are ready for the rehearsals on site the following day.
Once the show is up and running, there is automatically a backup path between main and reserve machines, and off site. Typically, the machines wouldn’t be running at “show time” connected to the internet and syncing, naturally, for fear of inheriting changes at an inconvenient time, or because of the processing hit.
But machines can be sync’d up periodically or when changes are made so that they are kept in track with each other.
Just some thoughts.
Best wishes,
Richard x
--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/e9045fbc-3b03-4a3d-a3e8-b5187f7f2472n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages