new soundfx installation on OS4.1u3

folks,

i'm having difficulty getting soundfx installed on my SAM. specifically i'm told that a 'string is too long' on line 32 of the installation script. apparently some included tool, gettag, returns a string which is too long? can't see to get around it.

has anyone here been able to install v4.3 onto their amiga NG systems successfully? any hints?

-- eliyahu

Don't use the installer.
Extract the bin and base archives to ram:

move sfx-data/libs to libs:
move sfx-data/classes to sys:classes
add icons of your choice and copy contents of sfx-data and sfx-bin to an empty drawer on your hd...

@Severin
Quote:
What's so bad?

Interesting - I never got SoundFX to work correctly. Please report back, if it works for you...

Don't move anything into libs: and classes: as recomended above, in my SFX installation they are in the programs directory, and it works fine.

PROGDIR:libs is the first place in the library search path, importnat pint if a prgram is installing non standrad libs....

I can't remeber exactly how I installed it now, may have been by hand. But once you get t there it works and is worth registering.

SFX seems to work fine here, except that it won't play sounds even after I select AHI (but maybe a problem at my end). Manual installation should go something like this:

1. Unpack all 2 or 3 archives to RAM: .
2. Create a folder for it (say Programs:SFX).
3. Copy the contents of RAM:sfx-data & RAM:sfx-bin into the same folder you created (Programs:SFX).
4. Copy the icons from RAM:sfx-data/Icons_gi to the folder (Programs:SFX).
5. Rename the iconless SFX file to SoundFX .
6. Optionally copy the documentation from RAM:sfx-doc into the folder (Programs:SFX).


OK, to make it REALLY easy, please download & unpack the following three archives to RAM:
sfx-bin_40m.lzx
sfx-data.lzx
sfx-doc_eng.lzx

And then enter these Shell commands to install it to the RAM:SFX_installed folder:

MakeDir RAM:SFX_installed
Copy EnvArc:Sys/def_drawer.info RAM:SFX_installed.info
Copy RAM:sfx-bin RAM:SFX_installed ALL CLONE QUIET
Copy RAM:sfx-doc RAM:SFX_installed ALL CLONE QUIET
Copy RAM:sfx-data RAM:SFX_installed ALL CLONE QUIET
Copy RAM:sfx-data/Icons_gi/#?.info RAM:SFX_installed ALL CLONE QUIET
Rename RAM:SFX_installed/sfx RAM:SFX_installed/SoundFX

You can than drag'n'drop RAM:SFX_installed to where-ever you want

@ChrisH
I haven't used SoundFX for a long time but I opened my registered copy and was able to play a sound with AHI set in the top toolbar. I didn't do any extensive testing but it appears to work fine. P.S. My SFX version is 4.3.90, which I believe is the version fixed to work with OS4.

@ChrisH

Quote:

Just use IBrowse and you will see...

@cha05e90

It works fine here and has done since I worked with the developer way back in '05 to fix the few os4 problems it had.

The only problem with it now is that the mp3 import module will crash sometimes. I use:

alias ripmp3 mpega -s -A -T [] -o ram:Converted_mp3.AIFF

To quickly convert mp3s to aiff before loading into soundfx. Add it to your s:shell-startup or paste the following line into a shell if you're too lazy to type

echo >>s:shell-startup alias ripmp3 mpega -s -A -T [] -o ram:Converted_mp3.AIFF

@ChrisH

Everything you did except uses the 020 packages not the 040 optionally the floating point as they now work (was some issues in early versions)

Unless I'm mistaken Petunia emulates a 68020 with FPU (68881?) not an 68040

Quote:

Works in AWeb

(long as you don't mind the colour grey)

@ChrisH

WRT to AHI plackback, check what frequency it's mixing at, it uses something odd by default, and not all drivers support all the unusuall frequencies. Envy24HT doesn't support 22Kz for example

Quote:

I often run 040 and 060 stuff with no problems, there seems to be no difference in speed between the different cpu specific compiles of any program I've tried except between vanilla and fpu/040/060.

@broadblues
Petunia is compatible with a 68040, and I always use '040 executables where possible (it's also what Amithlon & WinUAE's JIT emulate).

@ChrisH

What benfit do you get from running O40 code? There is no real O40 so the optimisations for pipelines / caches / instruction timing etc etc that might make fully optimised 040 code faster are null.

The benefit I get is that same executable is usable on all different JITs (not that it really matters to me now), I already had a load of 040 executables, and it makes sense to standardise on one particular CPU (rather than having a random mix).

Ah so it's not so much a technical deceision as a conveninec decision, well that's fair enough.

@thread

thanks for everyone's assistance here. it's running well now, and wow, this is an awesome program. i'm going to keep playing to test stability and if no issues, will register.

it's amazing that these things not only still run programs this old, but that programs this old as are as good as they are.

-- eliyahu

...ok, installed again and...works (up to now) without any problem! Played a littlebit with it and I must admit I'm impressed so far - registration time, I suppose.