2.14.2: Audio map gone in Win10?

[Eriksson]

Just updated my computer farm to 2.14.2.
In Windows 10 the audio map field is gone. There is just some sort of slidebar visible.

Win_10.jpg

In Xubuntu 16.04 it's there, but shrunken somehow.

Xubuntu_16_04.jpg

Am I missing something here? Anyone else seen this??

/M.E.

[Carsten]

It looks okay in 2.14.2/WIN7. There are some minor redraw/scrolling issues, but, I think this is intentional. Could you try the english language setting? You can also now drag the separation area between content list and audio settings up and down. Maybe it makes a difference. I once noticed such issues after a fresh install, and when I adjusted the GUI, everything was there.

- Carsten


edit - it may indeed be the new separation adjustment. I was able to get a similar appearance as you on my Mac system when I dragged the separation down far enough. So, try playing with it. I suggest dragging it up. The windows version doesn't show that tiny dot, maybe Carl can work on that. Just click on that narrow white separation line to adjust.

Bildschirmfoto 2019-05-11 um 15.52.30.png

[Eriksson]

No luck. If I adjust the separation up I just get an empty field where the audio mapping is supposed to be. If I do the same in Xubuntu and move it down I can get something similar by "hiding" the audio map.

Win10_again.jpg

But: I installed 2.14.2 on another Win10 computer, a really slow "remote drone" without monitor used for remote access at a cinema nearby. And that works!
So I went back and started investigating output resolution, switching monitors and all kind of tricks. No luck, no audio map.

Another thing I noticed. 2.14 seems more demanding than 2.12 when it comes to computer performance. The slow remote drone took quite some time "loading" the audio map when switching between audio and video track. My own Win10 desktop computer is no 2019 Lamborghini, but reasonably fast for it's age. It had no problems with 2.12, but staggers conciderably when running 2.14. Every 10 seconds DCP-o-matic UI says "not responding", but then comes back and continues. The DCP:s coming out are fine though.

Maybe a fresh install of DCP-o-matic would be the next thing to try?

/M.E.

[Carsten]

What's the screen resolution on that problematic machine?

- Carsten

[Eriksson]

1024 x 768 normally. VGA from the motherboard to a s**t monitor (this computer farm is mostly run remotely) plus DVI from a separate card to a 1920 x 1080 TV.
But I tried every possible resolution with these monitors in different combinations with the same result.
However, a new desktop computer for Windows is on the shopping list for this year...
/M.E.

[Carsten]

When I set my Mac screen resolution to 1024/768, I get the same issue, and no adjustment solves the issue.

So, it's the comparably low resolution. Maybe Carl can fix that, but, I guess we have to acknowledge that a feature-loaded GUI simply needs a minimal display resolution to work. Maybe you can tweak it further by adjusting GUI settings, font size, etc. I am not familiar with these settings in WIN10.

- Carsten

[Eriksson]

Or is this the right time for me to put that crappy monitor back in the attic (where I found it ten years ago) and get a real one instead.
Working with DCP-o-matic is working with film for the big screen, right
/M.E.

[Carsten]

You mean you are about to abandon a perfectly working piece of hardware? NOOOOOOOOOOOOOOOOOOOO!!!1!1!!!111!!


- Carsten

[Eriksson]

Not abandon, just put it away somewhere dark and cool to mature.
Like a bottle of fine wine
/M.E.

[Carsten]

puhhh... make sure it's wrapped nicely with cables and manual in case someone finds it for reuse...

I WOULD take it, but I have no space left in my attic.

- Carsten