@all

Rave 1.10 has been released on OS4depot. I'd like to thank users who reported problems with the previous version - above all, Mike Steed, Niels Bache, and Javier de las Rivas - and helped with the testing.

As usual, there is an article on my Ko-fi blog that tells the story behind the current release. If you like what I've done and want to support my efforts, I won't say no to a coffee

Thank you, and enjoy!

@jabirulo

Quote:
This should now be fixed too for Rave 1.10.

@FlynnTheAvatar

Quote:
Open the information window on the Shell icon in SYS:System, remove "TABBED" from the WINDOW argument, and save.

@joerg

Quote:
That, or possibly some other specialist.

@FlynnTheAvatar

Quote:
Try disabling the tabbed mode before my console fix hits the public.

@icbrkr

Quote:
Absolutely not! The OS4 installation on my X5000 is very stable. But then again, I run more or less pure Update 3 - the only "foreign" component is the Radeon RX driver from the Enhancer Pack.

You seem to be having a hardware problem. I'd check your PSU or RAM modules first.

@nbache @jabirulo

I'll send a test build to both of you before releasing Rave 1.10.

@jabirulo

I can't reproduce this either. However, I reviewed the waveform gadget's selection hook, and I found a situation similar to the one that caused the race condition in the Settings, so I applied the same kind of fix just to be on the safe side.

@msteed

Quote:
It was a race condition. More details in my next blog post

@all

With the help of Niels Bache, the X1000-only crash has been fixed for Rave 1.10.

@Elwood

It has always been this way: a BOOPSI gadget that becomes activated receives all input until it is deactivated. So an active string gadget (for example) will swallow the ESC, instead of the application receiving it. It would require some redesign in the framework to do something about it. I have no idea (yet) what the needed scope of the redesign would be.

@jap

The loading and saving is handled by sndfile.library, so its limitations apply to Rave as well. The library does not support 4-bit linear PCM data, so you can't just take a sample and save it as a 4-bit WAV. 4-bit data is mainly supported through the IMA ADPCM format, which effectively encodes audio using 4 bits per sample. Rave already supports IMA ADPCM for both loading and saving. However, when reading such files, the library API returns the data as 16-bit integer or float, so there's no way to get the raw 4-bit data unless you parse the file yourself, bypassing the library. The effort/benefit ratio would be so low here that I don't see myself going down that route.

On the other hand, sample rates below 8000 Hz are perfectly possible, it's just a matter of lowering the current limit. (Although I wonder what the actual use case could be.)

A waveform generator is doable as well, and Rave's custom shape.gadget can easily be extended to display basic waveforms.

My current priority is fixing the lockup that affects X1000 machines. When this is done, I'll likely release a quick bugfix update that will also feature the <8 kHz sample rate support.

How much time I can devote to Rave development this year depends on the OS4 work, which currently looks endless Rave has grown quite complex, and development requires a continuous free-time period, rather than the 1-2 hour bedtime stints I can give it at the moment. I'll probably be better off time-wise during the summer, when I'd like to finally rewrite the plugin system to allow realtime operation.

@jap

My own list is longer

Congratulations on funding the book!

This being said, we don't need two separate topic threads on the same thing, so the other one has been removed. Please use this thread to post more information about the project.

@msteed

Let me contact you off-forum and send you a debug build for more information.

@msteed

Quote:
Hmm, sorry about that, but this is strange because I haven't touched this part of the program since the previous version at all.

I test Rave on three different systems: X5000/020, Sam440ep-Flex, and WinUAE running AmigaOS4 FE for Classic. All of these machines are at Update 3, and none of them shows the problem you've described. So I don't know what to say

I released a small update for the Rave audio editor yesterday night, and as usual, my Ko-fi blog drops a little post to go with it. Enjoy!

@Tuvok

Quote:
OS4 is not exactly standing still either at present.

@nbache

Quote:
Now I feel honoured