I described that gigastudio 3 crashed when I run the application.
here, to illustrate you what exactly happens.
heeeeeeelp.
please notice, that you unfortunately have to start from the buttom of the page to follow the path.
concerning to paralysed gigastudio showed below
concerning to paralysed gigastudio showed below
- Attachments
-
- this happens when I apply gigastudio 3. what comes next when I press yes you´ll see below.
- giga01wenn_ja.JPG (55.45 KiB) Viewed 1065 times
-
- this mask is not editable. as soon as I quit the window the program automatically disappears.
- giga02wenn_ja.JPG (78.66 KiB) Viewed 1065 times
-
- here you can see what comes if I press no instead of yes at the beginning.
- giga03wenn_nein.JPG (35.3 KiB) Viewed 1065 times
Hi,
I don't have Giga, but some points draw my attention!
1rst screen seems Giga first run using scope in XTC mode, and checking all XTC plugins one after the other.
If it is the case, 1rst launch Giga in SFP mode with the latency you'll use in XTC mode.
Then, go to your XTC plugin directory and remove all delays and reverbs plug (move their directory somewhere else, and launch Giga in XTC mode. Normally it should parse other plugins correctly.
Then add One by One the delays and reverbs plugins followed by a launch of giga. It should be OK then.
Facts are that XTC delay and revebs aren't stables during the First scan at low latency (64 samples?). Mostly because the scope add and remove plugins quickly. After, when in normal use, you won't have these prob lems.
cheers
Michel
I don't have Giga, but some points draw my attention!
1rst screen seems Giga first run using scope in XTC mode, and checking all XTC plugins one after the other.
If it is the case, 1rst launch Giga in SFP mode with the latency you'll use in XTC mode.
Then, go to your XTC plugin directory and remove all delays and reverbs plug (move their directory somewhere else, and launch Giga in XTC mode. Normally it should parse other plugins correctly.
Then add One by One the delays and reverbs plugins followed by a launch of giga. It should be OK then.
Facts are that XTC delay and revebs aren't stables during the First scan at low latency (64 samples?). Mostly because the scope add and remove plugins quickly. After, when in normal use, you won't have these prob lems.
cheers
Michel
nice advice, michel.MD69 wrote:Hi,
I don't have Giga, but some points draw my attention!
1rst screen seems Giga first run using scope in XTC mode, and checking all XTC plugins one after the other.
If it is the case, 1rst launch Giga in SFP mode with the latency you'll use in XTC mode.
Then, go to your XTC plugin directory and remove all delays and reverbs plug (move their directory somewhere else, and launch Giga in XTC mode. Normally it should parse other plugins correctly.
Then add One by One the delays and reverbs plugins followed by a launch of giga. It should be OK then.
Facts are that XTC delay and revebs aren't stables during the First scan at low latency (64 samples?). Mostly because the scope add and remove plugins quickly. After, when in normal use, you won't have these prob lems.
cheers
Michel
the first thing I did was to remove the illustrated xtc-folder from steinberg´s vst-plugin-folder. unfortunately this didn´t work that problem out.
Hi,
Can you at least have SFP and giga working altogether?
Setup the system (latency frequency, ...) in Giga/SFP.
Then, if it is OK, setup the intblksize in cset.ini for XTC mode according to what you have setup in giga previously.
move away the XTC folder from the vst folder and test it.
cheers
Michel
Can you at least have SFP and giga working altogether?
Setup the system (latency frequency, ...) in Giga/SFP.
Then, if it is OK, setup the intblksize in cset.ini for XTC mode according to what you have setup in giga previously.
move away the XTC folder from the vst folder and test it.
cheers
Michel
go to set/settings and uncheck enable xtc mode on the live bar.
if you are not using xtc mode, just trash the xtc folder, otherwise, you will have to deal with giga trying to make the xtc plugins work, finding out that they are impotent in scope mode and then crashing and disabling the plugins one by one, a sad giga reality...
if you are not using xtc mode, just trash the xtc folder, otherwise, you will have to deal with giga trying to make the xtc plugins work, finding out that they are impotent in scope mode and then crashing and disabling the plugins one by one, a sad giga reality...