You're wrong.Originally Posted by Jcschild
TASCAM is making "changes." They've created (or, at least, are working with) the learngigastudio.com site to "bulk-provide" the tech support that they, it would seem, haven't been able to implement successfully via one-on-one telephone service. If it works, it will be a very efficient way to turn each person's problems into many people's solutions.
There are, in fact, TASCAM people reading the forums there -- I've been PM'd directly by someone from TASCAM in the last two days.
They've built up (only a little bit, I'll admit, but it's a start) the tascamgiga.com pages to provide more info about Giga, as well as its hardware needs and preferred Windows tweaks...
TASCAM deserves some credit for bringing in new people internally to develop/promote/support Giga, and for starting to build up its public support mechanisms. Complaining about how they haven't solved everything at once is neither productive nor realistic.
Change is slow and incremental for any organization... look how hard it is for some folks right here to stop griping reflexively about TASCAM and Giga and start talking about interesting ways that they've used the program, or cool music that they've created using it...
Although I've singled out one snippy comment, above, the problem is really endemic throughout this entire forum, and it is really hurting NSS' otherwise phenomenal signal-to-noise ratio.
"Oh no, GVI requires a dongle," "omigod, GVI shipped out x-weeks after expected," "the world will end -- Giga/GVI may-or-may-not work on some future Windows configuration," "I'd rather complain about TASCAM's lousy tech support than use the same time and effort to ask you people a question about how to get Giga to work," and so on...
I swear, some of you cats must lead charmed lives, if GVI's use of the same dongle that Cubase and others have used for years is enough to inspire such anger and indignation... you'd think there was nothing really wrong in the world today to be upset about...
Please, people, try to keep the GigaGriping to a minimum.
We get it. Giga has its hardware/software issues. TASCAM's tech support has been spotty-at-best, in the past. There are going to be kinks that need to get worked out once GVI 1.0 hits the streets. Fine.
Having acknowledged that these problems exist, why keep dwelling on them?
I frequent forums (fora?) like this to learn how to make better use of my software apps and sample libraries, and to pass along whatever knowledge I acquire along the way.
Anyone who has read my early posts here knows what I nightmare I endured when I first entered GigaWorld. Things got better, thanks in large part to the helpful advice given here by people like Bruce Richardson and Jon Fairhurst. And they were only able to help me (and others) when I (and they) avoided generic grumbling about TASCAM and provided them with specifics about my system and my problems. That is the stuff that makes this place rule... And this site in tandem with learngigastudio.com, will make for a great collective knowledgebase.
And, as a matter of fact, I've had new memory-related problems since updating to v3.20, which will be the subject of a soon-to-be-released fact-rich, whine-free posting... Hopefully the brain trust will help me get through it with relative ease.
All the bitching about TASCAM is just headache-inducing... and it won't solve whatever hardware/driver conflict/configuration/tweaking issue is currently plaguing you.
And don't forget, TASCAM is taking steps to improve both their product and their customer support systems. If your only response is more whining and complaining, what will be TASCAM's incentive to work harder for us?
If you've got specific issues to address, bring 'em on, and we'll try to solve them as a collective unit. If all you want to do is complain about upgrade pricing, insufficient website information, waiting for hours to get a tech support person on the phone, non-optimal copy protection schemes, etc., then WRITE A LETTER TO TASCAM... and then come back and tell us about how you solved some Giga-related issue, or clue us in to something fantastic that you did with your sample libraries...