From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Dave B ·
A few things:
I spent some time working on a buffer example and was unsuccessful in getting it to work. I haven't determined yet if the memory was not being allocated, or if there was a problem with my algorithm(s), etc., but I was not successful in passing data through the buffer modules.
I'm having some issues getting the GUI components (particularly bitmap knobs) to scale and display properly. I only got SM a few days ago so I'm still in the learning stages. I must say I'm pretty impressed so far and look forward to the toolset growing a bit and some of the kinks to be worked out. I must say though that I feel the documentation, both on-line and the module help, are what I consider to be severely lacking. Although experimenting is a good learning tool, it's also a bit frustrating and unproductive.
Now for my biggest concern:
Tonight I tried porting my work-in-progress to my remote machine but my SX3 on that machine didn't like the DLL and reported it as unloadable. A couple of things came to mind but if you have some insight as to the problem it would be appreciated.
My development machine and my local SX3 machine are both running Windows 2K but my remote machine is running XP Pro. Are you aware of any incompatabilities with XP? Are there DLLs required to run SM that for some unknown reason I may be missing on my XP machine? I'm open to suggestion.
Finally, are you still accepting people into the early adopters forum? I was thinking after paying for the product I would automatically be given permission for that forum.
Overall first impressions are that SM is very interesting and productive. I would rate the documentation and tutorials as severely lacking, including the module help text for most modules.
I'm also a bit confused that some of the included modules seem to include assembled modules that don't show up in the toolbox. Is there any was to determine easily what those are and/or automatically add them to the toolbox?
Ultimately after finishing my first (and I think pretty aggressive) project using SM, the issue will them be whether anyone is willing to pay for the result. If not, I still get to emulate in a VST one of my favorite pieces of legacy gear. I'd be open to suggestions from those who have dealt with distribution issues. I may be way over optimistic but I'd at least like compensation for SM and some of my time.
Thanks!
infuzion ·
Dave B wrote: Finally, are you still accepting people into the early adopters forum? I was thinking after paying for the product I would automatically be given permission for that forum.
Overall first impressions are that SM is very interesting and productive. I would rate the documentation and tutorials as severely lacking, including the module help text for most modules.
I'm also a bit confused that some of the included modules seem to include assembled modules that don't show up in the toolbox. Is there any was to determine easily what those are and/or automatically add them to the toolbox?
1) Not web-automated; they add people by hand... but if you buy & aren't added in a few days, just email [email removed] (or webmaster?), & they'll sort it out.
2) Yea... a common complaint. I don't think modules should have that much help text; just a reminder/clue (I don't want file sizes to increase), but a in-line link to the full doc page would be great.
3) Are you uninstalling then deleting the full SM folder when upgrading? Please post examples of what you're talking about; kinda vague & there's dozzens of modules. cheers
malc ·
Hi Dave,
Welcome to the forum and thanks for your purchase 🙂
As infuzion points out, access to the Early Adopters forum is not automatic. This is due to the fact that it's not always easy to match a new user's forum registration to their payment details. There should be details about what to do in the confirmation email but maybe you skipped past it? It's not a problem anyway, I've added you to the list so you should have access now. Do let us know if you have any problems.
A full user guide has been started but we've been giving priority to bug fixing and other software issues. This will come but in the mean time Please feel free to ask any questions here.
Regarding components that don't show in the toolbox, I think these are most likely R&D components. You can make these show in the toolbox by selecting Advanced from the Options menu. R&D components are highlighted because they may be unstable. They are included for you to try them out. Over time many of these have stabilised and we need to go through and promote many of them to full release status.
If you've got a dll you can send me (and better still the schematic too) I'll have a look at the SX3 problem you're having. The only required dll I can think of is gdiplus but you should have that on XP.
Thanks,
Malc.
Dave B ·
infuzion wrote: 3) Are you uninstalling then deleting the full SM folder when upgrading? Please post examples of what you're talking about; kinda vague & there's dozzens of modules. cheers
Sorry I haven't replied...been busy working on my piece! It's not that big a deal but if I notice it again or have time I will list the ones I find.
Dave B ·
malc wrote: If you've got a dll you can send me (and better still the schematic too) I'll have a look at the SX3 problem you're having. The only required dll I can think of is gdiplus but you should have that on XP.
I think I still have a copy of the DLL. I haven't been archiving much and I'm working pretty quickly on learning and my first attempt at a project.
I'm also seeing a file called trk2tableSM.dat in the folder where I generate the DLL. Is that required or just the DLL?
jorge ·
Dave B wrote: I'm also seeing a file called trk2tableSM.dat in the folder where I generate the DLL. Is that required or just the DLL?
The tri2KtableSM.dat file is not needed. When the dll runs, if the file doesnt exist it gets calculated and saved.
Dave B ·
jorge wrote:
Dave B wrote: I'm also seeing a file called trk2tableSM.dat in the folder where I generate the DLL. Is that required or just the DLL?
The tri2KtableSM.dat file is not needed. When the dll runs, if the file doesnt exist it gets calculated and saved.
This got me to thinking. What happens if the file DOES exist. I copied both files over to my XP machine when I saw the problem with my DLL being marked as unloadable. Is there any chance that something in this file is different between Win2K and WinXP? I know it's a bit of a stretch but if the initial thought is that it should work it's something I thought about.
MyCo ·
I've heard that SM needs a CPU which supports SSE instructions. May be your Win2000 machine also has an older CPU ?!
Dave B ·
Ok, here's an example of what I was talking about with the toolbox:
Within the stereo chorus module I see a primative called SineLFO. It has the same inputs as the Sine module and indeed may be the same but with a different name but this one does not show up in the toolbox.
malc ·
Hi Dave,
The Sine LFO was superceded some time ago. It was exactly the same as the Sine osc except that it only calculated every 4th sample. So it was more efficient for cases where you didn't need the single sample accuracy. You can achieve the same thing with the code component using the hop command.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker