Page 4 of 5
Re: AudioBlock
Posted: Sun Jan 24, 2021 10:26 am
by wde
I think I found the cause of both of the issues. Updated.
Re: AudioBlock
Posted: Sun Jan 24, 2021 11:02 am
by IXix
Thanks for the updates. Seems to work okay in 32 and 64 although I've not stressed it at all. I do get this exception the first time I show the waveform view (in both 32 and 64) but it doesn't seem to stop anything for working as far as I can tell...
Re: AudioBlock
Posted: Sun Jan 24, 2021 1:11 pm
by wde
Fix.
Re: AudioBlock
Posted: Sun Jan 24, 2021 7:23 pm
by Candle
Just DL'd v. 1.2.3.4 & now Buzz won't start
Will try to re-install v. 1.2.3.2 (what I was running previously, I didn't get around to upgrading to v. 1.2.3.3 before you released v. 1.2.3.4). I'll let you know if that works to get Buzz started.
See You In The Shadows…
Re: AudioBlock
Posted: Sun Jan 24, 2021 7:26 pm
by Candle
Yeah, I reverted back to v. 1.2.3.2 & Buzz loads fine. Not sure what's going on…
See You In The Shadows…
Re: AudioBlock
Posted: Sun Jan 24, 2021 8:33 pm
by IXix
Sorry to be such a pain but still getting that exception when first showing the audio waveform. Rather than just complain though, I thought I'd try to be helpful. The exception is complaining that
evbSender.Index is -1. I expect that means something to you.
Re: AudioBlock
Posted: Sun Jan 24, 2021 8:41 pm
by IXix
Oh and the call originates in EnvelopeBox.Mi_Unchecked()
Code: Select all
private void Mi_Unchecked(object sender, RoutedEventArgs e)
{
this.EnveloperLayer.SetFreezed(this, false);
}
Steps to reproduce:
1. Add AB and open dialog.
2. Drag sample to AB slot from Wavetable View
3. Click Show/Hide audio view
Re: AudioBlock
Posted: Mon Jan 25, 2021 2:25 pm
by wde
Another try. It was something I tried but then forgot
Re: AudioBlock
Posted: Mon Jan 25, 2021 4:50 pm
by IXix
wde wrote: ↑Mon Jan 25, 2021 2:25 pm
Another try. It was something I tried but then forgot
Really sorry, I'm not trolling you honestly, but it still happens. Same steps to repeat, same issue in another location I'd guess? I can try debugging later if you like?
Re: AudioBlock
Posted: Mon Jan 25, 2021 6:26 pm
by wde
IXix wrote: ↑Mon Jan 25, 2021 4:50 pm
Really sorry, I'm not trolling you honestly, but it still happens. Same steps to repeat, same issue in another location I'd guess? I can try debugging later if you like?
I can't reproduce it but I think it is related to threads since that was the last area I modified. I have an idea why this is happening so can you try the two versions and let me know if it still happens?
Re: AudioBlock
Posted: Mon Jan 25, 2021 7:13 pm
by IXix
wde wrote: ↑Mon Jan 25, 2021 6:26 pm
I can't reproduce it but I think it is related to threads since that was the last area I modified. I have an idea why this is happening so can you try the two versions and let me know if it still happens?
Still happens with both of those. Only happens once, then all's well. Strangely it didn't happen when I tried B2 immediately after B1 without closing Buzz first, I followed the same steps and B2 didn't give the exception.
Re: AudioBlock
Posted: Tue Jan 26, 2021 4:33 pm
by wde
Some cleanups and fixes. Stay strong, we are getting there
Re: AudioBlock
Posted: Tue Jan 26, 2021 5:49 pm
by IXix
wde wrote: ↑Tue Jan 26, 2021 4:33 pm
Some cleanups and fixes. Stay strong, we are getting there
Ah, well, now I get a similar index out of range exception when I drag a sample from the WT view to an Audioblock slot BUT it occurred to me that as you can't replicate it, maybe it's a theme thing and I was right. I normally use the default them but switching to the iLKke machines theme stopped the exception from happening. A clue perhaps?
Re: AudioBlock
Posted: Tue Jan 26, 2021 7:42 pm
by wde
IXix wrote: ↑Tue Jan 26, 2021 5:49 pm
Ah, well, now I get a similar index out of range exception when I drag a sample from the WT view to an Audioblock slot BUT it occurred to me that as you can't replicate it, maybe it's a theme thing and I was right. I normally use the default them but switching to the iLKke machines theme stopped the exception from happening. A clue perhaps?
That is it and I can reproduce it. I don't have time to look into this right now but it looks like it is somehow theme related. For example context menu behaviour is very strange with default theme.
Re: AudioBlock
Posted: Fri Jan 29, 2021 9:29 pm
by thOke
Saving templates with reference to the wav files instead of saving them with the bmx does not work.
Actually saving works, but loading the template gives the following error:
"... The sequence does not contain a corresponding element"
- template.jpg (36.67 KiB) Viewed 13293 times
Re: AudioBlock
Posted: Sat Jan 30, 2021 3:27 pm
by wde
thOke wrote: ↑Fri Jan 29, 2021 9:29 pm
Saving templates with reference to the wav files instead of saving them with the bmx does not work.
Actually saving works, but loading the template gives the following error:
"... The sequence does not contain a corresponding element"
This happens with any template that has "Wave references only" enabled. Seems to be related to audio format: works with wav, but not with mp3 for example.
I did update AB to check if the wave is there to avoid crash.
Edit: Seems to be Buzz bug. Same problem if you create template that has only Jeskola Delay and you have mp3 files in wavetable.
Re: AudioBlock
Posted: Sat Jan 30, 2021 5:40 pm
by thOke
wde wrote: ↑Sat Jan 30, 2021 3:27 pm
I did update AB to check if the wave is there to avoid crash.
It works for wav files now! Thank you!
Re: AudioBlock
Posted: Sat Jan 30, 2021 7:39 pm
by rajmond
IN PLAIN SWEDISH:
SLUTA PORRA MIN HJÄRNA, VAD I HELVETE?
or translated into english:
STOP PORNING MY MIND, OMG THIS IS GERAT, WHERE DO I DONATE?
Re: AudioBlock
Posted: Sat Jan 30, 2021 7:48 pm
by rajmond
Silly question, how do I get it to display the snap-to-lines?
Re: AudioBlock
Posted: Mon Feb 01, 2021 3:44 pm
by wde
1.2.4.3
Bug fix.
rajmond wrote: ↑Sat Jan 30, 2021 7:48 pm
Silly question, how do I get it to display the snap-to-lines?
They should appear when you zoom in.
IXix wrote: ↑Tue Jan 26, 2021 5:49 pm
I normally use the default them but switching to the iLKke machines theme stopped the exception from happening. A clue perhaps?
Interesting: if you copy 'ParameterWindow.xaml' from iLKke machines theme to Default theme the problem disappears. So maybe some definitions are missing from Default theme.