@ChrisH

Funny enough I don't have an entry for Wordworth in my Prefs/Screens application. I started Wordworth (first start on Workbench), did the usual custom screen preferences IN Wordworth (1280x1024, 32Bit ARGB), that's it. No false colours. Everything's in place - the only minor thing is that WW uses of course the "old" OS3.x "theme" on his own screen - which is not that nice, but hey, it works!

@tonyw

This is strange, indeed. I shoved around Wordworth and my fonts drawers a dozen times, from OS3.1 up to OS4.1u1, 68k and PPC - after making the "FontInstall" Wordworth always worked correctly afterwards.
Please let us know, when you find the reason for your Wordworth struggle, maybe there's a new aspect we hadn't had so far...

@tonyw, ChrisH

Sweethearts, Wordworth will not (really) work this way!

Go to your Wordworth directory, find the "Wwtools" drawer, open it and look. You might see some icons, called i.e. "InstallFonts". Before you double click this icon you might make a backup copy of the files in Wordworth/Wwfonts/UFST/".

When starting the script "InstallFonts" you should be asked whether you want a new FontList (recommended when you installed/moved stuff to a new machine for example) or not, where your fonts are (i.e. "DATA:OutlineFonts/Truetype"), here you go. In Wordworth/Wwfonts/UFST a new FontList and the whole bunch of new .otag and .font files should be generated.

If you have more than one path to your fonts (i.e. you want to add the "SYS:Fonts/" TrueTypes, you run this script again and tell it NOT to generate a new FontList. The font files from the new path should then be ADDED.

Wordworth uses more or less it's own font engine(s) - so it NEEDS to have it's own installation procedure for your fonts (configure files in UFST), it doesn't know that much about any system font stuff. If you move your installation or fonts, you have to do it all over again - but it's rather straightforward.

I still have my Wacom graphic tablet attached to my A2000/040 - but I'm thinking about moving over to my SAM.

I'm using one of the famous Commodity drivers for serial port on OS3.9 - emulating a mouse. Some software (i.e. TVPaint) uses it's own routines to read the serial port - which works really nice, BTW.

Now I'm wondering if someone already uses the serial port of the SAM for stuff like this - and how's about "drivers"?

@ChrisH

Font handling and Wordworth. Pffff.

- What are your switches in Prefs/Text? Is "Postscript fonts" activated?
- Here I have TWO fonts: AachenMedium.type (=Intellifont) and AachenBLD.afm/.pfm (=PostScript)!
- Despite the fact that I have "Postscript fonts" activated, I soley use AachenMedium (Intellifont), 'cos sometimes the mix of Postscript and Intellifont lead to strange effect.
- Broadblues tip is really recommended - you can "switch off" the AachenBLD by deleting the entry in Fontlist (and still use all other Postscript fonts listeted there...).

@Hans

Ah, this is the reason why I never saw something reported through Rhingio - it's bound to the usbprinter.device! I soley use netprinter.device, so there's no notification...

BTW: Are there other "devices" that might use Rhingio? I.e. the USB stack reports plugged USB sticks with it's own requester window - it could/should use Rhingio as well...

@Chris

Hi Chris, thanks for the 5.5 version - works excellent so far. What should the Rhingio notification do? I have not disabled notifications in the Tooltypes but so far I have never seen Wet to notificate anything?!? Two things that I might mention:
- Wet is startet through DOS script here, using WBRun (don't ask why, I had a little hassle with TuneNet and Wet both started in WBStartup, now this way it works ok).
- "Notifications" reports Wet as "Wetter", so its translated to my locale here.

Ahem - and a feature request: it would be nice if the local temperature, that shows (usually) under the AppIcon, could be displayed in/under the Docky (I don't like appicons but I DO like Docky icons...).

Due to the fact that Rhingio is steerable through ARexx - and ARexx can do nearly everything on AmigaOS, that might be a way...

@bean

While you typed, I edited my last post ... Maybe the infos might help a littlebit.

Yep, PM is send. I hope to have more time tomorrow - thanks for your efforts.

Good night.

@bean

If you mean the Player Task Priority that can be set in the General Prefs Tab then it's set to "20" (GUI prio is "0").

Two other things I might mention:

- Since version 0.92 (OS4.1.1) I had to increase the streaming buffer to 64k to avoid warnings "buffer low" while streaming audio from internet - this didn't happen with the last semi-public 0.86 version (old setting was default 32k).
- Good thing I didn't get crashes here with the new gapless plugins, only the mentioned "stutters/gaps".

EDIT:
------
- Forget about the CPU usage - that seems to be some kind of artifact, I did some tests including clean reboots in the meantime and average CPU usage is at 6% while playing MP3s - perfect!

- I'm playing the same MP3 files from "RAM Disk:" in this very moment and guess what? No gaps, no stutter (so far...).

@bean

The MP3 files are located on a HD (SATA, SFS2, UDMA 6 enabled) - this should not be a problem. But after thinking about this it seems that the gaps and stutters with 1.19 occur (often - not always) shortly after disk access?!? In a first thought I suspected a too small TuneNet internal buffer to be the problem or some change in the disk access code - but I assume that you haven't changed much there from 1.14 to 1.19...

@bean

Yep, I moved all plug-ins except the three you mentioned in the "Disabled Plugins" drawer. No difference - I still have gaps and "stuttering" while playback with the newer MP3Cast plugins. Switching back to the 1.14 cures the problem - playback is smooth with no hearable problems.

The sound from the newer 1.19 plugin is clearer and more "crispier" - which is really nice - but sadly somewhat unusable for me at the moment.

BTW: My CPUDocky shows an avarage of 6% for the 1.14 plugin while playback - the 1.19 shows ~25% CPU usage. Is my machine too weak?

Strange that I have the opposite effect on my sam440ep/OS4.1.1 system:
I still revert to the 1.14 MP3Cast-plugin, 'cos all the newer ones (1.17 - 1.19) give me gaps an hangs while playing 192kbit MP3's from Harddisk! Are there special settings I have to do?

@Chris

...and if someone asks again, I'll answer: In Post 16.

@bean

My post actually describes TWO different (and I suppose not related to each other) crashes:

1. I have installed Chris' BMP.datatype which uses a shared object named nsbmp.sobj. The version which can be found in OS4Depot does NOT work with OS4.1 Update 1 anymore - so if TuneNet tries to load a skin with BMPs (i.e. the SONY skin) TuneNet crashes.

Chris did a newer version of the SObj in the meantime (part of Netsurf 3) which works o.k. with OS4.1 update 1 - so the solution already exists ...

2. Having Chris XMP plugin in the plugins drawer you can start TuneNet, play music, switch skins etc. - it works as expected. If you QUIT TuneNet (I mean really QUIT - not only iconify) and start it AGAIN it crashes.

The plugin worked fine with the 8x.xx version of TuneNet.

@BillE

Oops - it's the opposite here: While I had specific crashes under OS4.1 Beta (for SAM) WW7.1 now works rock stable with the Update 1. My PostscriptPrinterPrefs window in Wordworth opens here, I can do PS outputs to file and print to my postscript laser printer. Strange.

@Chris

Thanks for your reply!

I use (almost) *everything* you did for OS4.x ... - thanks for all your efforts as well!

BTW:

The XMP plugin chrashes here with TuneNet 0.92 (OS4.1 Update 1 Edition) if you start TuneNet a second time (not re-entrable?). I had to switch back to the "old" XMP plugin.

BTW, 2.: Off-topic -> while fiddling with XMP/TuneNet I discovered crashes with the "Sony/Expensive"-Skin which were caused by the BMP.datatype - or to be more precise - the nsbmp sobj. I found a newer nsbmp sobj in the NetSurf 3 package - this seem to work with no problem. Maybe someone should update the nsBMP.datatype in os4depot to the newer sobj ??

@orgin

Wow, man, how can you be so damn productive? Thanks for your efforts!

Maybe I do something wrong, but AISSView doesn't work with AISS 4.7 (OS4.1 Update 1) anymore. Are there settings I can manipulate to get it working again?