December 22, 2014, 09:46:32 pm
Welcome, Guest. Please login or register.
Did you miss your activation email
News: Arturia's webmaster is glad to offer you these brand new forums ! Have fun using it and feel free to email any encountered problem at webmaster@arturia.com.

Arturia Forums



Recent Posts

Pages: [1] 2 3 ... 10
1
KeyLab / Recommended DAW for Keylab?
« Last post by hondobro on Today at 07:14:47 pm »
Hello all, is there a particular DAW that most easily integrates with the keylab88?  I would appreciate any recommendations for someone who is replacing an all-in-one workstation keyboard with a controller+laptop and hasnt invested in any DAW yet.

2
BeatStep / Gated and Transposable?
« Last post by Man-Machine on Today at 05:42:45 pm »
Can BeatStep gated and transposable when I have a midi controller connected to it?

In other words, can I have the functionality that a keyboard with built-in sequencer has?

Specifically, being able able to transpose the sequence by pressing different keys and being able to run the sequence only when a key is being held.
3
Analog Lab Technical Issues / Re: Bugs in Analog Lab
« Last post by ben arturia on Today at 05:03:06 pm »
Did you put back Labo2.db file after reinstall ?
Did you have user's preset restored properly ?

I guess your problem is caused by an old dbsrc folder installed in a previous version (not 1.1 but before maybe 1.0.3 or 1.0.5)
In this folder were an old database backup.
I'll investigate.
Sorry for this and thanks for the feedback !
4
Solina Technical Issues / Re: Bug with Reverb
« Last post by stuart on Today at 04:51:39 pm »
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
5
Solina Technical Issues / Re: Bug with Reverb
« Last post by jackn2mpu on Today at 04:44:24 pm »
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.
6
Analog Lab Technical Issues / Re: Bugs in Analog Lab
« Last post by jackn2mpu on Today at 04:34:40 pm »
None of those synth (Matrix Vox Solina) are listed in any preset of Analog Lab ?!

Lets' try something else then :
- Copy the file Labo2.db located in library/Arturia/AnalogLab and paste it in a safe place of your choice. In this file is stored all your user presets. If you don't have any users preset ignore this step.
- Delete AnalogLab folder in library/Arturia/AnalogLab
-Reinstall
- Run AnalogLab and check if you can load any Matrix, Vox or Solina preset.
- Close Analog Lab and replace the Labo2.db file you copied before

I deleted the AL folder and reinstalling AL and that worked fine, seeming to solve the issues I wrote about. What I don't understand is when I downloaded and installed the latest build a couple of times this didn't solve the issue. Also it's weird that this happened to begin with. You may want to put this in a faq or something so that other people that have this issue can get a remedy.

Prior to this there were NO presets for Matrix/Solina/Vox that show when I try and click on the particular synth. As a matter of fact the synth wouldn't even highlight when clicked on like the others. Something else I haven't mentioned and you haven't asked is that in the Filter View where you see just the synth clicked on in that part of the gui where you can select a synth (not a patch in the left hand side of the gui) these three synths are NOT listed.
7
Solina Technical Issues / Re: Bug with Reverb
« Last post by stuart on Today at 04:09:49 pm »
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
 
8
jackn2mpu,

We released an update of all the softs of the V Collection 4 a few days ago, including several bugfixes.
Whether or not you believe in my previous post, it won't change our evolution towards continuous maintenance of our synths.

In the meantime, our users reports really are important to us. It allows us to target our bugfix work more efficiently.
9
Analog Lab Technical Issues / Re: Bugs in Analog Lab
« Last post by ben arturia on Today at 03:23:46 pm »
None of those synth (Matrix Vox Solina) are listed in any preset of Analog Lab ?!

Lets' try something else then :
- Copy the file Labo2.db located in library/Arturia/AnalogLab and paste it in a safe place of your choice. In this file is stored all your user presets. If you don't have any users preset ignore this step.
- Delete AnalogLab folder in library/Arturia/AnalogLab
-Reinstall
- Run AnalogLab and check if you can load any Matrix, Vox or Solina preset.
- Close Analog Lab and replace the Labo2.db file you copied before


10
Analog Lab Technical Issues / Re: Bugs in Analog Lab
« Last post by jackn2mpu on Today at 02:27:02 pm »
You should be able to open any presets of Matrix Vox and Solina even if you don't have license for them you are right.
Could you please try to remove all the .pref files in your :
library/Arturia/AnalogLab

Could you please check that you have a Matrix Vox and Solina folder in :
library/Arturia/AnalogLab/embedded
I trashed the prefs and that didn't help; still the same problems.

Yes I do have folders for the Matrix, Vox and Solina where you say they should be. Something I noticed is that those three folders, as well as the Wurlitzer one have a Resources folder in each folder along with the vst plugin. None of the other instrument folders have that resources folder.
Pages: [1] 2 3 ... 10
Carbonate design by Bloc
SMF 2.0.8 | SMF © 2014, Simple Machines