Arturia Forums
V Collection - Legacy versions => Solina => Solina Technical Issues => Topic started by: legreg6 on December 04, 2014, 05:21:16 pm
-
Most reverbs do not behave correctly. Some have a crackling sound, others turn into some nasty tremolo effect after a few seconds, with crackles too.
Anyone else experiencing this ?
PS: I own V Collection 3 and am actually demoing Solina to see if I want to upgrade. Can this issue be related to the demo version ?
-
Standalone or via a DAW?
I don't have the same issues? Of course, when you change the time or delay whilst playing, it will give you different effects similar to old tape echoes but that's a good thing.
Thanks, Stuart
-
Both Standalone and AU versions. Delay off.
E.g I pick the RSP 550 Shimmer verb, play and hold a chord, the tremolo effect fades in, then become prominent.
BTW, I am on Mac OS X 10.9.5 (MacPro 5.1, 8-core, 16 GB RAM, SSD system drive)
-
Not seeing that myself I'm afraid. Delays and 'Verbs react as i'd expect. They do crackle a bit when you change settings but that's mostly verb and delay time adjusting. I'm also on a 5.1 mac pro but i'm running 10.8.5, 48Gb RAM with SSD Drive
Try trashing your standalone prefs and restarting
/Library/Arturia/Solina V/tmp/standalone.pref
Thanks, Stuart
-
Will try, thanks ;)
Edit: Just tried and It did not solve the reverb issue.
BUT, I also tried that trick for the Wurlitzer, since I had an issue with the standalone app refusing to load (and had to Force Quit), and it fixed it. Thanks for that
-
Hey.. No problem. Glad you got something sorted.
It did notice that the Solina V is a bit memory heavy. In Pro Tools I had to increase my hardware buffer which I rarely do with 48Gb to spare.
So it may be that although you have a fair chuck of RAM, the Solina V wants more.
Thanks, Stuart
-
Hello
I don't know for you, but on my PC, the solina is using 54 MB which is not that much.
How much is it using on your computer?
Best
-
Hi Adrien
I shall check and get back to you
Thanks, Stuart
-
Hi Adrien
On Mac OSX 10.8.5. Solina V is using 15% CPU (2x2.93Ghz Quad Core) with 105Mb with 11 threads.
Thanks, Stuart
-
Adrien, it uses 91.3MB here.
Now Stuart...I totally overlooked the buffer size. I actually set it to 128 samples then thought I would increase it if anything. But I never did ::)
Reading your post got me embarrassed because I had a feeling that was gonna be it.
Indeed... it is :-[
I actually have to raise it up to 512 in order to stop this issue and have Solina play correctly...which is a lot though, isn't it ?
Well I guess this thread should be renamed...oops
-
Yeah, In a DAW you shouldn't have to increase it up that far although it depends how many tracks you are running and what other plugs you have open. In standalone it does depend who much RAM you have and what other apps you have open, 512 is halfway so... Once thing it will do is extend your latency which isn't great.
Thanks, Stuart
-
Solina will go to 100% CPU usage when I use reverb. turn it off and no problem.
lots of issues since upgrading to collection4
analog lab nothing below c3 issue
http://forum.arturia.com/index.php?topic=83579.0
solina bug with reverb massive CPU issue
http://forum.arturia.com/index.php?topic=83554.0
matrix 12 skipping voices issue
http://forum.arturia.com/index.php?topic=83577.0
matrix 12 massive CPU issue
http://forum.arturia.com/index.php?topic=83576.0
vox reverb cpu issue
http://forum.arturia.com/index.php?topic=83578.0
matrix 12 voice sound change issue after first 12 voices
http://forum.arturia.com/index.php?topic=83603.0
-
Yeah...that's my beef about Arturia. As much as I WANT to love their stuff, always a lot...I mean lots of issues. And some of them are simply never addressed (LFO trigger/reset on gate with Arp2600 and ModularV in order to make them predictable pops in my mind).
They do sound awesome...but over time, these issues discourage me from using them, since I often (most of the time) try to find workarounds for issues.
Not trying to be a party pooper here, this is just my experience...sort of a love and hate relationship.
PS: I did notice some erratic CPU activity with Solina that considerably settled when raising buffer to 512 samples. And yes, things are simply better when not using the reverb.
-
And besides, if you put the Solina V in a mix, you'd turn all external processing off and use one of your DAW reverbs. That's not a workaround, that's a real world scenario. :)
Thanks, Stuart
-
Stuart, I've essentially tested Solina standalone so far. Yes, when I use synths in daws, I never use their respective verbs and delay. The issues and workarounds I am talking about are encountered in daws, while producing, and are not related to internal reverbs and delay.
FYI, I had some serious issues with the Spark controller (a couple of them actually) that I never shared on any forum. I just ended up returning it.
Anyway, the twisted fact is that I sill might end up paying the $99 to upgrade...because 1) they do sound good, 2) it's affordable, 3) I'm a gearslutz, and 4) I really WANT to love Arturia stuff ;)
-
:)
Exactly! We work around this stuff because it sounds nice. I've lusted after a Solina for years, i nearly bought one in about 1997 when they were fairly cheap, but some reason I didn't bother. This one sounds great and it fits in my studio just right :)
Thanks, Stuart
-
I got the same issue with Solina when the reverb is active, i get spikes on cpu usage on an 8 core mac pro, no other plugin does that. If i turn the fx off, then it works, it should work with the fx, that is part of the plug and I did pay for it so there is that.
-
I have the reverb crackling issue when using Solina V in Analog Lab, but there's no way to turn the effects off. ::)
-
Open your preset up in Analog Lab and edit, this brings up the Solina. Remove the reverb and 'save as'. Re-open the new project in AL.
Likewise, open it up with the Solina and save as without the reverb. Open that preset up in AL.
By increasing your buffer the cracking should disappear, but it is reliant on you having RAM spare.
Hope that helps
Thanks, Stuart
-
I do not have the full Solina VST and the edit options are limited to just a few settings in Analog Lab. Reverb is not one of them, unless there is a hidden menu. This is the software which came with Minilab.
-
yeah, you need the VI installed as well as Analog Lab. Increase the buffer to full whack, that's the best thing you have at your disposal until a fix is in place.
Thanks, Stuart
-
Thanks for the assistance. ;) Not the most ideal solution, but I should get by until the Analog Lab issues are fixed.
-
Well, quite honestly, I think I am going to wait some time before upgrading after all. It's still $100 and this was NOT ready to be released. Just like so many Arturia products before, we are given a beta version. A lot of things need to be fixed. I would have thought Arturia would change this pattern at some point...
Frustrating.
-
Interesting i cant reproduce it or im not hearing it
HC capturing @30FPS stereo 16 bit 44100
http://youtu.be/Un4hIGWeeNo
Biggest jump was to 09 on the cpu when I opened the gui panel and It averaged about 5 on the cpu
Not saying you haven't got this issue and the video doesn't prove anything but thought I would post my results
You can also have a good laugh at my keyboard skills ;D
-
In all fairness, Solina seems to be much more stale in Live 9. Reverb issue gone. Did not have much time for extensive tests, and did not try in Pro tools 11 yet, but I was pleased to see that this issue was gone in Ableton. CPU usage rather stable too. High, but if you use U-he stuff...not that high after all ;-)
-
Performance in Ableton Live is fine, but it's almost completely unusable in Logic Pro X. The reverb crackle is really bad, and the plugin is extremely unstable, causing Logic to crash almost every time. I'm running it on a Mac Pro with OS X 10.10.
Hopefully we'll get an update from Arturia VERY soon...
-
How much RAM do you have in your Mac mrpingu?
Thanks, Stuart
-
So…I thought I would share my latest Arturia experience…if my post goes through the very selective forum filtering process (started 2 threads in the last 24h…still not published)
As I was digging in Matrix 12, and despite being aware of the many issues, I decided to pull the trigger to bypass the demo limitations. After completing payment I starting looking around, wandering how in hell I could unlock this this. Never received any email with serial number and activation code. Contacted support…who totally sucks. They even disconnected the 1 phone number that I used in the past to directly reach them (I am French) when dealing with new Spark controller with non-fonctioning XY pad.
Finally got a response from Jerome stating I would receive license info in less than 10min…that was 4 hours ago.
I mean…seriously…I've had issues with companies in the past, but to that extent…never.
Arturia, I've tried really hard over the years…but you are a joke.
I am simply about to contact Paypal and cancel the transaction.
-
Everyone is entitled to their own opinion, which is i'm sure based on their own experience. But... legreg6, this has nothing to do with a reverb bug or the Solina V.
If it were posted in the right place it might get to the people who could make a difference (Not all Arturia staff view all threads, as they have specific projects that are working on)
It's also messes up the thread it was posted on, making it more difficult to get solutions for everyone involved.
Anyway, hope you get your issue resolved
Thanks, Stuart
-
Stuart, let me be clear, and please, don't take it personally:
I've been reaching out their so-called customer service, started yesterday a new thread RELATED to that issue, and guess what… it is still waiting for approval, so not posted. I tried again today…same result ! Seriously. This is bad business practice.
I started this thread, and by the way, still waiting for a comment from someone at Arturia. Basically, the standalone version does not work, many have serious issues in different DAWs, different platforms. We are talking about the type of issues that make the stuff UNUSABLE.
You are a happy customer, glad to hear that. I am at this point not only unhappy, but now also outraged by the way they do business. I mean, 2 days later, I CANNOT USE THE STUFF THAT I PAID FOR !
Stuart, I deal with U-he, Slate, Native Instruments, DMG, Fabfilter, Blue Cats, Soundtoys, Eventide, Lexicon, Waves, Plugin-Alliance, Synchroarts, PSP Audioware, etc… NOT ONE of them as ever given me a fraction of the issues I've met with Arturia.
Now, if at least they had some decent customer support, you know, something that would make them likable despite the difficulties, but at least acknowledging them, in a respectful/acceptable delay…but they don't even do that.
Can it be more "messed up" than what it is ? In my opinion, hard to do. And I don't think I should receive any lesson in that respect by any other customer. On THAT issue, I insist.
Cheers
-
legreg6. You actually started this thread.. I didn't realise.
Anyway, I know how volatile these threads can get :) You must be one of the unlucky few. I've had a few issues with all Arturia gear, there's not been a single issue that I haven't been able to work out or get round by myself. Actually, no I lie. My minibrute took ages to get right, but it's fine now (Broken keys thing) and sounds amazing!
As far Solina, lets be fair, it's V1 of a product. Same with Matrix, it's V1. I think we need to be reasonable here :)
They'll be updates of these products and i'm sure V1.2 or even V2 of these things will be perfectly fine. I work with this stuff everyday and I don't think it's as bad as people make out.
Btw. When you buy stuff from Arturia, you now get the licenses deposited directly into your account. There should be no need to reply on an email for your activation codes.
Thanks, Stuart
-
"There should be no need to reply on an email for your activation codes"
Agreed. However, nothing on my account.
-
+2 on this. Purchased and installed by two different people, two different Macs, same result as described.
Reverb gets all clicky after a few seconds. I thought it'd be fixed with the update, and amazingly it was not...
-
I thought it'd be fixed with the update, and amazingly it was not...
What update do you refer to, Solina has never been upgraded, it's V1 fresh off the shelf.
Thanks, Stuart
-
With Solina I'm also experiencing performance issues when playing it in Garageband on my Macbook running with Yosemite. On occassion it starts to crackle and the sound may also drop out. But within Analog Lab CPU usage doesn't indicate any overrun (CPU usage ranges between 10-20%) and adjusting RAM Allocation in preferences to 'No Limit' doesn't bring any improvement in performance.
It's too bad really, because the Solina has some very nice sounds.
Worst off is the preset 'Deep Breathing PW' which runs horribly. The scratchy sounds that emerge after a few seconds remind me of a badly written CDR.
Hopefully, a first correctional update for the Solina won't take too long to appear.
MacBookPro 2.5GHz intel Core i5, memory: 4 GB 1600 MHz DDR3. OS X Yosemite 10.10.1
Garageband 6.0.5 (version 10 doesn't recognize Arturia software).
-
MacBookPro 2.5GHz intel Core i5, memory: 4 GB 1600 MHz DDR3. OS X Yosemite 10.10.1
Unfortunately, the 4Gb base RAM installed on your systems needs upgrading in order to really take advantage of audio units and RAM heavy VI's.
You can get 16Gb in your machine and it's fairly cheap to upgrade. Even 8Gb would see an improvement.
Thanks, Stuart
-
Im not a mac user and havent had the issues people have described in this post
Solina is not ram heavy for me
Also i think garageband is 32 bit so theres a ram limit there so more than 4gb wont really help the situation
Im sure arturia are working hard to identify and solve the issue
I think all departments are snowed under at the time of year to wind down for the vacation
Ive seen another forum user post a reply from support acknowledging that there are issues including the solina and are doing there best to remedy the situation
same here... I pointed them to the links to the issues i raised here on the forum.
"We took notes of your tests. Yet all the problems you are having (Matrix 12, Vox, Solina, Multiple midi devices in standalone versions) are important issues, that are being worked on by the the development team, which will release an update ASAP (by the end of the month).
Until then please accept our sincere apologies for the inconvenience."
@Legreg6 i hope your issue has been solved and you are using your instruments i myself are waiting for a sales inqury issue to be answered and solved and know how frustrating it is to wait
I have noticed slight changes in there support ticket system so they might be updating it
I hope these issues are solved ASAP for you users having issues i just wanted to make the point that this reverb issue is a compatibilty issue and not widespread across the board
-
Im not a mac user and havent had the issues people have described in this post
Solina is not ram heavy for me
Nor me, I just think, like other VI's it needs a decent amount installed.
Thanks, Stuart
-
I thought it'd be fixed with the update, and amazingly it was not...
What update do you refer to, Solina has never been upgraded, it's V1 fresh off the shelf.
Thanks, Stuart
The service center app updated it a few days ago, along with M12/Spark/Vox.
-
Im not a mac user and havent had the issues people have described in this post
Solina is not ram heavy for me
Nor me, I just think, like other VI's it needs a decent amount installed.
Thanks, Stuart
To be clear, the cracklin' reverb issue has nothing to do with ram, unless 32gb isn't enough.
-
I thought it'd be fixed with the update, and amazingly it was not...
What update do you refer to, Solina has never been upgraded, it's V1 fresh off the shelf.
Thanks, Stuart
The service center app updated it a few days ago, along with M12/Spark/Vox.
Are we not talking about Solina?
Thanks, Stuart
-
I thought it'd be fixed with the update, and amazingly it was not...
What update do you refer to, Solina has never been upgraded, it's V1 fresh off the shelf.
Thanks, Stuart
The service center app updated it a few days ago, along with M12/Spark/Vox.
Are we not talking about Solina?
Thanks, Stuart
It = Solina in my previous comment.
-
Im not a mac user and havent had the issues people have described in this post
Solina is not ram heavy for me
Nor me, I just think, like other VI's it needs a decent amount installed.
Thanks, Stuart
To be clear, the cracklin' reverb issue has nothing to do with ram, unless 32gb isn't enough.
It's a buffer issue as was stated in my 3rd post on this thread. Increase your buffer, it goes away.
Thanks, Stuart
-
Im not a mac user and havent had the issues people have described in this post
Solina is not ram heavy for me
Nor me, I just think, like other VI's it needs a decent amount installed.
Thanks, Stuart
To be clear, the cracklin' reverb issue has nothing to do with ram, unless 32gb isn't enough.
It's a buffer issue as was stated in my 3rd post on this thread. Increase your buffer, it goes away.
Thanks, Stuart
That's not a fix, thats a workaround. I'm just throwing in my 2 cents here to continue to draw attention to it for new users (like myself) who are heading to these forums for answers.
I've reported the issue to Arturia and reported it here. Job done :)
-
That's not a fix...
Indeed, never said it was. But it solves the issue until it gets looked at, which like other things is on a priority list.
Thanks, Stuart
-
It = Solina in my previous comment.
Solina hasn't been updated since 19th Nov which was version 1.0.0. 409. That's a month ago.
Thanks, Stuart
-
Buffer size i found personally on my setup i needed 256 samples @ 48000hz
Not because i had crackling or dropouts but i was stacking 3 instances of solina with 4 instances of the matrix and 3 instances of spark and 128 was not sufficent to do the job and i was getting realtime vst peformance overload in cubase
The higher the sample rate the quicker it goes though the buffer
Personally i dont think 256 is a massive buffer size and gives me sub 10 ms latency
48000hz suits my production skills and space requirments
Whats everyone else running ?
-
48k?
Are you working with broadcast or dubbing video?
Thanks, Stuart
-
No im just a hobbist by "suits my production skills" i mean i dont need to go higher for mastering like some do like 192
I have only been back tinkering for 2 years after a long break so still a lot to learn
I noticed from my point of view 48k is more forgiving when being encoded in lossy compression for soundcloud and such
Biggest plus really is it goes faster though the buffer so slightly less latency than 44100
-
Hi,
Are you going from 48k delivering at 44.1?
There's an entire thread that can be devoted to sample rate and src, but it depends on so many different factors. Different audio apps will give you different src which will in turn sound different on different apps. That part is subjective.
But as a 'rule', one should really be going in multiples of the base sample rate. To add even more confusion, high end clocks will deliver a better more transparent sound at 44.1 than lower end gear will at 4 x the sample rate (given that most low end gear might not even go to 96k)
But, if it sounds good then keep doing it :)
Thanks, Stuart
-
Im not a mac user and havent had the issues people have described in this post
Solina is not ram heavy for me
Nor me, I just think, like other VI's it needs a decent amount installed.
Thanks, Stuart
To be clear, the cracklin' reverb issue has nothing to do with ram, unless 32gb isn't enough.
It's a buffer issue as was stated in my 3rd post on this thread. Increase your buffer, it goes away.
Thanks, Stuart
That's not a fix, thats a workaround. I'm just throwing in my 2 cents here to continue to draw attention to it for new users (like myself) who are heading to these forums for answers.
I've reported the issue to Arturia and reported it here. Job done :)
Indeed.
I have uninstalled it entirely until I start to see people posting feedback that the issue is resolved. There is no reason why I should have to push the buffers up to some level that starts to show (hear) noticeable latency. I also try to keep it at 128 or 256 with 512 being my overhead room for when I do have projects that have allot of VSTs and VSTis.
I haven't read every post on this thread so apologies if I missed it but has Arturia even acknowledged this as an issue and have stated that they will fix it?
JB
-
There is no reason why I should have to push the buffers up to some level that starts to show (hear) noticeable latency.
There is, otherwise it won't work correctly.
I haven't read every post on this thread so apologies if I missed it but has Arturia even acknowledged this as an issue and have stated that they will fix it?
Well, not really. There's never admission of any issues, just updates.
Thanks, Stuart
-
Hey.. No problem. Glad you got something sorted.
It did notice that the Solina V is a bit memory heavy. In Pro Tools I had to increase my hardware buffer which I rarely do with 48Gb to spare.
So it may be that although you have a fair chuck of RAM, the Solina V wants more.
Thanks, Stuart
I don't have a dog in this fight as such, just cruising through, but felt I had to write to correct something. Hardware buffer in PT has nothing to do with your memory - those are two separate things. Hardware buffer affects latency which is due to the audio I/O used on a computer system, not ram.
Also buffer changes depend on which version of PT one is running. PT11 only has a setting for record buffer as playback buffer is taken care of automatically inside PT. In PT10 changing buffer size would affect both recording and playback which is why during mixing you'd see people raise their buffers to allow for more cpu intensive stuff like eq/compression/etc.
-
Virtual instruments have never liked Pro Tools, whatever the version.
Maybe some crossed wires here in that sometimes "we" talk about standalone and the AAX (or whatever other flavour of plug) in the same thread, and they work differently.
RAM affects the standalone and i've tested it, and obviously the more you have the better. I found significant differences with the intel macs, one with 8Gb and one with 48Gb - But that goes without saying, right? :) With 8Gb of RAM i found i could not really play it without it cracking or freezing under about 512, although that still has issues. Increasing to 1024 solved that. With the 48Gb machine, I could happily go to 32 and it not affect the sound.
As far as the plug in inside a DAW, there's so many things that affect it. Buffer, playback settings, track count, Core count, other plugs, voices, delay compensation, even having the bloody plug in GUI open.
Again, with the same two machines I had totally different experiences with the exact same set up of Pro Tools running the same session.
Playback / Mixing you can easily take it to 1024 and be happy that you are going to play everything fine, I've never had issues there. Recording and trying to get decent latency is different.
From my tests, the main reason this is so is due to having the GUI open, closing the plug GUI when playing results is a far smoother experience.
Thanks, Stuart
-
Virtual instruments have never liked Pro Tools, whatever the version.
Maybe some crossed wires here in that sometimes "we" talk about standalone and the AAX (or whatever other flavour of plug) in the same thread, and they work differently.
RAM affects the standalone and i've tested it, and obviously the more you have the better. I found significant differences with the intel macs, one with 8Gb and one with 48Gb - But that goes without saying, right? :) With 8Gb of RAM i found i could not really play it without it cracking or freezing under about 512, although that still has issues. Increasing to 1024 solved that. With the 48Gb machine, I could happily go to 32 and it not affect the sound.
As far as the plug in inside a DAW, there's so many things that affect it. Buffer, playback settings, track count, Core count, other plugs, voices, delay compensation, even having the bloody plug in GUI open.
Again, with the same two machines I had totally different experiences with the exact same set up of Pro Tools running the same session.
Playback / Mixing you can easily take it to 1024 and be happy that you are going to play everything fine, I've never had issues there. Recording and trying to get decent latency is different.
From my tests, the main reason this is so is due to having the GUI open, closing the plug GUI when playing results is a far smoother experience.
Thanks, Stuart
I know standalone and plugin versions like aax64 in PT work differently. No problem there. What I was trying to correct was the assertion that buffer setting in PT and ram are related and they aren't. Being you tried this on two different computers I submit that your comparison is invalid UNLESS they both had everything the same save for amount of ram. Same cpu, same audio I/O, same version of operating system, etc. The difference between 8 gig and 48 gig in standalone won't affect performance - it can't. Remember that Yosemite takes all memory that isn't being used for itself, unlike previous versions of OSX.
You shouldn't have to close a plugin gui for any daw work smoothly. To do so indicates poor programming on the part of the plugin developer. Most of the time one wants to have a plugin gui open, especially a synth, if one wants to or needs to make changes while playing - it's that simple.
-
Being you tried this on two different computers I submit that your comparison is invalid UNLESS they both had everything the same save for amount of ram. Same cpu, same audio I/O, same version of operating system, etc.
Of which they were. You can't run comparison tests unless they are.
The difference between 8 gig and 48 gig in standalone won't affect performance - it can't. Remember that Yosemite takes all memory that isn't being used for itself, unlike previous versions of OSX.
I'm using last mountain Lion release, stable for ages don't see the point in upgrading.
You shouldn't have to close a plugin gui for any daw work smoothly. To do so indicates poor programming on the part of the plugin developer. Most of the time one wants to have a plugin gui open, especially a synth, if one wants to or needs to make changes while playing - it's that simple.
Agreed, but my real world testing proves otherwise
Thanks, Stuart
-
And also, Pro Tools 10 isn't qualified with anything higher than Mountain Lion.
Doing some more tests with Solina, I can use it in Pro Tools at 192khz and it stands up fine with certain reverbs but others just die straightaway.
Dropping it down to 44.1khz and the second i lower the samples to even 512, I get break up.
I can record at 192khz normally and it's fine but even at sample rates 4 times lower the reverb breaks the audio up.
The usual caveats apply in that the faster the drives you use, the better results you will get. I'd be interested in what Arturia tested this on, what machine-drive set up they used.
Thanks, Stuart
-
And also, Pro Tools 10 isn't qualified with anything higher than Mountain Lion.
Doing some more tests with Solina, I can use it in Pro Tools at 192khz and it stands up fine with certain reverbs but others just die straightaway.
Dropping it down to 44.1khz and the second i lower the samples to even 512, I get break up.
I can record at 192khz normally and it's fine but even at sample rates 4 times lower the reverb breaks the audio up.
The usual caveats apply in that the faster the drives you use, the better results you will get. I'd be interested in what Arturia tested this on, what machine-drive set up they used.
Thanks, Stuart
True about PT10 not being qualified on anything higher than ML however it does run and run quite well. The only real problem is the uninstaller program doesn't work and would have to be uninstalled manually which is not impossible and Avid even gives steps on how to do that.
As to test setup on what Arturia used that would be nice to know. But like I said it runs just fine here on my setup which is a mid-2011 27 inch iMac with a 3.4 GHz quad core i7 with 32 gig ram and a 2 gig 7200 rpm system drive. My external drives are a LaCie Thunderbolt connected drive with two physical 7200 rpm drives (one for PT to record to and one for samples). I have a Glyph GPT50 2 gig 7200 rpm drive connected via the Apple Thunderbolt to FW800 adapter that is a backup for the same drive in the LaCie. Also have a second Glyph GPT50 2 gig 7200 rpm FW800 drive as a backup for the other LaCie drive half. Sometimes I switch the roles and use the Glyphs as mains and the LaCie as backup. I use an Avid 11 Rack connected via USB2 as my audio interface. When tracking I run at 64 samples and mix at 1024 samples; all sessions are 24 bit 44.1 KHz sample rate.
And it doesn't matter if a vi gui is open or closed - things run just fine. However I close all vi and fx gui's before closing a session because PT sometimes quits to desktop. Doesn't crash it quits.
-
Thunderbolt connected drive
I'm guessing that's what they test on, TB connected drives will give you far better throughput than say USB or FW. My audio drive is 6TB raided via eSATA. It's me 300 odd Mb second throughput. I think the guys running USB and internal drives for their audio also with I/O on the same bus are going to be running into issues because of data rates. I don't record at 192k I just did this as a full on test which it stood up to quite well. Dropping back down to my 88.2k means I can run multiple arturia plugs at the same time.
Also, Spark doesn;t work with anything higher than 96k because of the internal audio samples.
Cheers, Stuart
-
An update will come ASAP to fix this reverb bug.
Please be patient.
-
Thanks, Ben
:)
Stuart
-
An update will come ASAP to fix this reverb bug.
Please be patient.
Thank you and looking forward to the fix.
-
Hi all,
Solina 1.0.2 is online. No more CPU problems with the reverb !!
http://www.arturia.com/products/solina-v/resources
Thank again to all the betatesters on this one ! :P