Hi stuff,
anybody can tell with me please?
Best
anybody can tell with me please?
Best
-
Hi Stefano, try to be patient while the experts look into your problem. They are very busy dealing with users' technical queries, but they have always found a solution for me when I ran into VSL problems.
This sounds to me like the VI is struggling to access all the samples it needs. You say your Raptor HD is internal? What capacity is it? Did you fit it inside your Mac G5 yourself?
You said the problem doesn't happen with just one instance of the VI: I'd suggest you add a second instance, then a third, and so on until the problem occurs, then tell VSL support how many instances it took to create the problem. I'd also suggest you try this test with standard (not custom) patches and see if it makes a difference.
Lastly, it would be good to run these tests using a fresh Logic song, to avoid the possibility that the Logic environment may have become corrupted. Tell VSL the results!
-
Hi Stefano,
I just came back from Musikmesse and am working my way through the pile of mails I received last week, so please apologize this late reply!
Unfortunately, I cannot reproduce the behaviour you describe in the last arrangement you sent us, but I will look deeper into it tonight in order to hopefully find a possible culprit...
Best, Marnix
-
Thanks Marnix,
I wish to write and speak with you to explain exactly what happens in my system.
I never had some problems with other plugins and neither with Opus and EXS.
I can open more than 25 EXS with Opus and othr plugins, but with VI SE with Xfade on happens all this problems.
But I discovered an important thing: I can solve the problem if I turn off the realese samples, in this way, probably, there are less data to compute!!!!!
Before in all VI I had realese on is right or maybe heavy for my system?
Is possible that when I play every instrument with Logic in stop and with all the reaiese samples on, the system goes in overload for poliphony problems and so it can't be able to find in real time all the samples that I call during the performance? (sorry for English!!!!!!)
I think that this is the problem.,
My system work fine, HD is new and fast memory works because I never had problems before, system is upgraded, Logic is upgraded, I formatted and reinstalled all, I installed a new system in a new HD........the same!!!!!
With Opus, EWQLSO, Kontakt 2 all ok!!!!!
With Xfade programs in Opus all ok!!!!
In VI (14 Istances) with Xfade on and all realese sample on, my systen does errors.
Please help me or tell me that i'm asking too mutch from my system.
Mac ppc G5 2'7 Ghz Dual Processor, Ram 4,5 GB, VI on Raptor dedicated 10000 rpm.
Best
Stefano
-
Hi Conquer,
yes Raptor is internal, is 140 GB, yes I putted from myself but I'm non a newbe, is not the first HD that I put in my Mac, before in this HD there was Opus 1 and 2 without any problems.......I created a lot of new songs and all the same problems.....
Thanks Conquer I'm very depressed now, hours every day to solve the problem....
Best
Stefano
-
I tried now,
new song, 14 istances, no programs Custom, only matrix original, when I play instruments with Logic in stop, quicly passages, long notes, long bichords for every istances while move Modwheel (Xfade control) from th sixth or seventh istance notes disappear and when I try to reload that matrix: errors, a lot of sample are missing:"impossible to open "100 SpecialEdition.........." and all the name of the samples..........
-
hold on ... you say raptor and G5 ... it came to my ears that some G5 models don't work flawlessly with them (raptors are using NCQ but the controlle in the G5 does not ... something like that)
do you have a chance to doublecheck the same situation against another harddrive?
christian
and remember: only a CRAY can run an endless loop in just three seconds. -
What can i do now?
I tried to do all you suggested me!
Why if I turn off realese sample all works fine with Xfade on too?
At this point I don't believethat my HD or my Mac has some problems.
All works ok only VI SE with Xfade on don't work properly!
I'm interested to buy other VI Lybraries, but I must before to solve this problems.
Tell me
Thanks
Best
Stefano
-
>I can solve the problem if I turn off the realese samples, in this way, probably, there are less data to compute!!!!!
Yes, if you turn off the release samples it drastically reduces the number of active samples and the strain on CPU. Obviously your system can't cope with the number of samples you're trying to use. How much free space is there left on the 140GB Raptor drive? Is the Vienna Instrument installed on a different drive from the samples?
I still think you should try what I suggested: start a fresh song with only one instance of the VI. Make sure the problem is not happening, then add a second instance. If there is still no problem, add a third instance, and so on until the problem appears. Tell VSL support how many instances it takes to make the problem happen.
-
Hi Conquer,
the space avable is 51 GB, VI is installated in my system Hd, samples are in another.
I tried to do what you suggest me.......
With one istance , no problems, untill five.
From the sixth starts the errors, if I try to reload samples into VI starts all the errors"I can't open..........", but if I push play or record button, I don't know,the system reorganise itselfs.
With other sequencers is the same!!!!!!!!!
In standalone mode no problems, with the same matrix loaded with Xfade and realese on!!!!!!!
I think that VI goes in confusion when I open many istances and when i play each with Logic in stop, touching Xfade control.
The test is this:
Create this:
Piccolo: 2 cells sustain e staccati
Flauto: the same
Oboe: the same
Corno Inglese only sustain
Clarinetto: 2 cells sustain e staccati
Fagotto: 2 cells sustain e staccati
Trombe sole: 4 cells sustain e staccata, a 2 sustain e staccati
Corni 4 cells: a 4 sustain e staccati, a8 sustain e staccati
Tromboni 4 cells: solo sustain e staccato, a3: sustain e staccati
Tuba: 2 cells sustain e staccati
Violini: primi: 7 cells: sustain staccato,tremolo,pizzicati,detache,legati
Violini: secondi: like 1violins (7 cells)
Viole: like 1violins (7 cells)
Violoncelli: like 1violins (7 cells)
Contrabbassi: sustain, staccati,pizzicati
obviosly XFADE and REALESE ON!
Play from the first to the end all instruments for half minute- 45 seconds everyone in this way:
Important Logic in STOP!!!!
always touching Modwheel (control for Xfade) play fast passages (switching to the cells too) and long bichords, always make crescendo and diminuendo with Xfade-Modwheel.
Until the fiifth istance no problem but from the sixth, errors..........
[[[[:(]]]] [[[[:(]]]] [[[[:(]]]] [[[[:(]]]]
Maya, Marnix tells to me that I'm asking too much from my setup.
If not help to solve this problem.....
Please, please
Conquer, thanks for your gentility
Best
Stefano
-
Hi Stefano, I use Vienna Instruments on a 2GB PC and don't have VI SE, so unfortunately can't replicate your instrumental set-up. I'm sure VSL support will try their hardest to think of a solution, because if you run into problems using only 6 instances on a computer with 4GB of RAM it does seem to indicate that something is wrong.
In the meantime, a temporary fix would be to freeze your Logic tracks and/or use your VI's 'learn' and 'optimize' functions so that the instrument only uses the samples which occur in your arrangement - that makes an enormous difference to RAM consumption. If you don't need X-fade on some of the instruments, turn the function off - some cell switches might sound OK without X-Fade. You might also consider temporarily turning the release samples off so you can at least finish programming the arrangement you're working on!
I hope someone finds a solution so you can use 14 live instances with X-Fade and release samples. VSL's instruments do use a huge amount of 24-bit samples (more of a strain on CPU than the 16-bit Pro Edition / Opus versions), so I guess it's possible you may have to adapt your working method slightly.
Good luck!
