Arturia Forums

DRUMS => Spark => Spark Technical Issues => Topic started by: artao on June 26, 2017, 12:23:29 am

Title: Spark 2 Bug Fix Requests Compilation
Post by: artao on June 26, 2017, 12:23:29 am
This is just a thought.
Considering that the devs are looking at bug fixes for Spark 2, perhaps we could come up with a list of everything we've noticed and would like to see fixed, possibly improved. They're all kinda scattered all over the forums here.
No "new features" tho please. Let's keep it chill, eh? :)

EDIT: As suggested by Edouard Arturia, I will try to keep up with collating the responses to this thread here in this first post. If any admins feel up to it, I'm open to help in keeping this up to date. Thanks!
Please check this list before posting.

Don't forget to always mention: Your precise OS version, DAW version and the precise steps to reproduce the issue.
Otherwise your posts won't help....


- Inconsistent results when drag-n-dropping samples onto pads, ESPECIALLY when trying to layer sounds. Very glitchy, and not even remotely a smooth workflow.
- Sampler exceedingly difficult to work with, seems to "lose" sample assignments sometimes.
- Modular view resets zoom and pan and module arrangement every time you leave it.
- Slow loading times in the Library browser (even off an SSD)
- When recording knob movements (using hardware) the result is inconsistent. Knob often resets to a default value.
- Drag-n-drop .wav export of patterns very inconsistent, sometimes crashes Spark. (MIDI works fine, for me)
- Changing effects presets extremely slow ... even simply changing parameters painfully slow.
- Some of the effects are buggy. I'm looking at you, Distortion and vocal filter
- When drag-n-dropping samples directly onto pads in the main interface, WHY does it always insist on putting in two Bode filters. If I wanted Bode filters, I'd put them in myself.
- no adjustable velocity threshold for layering samples. Used to be there, isn't there anymore.
- Loading samples has a pop up windows that says "please select the MOOSE you want to use". Bad translation.
- drag and drop samples is inconsistant on windows 7. Spark 1.6 was good with this but hasn't worked since 2.0 dropped.
- Spark Dub, Spark EDM, Spark 2 with Catanya2 added to the mix crashes any DAW with an Access Violation error.
- The Spark software is using the shared memory addresses in a wrong manner. This is the reason why you have capped the VST amount to 4. Its unstable because of this reason. (EDIT BY OP: Not sure what this means, but I added it to the list)
- MIDI learn seems to work fine when you map notes to the pads, it doesn´t seem to recall correctly all of the mappings when I reaload the project
- Ispark app on IOS has no volume adjustment for metronome. It just blasts your eardrums, like a screaming baby (EDIT BY OP: This isn't really about iSpark, but I added this anyhow)
- Song position pointer not working right in Cubase 6 thru 9 Pro (other DAWs as well?) .. doesn't follow song position properly after stopping and re-starting
- the dialer on the CDM hardware to browse thru samples on disk in the library tab ... after I assign a selected sample to a pad by pressing the dialer, the list always resets (to 1) when I turn the dialer to select a new sample for another pad
- The software MUST be on the Library screen for the Big Knob on the hardware controller (CDM here, can't comment on LE) to browse thru instruments. Should be able to do that from ANY of the screens.

BIG list update, copied directly from the post.

Master Track Limit - There is a built in limiter on the Master track which affects making a proper drum track.  Either the limiter should be removed from the Master Track or an Out1 should be added to the output section when using individual outputs. (Only thing I consider a big issue. Your kick drum is probably being affected.)

Equalizer - If you add the Equalizer to a drum, and bring down the 63Hz fader all the way (-40db), save the project, and return to the project the sound of the drum disappears to silence. There also seems to be a problem with the 32Hz fader when brought down all the way and saved.

Leslie Effect – The Leslie Rotation Speed knob is mislabeled.  When the Leslie Rotation Speed knob is set to "Fast" the speed eventually stops.  When the Leslie Rotation Speed knob is set to "Slow" the speed is actually fast.  When it is set to "Stop," the speed is actually slow.

Distortion – The Tube Distortion type does not work at a 100% Wet setting.

Saving - “Click to choose” an image does not work when saving a preset.

REV button – In the Studio panel, if I press the REV sample button on one instrument pad and then move to another instrument pad, the REV button still remains illuminated. Visually there is no way to tell if a sample is reversed.

Vocal Filter LFO - The LFO Off/On Switch on the Vocal Filter behaves like a slider instead of a button.

Select 12 Shortcut - The Select-12 shortcut turns off both Accent Mode and Song Mode.

Tune Mode – Tune Mode cannot be played with the Sequencer Step buttons on the GUI.  They can only be played with the hardware.

Tempo Knob after switching GUI – When switching from one GUI interface to another the tempo knob gets panned to a hard right at 300bpm (although the tempo itself will not be affected).

Library Panel - In FL Studio, when the Detached option is chosen while the Library Panel is open, then the Library Panel disappears.

LCD & Song Button - When pressing the Song button in the Main Panel to turn on Song mode in either the SparkLE or Spark Creative GUI Interface, the LCD displays "Step Mode 3.0" instead of "Song Mode:  ON."

Drum Pads 15/16 – When Pad 15 & 16 is selected, often the third Instrument Parameter knob's assignment text will not be displayed.  For example, if I load the "Alien Circuit" project and select Pad 15, the third Instrument Parameter knob shows that it is assigned to Freq Shift but not text is displayed beneath it  Pad 16 shows it is assigned to BPF Cutoff, but again the text is not displayed.  When the knob is adjusted a tooltip appears that displays "MUTE OFF."  Also when the knob is in this state, right-clicking it does not bring up the "Enable/Disable motion" & "Edit motion" options.  Most of the projects that seem to have this problem belong to the "Spark Factory," "Spark Vintage,” and some of the demo expansion packs.  It's always the third Instrument Parameter knob for Pads 15 & 16 that is affected.

Effect Presets – I can overwrite the default factory Effect and Mixer Output presets.  I can also delete them.

Mixer Faders – Double clicking the mixer faders bring them back to a value of -33db instead of the expected 0db.

Speark Creative Tap Tempo - If I tap out a tempo on the tempo pad in the the Spark Creative GUI, the tempo will update but the tempo knob itself does not react to the change.

Spark Creative GUI 9-16 - Instruments 9-16 do not display underneath the drum pads in Spark Creative GUI’s Main Panel.  Instruments 1-8 remain on the display when switching to Instruments 9-16.

Verbose Mode – No accessible verbose mode on SparkLE GUI. Verbose Mode on Spark Creative GUI is incorrect. For example. Select 4 says “Prefs” but it actually opens the Studio Panel. Select 5 says “Studio” but it actually opens the Modular panel. If you leave Verbose Mode on in the Spark Creative GUI and return to the SparkLE, the layout of the text is poor, incorrect, and ugly.

Export Icons - In Windows, if you export a Spark kit the resulting icon has an iSpark logo. An exported iSpark kit has no icon.


EDIT:
I'm going to sneak in here a small section of requests as well. I hope that's okay. I readily admit I'm doing this because of three rather standard sequencer features I think are glaringly missing.

- Ability to copy/paste individual instrument patterns between each other
- Ability to shift patterns left or right (individual instruments as well as full pattern)
- Randomize pattern (including velocity)
... those are my three then ;)
others ...
-output each instrument to mono rather than stereo
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on June 27, 2017, 08:44:19 pm
okay, I'll start  ;D ........ (I have the CDM hardware .. running Win 7 64-bit Pro, using both Reaper 4.x thru current and Ableton Live 9 Lite)

Inconsistent results when drag-n-dropping samples onto pads, ESPECIALLY when trying to layer sounds. Very glitchy, and not even remotely a smooth workflow.
Sampler exceedingly difficult to work with, seems to "lose" sample assignments sometimes.
Modular view resets zoom and pan and module arrangement every time you leave it.
Slow loading times in the Library browser (even off an SSD)
When recording knob movements (using hardware) the result is inconsistent. Knob often resets to a default value.
Drag-n-drop .wav export of patterns very inconsistent, sometimes crashes Spark. (MIDI works fine, for me)
Changing effects presets extremely slow ... even simply changing parameters painfully slow.

That's all I can think of off the top of my head. I'm sure I'll remember more next time I'm working with Spark.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: 019297 on June 28, 2017, 03:52:01 am
Some of the effects are buggy. I'm looking at you, Distortion and vocal filter
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: CC4 on July 07, 2017, 03:03:02 am
...Considering that the devs are looking at bug fixes for Spark 2...

Is there confirmation of this somewhere?
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on July 07, 2017, 04:41:50 pm
...Considering that the devs are looking at bug fixes for Spark 2...

Is there confirmation of this somewhere?
After repeatedly bringing it up on their Facebook page -- in particular pointing out that they're still selling the SparkLE with the software, which they know is buggy -- I finally got a response saying that "I had a valid point" and that they were going to have the devs take a look at what they can do.
So I can't give you rock solid confirmation. No.
BUT!!! That's the most direct response I've yet seen from Arturia at all on this. Pretty much the ONLY public comment regarding the future of Spark 2.
So hold out hope.
ALSO! Please remember to submit your bugs and gripes and irritations with the software, otherwise they won't know what we, the users, are experiencing and would like to see fixed or improved.
No new features, mind you. I'm okay with them holding off on that for a new version of Spark. For isntance, a TOTAL rework of the sampler module. Or more extensive sequencer controls (like copying patterns between instruments, pattern shifting left and right, or even random patterns)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on July 14, 2017, 08:20:47 pm
Two more things:
A) When drag-n-dropping samples directly onto pads in the main interface, WHY does it always insist on putting in two Bode filters. If I wanted Bode filters, I'd put them in myself.
B) While working on a track the other day, I created a new kit. For awhile, all the pads were empty, but after setting up my pads for awhile, all of a sudden Spark 2 had filled in all the other pads that I hadn't yet touched. I was VERY thankful that it hadn't screwed with the pads that I'd already set up, because I had carefully layered several samples onto them. Clearly some sort of odd bug there. ... ALSO, for some reason, it had put "default" effects on the two sends as well as the master, and also somehow defaulted several of the pads to have sends set up for pads I hadn't even touched. It took me a good while to figure out why my samples didn't sound right, until it occurred to me to check the mixer. That was very irritating.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: 019297 on July 14, 2017, 10:09:05 pm
no adjustable velocity threshold for layering samples. Used to be there, isn't there anymore. Loading samples has a pop up windows that says "please select the MOOSE you want to use". Bad translation.

drag and drop samples is inconsistant on windows 7. Spark 1.6 was good with this but hasn't worked since 2.0 dropped.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: UNHAPPY WITH ARTURIA on July 20, 2017, 07:23:40 pm
Spark Dub, Spark EDM, Spark 2 with Catanya2 added to the mix crashes any DAW with an Access Violation error.

The Spark software is using the shared memory addresses in a wrong manner. This is the reason why you have capped the VST amount to 4. Its unstable because of this reason.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: SoliDeoGloria on July 23, 2017, 03:16:54 pm
Hello!

I´m new to the forum, but I just wanted to point out that Spark 2 is giving me some problems since I adopted it for my productions. Specifically, the most prominent issue is that while MIDI learn seems to work fine when you map notes to the pads, it doesn´t seem to recall correctly all of the mappings when I reaload the project. While I haven´t made a proper bug test, this has happened on various occassions and I sincerely have to move for now to NI Battery to continue working properly. I hope that there can be a bug revision on this instrument, since it sounds very nice and has a bunch of features that are interesting for my taste...
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: 019297 on July 24, 2017, 11:45:25 pm
Ispark app on IOS has no volume adjustment for metronome. It just blasts your eardrums, like a screaming baby
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: Edouard_Arturia on July 25, 2017, 09:40:07 am
Hey Guys.
It's a good Idea to reference here the bugfixes you have found.
It would be great to raise a list on the first post, so the other pals can see what has already been dig.
Then later we can maybe start a poll to check what's the most important to you guys.
With all the respect, I won't edit your post without permission, so just a suggestion here..
Cheers
Edouard
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: matjones on July 25, 2017, 11:43:09 am
Please can we have the option for mono outs and song position pointer............ the onboard sequencer in Spark is pretty much useless in a studio situation, song position pointer would make Spark MUCH more useful and powerful.

Thanks  8)

PS, how come my post is 'awaiting moderation' yet spammers can post quite freely? This happens to me nearly every time i post on here...
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on July 26, 2017, 02:43:10 am
Hey Guys.
It's a good Idea to reference here the bugfixes you have found.
It would be great to raise a list on the first post, so the other pals can see what has already been dig.
Then later we can maybe start a poll to check what's the most important to you guys.
With all the respect, I won't edit your post without permission, so just a suggestion here..
Cheers
Edouard
That's a great idea Edouard, I hadn't thought of that. If you feel up to editing it, by all means go ahead. I will do my best as well to keep up with it.
Very glad to see that Spark 2 may be getting some love. Cheers! :D
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on July 26, 2017, 02:54:35 am
Please can we have the option for mono outs and song position pointer............ the onboard sequencer in Spark is pretty much useless in a studio situation, song position pointer would make Spark MUCH more useful and powerful.

Thanks  8)

PS, how come my post is 'awaiting moderation' yet spammers can post quite freely? This happens to me nearly every time i post on here...
If you pan to center, you essentially get mono out even tho it send to a stereo pair.
The Sequncer view has a song position pointer. It's a light line traveling through the sequencer. On the main panel, the sequence step lights up (on both the software interface and the hardware) as the step is activated.
:D
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: matjones on July 26, 2017, 02:12:15 pm
Please can we have the option for mono outs and song position pointer............ the onboard sequencer in Spark is pretty much useless in a studio situation, song position pointer would make Spark MUCH more useful and powerful.

Thanks  8)

PS, how come my post is 'awaiting moderation' yet spammers can post quite freely? This happens to me nearly every time i post on here...
If you pan to center, you essentially get mono out even tho it send to a stereo pair.
The Sequncer view has a song position pointer. It's a light line traveling through the sequencer. On the main panel, the sequence step lights up (on both the software interface and the hardware) as the step is activated.
:D

Hi Artao and many thanks for your input.

The reason for asking for mono channels is that some of us use UAD plugins and some other DSP heavy plugins such as waves J37 which use twice the amount of UAD sharcs or twice the amount of native DSP as a mono channel, obviously running a mono sound through a stereo channel is a waste of processing power, ok it's possible to route each stereo channel to a mono bus but that's annoying.... BFD and other drum VSTis have mono outs so why not Spark?

Also, i've just spent 40 minutes trying to get song position pointer working as it should... it does not work!
If i stop a project on bar 40 and then return the project to the first bar Spark will not track this, it will just stay on bar 40 and will continue from there instead of following the project position.... this is useless!!!!!!!!!!!!!!!
Unless of course i am missing something here... i have been through the manual several times on several occasions and can still find no way of doing this....
So unless there is a specific problem with Cubase , versions 6 through to 9Pro, or i'm missing something here as song position pointer does not work!

I hope that clarifies my points for you :D
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on July 27, 2017, 03:59:12 am
Mattjones ... Righto. I understand now.
I would think mono channels would fall under "new features," but your song position pointer is certainly an odd one, so I'll add that to the bugs list. :)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: matjones on July 27, 2017, 11:50:29 am
Again, many thanks for your reply artao.... RE mono outs.... yes that's fine, they would come under new features.

Re Song position pointer..... That would be MUCH appreciated, thank you. If the sequencer worked as it should do it would save me a LOT of time, i look forward to this being addressed in the, hopefully, near future :D
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: 019297 on July 27, 2017, 09:38:14 pm
Thanks to everyone who is putting work in on this, both in and out of arturia.

Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: lordjingjing on July 28, 2017, 01:09:33 pm
I have a bug (I think?), I use the dialer on the CDM hardware to browse thru samples on disk in the library tab, the thing is that after I assign a selected sample to a pad by pressing the dialer, the list always resets when I turn the dialer to select a new sample for another pad. Example, if I have 200 samples in a folder and have selected sample 150, instead of browsing to say sample 151 when I turn the dialer again after assigning, it always begins from sample 1. This is a pain if you have large folders and just want to use the dialer to browse and not the mouse.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: deanfreud on August 14, 2017, 12:32:39 pm
It's completely disappointing that nothing is happening with the Spark software! We talked about this for months now and there is no real reaction from Arturia! We got the DrumBrute and the BSP with both polyrhythmic... something is missing, don't you think?
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: jasonwann on August 20, 2017, 12:05:11 am
Numerous issues in Logic with SparkLE controller maxing out the Midibus memory and locking up.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: syz-x on August 21, 2017, 10:43:28 pm
I would like to add following to the fix list, witch I think is a main SHOW-STOPPER for Spark:

I have the hardware (the big one) and use Logic X.

A. When using Spark + Spark hardware controller + External Midi gear (synths, drum machines etc) Spark often loose sync with both Audio and Midi and behaves really unstable.
B. It's also not uncommon to crash when tweaking the hardware buttons during playback/record.

Read more of it in this very long thread: https://forum.arturia.com/index.php?topic=83908.0

To me Arturia Spark is a paper weight and as soon as I enable Spark in Logic everything gets unstable.

I have reported this to Arturia many many times with really advanced reports, but still no fix.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: electonic on September 08, 2017, 08:03:38 pm
Hello everybody!

Spark LE is my very first "musical" product for the computer I've ever bought. Because drum computers and sequencers really interest me.

Here's a problem with Spark Software which came to my eye immediately, but nobody seems to mention it here:
On a Retina Screen MacBook Pro 13, the interface is so small, it is practically unusable. I have to manually set my resolution down and make the image look unsharp etc., just to use Spark. You can't even make the window bigger. Other Arturia software can be scaled up and gets bigger.

Please fix this! :)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: Edouard_Arturia on September 11, 2017, 09:33:02 am
Hello.
Since the VC5, the V Collection plugins have a resizable GUI.
However, the pre-VC5 virtual instruments doesn't, and Spark2 is a VC4 plugin.
That's why it's UI can't be resized.
Sorry for this inconvenience.
Edouard
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: electonic on September 15, 2017, 09:39:09 am
Hello Eduard,

Thank you so much for replying!

I really do not understand what’s you want to tell me with VC4 and VC5.
I do not not what a vc4 plugin is. I just want to use the Spark App.

All I understand is that I bought this and it’s barely usable on any Mac you can buy right now, because they are all retina. 😉

If you have a solution for other apps, why can’t you update it to this “vc5” version you are talking about?

The solution seems to be right there: make it a vc5 thingy 😊😄
But I guess you are saying you won’t? 🤔

Thank you very much for your time 😊
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: CC4 on September 23, 2017, 06:30:11 pm
I'm a really big fan of Spark and use it quite a bit. As a beta tester, I am aware of some esoteric bugs that are difficult to explain that I won't bother listing. Here are some bugs I'm aware of that remain in 2.3.0:

Master Track Limit - There is a built in limiter on the Master track which affects making a proper drum track.  Either the limiter should be removed from the Master Track or an Out1 should be added to the output section when using individual outputs. (Only thing I consider a big issue. Your kick drum is probably being affected.)

Equalizer - If you add the Equalizer to a drum, and bring down the 63Hz fader all the way (-40db), save the project, and return to the project the sound of the drum disappears to silence. There also seems to be a problem with the 32Hz fader when brought down all the way and saved.

Leslie Effect – The Leslie Rotation Speed knob is mislabeled.  When the Leslie Rotation Speed knob is set to "Fast" the speed eventually stops.  When the Leslie Rotation Speed knob is set to "Slow" the speed is actually fast.  When it is set to "Stop," the speed is actually slow.

Distortion – The Tube Distortion type does not work at a 100% Wet setting.

Saving - “Click to choose” an image does not work when saving a preset.

REV button – In the Studio panel, if I press the REV sample button on one instrument pad and then move to another instrument pad, the REV button still remains illuminated. Visually there is no way to tell if a sample is reversed.

Vocal Filter LFO - The LFO Off/On Switch on the Vocal Filter behaves like a slider instead of a button.

Select 12 Shortcut - The Select-12 shortcut turns off both Accent Mode and Song Mode.

Tune Mode – Tune Mode cannot be played with the Sequencer Step buttons on the GUI.  They can only be played with the hardware.

Tempo Knob after switching GUI – When switching from one GUI interface to another the tempo knob gets panned to a hard right at 300bpm (although the tempo itself will not be affected).

Library Panel - In FL Studio, when the Detached option is chosen while the Library Panel is open, then the Library Panel disappears.

LCD & Song Button - When pressing the Song button in the Main Panel to turn on Song mode in either the SparkLE or Spark Creative GUI Interface, the LCD displays "Step Mode 3.0" instead of "Song Mode:  ON." 

Drum Pads 15/16 – When Pad 15 & 16 is selected, often the third Instrument Parameter knob's assignment text will not be displayed.  For example, if I load the "Alien Circuit" project and select Pad 15, the third Instrument Parameter knob shows that it is assigned to Freq Shift but not text is displayed beneath it  Pad 16 shows it is assigned to BPF Cutoff, but again the text is not displayed.  When the knob is adjusted a tooltip appears that displays "MUTE OFF."  Also when the knob is in this state, right-clicking it does not bring up the "Enable/Disable motion" & "Edit motion" options.  Most of the projects that seem to have this problem belong to the "Spark Factory," "Spark Vintage,” and some of the demo expansion packs.  It's always the third Instrument Parameter knob for Pads 15 & 16 that is affected.

Effect Presets – I can overwrite the default factory Effect and Mixer Output presets.  I can also delete them.

Mixer Faders – Double clicking the mixer faders bring them back to a value of -33db instead of the expected 0db.

Speark Creative Tap Tempo - If I tap out a tempo on the tempo pad in the the Spark Creative GUI, the tempo will update but the tempo knob itself does not react to the change.

Spark Creative GUI 9-16 - Instruments 9-16 do not display underneath the drum pads in Spark Creative GUI’s Main Panel.  Instruments 1-8 remain on the display when switching to Instruments 9-16.

Verbose Mode – No accessible verbose mode on SparkLE GUI. Verbose Mode on Spark Creative GUI is incorrect. For example. Select 4 says “Prefs” but it actually opens the Studio Panel. Select 5 says “Studio” but it actually opens the Modular panel. If you leave Verbose Mode on in the Spark Creative GUI and return to the SparkLE, the layout of the text is poor, incorrect, and ugly.

Export Icons - In Windows, if you export a Spark kit the resulting icon has an iSpark logo. An exported iSpark kit has no icon.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: Outof4mmo on October 04, 2017, 02:43:01 am
Couples of things that turn me off. I love my SparkLe+Spark2. But i have a some deal breaker issues
-I get a registration window everyday now since a couple of weeks. Even if my software is registered with ASC. Done the reinstall, re-registration, re-reinstall and re-re-registration without any success
-Custom drum kit do not save properly. I have to rebuild my drum kit every now and then. Goodbye workflow.
-Sequence do not save properly. I have to re-create my sequence all the time now. Re-goodbye workflow
(Look like Spark think i'm running in demo mode or something...)

All in all i love this little thing, once you know hot to use it it's powerful and versatile tool. I hope they are not giving up on it.
Now i'm saving money for a Tempest. Unless they come up with something within a year. I'm crossing my finger.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on October 15, 2017, 12:45:54 am
Hello Eduard,

Thank you so much for replying!

I really do not understand what’s you want to tell me with VC4 and VC5.
I do not not what a vc4 plugin is. I just want to use the Spark App.

All I understand is that I bought this and it’s barely usable on any Mac you can buy right now, because they are all retina. 😉

If you have a solution for other apps, why can’t you update it to this “vc5” version you are talking about?

The solution seems to be right there: make it a vc5 thingy 😊😄
But I guess you are saying you won’t? 🤔

Thank you very much for your time 😊

Spark is not part of the VC5 collection, only VC4 and before.
Displays like that commonly result in issues with the size of VST instruments. Perhaps lower your resolution is all I can say regarding that. Given a specific monitor size (say, 22"), as you increase resolution, ALL VST interfaces become smaller on screen. All software and fonts and stuff become smaller too. To get it bigger, you need either a bigger monitor or reduced resolution. That's just the way it is with the vast majority of software.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: deanfreud on November 03, 2017, 09:00:00 pm
November 2017 and nothing has changed...
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: aytekin on November 10, 2017, 09:41:38 pm
In ispark, Project browser isn’t loading and crashing the app. It happened after creating many kits. When I delete some of the new kits, it works, but when I have many kits (funny I know but as if there was a limit on the sample/kit number) I lose the project browser again. Does anybody know how to fix this? There’s no point in creating new kits if I won’t be able to browse, find and load them.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: boombaxx on December 06, 2017, 08:33:25 am
Years they have been promising an update to fix the vst. Still nothing
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: deanfreud on December 06, 2017, 10:37:23 am
Yes it's a shame!

Years they have been promising an update to fix the vst. Still nothing
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on December 06, 2017, 09:24:55 pm
In ispark, Project browser isn’t loading and crashing the app. It happened after creating many kits. When I delete some of the new kits, it works, but when I have many kits (funny I know but as if there was a limit on the sample/kit number) I lose the project browser again. Does anybody know how to fix this? There’s no point in creating new kits if I won’t be able to browse, find and load them.
Sorry aytekin, but this is about the full-fledged PC software, not iSpark. There is a separate forum for that tho.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on December 06, 2017, 09:26:06 pm
Couples of things that turn me off. I love my SparkLe+Spark2. But i have a some deal breaker issues
-I get a registration window everyday now since a couple of weeks. Even if my software is registered with ASC. Done the reinstall, re-registration, re-reinstall and re-re-registration without any success
-Custom drum kit do not save properly. I have to rebuild my drum kit every now and then. Goodbye workflow.
-Sequence do not save properly. I have to re-create my sequence all the time now. Re-goodbye workflow
(Look like Spark think i'm running in demo mode or something...)

All in all i love this little thing, once you know hot to use it it's powerful and versatile tool. I hope they are not giving up on it.
Now i'm saving money for a Tempest. Unless they come up with something within a year. I'm crossing my finger.
I hope you were able to resolve this. To me, it sounds like an issue with the activation process. Something got screwed up there.
If not, let me know (with a bit more detail) and I'll add it to the "Please Fix" list.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on December 06, 2017, 09:33:17 pm
Yes it's a shame!

Years they have been promising an update to fix the vst. Still nothing

Have patience and faith. Stay positive! :)
I too was VERY disappointed when Spark 2 was seemingly abandoned, with no word, when V Collection 5 came out.
However, we (and me personally) have had positive response this year from high honchos at Arturia saying that they're looking at fixing Spark 2 at the very least, if not upgrading it.
Thus the existence of this thread.

And NOW look what they just came out with. They're a small company. This new V Collection 6 was a lot of work for them. Perhaps now their software people will have more time to dig into Spark 2.
I've been concerned that with all this hardware they're coming out with, that they were reducing their interest in making sofware. I think the release of VC 6 shows that they still maintain a strong commitment to their software products.
.......... they're just not very good at communicating with US is all. ;) ;)

Perhaps it's time to start constantly posting on their facebook page about it again. That's what first got me a response regarding this subject.
Y'all can join me too! The more the merrier, and the more people the more they see actual interest in updating Spark 2.
If they don't see many people interested in them doing it, then why would they expend resources on it?
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: Edouard_Arturia on January 12, 2018, 03:06:42 pm
Hey Guys.

Don't worry, we have not forgot this update at all.
It is being worked on !

Yes it's a shame!

Years they have been promising an update to fix the vst. Still nothing

Have patience and faith. Stay positive! :)
I too was VERY disappointed when Spark 2 was seemingly abandoned, with no word, when V Collection 5 came out.
However, we (and me personally) have had positive response this year from high honchos at Arturia saying that they're looking at fixing Spark 2 at the very least, if not upgrading it.
Thus the existence of this thread.

And NOW look what they just came out with. They're a small company. This new V Collection 6 was a lot of work for them. Perhaps now their software people will have more time to dig into Spark 2.
I've been concerned that with all this hardware they're coming out with, that they were reducing their interest in making sofware. I think the release of VC 6 shows that they still maintain a strong commitment to their software products.
.......... they're just not very good at communicating with US is all. ;) ;)

Artao, your answer is relevant.
V Collection 6 was really a lot of work for the development team.
We now have a team dedicated to Spark 2 update.
But like you said, we are not a Google sized company, but a small company in the french alps.

Yes it's a shame!

Years they have been promising an update to fix the vst. Still nothing
Perhaps it's time to start constantly posting on their facebook page about it again. That's what first got me a response regarding this subject.
Y'all can join me too! The more the merrier, and the more people the more they see actual interest in updating Spark 2.
If they don't see many people interested in them doing it, then why would they expend resources on it?

The ressources have been allocated to this project. So I'm afraid it won't change anything.
Now the only thing that may help is time, and precise reports of the issues your are facing, so we can dig the bugs with your help.

Kind regards everyone and thanks in advance for you understanding.

Edouard
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on January 12, 2018, 06:28:47 pm
Hey Guys.

Don't worry, we have not forgot this update at all.
It is being worked on !
 ..........
Kind regards everyone and thanks in advance for you understanding.

Edouard

That's AWESOME Edouard. Great news!! WOOT!! Thank you. :D
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on January 19, 2018, 01:26:00 pm
Hey Guys.

Don't worry, we have not forgot this update at all.
It is being worked on !
 ..........
Kind regards everyone and thanks in advance for you understanding.

Edouard

That's AWESOME Edouard. Great news!! WOOT!! Thank you. :D

EDIT: Would you be able to tell us if you're looking at bug-fixing/updating Spark 2, or if you're going for a full-blown Spark 3? (or both)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: what5150 on January 19, 2018, 11:02:43 pm
I would like to add that externally sequenced pattern changes don't trigger the the first beat if the step wasn't in previous pattern.
Example, patterns set to change instantly and always changing patterns at step1.
Pattern1 is just hi-hats, pattern2 is hi-hats and kick, pattern3 is hats, kick, and snare ( instruments are variable just an example)
Going from pattern1-> pattern2 or 3, the first kick (step1) will be silent.
Going from pattern2-> pattern3, works normal.
Going from pattern3-> pattern2, works normal.
Going from pattern2-> pattern1, works normal.

If I change patterns in enough time before step one it works ok. But with Ableton clips triggering pattern changes, I can't "pre-send" the change. When I play spark live I can select the pattern sooner so it doesn't matter. It's annoying when I have so many changes on tracks that I have to use an Ableton scene to make it all happen and you miss the kick on 1. Heart sinks and failure sets in.

Arturia said this is normal behavior and that it just doesn't have time to load the pattern, but I can watch the sequencer GUI and see the step light up so the pattern is loaded. Idk just annoying and we're are talking about what, two bytes of data probably in RAM if not processor cache.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: lordjingjing on February 05, 2018, 01:40:10 pm
Hey Guys.

Don't worry, we have not forgot this update at all.
It is being worked on !

Yes it's a shame!

Years they have been promising an update to fix the vst. Still nothing

Have patience and faith. Stay positive! :)
I too was VERY disappointed when Spark 2 was seemingly abandoned, with no word, when V Collection 5 came out.
However, we (and me personally) have had positive response this year from high honchos at Arturia saying that they're looking at fixing Spark 2 at the very least, if not upgrading it.
Thus the existence of this thread.

And NOW look what they just came out with. They're a small company. This new V Collection 6 was a lot of work for them. Perhaps now their software people will have more time to dig into Spark 2.
I've been concerned that with all this hardware they're coming out with, that they were reducing their interest in making sofware. I think the release of VC 6 shows that they still maintain a strong commitment to their software products.
.......... they're just not very good at communicating with US is all. ;) ;)

Artao, your answer is relevant.
V Collection 6 was really a lot of work for the development team.
We now have a team dedicated to Spark 2 update.
But like you said, we are not a Google sized company, but a small company in the french alps.

Yes it's a shame!

Years they have been promising an update to fix the vst. Still nothing
Perhaps it's time to start constantly posting on their facebook page about it again. That's what first got me a response regarding this subject.
Y'all can join me too! The more the merrier, and the more people the more they see actual interest in updating Spark 2.
If they don't see many people interested in them doing it, then why would they expend resources on it?

The ressources have been allocated to this project. So I'm afraid it won't change anything.
Now the only thing that may help is time, and precise reports of the issues your are facing, so we can dig the bugs with your help.

Kind regards everyone and thanks in advance for you understanding.

Edouard

That's fantastic news! :D I use the original CMD controller with Spark 2 inside Studio one, a very annoying bug is that when I turn a knob on the controller which I have set to say pitch, it often change another value like volume or pan. I have to stop and turn the knob again for it to change pitch as it was supposed to do from the start. :-\ That bug is so frequent that I for a long time have thought about switching to another software and controller, but I will wait for the update now and hope for the best! :) 
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: syz-x on February 09, 2018, 03:20:21 pm
Hey Guys.

Don't worry, we have not forgot this update at all.
It is being worked on !

Artao, your answer is relevant.
V Collection 6 was really a lot of work for the development team.
We now have a team dedicated to Spark 2 update.
But like you said, we are not a Google sized company, but a small company in the french alps.


Hi, I'm really happy that you finally decided to put some effort into Spark 2, some years down the line.

However I do believe most of us can accept that you are not 'Google sized', but that said, we as customers could not care less for excuses like that. We are not interested in how many new shiny products you produce when the ones we already bought dosen't work. That's a little bit like telling us you 'don't bother us with old products that you already paid us for, buy some new instead'.

I would really like to urge your management to change that view set. That for one reason is why I haven't bought a single product from Arturia since that, because I feel let down by you. Also be more open and honest with your replies on forums and other media. You told us for years that "updates are coming" etc when in fact you didn't put any efforts in it until now (if we even can believe that). That leaves a really sour taste in my mouth.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: deanfreud on February 11, 2018, 11:18:43 pm
Hey Guys.

Don't worry, we have not forgot this update at all.
It is being worked on !

Artao, your answer is relevant.
V Collection 6 was really a lot of work for the development team.
We now have a team dedicated to Spark 2 update.
But like you said, we are not a Google sized company, but a small company in the french alps.


Hi, I'm really happy that you finally decided to put some effort into Spark 2, some years down the line.

However I do believe most of us can accept that you are not 'Google sized', but that said, we as customers could not care less for excuses like that. We are not interested in how many new shiny products you produce when the ones we already bought dosen't work. That's a little bit like telling us you 'don't bother us with old products that you already paid us for, buy some new instead'.

I would really like to urge your management to change that view set. That for one reason is why I haven't bought a single product from Arturia since that, because I feel let down by you. Also be more open and honest with your replies on forums and other media. You told us for years that "updates are coming" etc when in fact you didn't put any efforts in it until now (if we even can believe that). That leaves a really sour taste in my mouth.


Arturia has many new Products but no Spark Update and no real plan for an real Update in the near future. Sorry, it’s ok that Arturia is a „small“ company but it’s not ok to let the costumers totally in the dark. How long do we talk about it, 2.3.0 was in May 2016 and this only added iSpark and solved  some export issues.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: deanfreud on March 06, 2018, 04:48:18 pm
BUG One thing that makes the Spark VST not good for Live performing is when you change the Kit it changes the Mixer Outputs!
 
When I want to perform with Spark + Spark LE + Roland MX-1 and Ableton it is not possible to change the Kit or the Project without losing the Mixer Outputs in Spark. And we need more dedicated outputs for Sends and Master.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: PSN_ONE on March 15, 2018, 05:59:26 pm
Short time user, first time poster...

So I'm running a Dell Inspiron 15 3000 Series and I can't get SparkLE to link with Ableton Live 9 Lite...

Tried a few things and so far nothing. I dig the Arturia line of products but finding decent tutorials or help for technical issues is straight frustrating..

So any ideas on how to get SparkLE and Ableton LIve 9 Lite to get it on?
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: deanfreud on April 16, 2018, 07:09:55 pm
hmmm? The BSP get's an Update but the Spark Update is still an empty promise! 
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: syz-x on April 27, 2018, 06:21:40 pm
I do not believe Arturia will ever fix/update spark. I dear to say that I honestly don't think they have put a single hour of work on it, cause it's an "end of life" product for them.

We who purchased the product (software/hardware) are kind of screwed. And this is one of the most misbehaved customer cases I ever seen, and a classic school book example of "how not to treat customers" in any marketing text book.

The only decent thing Arturia should do right now is to offer some kind of refund deal to customers who want to return their non-working spark software and/or hardware.

I really hope management@arturia come to their senses with this, that would be the only thing that could make me become a returning customer.


Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on April 27, 2018, 09:59:17 pm
I do not believe Arturia will ever fix/update spark. I dear to say that I honestly don't think they have put a single hour of work on it, cause it's an "end of life" product for them.

We who purchased the product (software/hardware) are kind of screwed. And this is one of the most misbehaved customer cases I ever seen, and a classic school book example of "how not to treat customers" in any marketing text book.

The only decent thing Arturia should do right now is to offer some kind of refund deal to customers who want to return their non-working spark software and/or hardware.

I really hope management@arturia come to their senses with this, that would be the only thing that could make me become a returning customer.

Take heed, the light waxes upon the horizon!!  ;D
I am allowed to say that I am beta testing for the Spark update (currently called 2.4) and I am downloading right now the first test build available to me.
So have hope! Action has been taken and results are being ...... resulted ...

l8r
artao
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: machinesworking on April 28, 2018, 10:15:12 pm
 8) 8) 8) 8) 8)

This is great news! I've given up on Maschine as a drum solution in general, all that's left to do is to print to audio all tracks in current songs and sell the hardware.
Maschine for the last 9 years has on and off been a total PITA with any time signature changes in a DAW. Dragging in MIDI to your DAW involves 16 MIDI tracks minimum for drums....
   Spark on the other hand is a fairly easy DAW integration, with only the odd counterintuitive hiccup related to not selecting it as a MIDI source , beyond that it's easy as pie. I've been terrified to use it for fear it gets major bugs and never updated. IMO Arturia dropped the ball with Spark, if actually finishing a song in it's pattern sequencer was set up a bit better they could take a significant market share with it. Compared to VSTi only solutions or Maschines bloat and shortcomings it could be the sweet spot to people if Arturia could figure out how to market it. A clue would be selling it as Drum Brute's digital brother, and making integration between the two a thing.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: lordjingjing on May 08, 2018, 07:35:06 pm
That´s great news! ;D Honestly I had almost given up hope, both on Spark and Arturia, looking forward to the update!  8)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: Matt Arturia on May 11, 2018, 04:27:08 pm
Hi guys,

As artao said, Spark 2.4 is currently being tested by external testers. Still some work to do but we are moving forward and we will deliver.

Regards,

Matthieu
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: ben arturia on June 08, 2018, 01:22:57 pm
Hi all,
Spark 2.4 is now available for download.
Please enjoy ;)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: lordjingjing on June 08, 2018, 06:23:35 pm
Hi all,
Spark 2.4 is now available for download.
Please enjoy ;)

Thanx for pulling through guys! ;D And what a great timing, going to be a fun weekend. ;)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: vaikl on June 08, 2018, 06:42:41 pm
Download error...Download error...Download error... >:( >:( :P :P Come on Arturia folks, pause your online games and let us download!!!

Seriously - that's always the same every time new downloads are acknowledged:/ I can't get Spark 2.4 nor the Analog Lab 3 update, neither from the ASC nor from https://www.arturia.com/support/updates&manuals. That's ridiculous.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: ben arturia on June 09, 2018, 04:25:46 pm
Thank you lordjingjing ! I hope you'll enjoy jamming with this 2.4 !
vaikl yes you're right too much people love Spark at the same time ! I guess the server bandwidth is too small. We didn't expect so much !
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: artao on June 09, 2018, 04:43:02 pm
Thank you lordjingjing ! I hope you'll enjoy jamming with this 2.4 !
vaikl yes you're right too much people love Spark at the same time ! I guess the server bandwidth is too small. We didn't expect so much !
Well, that shows you how popular Spark 2 still is, eh?
Perhaps a v3 is in order then? <wink><wink><nudge><nudge> ;)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: eisermann on July 05, 2018, 08:21:23 pm
Hi Everybody,

I'm new to this forum and new to the Spark 2 / LE topic so please forgive me if do something wrong. Here is my case:

Recently I bought a used Spark LE controller with Spark 2 Software (of course I downloaded version Spark_2_4_0_106.exe). I also own iSpark and it works fine for me on my iPad Pro.

I use Spark 2.4.0.106 standalone. Now I want to create custom synths on my DELL Studio 1747 with Windows 7 Pro 64 bit. I open the Modular page and everything seems to be fine, BUT there are no vertical scrollbars where I need them to see all the modules that are available. Same for the main (or "construction") section where I would drag the modules to. The only difference here is, that I can use the arrow keys to scroll up/down/left/right. I tried to jump to the Modules section using TAB, but - besides I don't get any visual feedback where I'm at - I can't scroll. The TAB-jumping itself seems to work, as I could change the first row of the Macro section.

The Modular page is THE page for me in Spark 2. I can do everything else I would want to do in iSpark, though it would be easier to access my samples on the hard-drive on my laptop and then export the whole kit from there. All videos I have seen so far only show Spark 2 for Mac, so I have no idea if I'm the only one experiencing this bug. I'll add a screenshot so you can see what I'm talking about. You will also see, that the Macro section looks cropped on the right side and also the main section kind of covers the modules where the scrollbar should be.

I hope this will be fixed in the near future! ;)
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: ben arturia on July 09, 2018, 01:32:28 pm
Hi eisermann,

Did you test with the mouse wheel ? or using 2 fingers on a track pad ?
No scrollbar should be displayed on the GUI there.
Using mouse wheel adjust zoom ratio or scrolls the menus.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: eisermann on July 19, 2018, 08:47:06 pm
Did you test with the mouse wheel ? or using 2 fingers on a track pad ?

Hi ben,

thanks for the suggestion. When I use the track pad it works - sometimes. I couldn't figure out how to get a consistent result.
Title: Re: Spark 2 Bug Fix Requests Compilation
Post by: vax71 on July 18, 2019, 04:01:55 pm
Hi
No scrollbar should be displayed on the GUI there.
Using mouse wheel adjust zoom ratio or scrolls the menus.
I like to use a stylus/tablet — without a scrollwheel! A scrollbar would be great.

Some bugs: