Hi
Having an instance of Artillery (AU or VST) in an Ableton Live project has an unfortunate sideffect: when changing the global tempo, the audio drops out for every bpm increase/decrease! This is definately because of Artillery since this behaviour stops as soon as Artillery is taken out of the equation.
Sincerely Janus
Mac OSX 10.5.8
Ableton Live 8.1.1
Artillery 2.1.0
Artillery bug: Tempo changes in Live with Artillery = audio dropouts
-
- KVRer
- 4 posts since 19 Aug, 2009
I am having the same problem. It gets much worse when having multiple instances.
Completely un-useable in any version of live right now.
I have emailed info a few days ago.
Where can I get the full version of 2.0.6, I can only find the demo version which doesnt allow me to enter my serial number, on Mac.
Completely un-useable in any version of live right now.
I have emailed info a few days ago.
Where can I get the full version of 2.0.6, I can only find the demo version which doesnt allow me to enter my serial number, on Mac.
-
- KVRian
- 1341 posts since 27 Apr, 2007
hi thegrammatron,
i am aware of this problem.
Unfortunatly there is not much we can do about.
Changing tempo is a heavy task since all tempo related calculations have to be done immedatly. With a lot fx this will naturally result in a cpu hit.
Maybe there is some room for optimization in certain fx's.
Do you have the feeling that certain fx will hit the cpu more then other ?
Or a general qustion how many fx are loaded (in all instance) when you run into cpu trouble ?
Maybe it could be an option to delay these calculations for the efects until the fx gets activated, i'll have look.
Robert
i am aware of this problem.
Unfortunatly there is not much we can do about.
Changing tempo is a heavy task since all tempo related calculations have to be done immedatly. With a lot fx this will naturally result in a cpu hit.
Maybe there is some room for optimization in certain fx's.
Do you have the feeling that certain fx will hit the cpu more then other ?
Or a general qustion how many fx are loaded (in all instance) when you run into cpu trouble ?
Maybe it could be an option to delay these calculations for the efects until the fx gets activated, i'll have look.
Robert
-
- KVRer
- 4 posts since 19 Aug, 2009
Robert,
I and I'm sure others will be dissapointed in your reply.
If the problem is a known problem then your users should be notified of this and your support team could have easily replied to me by now.
It is clearly a problem with the new effects you have added to the recent version. The previous version, 2.0.6 is not affected by tempo changes AT ALL. There are no cpu changes.
For me this software is used to manipulate live audio. Therefore, to use it I normally need to set the BPM, either by tapping the tempo or by punching in a number. For me I run into problems when the second instance is addedd. I did two sets of tests, one with my own effect template and one with the default template. Both don't see much difference but my cpu spikes are about 10-15% higher than the base point of 10%.
I had spent days trying to figure out what was causing the spikes because they would eventually cause my system to crash.
I have heard of users in the past running 7 instances on all their audio tracks and not reporting any problems and now we are un able to run more than one instance.
We all are after a stable, crash fee system and although the new features are amazing, I don't have this faith with 2.1 so I'll be reverting back to 2.0.6 until the issue is addressed. Could I please have a copy of the 2.0.6 version, who can I contact for that? I have contacted you - info@sugarbytes - in reply to my order information. I am having issues on Mac with not being able to enter the serial number into the demo version.
Kind Regards,
Dustin
I and I'm sure others will be dissapointed in your reply.
If the problem is a known problem then your users should be notified of this and your support team could have easily replied to me by now.
It is clearly a problem with the new effects you have added to the recent version. The previous version, 2.0.6 is not affected by tempo changes AT ALL. There are no cpu changes.
For me this software is used to manipulate live audio. Therefore, to use it I normally need to set the BPM, either by tapping the tempo or by punching in a number. For me I run into problems when the second instance is addedd. I did two sets of tests, one with my own effect template and one with the default template. Both don't see much difference but my cpu spikes are about 10-15% higher than the base point of 10%.
I had spent days trying to figure out what was causing the spikes because they would eventually cause my system to crash.
I have heard of users in the past running 7 instances on all their audio tracks and not reporting any problems and now we are un able to run more than one instance.
We all are after a stable, crash fee system and although the new features are amazing, I don't have this faith with 2.1 so I'll be reverting back to 2.0.6 until the issue is addressed. Could I please have a copy of the 2.0.6 version, who can I contact for that? I have contacted you - info@sugarbytes - in reply to my order information. I am having issues on Mac with not being able to enter the serial number into the demo version.
Kind Regards,
Dustin
-
- KVRian
- 1341 posts since 27 Apr, 2007
Hi dustin,
well i have better News today.
I investigated the problem and Found some ways to optimize the behavior.
If all goes well i could Provide you with a prerelease Version Tomorrow.
If Not i will send you the 2.0.6.
Sorry for spelling my iPhone is thinking German
Robert
well i have better News today.
I investigated the problem and Found some ways to optimize the behavior.
If all goes well i could Provide you with a prerelease Version Tomorrow.
If Not i will send you the 2.0.6.
Sorry for spelling my iPhone is thinking German
Robert
-
- KVRer
- 4 posts since 19 Aug, 2009
Robert,
I want to thank you for investigating this. Not much of a weekend for you, eh?
Looking forward to the pre-release, I'd be happy to beta test it for you and let you know the results.
Thanks...
I want to thank you for investigating this. Not much of a weekend for you, eh?
Looking forward to the pre-release, I'd be happy to beta test it for you and let you know the results.
Thanks...
-
- KVRian
- 1341 posts since 27 Apr, 2007