bugs

airlock · Posted: Sun Jul 19, 2020 7:10 pm Post subject:

Could you do one that shows how to wire an Osc for note and gate from LFO, Seq, RNDSIGS, etc? It looks like any patch I try to access as a reference from the old 32bit version gives me a handful of access violation errors.

Access Violation.png

Description:

Filesize:

6.29 KB

Viewed:

6744 Time(s)

blue hell · Posted: Mon Jul 20, 2020 4:49 am Post subject:

Wiring does not matter, that just should not ever happen .. can I have a patch please causing such issues? I think I would not need the audio sources that go with it.

airlock · Posted: Mon Jul 20, 2020 11:27 am Post subject:

Jan, color me clueless, I really am not sure how to wire these things! Razz

So, what I did as a check just now was open Wren, chose New, and open a random patch. It looks like any patch from the 32bit version will give me these errors, tho it seems not the error codes are not the same. (I'll double check that.)

Patch 2016-06-14-01 and 2017-01-01-01 return the following

2016-06-14-01.png

Description:

Filesize:

6.47 KB

Viewed:

6709 Time(s)

airlock · Posted: Mon Jul 20, 2020 11:32 am Post subject:

Then when I closed Wren, the following was sitting the in the middle of the desktop:

Closed.png

Description:

Filesize:

6.38 KB

Viewed:

6708 Time(s)

airlock · Posted: Mon Jul 20, 2020 11:50 am Post subject:

Patch 2015-09-08-01 opened, but trying to start a new patch and then opening another crashed the program in a polite manner with no error dialog appearing.

Starting Wren again after THAT, it loaded 2015-09-08-01 again, so I started a new patch and then loaded my own patch created Saturday (on 64bit Wren) and it too came back with the same Access Violation as originally described.

The next restart loaded the last patch, I unloaded that patch (New) and then trying to quit Wren with no patch loaded returned another Access Violation with a different number.

Next restart revealed that my own patch name was in the title bar but there were no modules (blank edit area.) Loading my patch revealed that it was now a blank page. Ouch. My fault, I was a little careless on the last exit.

blue hell · Posted: Mon Jul 20, 2020 12:20 pm Post subject:

I looked into it, not seeing those issues here .. but, suspecting where the issue could be ... I've found a handful of small bugs that might cause this .. more info already on https://bluehell.nl/wren/#changes

I'll post a new version soon .. food first though

airlock · Posted: Mon Jul 20, 2020 12:31 pm Post subject:

Recreated my lost patch, fiddled with it a bit and saved it. Started a New patch, Loaded and ran 2016-03-07-01, stopped it, hit New and got another Access Violation, tho the patch did clear to an empty edit screen. I just now noticed that hitting New does not clear the last patch name from the title bar. THAT might be a clue?

EDIT to add: loaded my patch Now What Laughing

, hit New, title bar now shows a patch name that was last loaded on previous start.

blue hell · Posted: Mon Jul 20, 2020 12:51 pm Post subject:

Can you try https://bluehell.nl/wren/wren.exe please?

You can just copy this exe over your existing one .. I mean the existing one is no fun to use anyway ...

airlock · Posted: Mon Jul 20, 2020 1:17 pm Post subject:

Wow, that updated exe made a difference. Every random old 32bit patch I tried works (!), and no access errors. This is huge, thank you Jan!

blue hell · Posted: Mon Jul 20, 2020 1:27 pm Post subject:

Heh, thank you for pointing out the bug & testing the new one Cool

I'll make it an official release then.

[There is, and has ever been, a very weak point in Wren. In order to let data travel from outputs to inputs as fast as possible there are no checks being made to see if valid memory is being used in the process - I'll just have to make the lists specifying the locations correctly (and that is about 6000 items I think), or it may crash on accessing memory that 'is not there'.

And I should have done this long ago .. it is possible to run checks to see if such issues exist .. I finally made those checks .. checks that can run without actually making a patch, but are just creating module by module automatically .. and then see if there are inconsitencies in the way input/outputs are named and numbered.]

Anyway, sorry for the mess up Embarassed

blue hell · Posted: Mon Jul 20, 2020 1:37 pm Post subject:

New release made, see: http://electro-music.com/forum/post-445766.html#445766

airlock · Posted: Mon Jul 20, 2020 1:41 pm Post subject:

boaone · Posted: Thu Jul 30, 2020 11:04 pm Post subject: Parameter typing from keyboard.

I ran into a little problem with parameter changing with type from keyboard. Sometimes it didn't work randomly.

blue hell · Posted: Fri Jul 31, 2020 4:41 am Post subject:

Not all parameter editing works .. the params that have knobs mostly work not ...

Then for text that has to be entered .. when you move the mouse outside the text field the edits get cancelled .. not really handy that ...

Is it like that?

boaone · Posted: Fri Jul 31, 2020 10:37 am Post subject:

With empty wren im loading first osc module then ctrl click to type 220.0 hz while hovering mouse pointer at number after that there is still 440.0 Hz and parameter become locked.

blue hell · Posted: Fri Jul 31, 2020 11:15 am Post subject:

Yeah that is a known bug, and not very easy to fix unfortunately ... you just have to use the knobs.

blue hell · Posted: Fri Aug 07, 2020 7:57 am Post subject:

Discovered an issue with the recorder module, it, at times, may crash Wren - it is a bit random.

Ran into it while working on the poly version and seem to have fixed it there, but it may crash the current release version too.