here is the screenshot showing the deck popup list
- Resolume_scrshot_deck_popup.jpg (87.31 KiB) Viewed 3321 times
To Resolume developers> while making this screenshot I noticed these additional issues:
1) Double-clicking on a deck name under the "composition panel" will load it at a random location, sometimes as a visible deck, sometimes inside the pop-up list. So basically if it loads inside the popup list, there is no way to access it anymore.
2) Loading a deck this way does not affect too much FPS, that's good. However there is no "progress bar" or even something telling you that the GUI recieved the command and is loading the deck, except that the whole GUI is not responding to mouse clicks. If you dare to click on any clip thumbnail while the deck is loading this will completly freeze the whole app (Windows says: "not responding"), including frame playback of course, until the deck is loaded. So one has to be careful and patient (about 10 seconds on my machine depending on deck size).
Unfortunately I am going to stop using R3 as long as these issues are not solved:
- deck popup list not working
- composition not reloading all decks with the same arrangment as when composition was saved
Regarding the discussion we had about loading clip to RAM or streaming from disk. In my opinion, the easiest things would be: the first time a given clip is loaded into a given layer, allocate a RAM buffer of its size and stream the file to both GPU and RAM at the same time for 1 cycle (I mean from the first frame to the last, once). Then, since Resolume is about looping clips, for all the next loops: stream from RAM and forget the file. There could be a user setting to limit this process to files under a given size.
Well, I am sure you already thought of it
In a previous post I said I was going to have a look at what happen when loading my big composition with one big deck. The file size is 15MB and as expected the hard drive is not all the problem: the whole file seems to be loaded in memory very quickly. Resolume then probably parses the XML file for minutes. It seems that it does this with only 1 thread, as it uses 100% of only one of my 2 cores. I guess that this is even done in the main thread as the GUI is not responsive and not refreshed during this time.
Sorry to "disclose" all this, but any user can figure it out, and my goal is to provide detailed feedback.