During exporting Wire does not like Alley being used for conversions

[webel]

Wire: 7.10.1 vs Alley: 7.10.0 vs iMac 5K 2017

I've recently revealed on this forum that while "taking Resolume on a second date" I've also been dating Wire. Turns out that Wire likes to talk to Avenue, so that's all good. But dating Alley and Wire at the same time is not working out so well. Wire gets upset while exporting, and Alley gets upset while converting. Wire even freezes on me! Guess I've been pushing my luck too far. I won't provide the grubby details here, but I'm blaming it on Mac not paying enough attention to Alley and Wire. For now I'll just date either Alley or Wire one at a time. Wire is sometimes a bit unstable but so enticing and worth the patience and effort.

[Arvol]

What are you doing?
Alley is a multicore converter, so if you're converting 10+ files, that is a BIG system load. I wouldn't do anything else during that process.
Also, mac... say no more lol

[webel]

@Arvol

> What are you doing?
Specifically? Converting a single MP4 file on Alley while exporting a 4K patch on Wire. Exporting to DXV from Wire is clearly less load than exporting to ProRes.

> Alley is a multicore converter, so if you're converting 10+ files, that is a BIG system load.
Where did 10+ come from?

> I wouldn't do anything else during that process.

The ideal workflow indeed seems to be to perform all Alley conversion to prep resources before using in Wire. The main issue is that Wire is sometimes freezing after exporting about 20s of 30s.

The question is whether Alley and Wire are somehow competing for specific resources during their mutual operations.

[Zoltán]

All system processes are competing for resources.
Does your imac have an ssd?
Which cpu?

[webel]

> Does your imac have an ssd?

Fusion Drive, but I'm exporting to a Samsung T7 SSD via USB3 (Thunderbolt port).

> Which cpu?

3.5 GHz Quad-Core Intel Core i5

Graphics: Radeon Pro 575 4 GB

Since reporting this, I've since determined that there may be a memory issue when exporting to ProRes from Wire 7.10.0.12509. I've emailed details and log files and an example patch. The memory on exporting from Wire multiple times to ProRes from a 4K patch with random gradients grew to over 84 GB (on a 32 GB machine). This might be what I am seeing.

Since reporting, I've been using only Wire without Alley running. (What I might have been seeing with Alley+Wire is just the straw that broke the camels back.)

[webel]

@Zoltán. Attachment shows massive memory usage over 38GB on export of a 4K random gradient patch (16 bpc) from Wire on a 32GB machine, during the export.

[EDIT: Won't add further attachments, but that memory stays consumed even after the export completes, and after closing the Export dialog, it is only recovered when Wire is fully closed.]

[Zoltán]

Hmm, that looks like a memory leak.
We'll see what we can do.