would be nice to be able to see the current scene name on all the screens and to see if it has changed
also a shortcut button to go quickly to the scene page from all the screen would be useful to quickly recall them during a show
ah and a search field for the scenes
YES ! It is a great feature to add
+1
Would also like a screen reminder of what SHOW file Iām working on?
In addition H & H should add āAutoSaveā feature
Again, as mentioned many times before in other threads, there is no current scene.
There is only a last recalled scene. The state of the desk is already changed if you just slightly adjust a fader.
So the current data wouldnāt match the scene content anymore, shortly after the recall.
Perhaps someone donāt think like you, unless you said not enough many times ? 
Scenes are stored only in the NVRAM until a show is saved at which point that scene is backuped. The last opened show sets the NVRAM data at the commencement of next session. The SHOWS are actually created in sequential file number order so 000 first incrementing by 1 on each save.
Unfortunately the Shows list sorts the shows in Alpha order on the mixpad display of names not the order they were created (see the number sequence against the show names on the list).
This alpha sort order default can lead you to believe the last Show on the list is the last one saved and make you think thatās what youāre working with.
This is why Iād like to see the actual current SHOW and SCENE names which are sitting in or loaded to NVRAM at each mixer boot. Not so concerned about changes during the session given as someone pointed out every little change from boot is likely to change the NVRAM data in the miser in real time.
I know if I donāt want to lose work that I need to save scenes, I also know unless I save a SHOW the SCENES are not backed up to USB, but I do need a memory reminder of which was my last saved SHOW given the way the sort list can lead you to wrong assumption and may cause you to overwrite the wrong scene.
A better indicator based on NAME of last saved SHOW than just the small numeric against the names would, for me, help prevent error.
I totally agree, that an indication of the last recalled and saved scene/show would help.
But it is important to understand that there is no current scene or show.
To ignore these facts, will lead to unintentional results.
What Steffen is saying is 100% true. Some might think it is just semantics between saying āCurrently loaded Show/Sceneā and āLast Recalled Show/Sceneā, but it is important to understand the differences and why one is correct and the other is not.
The last recalled show or scene āchangesā as soon as you move your first fader or change anything else on the console. It cannot be called the ācurrently loaded show/sceneā because the current state of the console does not match the saved setting in the saved show/scene. Therefore there really is no such thing as a ācurrently loaded show/sceneā except for the few seconds between actually loading a show/scene and when you first use the console after loading it.
Listing the āLast recalled Show or Sceneā is the only way to accurately depict this on the console. That statement is still true even after the console has been adjusted after loading a show/scene.
This is all semantics and not relevant to the problem at hand: What recall are we on? Itās useful to know without having to go to āHomeā āDataā to see the little indicatorā¦
As mentioned before, not understanding what we are saying or ignoring it, will lead to unwanted results with the recall function.
To say you need an indication what recall are you on is exactly the problem.
You are on no recall.
You can alter the whole system, and still, if it shows a current scene means you are misled to a state that has nothing to do with the last recall or the state the system is in. Even if you store scenes in between, the last recalled scene information is misleading.
That all means you canāt trust the information you are requesting.
Ok Iāll explain my use case
i use the desk with different band/situations and also at home recording with different setups.
my issue is remembering what scene/setup Iām currently using/was my last loaded as a lot of time i end saving the wrong scene
would be useful to have the last loaded scene like preselected in the save menu somehow and have an indication if the scene has changed.
on the recording setup for example i donāt change anything and i want to know if i did it by mistake.
or imagine using this in a theater where you have multiple scenes you need to know if you have to resave a scene or not and seeing some indication in the scene page regarding the last selected scene (with a dot if the scene has changed) would be useful
What you mean with you donāt change? You donāt even press a mute button or move a fader?
Scenes are not like documents in a software. A scene stores the complete state of all parameters. Always. If you press save, it stores everything.
First @steffenromeiss please be less rude in your responses and accept that people can have different use cases than your own
no as at home i Just Need to set the correct routing from the usb/gear that are already connected to the cq ā i have a couple of synths, a fractal etc etc and i use the cq for playing and for routing applications via usb to the out
i also do rehearsal with it and in there i want to save everything that i changed or not (but i Need to see if something changes) as for example i want my in ear to be the same as rehearsal (so i want to see if i changed something from the scene)
I wasnāt rude, show the terms that indicate rude language. And it has nothing to do with use cases. It is a general misunderstanding of how the scenes working.
My second answer:
That is absolutly irrelevant to the discussion.
I do understand what the scenes are used for. And how you are achieving specific goals with what you have. We all use it for the very same reasons.
But to express a wish for a specific function means not that it is possible to implement. The whole discussion is not about the marks in the scenesā system, it is about your expectations of what this can do for you.
It is totally fine to get the last recalled scene/show highlighted.
But to call it the current scene is the fault we are trying to clarify.
If you select a new scene, by intention or not, that will be the current-selected scene as the target for scene operations like save, delete or overwrite. That is the only point where we can call something, current.
To show if a scene has change is another problem. If you recall a scene, touch a fader and voilĆ , the scene is changed. It stays changed until you save it again, but you need to keep in mind that the content is totally unrelated to what was stored before. And you touch a fader, it is changed again. I hope you get the point.
Scenes are snapshots in timeā¦not more or less.
Bref !
We really need to know the last scene recalled (or memorized) This morning I went to my rehearsal room, turned on the sound system and saw that the system seems to indicate that the āConcertā mode has been memorized.
By going into the scene under input I could see that it was rather the āRehearsalā mode (Scene).
Itās annoying to have this confusion. It would be very useful to display the last scene memorized, also after a shutdown and restart.
You clearly see below that confusion
Picture 1 after restart
Picture 2 after āRecallā
Whe see that the information is momentally stored, the āVUā indicate (not visible on photo but Yello) the ācurentā scĆØne.
It could be really usefull tu have at minima, a definitif store of that information, including after restart at the same position.
AND if possible, having an indication of ācurentā or ālastā scĆØne reacalled. It could be on the MAIN HOME screen, (lot of place for this)ā¦
The higher elegance would be to have an autosave in question during the shutdown.
So exegetical responses donāt help.
Thanks
My observations
I think some of the confusion re SCENES is related to the terminology we use and how this all works. Scenes are simply computer memory spaces on the CQ. So a new scene save is simply a new set of data to a specific memory address space in the NVRAM within the mixer.
None of the scenes data locations in the CQ mixers are backed up from the CQ to external storage without a SHOW file save.
The naming function of these spaces in the Mixpad software are restricted via the FAT32 file system used in the mixers specs. ie 8char max names. The longer names we see on screen simply create an index file which is stored in the SHOW file if you backup as well as a NVRAM memory space.
Those names do not initially relate to files or folders just memory spaces and as such the data is already in the NVRAM just a different memory location to the āworkingā memory space.
After backing up the SHOW file the index to those differing memory spaces are also backed up.
On start up the mixer just recalls the last state currently held its NVRAM.
Starting from a new designated already saved scene is not really necessary because thats the position you had at switch off.
For me the problem I saw was that the FAT32 file system is only 8 characters and the data I enter in the name field on screen is longer so it requires an index file to correlate what you see on screen to what the file system can handle. That index file is stored only in the SHOW file to external storage if you manually save.
However with the WAV files in the USBPLAY and RECORD folders I can rename them on my PC to longer names and when I put them back in the mixer the mixer has no problem with using them. However thats simply because I am lucky that the first 8 character of each of the files i renamed remained unique because FAT32 will only use the first 8 characters. If two files have the same name the recall system to use the file may fail.
Now I initially thought that would be the case with naming SHOW folders but they are all 8 character names when created by the mixer and the index to what you choose to call them is held in a file call SHOW.dat in the saved SHOW folder set and also the NVRAM memory itself.
No Ive no idea how big the NVRAM memory address space is but assume itās not unlimited so would have to offload its memory addresses to external storage at some point. Im guessing thats the purpose of the NVDAT file in each of the SHOW folders. Clearly if you alter those file names on your computer you will destroy any index linking to the mixers NVRAM locations and its FAT32 file system which the mixer requires. But thats a bit off topic here re the SCENES bit of NVRAM.
An auto save of the SHOW file whilst potentially desirable would always need the USB storage device to always be attached at that point (which of course software could detect but thats add more coding simply to to warn you it canāt backup automatically, ie nearly pointless code). You donāt actually need any external storage to run the mixer.
So what we see is not necessarily what we get, we have to think computer memory addresses and their indexes not just files and folders when looking at how all this works.
Not an easy subject to discuss / explain.
David
Pic one should be scene in use at turn off ie an automatic recall of NVRAM state at turn on.
Pic 2 should be SCENE you manually choose. (overwriting the specific current memory space used in the mixer for current SCENE parameters ie moving from stored memory address (storage) to working memory address. The indicator highlighted in both pics show the SCENE in use.
At this point none of this is related to external storage and FAT32 file naming issues ( 8 chars v longer field names). I fell into the trap of only thinking about files and folders and not about memory spaces in NVRAM and other ares of the processor. ( I generically and incorrectly call them all NVRAM spaces but they are not as CPUs have working memory spaces plus other chips.) However the point is they are more forgettable in our minds than Files and Folders so we jump to wrong conclusions.
There are FAT32 file naming glitches ie Ive saved a library file form the mixer memory to a USB stick and seen the file name as shown on screen get a differing name on the USB stick as FAT32 can only have 8 characters in a File name but the Screen shows more due to indexing processes. But those glitches only affect the name of the file not the contents, but it does make recall a lottery so that needs to be addressed as a bug.
I have a background in computing so itās logical to me, apart from using the wrong terminology on describing the differing computer memory addresses but thats an age thing lol.
I thought as you did initially re SCENES but I have come to the conclusion its not quite as useful as I first thought due to the way the mixer processes the memory address spaces.
Hope this assists
David
Wowā¦ The Catholic Church didnāt do any better!
I was also a āComputer Development Analystā for 40 years. I am now a āREDā (as in the famous CIA series), thatās why I donāt believe you blandly.
This is something I learned and taught: long explanations only say the incompetence of the programmer to solve the userās problem.
In addition: Fat 32 structure is a pore excuse dating from before 1995 at leastā¦
Show the last scene recalled and we will say a BIG THANK YOU.
PS : For David, humoristic is not offenceā¦
