Version 7.22 major issues!

[EBMCreative]

I was excited for this update.

But sadly it is unusable.

1. Loading and quiting now takes 5+ minutes each way.
2. Frame rate now drops to 9-5fps or below.
3. Destroyed all my autopilot setups. Including play next clip and loop counts
4. Memory use has gone sky high. 50% increase.
5. Lost some of my midi mapping.

On a positive note.... My midi map now opens quicker.

I'm sorry but what in the F are you all doing to make this happen so poorly.

And I have a feature request..... Can you turn off and hide the column play rows. Or maybe have the option to turn them off per group. Maybe this is there and I did not explore to look because I have to now go back to the older version and spend hours to fix everything in the composition that this update has screwed up!

Did you even bother to test this version before releasing it. And I just paid to renew the license for this version and it's useless.

Really not happy!

Before 7.22

Before 7.22

After 7.22

After 7.22

[mowgli]

I've only just started test-driving this release and it's unusable.
Like the OP, my fps on comps that were running smoothly are now below 12fps.

I still have Resolume 6 installed on the same machine and similar comps are running smoothly at 60fps.

[mowgli]

After testing on 6 I reopened 7.22 and magically everything works again...
I don't know what to think.

[EBMCreative]

I don't know what to think. I don't have the patience to reinstall and see if it magically fixes itself. Plus I am coming from 7.21, so the new 7.22 installs over 7.21.

And why should you have to install it twice? Or open an older version to them open a newer version so it works correctly.

Besides the low fps. The 50% increase on memory use and the 800% increase on cpu usage is also a huge issue.

[Christoph]

Yeah looks like there were a few issues that slipped through the testings with the big changes in that update. We'll work on getting those fixed asap, but need a little more information to find out what is going on here.

1. Loading and quiting now takes 5+ minutes each way.
2. Frame rate now drops to 9-5fps or below.
3. Destroyed all my autopilot setups. Including play next clip and loop counts
4. Memory use has gone sky high. 50% increase.
5. Lost some of my midi mapping.

1. How big is such a comp that is taking that long for you, how many layers and columns?

2. This sounds serious and we'll need to find out what causes this. Do you see the same with a fresh new composition of only with a particular old composition or all old compositions? How are your files encoded?

3. Sorry for the loop counts, this slipped through and we'll fix that. Can you give some details to the play next clip? Haven't seen issues with this yet.

4. Again for the increase from 36% to 53% would be good to have some context, how many clips are approximately in such a deck and how much RAM do you have in your machine?

5. Can you tell what MIDI mappings you lost? Are whole preset-files gone or some shortcuts missing from a preset?

Do you have any external protocols like MIDI (I guess yes), OSC, DMX or Webserver activated? If so, which ones?

Can you submit a log-file via the feedback-tab of the preferences and mention that forum thread in the text-field?

[EBMCreative]

Thank you for your response.
My answers are below.

1. How big is such a comp that is taking that long for you, how many layers and columns?

2. This sounds serious and we'll need to find out what causes this. Do you see the same with a fresh new composition of only with a particular old composition or all old compositions? How are your files encoded?

3. Sorry for the loop counts, this slipped through and we'll fix that. Can you give some details to the play next clip? Haven't seen issues with this yet.

4. Again for the increase from 36% to 53% would be good to have some context, how many clips are approximately in such a deck and how much RAM do you have in your machine?

5. Can you tell what MIDI mappings you lost? Are whole preset-files gone or some shortcuts missing from a preset?

Do you have any external protocols like MIDI (I guess yes), OSC, DMX or Webserver activated? If so, which ones?

Can you submit a log-file via the feedback-tab of the preferences and mention that forum thread in the text-field?

1. My comp size is about 16.5mb.
67 layers total
303 columns
This is the breakdown of it.
16 groups total
16 layers rarely used 1-2 times a week
The above are Mostly only used for testing purposes.
2 layers for strobe content
28 layers bypass but playing
18 layers playing visual content 3 of these are routed layers to play on another layer
of the above layers only 7-8 have the opacity up at once.
3 layers random play during night for 2min each time maybe 10-15 times in a 6 hour time frame.

2. I installed the new version. And tested this with a brand new comp. I had 50 layers and tried HD, 4k, and my comp size of 5000x2250. The HD didn't have an issue. The 4k started to take it down heavily. If I ran 30 clips of my comp size it would start to dip below 25fps. But as I turned on bypass for some of the layers it started to get higher. But I only play max 5 layers normally that would be my comp size that are not bypassed. The rest is hd with some 4k content. But this is only happening when I am playing all of the bypassed layers at the same time. If I stop the bypassed layers from autoplaying then the fps goes back up. But It is only three layers that are playing comp size non bypassed clips. Everything is dxv except for 3 jpg files, some text blocks, and a handful of png files.
3. In the autopilot settings you have layer determined, do nothing, play next, play previous, select clip. The part next was destroyed and reverted to layer determined.
4. There is probably a total of 2500-3000 clips in all layers. The main machine has 96gb of ram running the latest update of windows 11 and Nvidia drivers.
5. Just a few shortcuts went missing. Most noticeable was the midi shortcut for the left to right composition slider to scroll 5th he columns.
6. We are only using midi shortcuts at this time.

I have some other information.

Load times for 7.21.3
35 sec open
95 sec close

Load times for 7.22
70 sec open
9.5 minute close

This is also happening on the backup computer as well.

I am going to send you the files that will have for

7.21.3
the midi mapping
comp
feedback log after startup

7.22
Comp saved from 7.22
A new comp that is untitled started with 7.22
Feedback log after startup.

I will submit that to mail@resolume.com with the subject referencing this forum post.

Pleaae remember that I don't have these issues on 7.21.3

Thank you.