![]() |
Hi jPV and AmigaSystem!
Thanks jPV for the info. I'll try to save a config... Still, what should db/lastfm_users.json contain? Maybe it would be better to provide db and the needed "blank" files by default? Also, would you have any idea about the 1000s of GetVar codeset_default? I'll go out on a limb and say that it's called for every char. shown in RNOTunes... :D AmigaSystem, my Amiga has nothing to do with RNOTunes not playing correctly some formats: if AmigaAMP or HippoPlayer can, so could RNOTunes ;) Please note that I'm not blaming RNOTunes (and certainly not complaining to jPV!), I understand that RNOTunes depends on Hollywood libraries, which may not be currently optimised for real 68k computers, but that's their problem, not mine in the context of my comparison. Take care! |
Quote:
Again, it's better not to create a "blank" file there, because the program creates it when a user changes his setup, otherwise it isn't needed and can break the default setup. But if you insist, the minimum needed text is (but you lose the exaple user then): Code:
[] Code:
["JellyPowered"] Quote:
|
Hi jPV :)
Thanks for your answer! One last question: would you have any idea about the OpenFont FONTS:.font and OpenFont FONTS:.otag? Maybe a (Hollywood) function expecting a font but accepting an empty string or even a NULL? Cheers! |
Quote:
|
Hi jPV!
Good point! I'll check this out later on my Amiga :) Take care! |
yeah maybe instead of using a specific font name its instead using the fonts MUI sets as smallest/normal/large/larger etc and if any of them happen to be blank/unset in MUI prefs, then maybe thats why your seeing a blank unspecified font entry in snoopdos.
I had a similar issue with a different program, in the end i just set everything as variations of XHelvetica or the EU version, even if a smaller/larger version isnt available id just reuse a close enough size. |
Hi jPV and DisasterIncarna!
Yes, exactly that :cool Once I set specific fonts/sizes in the Windows and Group pages of the MUI preferences, the "empty" font failure disappeared! I never had noticed these settings before, I learned something ;) Take care! |
Hi jPV,
Thanks very much for this program, looks really good. I just wanted to find out what precision the FPU version of RNOTunes requires. I tried this on the Icedrake V4 but couldn't play any files, they would just disappear from the list when trying to load them in. Thanks a bunch. |
Nice work! :great
|
Quote:
Quote:
|
Based on my experience where I used RNOTunes with my Vampire 1200 V2 (163 MIPS ) I found the following. MP3s play in slow motion with stutter as well. The fpu version of the program seems that doesn't work well and one of the thing it does is not to add any songs to the list. Using the non fpu version songs are added but the quality is very bad. The program seems too heavy even for vampire with 163 MIPS.
|
npagonis, RNOTunes is one of the best Multiplatform programs in the Amiga world, the problem is that on Amiga OS3 you have to use it on WinUAE or FS-UAE.
The Vampire is a machine too fast for old software, and too slow for modern software, the problems you have encountered are only on Real Amiga. On AROS for example RNOTunes works perfectly with all audio formats, see attached video https://youtu.be/SSHBxMKNDAg |
Quote:
The reason why I query the precision requirement is because the FPU in the Apollo V4 range is not 80 bit. I *think* it may be 64 bit, but I am not 100% sure, so please don't quote me. :) It was first thing that came to mind as to why the FPU version may not load MP3's on my A1200 with Icedrake V4. Unless, it's a completely different reason. Using AHI driver with Apollo's ARNE 16bit sound and Amiga OS 3.1.4. |
Quote:
Did you change "Music Unit" (NOT Unit 0) in the AHI driver to "Paula:Hifi 14 bit stereo++ calibrated" and 22050Hz? |
Quote:
There could be many reasons for the pops. Maybe it's not buffering the audio output enough, maybe source filesystem doesn't keep up (is there any difference if playing files from the RAM: disk?), maybe the AVCodec (FFMpeg) plugin is still too heavy for the CPU (FPU could help, but don't know if it'd be enough)... I have tested both 68k versions (FPU and non-FPU) on a WinUAE based setup as well as under MorphOS (with its internal CPU emulation), and didn't see any of these problems under them. I guess I'll have to ask about these things from the Hollywood author, if there'd be something to optimize/fix in the 68k version of the AVCodec plugin. Or if someone with Apollo/Icedrake/Vampire and Hollywood could provide a simple test case and report it on the Hollywood forums, it would be more helpful to get started. |
Quote:
|
Quote:
|
All times are GMT +2. The time now is 05:09. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.