StudioSound 2.00
|
It’s taken me a while to get to this, but I might have some spare time coming up, so will try to take a look.
The current set of sprites looks like it has a mix of palettes/colour depths. It would be good to standardise these to 256-colour versions. My preference is generally for optimised palette, ‘new’ format 256-colour sprites, since I think the difference in quality is often detectable. However, if you have strong feelings about using the default palette, let me know. There’s also the issue of providing low-res and high-res (Sprites11) versions of the file, but perhaps that’s a discussion for once the main set are done. |
|
Chris – I’ll gladly leave those kind of decisions to you. |
|
Surely anyone using a 32 bit machine would be using upwards from that? (pi default is 16m isn’t it?), if anything (to reduce size) an optimised palette should be used, with maybe an IF switch in the obey to support older hardware? I have always thought that the 22 11 should have been extended so you can provide a filename switch for colour depth as well… Depending on the icon / images being used default palette can look awful, even in simplistic icons. |
|
For a standard size icon (34 × 34) I can’t really imagine many occasions when you’d want to use more than 256 colours. I agree that the fixed palette can look a bit poor sometimes, but adopting an optimised palette is fine – bitmaps exported as icons from ArtWorks frequently use less than 256. There may be Style Guide rules on this (must buy that book!), but for an app’s icons I tend to create a baseline Sprites file in Mode 15, which ensures compatibility with absolutely everything and is very small, and Sprites22 and Sprites11 files that use optimised palettes. These are also pretty small, will work on anything from a RiscPC upwards and give good results. |
|
Notice that StudioSound converts most of the sprites to the current mode, whenever the mode changes. This is for reasons of speed. I am considering dropping that, except for the backgrund sprite, as I am having trouble converting the mask for some of the sprites, f.ex. the round playback speed icon. |
|
StudioSound 2.07 is now available in PackMan. The envelopes can now have up to 255 points- See the !Help file for details. |
|
Henrik: I (possibly foolishly) switched the ongoing discussion of StudioSound’s icon design to the Code Review forum, since it wasn’t strictly an Announcement – have a look in case you’ve missed it. If you don’t generally visit the other forums, though, perhaps best to keep the discussion here? |
|
StudioSound 2.09 (the christmas edition) is now available in PackMan. The most important changes: a few bug fixes, new icons by Chris Wraight, and a new type of tracks: Loop tracks. Loop tracks are intended for drum loops etc. Any track can be converted to a loop track, by selecting the type from the Track > Type menu. |
|
Nota: on Pi3, StudioSound is OK, but ProSound does not load. |
|
I installed StudioSound and the StudioLib package from !PackMan. |
|
Have you take a look to the Wiki ? Here you can find also a link to a scan of my old manual as pdf. As I remember (my Library exists) you have to open the lib with Adjust (right) click to the iconbar icon. Then copy the content of the downnloaded StudioLib folder to the lib window you open with Adjust. |
|
There‘s a serious problem with the 32-bit version If you click on the Fade icon and insert a couple StudioSound may have gone wrong then NULL.POINTER.DEREFERENCE at line 29698. Although it will let you save the resulting WAVE The !RunImage is in BASIC, and line 29698 is in 29674 : REM Shorties if anybody wants to take a look at it. This didn‘t use to happen on the 26-bit version I I‘ve tried getting a RiscPC version working, using I‘d really like to get the Fade effect working, Jon Robinson, Leeds |
|
Hi Jon I can’t find line > 2258 in the !RunImage, but I found DEFPROCcall: DEFPROCCall(code%,A%,B%,C%,D%,E%,F%) |
|
You do not say which version, or what you are running on, but I have just downloaded v1.09 as suggested by JMB above.
I ran it on my Titanium with RO5.31, and I tried to replicate your problem, but failed – but I have never used ProSound. Detailed instructions to reproduce may help. It seems that Code% is where the file Code is loaded, which is 69KB of assembled code. Without the values of all the parameters to the PROCcall that caused the problem, plus preferably the source of the assembled code, diagnosis will be difficult. If you are running the ZeroPain module, that may have logged an error which may have some clues. The *ShowRegs command, the *Where commmand, and then a *Memoryi around the failing code, may also help. The variable values could be found by running Reporter, and adding after the DEF PROCcall line
|
|
As I said above I use !Prosound to listen to and transcribe musical passages, it’s already very good. |
|
Dear Martin Thanks for replying to me. I‘m using an ARMBook with RISC OS 5.29, and the Version 2.09 (19th Dec 2016) To duplicate the error, create a 5 minute, 4 track If you click on the Fade icon (grey triangle), nothing If you now click on the top of that line with the left So far, there‘s been no obvious problem, but as soon If you try to save the project as a WAV file, BEFORE Regards, Jon Time: Thu Oct 24 18:48:36 2024 R0 = 00000002 R1 = 525153f0 R2 = 00000000 R3 = 000033c0 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 R15 = 203cfe08 = Module area +3cfe08 USR stack: Time: Thu Oct 24 18:48:36 2024 R0 = 00000002 R1 = 525153f0 R2 = 000033c0 R3 = 00006780 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:36 2024 R0 = 00000002 R1 = 525153f0 R2 = 00006780 R3 = 00009b40 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 R15 = 203cfe08 = Module area +3cfe08 USR stack: Time: Thu Oct 24 18:48:36 2024 R0 = 00000002 R1 = 525153f0 R2 = 00009b40 R3 = 0000cf00 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:37 2024 R0 = 00000002 R1 = 525153f0 R2 = 0000cf00 R3 = 000102c0 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:37 2024 R0 = 00000002 R1 = 525153f0 R2 = 000102c0 R3 = 00013680 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 R15 = 203cfe08 = Module area +3cfe08 USR stack: Time: Thu Oct 24 18:48:37 2024 R0 = 00000002 R1 = 525153f0 R2 = 00013680 R3 = 00016a40 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:38 2024 R0 = 00000002 R1 = 525153f0 R2 = 00016a40 R3 = 00019e00 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:38 2024 R0 = 00000002 R1 = 525153f0 R2 = 00019e00 R3 = 0001d1c0 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:38 2024 R0 = 00000002 R1 = 525153f0 R2 = 0001d1c0 R3 = 00020580 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 R15 = 203cfe08 = Module area +3cfe08 USR stack: Time: Thu Oct 24 18:48:39 2024 R0 = 00000002 R1 = 525153f0 R2 = 00020580 R3 = 00023940 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:39 2024 R0 = 00000002 R1 = 525153f0 R2 = 00023940 R3 = 00026d00 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:39 2024 R0 = 00000002 R1 = 525153f0 R2 = 00026d00 R3 = 0002a0c0 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 R15 = 203cfe08 = Module area +3cfe08 USR stack: Time: Thu Oct 24 18:48:39 2024 R0 = 00000002 R1 = 525153f0 R2 = 0002a0c0 R3 = 0002d480 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:40 2024 R0 = 00000002 R1 = 525153f0 R2 = 0002d480 R3 = 00030840 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 Time: Thu Oct 24 18:48:41 2024 R0 = 00000002 R1 = 525153f0 R2 = 00030840 R3 = 00033c00 203cfdc0 : 1207700f : ANDNE R7,R7,#&0F ; =15 R15 = 203cfe08 = Module area +3cfe08 USR stack: |
|
Thanks, my scroll wheel has now worn out. |
|
I have this newfangled thing called a Page Down key |
|
@ Jon: Probably not a good idea to post 2,500 lines of ZP logs! I have been unable to reproduce the problem, but I do not know StudioSound and the link to the docs is not available. Can you email me? Google “avisoft martin” and you should find a webmaster address. |
|
Must be newfangled – the OS presents it as Oh, and I just pressed |
|
<cough> Deepkeys <cough> |