New Build, All Meters Crashed. How?

[d.healey]

@Chazrox said in New Build, All Meters Crashed. How?:

gotta be something im doing in here...

That's why we are you using the test snippet, so we can figure out the issue without all the extra noise.

[Chazrox]

@d-healey Here it is doing that weird thing with the snippet. This is the latest commit from 15 Hours ago btw.

See it doesnt work but for some odd reason it works while im dragging it around. Not sure how I even figured that out.

Untitled.mov

[d.healey]

@Chazrox said in New Build, All Meters Crashed. How?:

it works while im dragging it around. Not sure how I even figured that out.

Sounds suspiciously like this issue - https://forum.hise.audio/topic/12235/shaders-looks-broken-on-new-build

[Chazrox]

@d-healey What should I do in my case?

[d.healey]

@Chazrox

Ask @clevername27 if he can recreate the issue with your test snippet, since he was also having the problem.

Roll back through different HISE commits until you find the earliest commit where the problem started. Then post the commit hash here and try and get Christoph's attention.

[Chazrox]

@d-healey How do I find the other commits? I can only see this one. Am I in the right place? Still getting used to Github. I watched your git versions video but I dont see the same options here.

[ps]

display buffer based paint routines are super laggy suddenly with latest commit here as well (also in exported plugin) - had to roll back to a january commit - I also built very latest commit without any of my modifications from the source and same problem. If anybody finds the last working commit so we can find out what's going on that would be awesome :)

[clevername27]

@Chazrox @d-healey

• Have you tried compiling it?

• Are you using shaders for the meters?

[Chazrox]

@clevername27 I compiled and meters are broken in DAW also. Meters are all LAF.

[d.healey]

@Chazrox said in New Build, All Meters Crashed. How?:

How do I find the other commits? I can only see this one.

What you're seeing there is the list of branches.

Click on a branch to view the code in that branch. Then click the commits button to see all of the available commits.

Then use git to checkout the commit you want. I usually start by going back a couple of months and trying a commit from there. If it works I go forward a few weeks and try one, if it doesn't work I go back another month, etc, etc. Doing this you can narrow down the problem commit pretty quickly without having to try every single one.

As always, make sure you only have one copy of the HISE source code on your system at any time. Resave the juicer file and clean the build folder between builds (you don't always need to do this, but unless you know for certain that you don't it's safer to do it).

You will probably benefit from this video too

[Chazrox]

@d-healey What does this mean?
I ended up finding it. Im following along with the video again. I used your video to originally get the latest commit. When I try to checkout I get this message. I deleted all other versions of HISE also.

[d.healey]

@Chazrox That's telling you that you have made changes to the HISE Standalone.juicer file so you can't checkout another commit until you either commit those changes or undo them - this is to stop you overwriting changes you've made.

You have three choices.

If you want to keep the change then you need to commit them.

If you want to discard any changes you've made then type git reset --hard

If you don't know, type git stash and it will put them into a magic bubble which you can burst later by typing git stash pop when you want to retrieve the changes.

[Chazrox]

@d-healey this commit works. Not sure about the date. This is an older version I downloaded a couple of weeks ago I think.

22fc80083350aa3daa41e39ef6fc5090db505056

[d.healey]

@Chazrox said in New Build, All Meters Crashed. How?:

this commit works.

Good, now find the first commit that doesn't work :)