Q Light Controller+

Hi. Dear friends. I think it's not good that any scenes, chasers and etc. in QLC+ don't download (copy) to the individual file. If it will be so users will have very easy way to download scenes, chasers and etc. to any project (show) they want or copy scenes, chasers etc. between the projects (shows). For example on some another dmx soft each scene is an individual file. Or maybe will be fine to make on QLC+ function with which help users can copy scenes, chasers etc.between the projects. Best regards

I vote against ... don't make projects consisting of hundreds of files and if one breaks it breaks all.
And what if you really want to copy a portion of a project ... who or what will rename all those files?
It will definately slow down projects on a Pi where io-access is limited (SDcard - or do you want to read them into ram once? and then you copy a portion to a new project etc etc)

An export / import module would be handier (select existing source project, select what you want to export, select destination project - do some checks to make sure it fits and go)

Thanks for your opinion. I didn't say about rename and copy files with scene and etc. every time from one project to another. The users can use this files with scenes etc. in every project, for example - scenes named - 1,2,3,4 can be fixed in the chasers on project 1 or project 2 etc. When user want to make some chaser - he can open folder with scenes and to fix them in the chaser.Like tables in the databases. Scenes, sequences should be basis of the projects like bricks on the wall. I think so.

From a programming standpoint, it probably isn't as easy as you may think, by looking at it.

Consider this:
In order to simply copy a scene, you also need to copy all of the fixtures, which are separate entities within the XML file. That design allows you to define the fixture once, and use it in multiple scenes, without defining it again.

Next, if you end up copying 2 different scenes into a new project, and there's any overlap in the fixtures which are used, which fixture definition do you import?

Further, suppose you import 2 different scenes from 2 different projects, how do you resolve the fixtures defined in both scenes.

While what you're asking for may seem straight forward, believe me, it isn't.

I'm not one of the programmers for QLC+, but I do have a programming background, so I do understand the process.

What you can do, which is something I do on a regular basis, is to create a base project, and use that as the basis for all of your projects.

Thanks for your reply. Maybe you are right. But I don't understand about fixture? Fixtures are the files on the library, am I right? So why scenes with information about fixtures files can not be individual files? And about bases project. If I make new scenes and etc. in the bases project how I can download new scenes and etc. to another, which were made from bases project , if I need to update those projects

A function to export and import functions would be very nice. But if the copy and paste function would work better (and for all functions) I think that would save us hours and hours too. Unfortunately Massimo is probably busy with other things then QLC+, which is of course no problem. I respect the job he does with this software, so don't get me wrong, but it could use some other attention at this moment.

Thanks for your reply. There is the 5 release, and I thought that for that new release it will be nice to think about a change scenes and other function between the projects on QLC+.

We are relatively new users of QLC. We used to use a different commercial package (Venuemagic) which had some great functionality, but we bumped into some issues that pushed us in another direction. As a new user to QLC, we started building different projects to test different capabilities. in the end we will have two different projects that will run simultaneously to support different effects in different locations based on different sets of events. Some fixtures and functions will be "moved" to the other project as we replicate the best of both when it makes sense. The fixtures and addresses are not the same, but we have common types of fixtures in both.

I strongly support the notion that an import/export capability for both fixtures and functions would add significant value. While there are complexities, something very basic would be immensely helpful in working across projects.My thoughts would be......

Fixtures:

• Allow selection of multiple fixture and export to file.

• Import of fixtures allows selection of start address or SKIP.

• If fixture model is not defined in target, simply skip and message user.

Functions:

• Allow selection of multiple functions.

• Identify referenced fixtures and include in exported file.

• When importing functions, start with fixtures

• Capture mapping between fixtures from import to target fixtures. User selects from existing fixtures of same model, or creates new at selected Address.

• Then import functions, displaying ones that could not be imported because of "missing" fixtures.