From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Slobos ·
Error: Loading wireless - found non wireless in - Type=1, Load
I edited a file a bit and closed it. I was asked if I want to save it. I said no and app crushed. I then reopened file and got that message. Every time I reopen file I get that message. Will be testing for functionality issues but it is not that easy because it grew a bit.
ADDED:
Checked for most obvious wireless connections (those I programmed in and even not all of those) saved file again and seems to be working now.
Slobos ·
I got the same message again after downloading file from forum. Here is screenshot.
Here is link to a post: Property from inner module displayed on parent module And here is TimeStamp of the post where you may download file for debugging: loopeytunes on Mon Sep 20, 2010 10:03 am
trogluddite ·
Similar problem here - see This Post I had already made the post before I saw this thread - so was very interested to see that your description of the circumstances is suspiciously similar, but with a totally unrelated file. I guess from your earlier posts about programming that you probably have better systems experience than me - my guess from my amateur detective work is that there is a memory leak problem with SM - is there any easy way to tell for sure?
Slobos ·
Yes. There are tools made by Sysinternals, particulary VMMap. Tools are available for free and are provided by Microsoft, made by one Russian programmer.
I was able to hunt down and exterminate all memory leaks from my application using this tool. It does require some internal knowledge to use. For beginner it is not straight forward. For someone who knows what memory management is it should be possible depending on if what you already know will help you.
If you need assistance using this tool let me knew.
Google - VMMap
trogluddite ·
Thanks for the info, I'll check that out when I've sorted my latest little SM problem...
Sadly, I spoke too soon about the 'wireless not found' re-saved files being OK 🙁 I've now got to redo about 6 hours work because of a corrupt .osm. It's the weirdest thing; I've been working away, saving new versions every hour or so, with no problems - everything working perfectly fine. Until I decided to see if I could optimise the reverb on it. Of course, as every good programmer would, I worked on the new 'verb in isolation until everything was nicely optimised (its very basic, like yelling into a trashcan!). Trouble is, I can't put it into the main schematic - every time I try to delete the old reverb, CRASH. Tried deleting it a bit at a time - as soon as the last stream connection is removed, CRASH. I can delete and replace it if I disable the soundcard - but as soon as the audio is active again, CRASH. No wireless connections involved, no ambiguous connector types, no glitchy audio, the schematic just likes the old reverb so much it can't bear for me to delete it! Found the last saved version without the bug - I can replace the reverb with the new one just fine there, just a bugger having to replace all the other nice goodies I made (I don't trust to cut and paste them from the buggy one)
So be very careful with those 'crashed on saving' files; they may seem OK for a long time, but.... 😠
Slobos ·
Well, the file I posted on help under same topic as this, curshed when I answered no to "do you want to save file" dialog. I can recall that.
The trouble you have might be a separate bug.
I like the concept and ease of use of this software but programming is awful. Like old pluming that is leaking all over the place and all you have to fix it is duckt tape.
trogluddite ·
Slobos wrote: The trouble you have might be a separate bug.
Quite possible of course, but this is a project that I've been working on for over a year with no problems (other than programmer's brain farts) - then 'wireless not found', crash on save and now crash on delete all in very quick succession. As they say:- once is bad luck, twice is coincidence, three times...
Still, all my own fault for trusting the post-crash saved file, doh!! - should have had the sense to revert to the last known good version (and get out of the house more!). The silver lining is that I've found a few more new optimisations while doing all the repairs.
Slobos wrote: all you have to fix it is duckt tape.
😀 He he, programmer's duct tape, now there's a good idea! - I'll take ten rolls.
trogluddite ·
Aha, I think I may have found my bug - See Here Got the cause and effect reversed I think - assembly bug >> crash >> bad wireless, rather than it being the wireless error causing the bug. Gonna take a lot of duct tape to fix this one (and coffee) - I've now got to go through the whole of my 33000 primitive schematic!
Slobos ·
With 33000 thousand primitives I would have imagined VST would be a CPU eater, but if it isn't SynthMaker has a good future if they pull it together.
trogluddite ·
About 15% CPU on my QuadCore, and a big chunk of that is down to GUI animations (SM is pretty poor at drawing to the screen) - so I'm pretty chuffed with the optimising I've done, though to be fair a lot of those primitives are run-on-demand green/GUI stuff (a standard Animated Knob from the toolbox is 365 primitives, for example) Got all the features for this version in place now, just need to do some heavy duty testing - you can have a peek at the previous version HERE There are some areas of SM that really do kill the CPU cycles (GUI and Arrays spring to mind), but if you're prepared to do a bit of coding, and to chase after every unnecessary green trigger, it's quite amazing how efficient you can make it - best to think of the stock toolbox modules as 'examples' or 'prototypes'; great for a quick experiment, but rarely the best solution for the finished product.
Slobos ·
Thanks, I'll take a look at it.
EDITED: Really, really nice interface! As soon as I am able to I'll play with it a little more.
EDITED: Something just happened and I can't turn the volume down, I've tried everything. The noise that is coming out is not audible but no other softwares sound can be heard. If I turn the main volume of the soundcard down then I can hear for example winamp but VU-Meter is constantly maxed on soundcard Playback Monitor.
trogluddite ·
Thanks for the report - the screenshot pointed out the problem really nicely. The trouble is with the Delay FX - looks like I need to scale the feedback parameters better - with both knobs fully on (as in screenshot), there's obviously far too much feedback - so the audio output is going way over the -1/+1 limit for audio signals, which the output section just clips to a static +1 DC signal. Should be able to get that fixed pretty easily for the next version by limiting the feedback path.
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker