Page 1 of 2

I'm DISGUSTED with Korg M3 engineers

Posted: Sat Jul 17, 2010 5:07 pm
by 25ghosts
Been A VERY LOOOOOOONG while since reports about the Firewire integration with the M3 was NOT REALLY WORKING RTAS and AU Wise.

STILL NO FIX....


Love the Korg Sounds BUT I have bought MY LAST Korg product UNTILL you guys start FIXING the errors....


I am ashamed of you as a company. PERIOD

Such WILL be my Korg´Reflections on ALL FORUMS AROUND

Posted: Sat Jul 17, 2010 6:02 pm
by BruceL
yeah! i voted for obama, too. :D

Posted: Sat Jul 17, 2010 6:13 pm
by BasariStudios
Obama Rulez!

Re: I'm DISGUSTED with Korg M3 engineers

Posted: Sun Jul 18, 2010 12:49 am
by MartinHines
25ghosts wrote:Been A VERY LOOOOOOONG while since reports about the Firewire integration with the M3 was NOT REALLY WORKING RTAS and AU Wise.

STILL NO FIX....
Have you worked with Korg Tech Support in your country to solve whatever problems you are having?

If you have contacted them, follow up with them to see if they can replicate the problem. Unless Korg Japan (who modifies the software) is aware of the problem and can replicate it themselves, no action will be taken.

Posted: Sun Jul 18, 2010 3:02 am
by mocando
BasariStudios wrote:Obama Rulez!
Sniff... I hope we can get someone like Obama... Or Uribe... :cry: It's been 11 years and still we can't get this pest out. I didn't voted form him, BTW :roll:

Sorry for the venting, Sharp. No politics :oops:

Posted: Sun Jul 18, 2010 3:14 am
by mocando
Regarding the OP's topic.

Are you sure is a known issue reported by several people and not just a few? In my very small experience with electronics and other tech products, if is not a real malfunction that can be replicated easily and on every single iteration, they will not take action and it will not be considered as a bug altogether.

Having said that, they should do consider your issue and look deep into it and help you find out if is a problem with your particular synth, or a bad batch and guide you through until a fix is found or your product replaced. Call or write them and try to get a personal response, not an automated one. :roll:

Posted: Sun Jul 18, 2010 7:19 am
by BasariStudios
Lol Mocando, well what do you want more...now Simon Bolivar is
coming back...the frikin guy even took him out of the ground...lol.

Posted: Sun Jul 18, 2010 3:01 pm
by mocando
BasariStudios wrote:Lol Mocando, well what do you want more...now Simon Bolivar is
coming back...the frikin guy even took him out of the ground...lol.
Tell me about it :roll: This guy is playing god... No, worse, he is playing devil. God protect us. :(

Posted: Thu Jul 22, 2010 11:53 pm
by 25ghosts
mocando wrote:Regarding the OP's topic.

Are you sure is a known issue reported by several people and not just a few? In my very small experience with electronics and other tech products, if is not a real malfunction that can be replicated easily and on every single iteration, they will not take action and it will not be considered as a bug altogether.
OK -- I'll bite


Since ONE year

1) Saving a Song in either Logic Pro or Pro Tools HD, with ONLY the M3 Editor inserted on ONE track,
and choosing 'revert to saved' will CRASH the DAW.... Immediately... and THAT every time...
(This is using the Firewire capabilities of the EXTRA FW card that I bought)

Since ONE YEAR....

2) I have been ON and OFF with Korg in Germany and I even called the US once,
telling them ABOUT this problem and exactly how to re-create it.

They CAN re-create it but their comment was:

'There is nothing we can do about it, sorry. Not at this time'


Now I ask..... Is that nice


PS - Just enter this here search string in the search field 'M3 Expansion'
On a mile-long result page M3 will appear twice. So much for Korg engineering.

I've bought my last Korg product. Got the Trinity, Triton and now the M3.... Sound wise, it hasn't really evolved.
But the now that software is plying a larger part it goes to show that Korg has little knowledge about DAW integration.

To the Korg Engineers who did this, if you're reading or still working for Korg.
The day you lie on your death-bed, are you going to be PROUD of the M3 DAW integration or are you going to wish that you had
paid a little more attention in engineering class.

Posted: Fri Jul 23, 2010 1:28 am
by kanthos
25ghosts wrote:To the Korg Engineers who did this, if you're reading or still working for Korg.
The day you lie on your death-bed, are you going to be PROUD of the M3 DAW integration or are you going to wish that you had
paid a little more attention in engineering class.
The fact that you're calling it 'engineering class' and thinking that anything they could learn in school would have any relevance here just shows that you don't have a clue what you're talking about. I say this as a software developer myself, and as one who's done a bit of work with plugins.

I've seen plugins that are entirely stable in one DAW crash others. Or have I? How do I know that it was the fault of the plugin and not the DAW? What evidence do you have that it's the fault of the plugin and not the DAW? How do you know that the specific hardware on your computer isn't a factor? The drivers for the firewire card (which Korg may not have written, or at least not done solely on their own)?

At any rate, regardless of why you're having problems, I know it's frustrating, but ranting at Korg on unofficial forums won't get you anywhere.

Posted: Fri Jul 23, 2010 11:20 am
by 25ghosts
kanthos wrote:
25ghosts wrote: I've seen plugins that are entirely stable in one DAW crash others. Or have I? How do I know that it was the fault of the plugin and not the DAW?
Pretty EASY.. You test the Plug in SEVERAL DAWs.... Like I have

DP7
LP
PT HD
PT LE
Reaper
Bias Peak


ALL SHOWING THE SAME BEHAVIOR...

Now.... do YOU still think it was the DAW that was at fault ???

Posted: Fri Jul 23, 2010 12:57 pm
by ngr33n
How often do you "Revert to Saved"? Hardly seems like a problem worth ranting over...it's a bug, at most. So you're mad because they failed to release a whole new version of their software (or drivers or whatever) to fix one out-of-the-way issue? I mean, yeah, it's a pain that it crashes, but couldn't you get around it by closing and re-loading the project? It's gotta take what, an extra minute or so, tops?

As for this...
Now.... do YOU still think it was the DAW that was at fault ???
...<a href="http://xkcd.com/169/">no need to get all smug.</a> kanthos didn't know that you'd tested it in different DAWs because you never said that.
At any rate, regardless of why you're having problems, I know it's frustrating, but ranting at Korg on unofficial forums won't get you anywhere.
Especially when you're ranting at Korg on unofficial forums full of people who love Korg.

Posted: Fri Jul 23, 2010 1:05 pm
by kanthos
Ok, probably not. Of course, if you'd actually decided to come and describe your problem and the step you'd tried, I'd have known that, wouldn't I.

And what makes you think that people are going to take you seriously? It's one thing to go to various forums and post a calm report of the specific problem you had and its resolution or lack thereof; that kind of thing would be taken seriously. But you're not going around to various forums to warn people and help them avoid problems; you're doing it to throw public tantrums at Korg.

As I suggested in another thread you posted in, someone considering an M3 should read your posts to be aware of the problem but should also decide whether it will actually affect them. You're not the only Korg user with the firewire expansion, and some of them have clearly had success using it; if NONE of them worked, that would be common knowledge by now on these forums, and it's not. No one, however, should choose not to buy a Korg product simply because only one person says so, especially when that person comes across like a whiny toddler who wasn't allowed to get cookies in the grocery store.


ngr33n wrote:How often do you "Revert to Saved"? Hardly seems like a problem worth ranting over...it's a bug, at most. So you're mad because they failed to release a whole new version of their software (or drivers or whatever) to fix one out-of-the-way issue? I mean, yeah, it's a pain that it crashes, but couldn't you get around it by closing and re-loading the project? It's gotta take what, an extra minute or so, tops?
In the software world, we have a few choice terms to describe idiot customers like that ;) Most people don't have a clue what goes into software development, and think that changes can be made instantly, without realizing that even once the programmer has made the change to fix the problem, there's a huge amount of effort required to get the fixed version out the door. And of course, before someone says, 'software should be perfect', well, are *you* always perfect at *your* job?

It's also possible that Korg had to pull the programmers from the firewire drivers and M3 editor onto another project. That's the situation I'm in at my work right now; I'm the only one working on a massive project, just to keep it going and retain customers, while all the programmers who'd been on my project for 10 years or more are on other projects now that will bring in more customers and increase sales. So let's not assume that the programmers are just lazy; management may be preventing them from doing fixes they might want to do.
ngr33n wrote:...<a href="http://xkcd.com/169/">no need to get all smug.</a> kanthos didn't know that you'd tested it in different DAWs because you never said that.
Gotta love XKCD.
ngr33n wrote:Especially when you're ranting at Korg on unofficial forums full of people who love Korg.
Not everyone here is a rabid Korg fanboy. I'm certainly not, and all the regulars with high post counts are more than aware of the issues various Korg products have. Heck, Daz, one of the two forum founders, recently sold his OASYS and left the forums and the Korg world. Most, if not all, of the core group here would rather see productive discussion, both good and bad, than pointless ranting or over-the-top praise of Korg products.

Posted: Fri Jul 23, 2010 1:17 pm
by ngr33n
Anyway. Just had a thought...have you tried replicating the problem using the USB connection? If it also occurs in that case it'll give us more of an idea where the problem is...

Posted: Fri Aug 06, 2010 6:29 am
by tweakheadz_lab
1) Saving a Song in either Logic Pro or Pro Tools HD, with ONLY the M3 Editor inserted on ONE track,
and choosing 'revert to saved' will CRASH the DAW.... Immediately... and THAT every time...
(This is using the Firewire capabilities of the EXTRA FW card that I bought)
Not a bug that would stop me from using the FW card. How many times does on have to use revert to saved when you know it will crash? You can still close the song and load it again.

But Im interested in this card. Just dropping my .02s on the way.