DigitalCD/RISC OS 5.19 and SoundDMA issue?

Hi

I have installed the latest RISC OS 5.19 (2nd April) ROM on to the SDCard for my BB -XM and I have noticed that DigitalCD now aborts when trying to play a AMPEG file.

I have narrowed the error down to it being seen if you have a ROM build later than 1st March, though I can’t be precise as I only have 1st mMrch and then 26th March to use other than 2nd April.

I get an error from DigitalCD that follows the format below:

“Internal Error , no stack for trap handler :Internal error : Abort on data transfer at &FC27D220 , pc = 2000B688 , registers at 00080AA4”

Where gives “Address FC27D220 is at offset 0000049C in module SoundDMA”

I have also got an address as &FC27D218 as well and that points to the SoundDMA module.

I have tried DigitalCD version 3.05 and also the latest DigitalCD modules as well all with the same issue.

The other strange thing is that the directory window where DigitalCD is located flickers if it is opened up whilst DigitalCD is paused.

In addition if I load !KinoAMP v0.42 and play a MPEG (bf8) video clip first then DigitalCD works OK on RISC OS 5.19 26th March onwards.

I have sent Andre Timmermans the details above but would like to rule out an issue with the SoundDMA module as I noticed that a lot of changes have gone on in the sound area over the past month.

I have the same setup on my Iyonix but do not have the same issues/crash, apart from the strange window flicker, with the latest 5.19 softloads.

It’s certainly possible the crash is my fault – I’ll take a look tonight.

It looks like it was a bug inherited from the (disabled, and rather broken) oversampling code that’s in the Iyonix version of SoundDMA. The wrong buffer size was being checked for, so it was allowing oversampling to be used in situations where the resulting buffer would be too big – hence causing the crash.

A fix is checked in, so everything should be OK once the new ROMs are ready in the morning.

Jeffrey

Thanks for the speedy response and fix.

I’ll wait for the new ROM’s to appear, as the latest seems to be 2nd April still at the moment, and then test things out.

Doug

That’s my fault for breaking the autobuilder. With any luck, it’ll be working again tomorrow.

Steve

The ROM is now built and tested as OK on my Beagleboard but there seems an issue with the auto build of the HardDisc4 (Self Extracting) image in that !Printers seems not to be built correctly.

Doug