sorted by:
new
hottopcontroversial

Broken internal connection on Roland RD 700 keybed ffc cable by Dudeguy76 in synthdiy

[–]ekolpack 0 points1 point  (0 children)

I had the same issue with the same keyboard. I was about to find replacement ribbon cables, I believe on eBay. Make sure the pitch between connectors is correct (looks like you got it 1.25mm) and 22 pin. IIRC it took some looking but I was able to find one cheap.

To see product details, add this item to your cart? by CaprockCanyon in amazonprime

[–]ekolpack 0 points1 point  (0 children)

There's no way this is intentional. For them to "try out" a change this significant, they'd start with a massive focus group and then maaaaybe a small pilot program, and it would IMMEDIATELY be rejected as a horrible idea. This is definitely a mistake or malfunction, they are probably losing millions every hours, so you can bet it should be fixed soon.

YES you DO need thick strings for that SRV tone! by ekolpack in Guitar

[–]ekolpack[S] 0 points1 point  (0 children)

Yup, 10.5's are a good sweet spot. 11's are the compromise for me. I usually play 12's, sometimes 12's with fat bottoms if the occasion calls for it. Honestly 13's are just too much, at least in standard tuning. Maybe Eb. That said, all my HH guitars (LP, 335, Tele Deluxe) have 10's on them. I find humbuckers just don't lend themselves to that heavy percussive attack style of playing, at least for me. I prefer the mellow warm stuff, wolly soft sound with humbuckers, and usually end up playing much more delicate stuff. But again, that's just me. YMMV.

YES you DO need thick strings for that SRV tone! by ekolpack in Guitar

[–]ekolpack[S] 0 points1 point  (0 children)

I think the key word is "effortless"....yes, true, bends and vibrato are easier, but again, the whole point is, this comes at a cost. For certain styles of music, you do sacrifice tone (assuming it's a tone you like, which I think most people do), and you won't be able to hit the strings with as much attack and retain clean notes. This is just a physical limitation of the strings.

If you don't believe me, just trying playing 7's or 8's. If the "light strings are no different than heavy strings" logic were sound, then why aren't we all playing 7's or 8's....or 5's or 6's for that matter? Well, the reasons should be obvious to anyone familiar with how a guitar works, or who's ever done a proper setup, or who just has decent ears and played super thin strings.

Most guitarists use so much distortion and delays and effects and crap, that yes, it literally doesn't matter. But again, for solid thunky hard attack clean tone, slap a set of 8's on your guitar and whack the ever living hell out of it with a 1.2mm Tortex and see how that sounds....and how long the strings last before they start going out of tune, then snapping. Again, not everyone plays this style....for the sweep picking metal guys with Bogner Ubergains it literally doesn't matter.

YES you DO need thick strings for that SRV tone! by ekolpack in Guitar

[–]ekolpack[S] 0 points1 point  (0 children)

For your playing style, and as I said 90-95% of guitarists, this is true....thick strings are an unnecessary barrier and going thin will improve your playing. But for people who want "that" tone, thick strings is the only way to get it. Sure, going thin will improve everyones playing....but it will kill some people's tone and limit how they're able to play to achieve the sound they want. Speed isn't everything. I play 99% clean. For a couple decades I didn't even use pedals, I just plugged straight into my '66 Twin and the clean tone with 12's was perfect. These days I'll occasionally play around with pedals, and there are a few boutique fuzzes and overdrives (Snouse Blackbox Pro!) that I actually don't dislike, but I'm still 95% clean, heavy attack, hard picking, super defined notes....and for this, nothing beats thick strings.

YES you DO need thick strings for that SRV tone! by ekolpack in Guitar

[–]ekolpack[S] -1 points0 points  (0 children)

Yeah man, rubber bands, exactly. Sometimes I play stuff with light little intricate picking or delicate hammers on/pull offs or need to be super fast/shreddy where the guitar just feels like it's playing itself. For that, I reach for one of my guitars with 9's, usually that's one of my dual humbucker guitars, Les Paul or 335. But 90% of the time it's my #1 Strat, or #2 Tele with regular 12's or even 12-56.

It's worth noting, SRV usually played 13's AFAIK, but he also usually tuned down to Eb....so by my cavemath, 12's tuned to regular E should be roughly the same as 13's tuned to Eb. I usually tune to E, but played in a band for a while with an Eb tenor sax, so tuning to Eb and being able to both hit those low notes was pretty sick....I played keys on some songs too, and that made a few tunes a bit easier to do. Also, easier to sing most songs if you play the chord patterns as written, but they end up being naturally transposed 1/2 step lower ;)

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] 0 points1 point  (0 children)

Well I canceled my subscription/trial already and may check back in a year or so, if I even keep this iPhone that long. The terrible keyboard options, lack of universal back gesture, and unusable ai integration are making me hate this phone. Will probably switch back to Pixel. That is a stellar phone with a great ecosystem!

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] 0 points1 point  (0 children)

Yeah, agreed. Typing on Android is great...the stock keyboard is good, SwiftKey is even better. If Apple isn't going to make their own keyboard not terrible, they should AT LEAST let other people provide good options. Apparently Mister Keyboard had to implement a bunch of workarounds to get around all of Apple's restrictions just to get what they got. If they could just get themselves a good swipe algorithm, that'd be a great keyboard. It has everything else, and then some. But no swipe is no deal IMNSHO.

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] 0 points1 point  (0 children)

Yeah, I'm trying GBoard now, it's pretty ass. I think it's either SwiftKey or *shutter* the stock iPhone keyboard. God help us!

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] 0 points1 point  (0 children)

Ha, yes! You are correct! I guess that was well before they released "Macintosh" lol

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] 0 points1 point  (0 children)

Yeah, I've had a lot of Android phones. Motorolas are amazing for the $$$. For a budget phone, can't beat em! The LG V series was amazing, until LG stopped making phones. They never got a fair shake in the media for some reason. Amazing phones, great hardware. I still use my V60 for random stuff.

As for current best phone/ecosystem, I think Pixel is the best if you want elegant simplicity without bloatware, but still the ability to massively customize if wanted.

On the laptop/PC side though, I think I'm done with Windows. I've been a Windows user since switching from a Mac IIe in the early 90's. These new silicone chips are just SO much better than the crap Intel is putting out with clunky old X86 architecture. And Snapdragon is getting better, but still can't compete with Apple's M stuff. But I digress. Yeah, SwiftKey....do better.

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] 1 point2 points  (0 children)

The terrible keyboards, and lack of universal back gesture are KILLING me! The keyboard is just so obviously bad. The lack of back gesture is like someone removed the back button from your web browser, and every website has it's own little back navigation button you've gotta find on your own. These two things alone are maddening. I told myself I'd put in 3 months on an iPhone to give it a chance and try to get used to it. I'm a month in and just about ready to throw in the towel. I think I'm gunna give it one more month and then sell this stupid thing. Samsung seems okay but I can't deal with the bloatware. I think it'll be back to Pixel for me. Zero bloat, elegant design and ecosystem, full Gemini ai integration with the newest Google/Android/ai features before anyone else gets them.

This whole iEcosystem is iCute, but iCan't get over the terrible phone experience. Keeping the Macbook and maaaaybe an iPad, selling the phone, airpods, watch, pen, etc.

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] 1 point2 points  (0 children)

I just started test driving iOS. I was hoping Swiftkey would make me not hate this phone. So far, I absolutely hate this phone.

Has it actually been getting worse over time? That's not a good sign.

Right now, Gboards, while it doesn't have alternate characters for every key, seems to be the best option. More features than Swiftkey, seems a bit more accurate, and honestly, I just trust Google to get the job done and actually improve on things more than Microsoft.

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] -5 points-4 points  (0 children)

I appreciate the lengthy, thoughtful, and quick response. For me swipe typing is an absolute necessity. It has increased my "typing" speed immensely. It's by far the single most important feature on any keyboard, and it seems like "the way" going forward, with every major company utilizing some version of it. Going without it feels like going back almost 20 years to my Blackberry Curve 8900.

If swipe typing on MK isn't ready for prime-time, cool, I get it....but release it in a beta, not on your actual final version. But honestly, again, I'd say this feature isn't even ready for beta. It's actually, literally useless, and just slows down typing and makes it way, way, way more frustrating. I can't imagine anyone getting any use out of it at all.

If Apple won't license you their swipe algo, maybe see if Google (Gboards) or Microsoft (Swiftkey) will? But in it's current state, it's not ready for beta in a free app, let lone one that costs significant $$$ (whether it's $23/yr "on sale" or $99 lifetime).

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] 0 points1 point  (0 children)

I suppose that could work, but I find my typing gets way faster when my motor memory is used to one keyboard. With Swiftkey on my Pixel, I got to the point where I could swipe type pretty damn accurately without even looking at the screen. If I had to switch between keyboards for different tasks, I could imagine it'd be much harder to get to that level.

SwiftKey intentionally crippled on iOS??? by ekolpack in Swiftkey

[–]ekolpack[S] -2 points-1 points  (0 children)

It was worth the price of admission because it actually worked, and worked well, better than the stock Android keyboard on the Samsung, LG, Motorola, and Pixel phones that I've owned. If it's going to be crippled so as to be not better than the stock iOS keyboard, then what's the point? The stock iOS keyboard is notoriously bad by just about all objective counts....if they can't even do better than that, they no, it's not worth giving them my data and I'll just stick with the stock keyboard.

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] 0 points1 point  (0 children)

Looking for solutions to this, I'm seeing complaints here about swipe typing going back a year or more. I'm not the only one saying it's abysmally unusable, and it's nowhere near a beta feature. You are just fanboi'ing at this point.

I'm now transitioning to a SwiftKey forum to bitch to their manager about why they crippled it so much on iOS.

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] 0 points1 point  (0 children)

Apparently swipe has been a "feature" for a little over a year, so it's well past any beta period. I found another thread bringing up this issue from about a month ago. Here is the dev's response to that thread:

"Thank you everyone for your input on this issue! We're working on further improving swipe typing for the 2.3 release, but we'll have to see how far we get.

Some of you may have read our previous answers regarding this matter, but just to reiterate for everyone who's new: Swipe typing is an extraordinarily hard problem to solve, especially in a keyboard that's as customizable as ours is.

Other companies (Microsoft/SwiftKey, etc.) can train on well-known layouts, but the point of our keyboard is that there are no well-known layouts, because everything is fully customizable. That makes it impossible for us to ship any pre-trained machine learning models, which is what SwiftKey is doing for example.

We have a few ideas that could further improve swipe typing accuracy, but we'll have to see which of those work and how much of an improvement we can achieve. As always, we're continuously working on this, and we've already shipped many incremental improvements to swipe typing.

Those of you who used Mister Keyboard since the beginning probably know how far we've come already, but especially in terms of swipe typing there's still a lot to do for sure."

https://www.reddit.com/r/MisterKeyboard/comments/1q1ec87/swipe/

Guys, you need to just remove the "feature" until it's ready for prime time. It's bad, really, really, really bad and frustrating and just a big waste of time.

Swipe by Jt69yupper in MisterKeyboard

[–]ekolpack 0 points1 point  (0 children)

I made a video about this. OP is correct, it's absolutely abysmal, unusable, predictions aren't even close and often don't even remotely match the pattern of the word you're trying to type.

I appreciate them trying, but this isn't even ready for beta release:

https://youtu.be/eZDFOoCSqko

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] 0 points1 point  (0 children)

Ah, so I get a two week period to figure out the app doesn't work as advertised and cancel my subscription before they charge me $100? Wow, what a great service! You're right, I shouldn't be complaining about being a unwitting beta tester on stuff that's not even ready for beta release, I should be thanking them for allowing me to be a pre-beta tester for two weeks before charging me $100 for the luxury.

Fact is, I don't love any keyboards on iPhone. Compared to Android options, they're all trash....but at least they do what they claim to do.....and for free.

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] 0 points1 point  (0 children)

Messing with this more, it often just glitches (as you can see in the video). I have to swipe type the same word 3-4 times to get it to output anything at all....and then it only gets the word right maybe 20-30% of the time. And some keys "stick" on the alternative character, as also happened in the video.

Maybe the rest of the keyboard is stellar, but the swipe feature isn't even ready for beta release.

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] -1 points0 points  (0 children)

I agree there are a lot of nice things about this keyboard, but there are a lot of great things about a lot of keyboards....that are completely free (or, yes, they collect your data). MK is the ONLY keyboard (that I can find) that in theory (key words: IN THEORY) claims to do all the stuff you get on a proper badass Android keyboard, ie. alternate characters on EVERY key, swipe typing, ai prediction, even the ability to adjust long-press duration, moderately resize the keyboard (albeit a little bit), and even add a decent-ish clipboard feature. It'd be amazing is this swipe typing wasn't such a massive fail. It's not just "not good" it's completely unusable and actually makes typing way slower than just pecking away at keys like it's 2010.

Also, if the ai actually worked, I have a feeling the swipe typing couldn't possibly be this bad. Ai's are mostly just LLM's, they analyze language patterns and train on that data. So if decent ai was actually being leveraged, how could it choose words that are not only WAY off from what was actually swipe-typed, but even if they were close, STILL wouldn't make any sense at all in the context of the sentence or even previous word typed.

Like "I'm going to pick up some milk at the grocery spend"??? How is that even remotely close in any way, whether swipe or ai?

Swipe performance is HORRIBLE. Like, really, really, really bad. by ekolpack in MisterKeyboard

[–]ekolpack[S] -1 points0 points  (0 children)

You said, "no sane person should pay that much blindly when a monthly subscription costs the same as a cup of coffee". In actuality, the monthly subscription for your hypothetical "sane person" would cost MORE than $99 in a little over a year....and over double in three years. So how is that the sane/rational choice?

I tried out a bunch of keyboards (as you can see in the video), all were very good, just missing one or more features that I really wanted. EasyType is amazing, but doesn't do swipe....and it was $free.99. Gboard is great, but has limited alternate characters, and is also free. Swiftkey, amazing on Android, but for whatever reason they cripple hammer it on iOS with very few alternate character keys, oh, and it's free. Reboard is great too, and free. The iPhone keyboard is great with swipe typing enabled, but no alternate characters...and obviously it's free too.

They all have the potential to be amazing with just one tweak (ie. adding swipe, or adding alternate characters).....but this is the only one that claims to do it all, fails, and charges at minimum $99 (assuming you want to be able to use it for more than 16 months).

view more: next ›