Page 3 of 3

Posted: Fri Apr 11, 2008 2:16 pm
by capacitor
Thank you, John!

I was going to offer to edit my posts for the same reason. I'm not sure people really want to see my in-process ramblings anyhow. :wink:

If anything, this thread shows that the Scope community would like access to this kind of stuff.

Open invite to SC: if this is something I can help with - without being a Sonic Core employee - let me know.

Posted: Fri Apr 11, 2008 11:31 pm
by Lima
Will we maybe see this feature in the upcomming V5? ;-)

I hope so! :-D

Posted: Sat Apr 12, 2008 12:36 am
by devo
astroman wrote: SonicCore on the other hand seems to be very open minded in that domain, as you can see by the number of recent software releases.
hmm, maybe I should dig up that ol' mail from the archives and make a new try...
astroman wrote: On the other hand, you shouldn't mess SFP presets with the parameters of a (say) DX7.
You are right...I am really assuming that presets only consists of values corresponding to what can been seen and changed in the device UI - if that is not the case, then it is a different ball game. But I cannot think of a reason for storing any other information in a preset...

I just think that an open preset file format could be very useful for managing and exchanging presets.

Posted: Fri May 16, 2008 8:48 am
by johndunn
Well, OK, it's been a month since I sent two emails to SonicCore about this, one on April 11, and one on April 16. Both of which were ignored. Simply ignored. These were sent to support@soniccore.de - I know this is a working email address because an enquiry about buying something from them was answered promptly. Here is the email I sent:
Hello,

I am the author of "ArtWonk," an algorithmic music program that can be used with Scope. My program has a feature that allows automated patch changing by MIDI control, and it has the ability to list the patch names if a text listing of them can be extracted. For example, you can use my software to change patches by name from Emu synths, smaplers and software.

I wish to support Scope patches, however most are encrypted. The ones that are simply compressed, which mostly are the effects patches, are no problem and I can extract the patch names from them without problem. What I need is a way to access the text information in other patches, specifically the synthesizer patches.

Can you kindly provide me with the information I'll need to extract the text names of Scope synthesizer device presets?

Thanks much,

John Dunn
Algorithmic Arts
http://algoart.com
Now, I realize the people at SC are going crazy trying to get their new products out the door, so I wouldn't expect a lot of time spent in answering me. But to ignore a request like this from someone who is only trying to make the product more useful is - well, it's something the old CreamWare people would do.

I think Scope and the boards and probably (hopefully) the Xcite box have a great future because they are like fine musical instruments. The sound quality is the best, and as long as they are treated well, given lots of ventilation so they don't overheat and fry, these cards will last a very long time. So I would not hesitate to purchase, or to recommend purchasing, the Scope platform in any of its incarnations.

But I don't have similar expectation for SonicCore as a company - at least at this point they are showing all the paranoia and arrogance that buried CreamWare.

A couple years ago, I was prepared to put a great deal of my time into developing for Scope - but the unprofessional manner in which they treated developers - not giving needed information, ignoring email requests for information, and perhaps worse of all, treating developers as an income source instead of as a product enrichment resource. So far, I have not seen any indication that SonicCore is going to do any better - and that, historically, is the mark of doom for a computer peripheral maker that produces a niche product that requires a strong offering of 3rd party applications.

I really hope SonicCore proves me wrong, and starts treating developers and potential developers and even customers who want to extend the platform such as this Patch Names thread was about, starts treating them like the resource they are, and not as at best a bother and at worse a potential threat. I hope but I don't expect.

Still, Scope is the best, and it will continue to be a great system whether SonicCore survives or not.

Posted: Fri May 16, 2008 9:42 am
by irrelevance
Well I'm not sure of what to make of your email johndunn really.
Email is such a poor medium with which to communicate and I'm really not sure that you came across very well.

"The ones that are simply compressed, which mostly are the effects patches, are no problem and I can extract the patch names from them without problem. What I need is a way to access the text information in other patches, specifically the synthesizer patches."

So you were able to get part of the way without Sonic core's help and now you can't get any further so now you decide to contact them?

"Can you kindly provide me with the information I'll need to extract the text names of Scope synthesizer device presets?

Thanks much, "


You sound like you are a customer who is owed the service, not a potential business partner or someone who really has a passion or the system.

Perhaps it was a little rushed on your part or maybe I'm casting an overly critical eye (it's easy to do isn't it!?)

Perhaps there are some companies that would respond as you wished but if Creamware didn't and Sonic Core haven't then maybe whats needed is a change of approach?

I don't mean to be negative. I think your products are great and are proven to work well with Scope. Don't give up! It would be great to have you on board as a third party Scope developer!

Posted: Fri May 16, 2008 10:17 am
by astroman
John's email isn't harsh in any way - all he expects is a ' ... we received your request, but unfortunately cannot be of any help...
of course he would greatly appreciate more details, but all he complains about is just this 'missing' answer ;)
johndunn wrote:... not giving needed information, ignoring email requests for information, and perhaps worse of all, treating developers as an income source instead of as a product enrichment resource. ...
imho you got the 2nd part of the statement perfectly right - that's how it was.
Not sure if it still is - I'd assume they'll be quite helpful if a product promises some kind of business success.
But this applies to the SDK/DP domain only - don't expect even a hint about the system's internals.

like it or not, but you really got to understand that this is not a general purpose coding system - it is an application providing a specific way to control IO and dataflow. No more - no less.
you simply cannot expect conversations like (say) about VST or DirectX

btw I recently had a problem with some M$ GDI stuff in the developement system I use for database and graphics programming - my emails were promptly answered and the problem was solved within hours - with a couple of undocumented functions...
...did I mention the 2k Euro annual subscription for updates and support ? ;) :D

cheers, Tom