Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[StFeder]

In visualizations the function "REMAINING_TIME" isn't working correct any more with build 20.0.73. It displays something like "596523:13:22".

Interestingly it only fails for files imported after 2010/07/12 and works for files imported before 2010/07/10.

I don't know about the days in between, because I didn't import anything these few days

[StFeder]

Still there in 20.0.74.
Attached is a screenshot showing a file imported at 2012/12/08. As you can easily see, the time is shown correct in the above display, but not inside the visualization using the "REMAINING_TIME" variable.

[Matt]

REMAINING_TIME is working here on build 20.0.75.

[Matt]

REMAINING_TIME is working here on build 20.0.75.

I did find a weird problem where mystery text would display on some of the frames.

I can't explain it, but it'll be fixed in a coming build.

[StFeder]

Sorry, I messed up the version numbers. I was referring to the two last public (not beta) builds 20.0.73 and 20.0.74. Corrected it in my above posts.

The "mystery text" bug should be the one I reported in my other topic (can't post links via smartphone). Nice to see it fixed

As always: Thanks for taking the time to answer and doing the fix!!

[Matt]

I can't explain it, but it'll be fixed in a coming build.

I can explain it now (not that it matters).

We were returning the pointer to a JRString object, but the JRString would go away and make the pointer junk.  Doh!

[StFeder]

I can confirm: the flickering is gone in beta 20.0.76.

But the wrong time display is still there. I found, that for the first second the display in MC also is "strange" (see attached Screenshot) but after 1 second it gets sorted and shows the right timecode. It does not always happen for the main display, but happens every single time for the visualization.

I tried to reimport an old file which works correctly. Coping it to another location and reimporting it makes the time display start running wild. Setting the PC time back to 1990, importing a file: time display broken. Set the time back to current date, time display for the file still broken.

When system time is set to 1990, it's still the same set of files which are working well and which time display fails. It fails for files imported after 2010/07/12 and works for files imported before 2010/07/10. I'm not sure if it is really connected to this date or the value of that field. I guess no. Reanalyzing doesn't change anything, neither does it break working files nor does it fix failing files.

So far I didn't find a way to make failing files work again. It neither seems to be related to the audio hardware nor to some playback settings (I'm using MC in different environments).

Creating a new library doesn't solve the problem.

If I get the time I'll get my old laptop and see what happens there.

[StFeder]

Played around a bit more and can say: for REMAINING_TIME build 20.0.72 is fine .73-.77 isn't.

Looks as if some other things got messed up since build 20.0.73. There appears a bug which makes impossible to save some changes to Visualizations.

I use this Vis:

Code: [Select]

<MJV Version="1.0">
<Component GUID="36267E6D-70E1-435e-9E2A-428EEA2D3C7E" Name="Flush">
<Properties>
<OnEquation>on=1</OnEquation>
<Color>0x000000</Color>
<Rectangle>0,0,1,1</Rectangle>
<FlushEquation>f=1;</FlushEquation>
</Properties>
</Component>
<Component GUID="B21F9002-EF2E-4d5b-9D40-F61B8F3B34D8" Name="Spectrum Analyzer">
<Properties>
<OnEquation>on=1</OnEquation>
<DrawSource>0</DrawSource>
<Channels>0</Channels>
<DrawPeaks>0</DrawPeaks>
<DrawBars>1</DrawBars>
<Mirrored>0</Mirrored>
<ImageFile>COVER_ART</ImageFile>
<PeakGravity>512</PeakGravity>
<BarGravity>1024</BarGravity>
<PeakTerminalVelocity>0</PeakTerminalVelocity>
<BarTerminalVelocity>0</BarTerminalVelocity>
<PeakThrowForce>0</PeakThrowForce>
<FFTElements>400</FFTElements>
<FrequencyScale>1</FrequencyScale>
<TopWeight>5</TopWeight>
<UpScale>100</UpScale>
<BarWidth>0,0050999997183681</BarWidth>
<BarSpacing>0,0015000000130385</BarSpacing>
<PeakHeight>0</PeakHeight>
<PeakColor>0xFFFFFF</PeakColor>
<Gradient>{3, 1} [[0x404040,0x000000,0x000000]]</Gradient>
<MainRectangle>0,0,1,1</MainRectangle>
</Properties>
</Component>
<Component GUID="BBEC668A-420F-4faa-856D-880DACE05B5B" Name="Text">
<Properties>
<OnEquation>on=1</OnEquation>
<Text>[Tanz]</Text>
<RenderDelayMilliseconds>0</RenderDelayMilliseconds>
<RenderDuration>0</RenderDuration>
<TextLocationEquation>x1=0;y1=0;x2=1;y2=.1</TextLocationEquation>
<FontName>Calibri</FontName>
<FontSize>0,0599999986588955</FontSize>
<TextColorEquation>r=1;g=1;b=0;</TextColorEquation>
<TextAlignment>1</TextAlignment>
</Properties>
</Component>
<Component GUID="BBEC668A-420F-4faa-856D-880DACE05B5B" Name="Text">
<Properties>
<OnEquation>on=1</OnEquation>
<Text>REMAINING_TIME</Text>
<RenderDelayMilliseconds>0</RenderDelayMilliseconds>
<RenderDuration>0</RenderDuration>
<TextLocationEquation>x1=0;y1=0.2;x2=1;y2=1</TextLocationEquation>
<FontName>Calibri</FontName>
<FontSize>0,1599999964237213</FontSize>
<TextColorEquation>r=9;g=9;b=9;</TextColorEquation>
<TextAlignment>5</TextAlignment>
</Properties>
</Component>
</MJV>

Saving this in 20.0.73 to 20.0.76 messes up the color of Spectrum Analyzer. This line is affected:

Code: [Select]

<Gradient>{3, 1} [[0x404040,0x000000,0x000000]]</Gradient>
Saving it changes the first color value to something like 040040.

[Matt]

REMAINING_TIME is working fine here.

I wonder what might be different?

[StFeder]

A fresh portable installation on the same PC also fails. I'm using MC with English language but Windows is a German version. Maybe there is a strange connection due to some regional settings?!

I'm on vacation for two weeks, so it'll take some time before I'll do some further investigation...

[Matt]

A fresh portable installation on the same PC also fails. I'm using MC with English language but Windows is a German version. Maybe there is a strange connection due to some regional settings?!

I'm on vacation for two weeks, so it'll take some time before I'll do some further investigation...

I tried running with a German translation and it still worked fine.

[Hendrik]

I think I've found a problem, I'll try to make sure and fix it tomorrow.

[Matt]

I think I've found a problem, I'll try to make sure and fix it tomorrow.

Care to share what was going on?

You could email me if it's confidential.

[StFeder]

That sounds great I'll be happy to be back at home and see the visualization work again!

Thanks for spending the time to find the clue