I have had the Black Sledge for about 1 year. updated it to 2.5.1. I got some sound patches on line and loaded them via Midi (not so intuitive because it can write over other patches. What can I say, I found that if I change patches fast there are occasional glitches, but if I dial the patch and let it completely load there are no problems. I think that most problems people are having come from navigating through patches and cursors fast and the hardware is not able to keep up. I am keeping my Sledge Black, its not perfect, it requires patience and a gentle touch and in return it gives back great sounds and endless tweeking potential.
The init bug is only an issue if you grab the data knob and go crazy with it, switching between patches and overloading the CPU. I'm on 2.5.1 on a yellow Sledge, and on the rare occasion that this init bug occurs, you just have to reload the sound. Layers, splits, etc no issues, but if you want to switch through 30 patches at once, holding all different keys, you might have an issue. This is most likely the result of the CPU trying to layer/split the sounds, because of the way the layer/split function was implemented. You can actually turn it off (automatically layer sounds) in the settings menu. I wonder if that would help? Otherwise, why is it a big deal? If it only occurs when you deliberately try to overload the CPU, just don't do that. Or is there something else?
When I originally posted this video a couple years ago I received both messages from people who said they had the same problems and messages from people who said there's nothing wrong and that I was going through the menus too quickly. You're the first to offer a constructive and non confrontational response and I appreciate that. The issues still would occur if I went slowly from patch to patch, I only did them quickly for the video to keep things moving, however your advice sounds like a great thing to try. I do not have it anymore, obviously but it would be nice if anyone out there who has these same experiences would give your idea a shot. It's much more constructive than what the company provided, that's for sure. Thanks, Adam!
@@alternatingbitmusic can i play the synth into the daw? Im trying to connect sledge with midi cables and usb but it's still not working into the daw. I have the new firmware. I m trying with maschine, samplitude, fl studio.
@@alternatingbitmusic Yeah, I think I remember seeing your original video, and I was looking for it to try and leave this comment, but it was gone. I rarely get this with my Sledge, like.... honestly I think I could count on my fingers the amount of times it's happened, but I never gave it any thought because I'd just go up/down a patch and be done with it. I've been working on a ton of amazing layered patches, and as I was, it occurred to me that it might have something to do with the init bug! Alas, I was too late! Sorry you had such bad luck with your Sledge, because I love mine - it seems like the only people who have really been having issues are owners of the black Sledge, but I doubt that's anything more than a coincidence.
@@alternatingbitmusic Also, some patches not sounding is because of a setting in the main menu which is set weird from the factory, but it's "Send current sound". When I got mine, it had that issue with the first patch - all you have to do is switch it to "send all sound" and the problem is fixed.
For me was the solution to make my own INIT Patch, after that i have not much problems anymore. I can play days without the patch hanging. The Sledge is one hell of a synth. Super nice priced. If you see other brands for triple the prices, those synths are not worth it. Don't be negative about this one. Make an INIT patch rotating and pressing al the button and try again. It helped mine. Have fun! The easiest and fastest way is to copy the new INIT patch in the sledge software.
It's still not right to have to make workarounds and have fingers crossed but I'm glad you're happy with it. I think if the company admitted fault and made effort to actually assist I would have felt better about it.
Thanks for posting this. I just ordered one of these from Zzounds, am having the same issues, and have put in for a return. Knowing that they’re customer service isn’t helpful, and you’ve been waiting 2 years for a replacement says a lot about the company. If they wanted you to take down and honest review and add a positive one, they should be worthy of it. I’m going to get a Roland JD-AX (different but I’m all over the map with synths).
I bought one of these early last year with 2.5.1 loaded into it, never encountered this issue. Had a power surge in my apartment that fried the unit. Took it to a repair shop and had a new motherboard installed. I now have the INIT bug constantly.
Restarting the unit is only a minor headache though. This synth is still a lot of fun and a great entry point for those new to synthesizers. Would not recommend for live performances.
the sledge black simply seems to have a slow internal operating system. I have learned to dial my patches with the number buttons, and wait until it fully loads. other then that the synth is ok, not great, just ok
Firmware 2.5.2 apparently addresses these issues. But zipping though the presets at speed just pisses the synth off... SLOW down a bit... Let each preset load properly before selecting the next.
Thank you for making this video. The problem itself is not so much the issue for me. I understand firmware issues being difficult to nail down. That being said this where any company should step in a fix them. Or else I would never buy from them as a lot of people I’m sure would agree. Thanks for saving me from this heartache and glad it worked out for you to find the virus. I was planning on grabbing the sledge used because the new price is too steep for me. And from what I’ve seen of the virus is even used those are to much $$ for me.
From what I've gathered from tech support, the main issue is due to the standard INIT patch being incomplete - it does not reset all the parameters it should do. I believe extra parameters were added to the machine's state at some point in the development, and these were never added to the INIT patch so they never get reset. This means if you load INIT, or any patch created from it, the machine is not fully defined and is unreliable. This also applies to the INIT patch on Spectre. The other (non INIT) factory presets do not have this problem; they update *all* parameters when you load them, so there is nothing left undefined. My solution was to start from power on, load factory patch 1, adjust all controls to an 'init' state (however you want to define this), and then save it as 'My Init'. Then overwrite *all* the factory INIT patches with this new init patch to avoid accidently loading the duff ones in future. It can be tedious to do this manually so I dumped it to the computer and used SoundMapper to propagate the patch to every empty slot. I also deleted all my own patches just to be safe, as I couldn't remember how they had been created. The bottom line is that if ever you load an old INIT from the machine or from Spectre, or a patch which was based on INIT (whether you made the patch yourself or copied it from someone else), the machine will be in an unreliable state. I would still recommend being patient when changing patches, but once the above procedure was done, I've had no 'init' issues. There are still a couple of minor issues with MIDI, but these are not show-stoppers for me. Overall, I agree the machine feels unfinished, and it is annoying that there have been no firmware updates for a long time. I was told at the time there were long delays in communication between Studiologic and Waldorf (maybe Waldorf were putting all their effort into the Quantum?). Either way, it's been a few years now so it's very poor support. By the way, I'm on the black sledge with v2.5.2
@@alternatingbitmusic No problem. I just hope it's a solution for others. I posted this on the Facebook Sledge group in 2017 but didn't see any confirmation. All I know is it worked for me :)
Hello ...I just bought Sledge 2 Black Version... I just have downloaded the Sound Mapper archive....but inside I can t find anywhere the .exe setup for SoundMapper (o9nly META.INF....and SledgePackage with classes file, ico and bmp) Where can I find Sound Mapper executabile file please? Thank you!
A bit late in the day. Indian way has a very slow attack; did you take this into account? They way you were hitting the keys, it wouldn't have had time to respond.
I was acting faster for the sake of the video... they didn't work slow or fast... and the sounds that DID work had no issue with my speed (also demonstrated).
Thanks for the warning! It seems Studiologic have addressed it, but your video is still worrying. On their website at the moment of writing this (because I'm considering buying a second hand unit at €400) I found: Release note 2.5.2 Fixed: a random issue of some Sledge, not generating sounds at Power on or on selecting a Program, which required further selection.
these vids are nice to have to make users aware and put pressure on companies to fix the issues unfortunately it seems to be more common these days with the rush to get products out and lackluster QA (hell, Microsoft has been doing it for years with Windows) - I got a good deal on a used Sledge Black 2.0 and with my positive experience so far and the helpful workaround comments here I see it as a keeper - sounds and controls are great and more fun than my Blofeld or even Waldorf Microwave XT (Sledge has more: wavetables, VA, and samples with some decent basic FX) some companies like Alesis released stuff like the flagship Andromeda A6 16-voice analog synth, which is coveted these days and goes for crazy money, but has several famous issues that will never be fixed (company ditched the old tech before being acquired by Numark, etc. - I forgot the exact company details) - not to mention the custom ASICs onboard that are impossible to replace when they fail (Waldorf Wave has that issue too - too specialized for its own good) I experienced a couple of the famous Andromeda issues firsthand like system lockups needing a power cycle and unusual knob behavior where the supposed knob-per-function actually had multiple parameters changing at once with a single knob turn - however the synth is still coveted to this day - people can work around the issues but it's a shame it will never be fixed and paying top dollar (over $2500k) for a synth that may need workarounds is sad at least the Sledge still has updates coming out for now
Thanks for the video. I was considering the Sledge 2.0 but it STILL has these kinds of bugs like that? Yikes, that is AWFUL Who is to blame on the unstable OS Studiologic or Waldorf? I own neither and at this rate looks like I will never.
This 'synth' only lasted 2 days in my studio. Same bugs. Now to be honest, I recently bought a Novation Summit. Also very annoying bugs. i.e. Unable to Save Multi's when Midi connected and Local OFF. Multi Programs showing INIT after saving with a name and scrolling back. Not showing single patch bank/nrs in a Multi....Thing is, the Summit sounds soooo well that I'll wait for Novation to come up with a decent OS update, soon hopefully. Access ? Deutsches grundlichkeit ! (my Virus Classic & TI)
You can't do anything with local off. There's nothing wrong with your summit lol. Admittedly it's a stupid thing that they disabled so many functions when local is turned off. Regardless, summit is incredible. Hope you kept yours. ;)
Any update on if this got resolved? Was considering this cause of the FATAR keybed and you know, Waldorf is sweet, having both in one just seems awesome
I don't think so though anyone else can chime in. My understanding is Studio Logic used Waldorf's engine but Waldorf no longer supports or updates it as it is in SL's hands, and Studio Logic doesn't seem to do much. Meanwhile Waldorf had run constant updates & fixes on their Blofeld over the years, for instance. If there is evidence of the issues I've presented as addressed and fixed I'd revisit this synth because I did like it otherwise. Sadly with a fraction of them apparently being free of OS problems, it is hard to know (which is why I feel SL needs to be open about the issue).
Feel free to dig into the comments here to research more... some mention things have improved some or you learn to ignore the faults. For me it was more of an ethical choice to move on.
Was thinking of getting one of these till now!! Too bad they can't get their shit together...there seems to be a bunch of cool sounds. I'm surprised Waldorf doesn't get on them for this bush league build. My buy went to the Modal Argon 8x ...it awsome!
I just updated my Sledge 2.0 to firmware version 2.5.2. Now I can't access the Samples section of Oscillator One on a regular basis. Sometimes I can, sometimes I can't. Very unreliable synth.
@@vforvillain77 I own both versions of the Sledge and have never had a problem with either of them. I use the black one every day and my whole channel is very Sledge-centric these days. If you're on the fence about it, scroll down to my big comment on this video with the 12 replies, where I explained his issue in more detail. Check my channel out if you want to see how I use mine.
I bought a Sledge secondhand and upon updating from 2.0 to 2.5.1, the entire unit is completely bricked. It powers on seemingly as normal, but doesn't respond to any input, doesn't output midi, and doesn't respond to USB connection. It seems like their software for this model was really hacked together and unstable.
Same thing happened to me and SL offered to replace the board but have yet to follow through. If they don't I'm thinking of taking action against them for willfully releasing software they knew damaged keyboards. Did you ever find a resolution for yourself?
@@jamestillman5247 SL offered to RMA it but I would have been on the line for shipping. I didn't end up doing it. The Sledge is just taking up space at the moment unfortunately.
Layering is fun also. You end up with great sounds but sadly they appear across all patches whether you like it or not. Imo the Sledge has the potential to be a great synth but what Company with any credibility would repeatedly churn out such substandard and bug ridden code. Even basic modulation functions don’t work.
Visa, Master Card or Paypal would have given you a refund option. Your video is really a contribution to the synth world. The question is: your validating the number of bugs of which the manufacture is aware of, is the dealer continuing to sell this product? With much gratitude, thank you.
Some patches not sounding is because of a setting in the main menu which is set weird from the factory, but it's "Send current sound". When I got mine, it had that issue with the first patch - all you have to do is switch it to "send all sound" and the problem is fixed.
I'm a pretty long time Sledge owner, a Black one, and to me it looks like you are hitting the keyboard too soon after changing the patch. Remember, holding down one key while you change patches is the Sledge command to make a Split with the 2 adjoining patches. And holding down more than one key makes a Layer. So I'd bet you're inside some tight timing Range and that's unintentionally glitching the Sledge.
Thanks, Tommy. You're not the first to point out about the speed at which I demonstrated however the same would happen at a slower pace; I just wanted to get to the point in the demo. Remember not ALL units are defective so you may also be one of the lucky ones. Thanks for your input though.
@@alternatingbitmusic well i ended up having a Midi Apocalyptic Event, and that somehow put my Black 2.5.1 Sledge into another freeze, where all the patches are named 111111111111, and any edit and save to one does that to all of them; no sound, no MIDI after the initial bootup, and NOT fixable by a reboot. I tried swapping the Left of the 3 main boards (not counting the one with the jacks on it) and that didn't fix it.
Dang... Id narrowed down my choices for a synth purchase and this 1 was climbing to the top 3. But not interested in these issues. Sucks too cuz i was close to calling sweetwater w/ my cred card nxt wk. Smh
Interestingly I posted it long before the post date (in case you didn't see the description) - so for a long time the warning was silenced lol. I'm glad I could be of help.
Locking up to the point where all patches become an init patch? Having to reboot often? I'm not sure if other problems exist as I didn't keep it. I saw someone else demo it and he discovered sometimes patches can bleed into the next.
This isn't a super computer. Still with today's computer to overwhelm it with commands can cause an app or the computer to malfunction and get buggy. The conclusion is: work at an adapted pace.
I appreciate that... however it's not about the speed. I acted quickly in the video to keep things moving. It had the same issues whether or not I paused for a long time in between.
lot of men think like girls he held a bad review hostage to get a replacement unit when the baby didnt get his way_he decided to take the time & repost it to slander the whole brand this is so high school girl_whatever rare non-issue glitch this is_we're surrounded by evil petty idiots
WHAT?? The initial post was removed because I had included names of the sales people I dealt with and I was asked to remove it for the sake of their identity. Replacement unit?? I got rid of it and bought an Access Virus instead, if you watched the whole video you would have seen that part. I suspect trolling gives you kicks, which makes you the "baby." Thanks for watching.
I have had the Black Sledge for about 1 year. updated it to 2.5.1. I got some sound patches on line and loaded them via Midi (not so intuitive because it can write over other patches. What can I say, I found that if I change patches fast there are occasional glitches, but if I dial the patch and let it completely load there are no problems. I think that most problems people are having come from navigating through patches and cursors fast and the hardware is not able to keep up. I am keeping my Sledge Black, its not perfect, it requires patience and a gentle touch and in return it gives back great sounds and endless tweeking potential.
The init bug is only an issue if you grab the data knob and go crazy with it, switching between patches and overloading the CPU. I'm on 2.5.1 on a yellow Sledge, and on the rare occasion that this init bug occurs, you just have to reload the sound. Layers, splits, etc no issues, but if you want to switch through 30 patches at once, holding all different keys, you might have an issue. This is most likely the result of the CPU trying to layer/split the sounds, because of the way the layer/split function was implemented. You can actually turn it off (automatically layer sounds) in the settings menu. I wonder if that would help? Otherwise, why is it a big deal? If it only occurs when you deliberately try to overload the CPU, just don't do that. Or is there something else?
When I originally posted this video a couple years ago I received both messages from people who said they had the same problems and messages from people who said there's nothing wrong and that I was going through the menus too quickly. You're the first to offer a constructive and non confrontational response and I appreciate that. The issues still would occur if I went slowly from patch to patch, I only did them quickly for the video to keep things moving, however your advice sounds like a great thing to try. I do not have it anymore, obviously but it would be nice if anyone out there who has these same experiences would give your idea a shot. It's much more constructive than what the company provided, that's for sure. Thanks, Adam!
@@alternatingbitmusic can i play the synth into the daw?
Im trying to connect sledge with midi cables and usb but it's still not working into the daw.
I have the new firmware.
I m trying with maschine, samplitude, fl studio.
@@alternatingbitmusic Yeah, I think I remember seeing your original video, and I was looking for it to try and leave this comment, but it was gone. I rarely get this with my Sledge, like.... honestly I think I could count on my fingers the amount of times it's happened, but I never gave it any thought because I'd just go up/down a patch and be done with it. I've been working on a ton of amazing layered patches, and as I was, it occurred to me that it might have something to do with the init bug! Alas, I was too late! Sorry you had such bad luck with your Sledge, because I love mine - it seems like the only people who have really been having issues are owners of the black Sledge, but I doubt that's anything more than a coincidence.
@@alternatingbitmusic Also, some patches not sounding is because of a setting in the main menu which is set weird from the factory, but it's "Send current sound". When I got mine, it had that issue with the first patch - all you have to do is switch it to "send all sound" and the problem is fixed.
@@matteo8748 No idea, sorry - as I said in the video I sent it back. I only had it for a couple of days.
Please, don't ever delete this video.
For me was the solution to make my own INIT Patch, after that i have not much problems anymore. I can play days without the patch hanging. The Sledge is one hell of a synth. Super nice priced. If you see other brands for triple the prices, those synths are not worth it. Don't be negative about this one. Make an INIT patch rotating and pressing al the button and try again. It helped mine. Have fun! The easiest and fastest way is to copy the new INIT patch in the sledge software.
It's still not right to have to make workarounds and have fingers crossed but I'm glad you're happy with it. I think if the company admitted fault and made effort to actually assist I would have felt better about it.
Thanks for posting this. I just ordered one of these from Zzounds, am having the same issues, and have put in for a return. Knowing that they’re customer service isn’t helpful, and you’ve been waiting 2 years for a replacement says a lot about the company. If they wanted you to take down and honest review and add a positive one, they should be worthy of it. I’m going to get a Roland JD-AX (different but I’m all over the map with synths).
I bought one of these early last year with 2.5.1 loaded into it, never encountered this issue.
Had a power surge in my apartment that fried the unit.
Took it to a repair shop and had a new motherboard installed.
I now have the INIT bug constantly.
Restarting the unit is only a minor headache though. This synth is still a lot of fun and a great entry point for those new to synthesizers. Would not recommend for live performances.
@@SIR_L0IN It's a game of Russian roulette that I don't care to play, no matter how great the synth, but thanks for sharing.
the sledge black simply seems to have a slow internal operating system. I have learned to dial my patches with the number buttons, and wait until it fully loads. other then that the synth is ok, not great, just ok
Firmware 2.5.2 apparently addresses these issues. But zipping though the presets at speed just pisses the synth off... SLOW down a bit... Let each preset load properly before selecting the next.
Thank you for making this video. The problem itself is not so much the issue for me. I understand firmware issues being difficult to nail down. That being said this where any company should step in a fix them. Or else I would never buy from them as a lot of people I’m sure would agree. Thanks for saving me from this heartache and glad it worked out for you to find the virus. I was planning on grabbing the sledge used because the new price is too steep for me. And from what I’ve seen of the virus is even used those are to much $$ for me.
From what I've gathered from tech support, the main issue is due to the standard INIT patch being incomplete - it does not reset all the parameters it should do. I believe extra parameters were added to the machine's state at some point in the development, and these were never added to the INIT patch so they never get reset.
This means if you load INIT, or any patch created from it, the machine is not fully defined and is unreliable. This also applies to the INIT patch on Spectre. The other (non INIT) factory presets do not have this problem; they update *all* parameters when you load them, so there is nothing left undefined.
My solution was to start from power on, load factory patch 1, adjust all controls to an 'init' state (however you want to define this), and then save it as 'My Init'. Then overwrite *all* the factory INIT patches with this new init patch to avoid accidently loading the duff ones in future. It can be tedious to do this manually so I dumped it to the computer and used SoundMapper to propagate the patch to every empty slot.
I also deleted all my own patches just to be safe, as I couldn't remember how they had been created.
The bottom line is that if ever you load an old INIT from the machine or from Spectre, or a patch which was based on INIT (whether you made the patch yourself or copied it from someone else), the machine will be in an unreliable state.
I would still recommend being patient when changing patches, but once the above procedure was done, I've had no 'init' issues. There are still a couple of minor issues with MIDI, but these are not show-stoppers for me.
Overall, I agree the machine feels unfinished, and it is annoying that there have been no firmware updates for a long time. I was told at the time there were long delays in communication between Studiologic and Waldorf (maybe Waldorf were putting all their effort into the Quantum?). Either way, it's been a few years now so it's very poor support.
By the way, I'm on the black sledge with v2.5.2
Thanks for sharing your findings... they would definitely be helpful for those who have the issue and still want to press forward.
@@alternatingbitmusic No problem. I just hope it's a solution for others. I posted this on the Facebook Sledge group in 2017 but didn't see any confirmation. All I know is it worked for me :)
Has any of the current updates solved these glitches?
Hello ...I just bought Sledge 2 Black Version... I just have downloaded the Sound Mapper archive....but inside I can t find anywhere the .exe setup for SoundMapper (o9nly META.INF....and SledgePackage with classes file, ico and bmp) Where can I find Sound Mapper executabile file please? Thank you!
No idea - I got rid of the unit after a couple of days owning it.
A bit late in the day. Indian way has a very slow attack; did you take this into account? They way you were hitting the keys, it wouldn't have had time to respond.
I was acting faster for the sake of the video... they didn't work slow or fast... and the sounds that DID work had no issue with my speed (also demonstrated).
Thanks for the warning!
It seems Studiologic have addressed it, but your video is still worrying.
On their website at the moment of writing this (because I'm considering buying a second hand unit at €400) I found:
Release note
2.5.2
Fixed: a random issue of some Sledge, not generating sounds at Power on or on selecting a Program, which required further selection.
Has anyone had any issues with this synth having a high noise floor? Just curious after reading one comment on a forum.
these vids are nice to have to make users aware and put pressure on companies to fix the issues
unfortunately it seems to be more common these days with the rush to get products out and lackluster QA (hell, Microsoft has been doing it for years with Windows) - I got a good deal on a used Sledge Black 2.0 and with my positive experience so far and the helpful workaround comments here I see it as a keeper - sounds and controls are great and more fun than my Blofeld or even Waldorf Microwave XT (Sledge has more: wavetables, VA, and samples with some decent basic FX)
some companies like Alesis released stuff like the flagship Andromeda A6 16-voice analog synth, which is coveted these days and goes for crazy money, but has several famous issues that will never be fixed (company ditched the old tech before being acquired by Numark, etc. - I forgot the exact company details) - not to mention the custom ASICs onboard that are impossible to replace when they fail (Waldorf Wave has that issue too - too specialized for its own good)
I experienced a couple of the famous Andromeda issues firsthand like system lockups needing a power cycle and unusual knob behavior where the supposed knob-per-function actually had multiple parameters changing at once with a single knob turn - however the synth is still coveted to this day - people can work around the issues but it's a shame it will never be fixed and paying top dollar (over $2500k) for a synth that may need workarounds is sad
at least the Sledge still has updates coming out for now
Thanks for the video. I was considering the Sledge 2.0 but it STILL has these kinds of bugs like that? Yikes, that is AWFUL Who is to blame on the unstable OS Studiologic or Waldorf? I own neither and at this rate looks like I will never.
This 'synth' only lasted 2 days in my studio. Same bugs. Now to be honest, I recently bought a Novation Summit. Also very annoying bugs. i.e. Unable to Save Multi's when Midi connected and Local OFF. Multi Programs showing INIT after saving with a name and scrolling back. Not showing single patch bank/nrs in a Multi....Thing is, the Summit sounds soooo well that I'll wait for Novation to come up with a decent OS update, soon hopefully. Access ? Deutsches grundlichkeit ! (my Virus Classic & TI)
You can't do anything with local off. There's nothing wrong with your summit lol. Admittedly it's a stupid thing that they disabled so many functions when local is turned off. Regardless, summit is incredible. Hope you kept yours. ;)
Any update on if this got resolved? Was considering this cause of the FATAR keybed and you know, Waldorf is sweet, having both in one just seems awesome
I don't think so though anyone else can chime in. My understanding is Studio Logic used Waldorf's engine but Waldorf no longer supports or updates it as it is in SL's hands, and Studio Logic doesn't seem to do much. Meanwhile Waldorf had run constant updates & fixes on their Blofeld over the years, for instance. If there is evidence of the issues I've presented as addressed and fixed I'd revisit this synth because I did like it otherwise. Sadly with a fraction of them apparently being free of OS problems, it is hard to know (which is why I feel SL needs to be open about the issue).
thanks for sharing the bugs, it looks like there is some memory buffer issue. I was considering to get one after reading some reviews ... this helps
Feel free to dig into the comments here to research more... some mention things have improved some or you learn to ignore the faults. For me it was more of an ethical choice to move on.
Was thinking of getting one of these till now!! Too bad they can't get their shit together...there seems to be a bunch of cool sounds. I'm surprised Waldorf doesn't get on them for this bush league build. My buy went to the Modal Argon 8x ...it awsome!
I just updated my Sledge 2.0 to firmware version 2.5.2. Now I can't access the Samples section of Oscillator One on a regular basis. Sometimes I can, sometimes I can't. Very unreliable synth.
Loaded 2.5.2 on the black version and no problems so far
how long have you been on that OS?
still no problems?
@@vforvillain77 I own both versions of the Sledge and have never had a problem with either of them. I use the black one every day and my whole channel is very Sledge-centric these days. If you're on the fence about it, scroll down to my big comment on this video with the 12 replies, where I explained his issue in more detail. Check my channel out if you want to see how I use mine.
Perhaps the black version is better? :) I've heard that once you go black, you never go back.
I bought a Sledge secondhand and upon updating from 2.0 to 2.5.1, the entire unit is completely bricked. It powers on seemingly as normal, but doesn't respond to any input, doesn't output midi, and doesn't respond to USB connection. It seems like their software for this model was really hacked together and unstable.
Same thing happened to me and SL offered to replace the board but have yet to follow through. If they don't I'm thinking of taking action against them for willfully releasing software they knew damaged keyboards. Did you ever find a resolution for yourself?
@@jamestillman5247 SL offered to RMA it but I would have been on the line for shipping. I didn't end up doing it. The Sledge is just taking up space at the moment unfortunately.
I wouldn’t want to be in the place of the owners of the $20,000 aluminum version when they discover these bugs...
Layering is fun also. You end up with great sounds but sadly they appear across all patches whether you like it or not.
Imo the Sledge has the potential to be a great synth but what Company with any credibility would repeatedly churn out such substandard and bug ridden code. Even basic modulation functions don’t work.
Visa, Master Card or Paypal would have given you a refund option. Your video is really a contribution to the synth world. The question is: your validating the number of bugs of which the manufacture is aware of, is the dealer continuing to sell this product? With much gratitude, thank you.
this problem is also detectable in the yellow version considering that it is the same instrument?
...the yellow one was featured just :57 seconds in this video, I guess you didn't watch much? lol
@@alternatingbitmusic ... yes, I hadn't seen this video from the beginning, on Monday I have to take one of these used sinths and I start to worry
@@valerioyou It is luck of the draw; I suspect most of them don't have this issue, maybe 30% of them but I am just guessing. Good luck.
I‘ll get one anyway. I am not crazily fiddling with switches and knobs, so I probably won‘t run into the issue.
I have the same problem with patches not playing, they did nothing to try and help ...
Some patches not sounding is because of a setting in the main menu which is set weird from the factory, but it's "Send current sound". When I got mine, it had that issue with the first patch - all you have to do is switch it to "send all sound" and the problem is fixed.
What synth do I go spend my money on then?
Totally depends on your specific needs & likes.
Had one with same issues.ball ache to load samples.felt cheap.nice sounds but overall crap.sold it and bought a dm12.. .
I'm a pretty long time Sledge owner, a Black one, and to me it looks like you are hitting the keyboard too soon after changing the patch. Remember, holding down one key while you change patches is the Sledge command to make a Split with the 2 adjoining patches. And holding down more than one key makes a Layer. So I'd bet you're inside some tight timing Range and that's unintentionally glitching the Sledge.
Thanks, Tommy. You're not the first to point out about the speed at which I demonstrated however the same would happen at a slower pace; I just wanted to get to the point in the demo. Remember not ALL units are defective so you may also be one of the lucky ones. Thanks for your input though.
@@alternatingbitmusic well i ended up having a Midi Apocalyptic Event, and that somehow put my Black 2.5.1 Sledge into another freeze, where all the patches are named 111111111111, and any edit and save to one does that to all of them; no sound, no MIDI after the initial bootup, and NOT fixable by a reboot. I tried swapping the Left of the 3 main boards (not counting the one with the jacks on it) and that didn't fix it.
I sent mine back because it just sounded too noisy and the reverb was awful , pity as the idea is great and it was well constructed.
Dang... Id narrowed down my choices for a synth purchase and this 1 was climbing to the top 3. But not interested in these issues. Sucks too cuz i was close to calling sweetwater w/ my cred card nxt wk. Smh
What did you go with?
I feel like the public is indebted to your work on this product's nightmare. Was just up for purchasing on CL.- I put a screeching hold on that.
Interestingly I posted it long before the post date (in case you didn't see the description) - so for a long time the warning was silenced lol. I'm glad I could be of help.
Is that the only problem?
Locking up to the point where all patches become an init patch? Having to reboot often? I'm not sure if other problems exist as I didn't keep it. I saw someone else demo it and he discovered sometimes patches can bleed into the next.
you stepped init
Did you resolve issues?
That was covered at the end of the video. :P
@@alternatingbitmusic I got bored It was dragging on a bit sorry LOL
@@Reg-Edit I thought 6 minutes was worth saving someone the headache of ordering an expensive, faulty synth.
This isn't a super computer. Still with today's computer to overwhelm it with commands can cause an app or the computer to malfunction and get buggy.
The conclusion is: work at an adapted pace.
I appreciate that... however it's not about the speed. I acted quickly in the video to keep things moving. It had the same issues whether or not I paused for a long time in between.
@@alternatingbitmusic I just got a Sledge a couple of weeks ago. Anyhow it's nice to point out bugs - in the hope the company will move.
access virus kc
lot of men think like girls
he held a bad review hostage to get a replacement unit
when the baby didnt get his way_he decided to take the time & repost it to slander the whole brand
this is so high school girl_whatever rare non-issue glitch this is_we're surrounded by evil petty idiots
WHAT?? The initial post was removed because I had included names of the sales people I dealt with and I was asked to remove it for the sake of their identity.
Replacement unit?? I got rid of it and bought an Access Virus instead, if you watched the whole video you would have seen that part. I suspect trolling gives you kicks, which makes you the "baby." Thanks for watching.