Відео

Yes, my NA3C and TabX are both working normally, as does my Poke 2, which will be I think 4 years now with me :)

heheheh good one, made me chuckle out loud :)

I fully agree. They should add more just for the sake of adding. I'd much rather see fewer yearly updates, but more meaningful and focused on the core principles of the RM2 as a device.

Thank you for your input, but this is not how such commands are implemented. The system gives a line suggestion, which means that regardless of how the selection is moved, if it is moved to the line, it needs to get there normally and without all of the bugs we've seen demonstrated here. So, the lesson is, Remarkable development team really needs to do a much better job at bug-testing their code.

Yet I make a dedicated video focusing exclusively on negatives, but you ignore that, interesting. What is your opinion of the Update 3.11 quality delivered to the Remarkable platform? And no, you don't get anything Gary, you've clearly demonstrated that time and time again.

It's a .11 release. I don't know anyone who actually creates products who would consider it anything but a minor bugfix release and be so disappointed by it that they'd take the time to create a rant video. Then again I don't want to turn the rM into a hypertext machine for the 10 people who want that, or a full-blown rich text word processor with a keyboard instead of a simple, focused FreeWrite typewriter replacement so what do I know? One negative video about a product surrounded by 100 positive ones, for a glitchy product but serviceable product like the SN doesn't scream "objectivity" to me. But I'm glad you have a product you love. We all do. Thanks to you I bought one. It's working great as a field photography notetaker for me, with its small size, etc.. I can easily work around the glitches.

"One negative video about a product surrounded by 100 positive ones, for a glitchy product but serviceable product like the SN doesn't scream "objectivity" to me." For almost every device I create 2 videos, Unboxing and In-Depth review. So, that is the baseline. For the A6X2 I have made: 1. Unboxing (initial impressions, commenting on not being a fan of the FW2) 2. In-Depth Review (covering quite a few cons, including the FW2, placement of the SD Card, and the impracticality of the Crystal version disassembly and assembly process and design) 3. A6X vs A6X2 (comparing features, and commenting again on the FW2 feel and me being a fan of the mechanical cover holder over magnetic cover holders) 4. A6X2 Top 5 features 5. A6X2 Worst 5 Things 6. A6X2 as a keyboard writer in the real world (concluding that while some things are a bit improved, A6X2 is still so bad as a keyboard writer that it shouldn't be considered for such use) 7. Update 2.14 / 3.16 (dedicating 25% of the entire video runtime to the disappearing strokes issue, and concluding that it is still present and should be improved further, that they really should get their version numbering synchronized between platforms, and a bit more) So no, not "100 positive videos and 1 negative". 7 videos in total, of which 2 are standard device coverage, 2 are entirely negative, 1 is focusing on the positives, and 2 are mixed. Just doing some basic fact checking here, for those interested in facts.

@@MyDeepGuide OK. You're objective, but are known to have a favorite device (see your 3 YTers videos). I'm obviously being figurative with "100 videos" comment. I'm glad you have a favorite. But a rant video for one bug? That's just not objective

Livescribe - myScript never worked. I don't believe you

Why would I? I am covering Remarkable platform as I cover every other platform that I have regular access to, so I don't see why would I stop covering them. I disagree that it is a waste of time, as it offers a very objective and clear cut view at what the company is doing and the direction it is taking. How about this, I continue making the videos, and since you know and accept that Remarkable updates are so pathetic that they are not worth even covering, then you don't watch the video, and you watch the ones you like :) I get it that this might not be for you, but that doesn't mean other users are not interested, or that they find it useful.

I fully agree.

I used the type folio in a meeting yesterday and I have to say that my text was very sharp and very crisp. Not a trace of bad rendering. And it still looks as good today. I have also just tried to reconstruct the strange behaviour of formatted text (bullet points etc). Maybe it's because I'm already running the latest beta version, but my text doesn't lose any formatting. None. Not even the bullet points. I ask you next time to really try out the software, discover it, before you make your judgement.

The version I was testing was not a beta of 3.12, it was the final release of 3.11, so performance of beta 3.12 is completely irrelevant to this release. I have tested it as you've seen, and this is how it behaves. I didn't invent anything, I simply tried to use it the way I would like to use it for my needs, and this was the result. Do you think that I made some kind of a user error? If so, can you please point it out, because it might be possible.

Tbh, no update is better than lackluster buggy update like this one is. I'd much rather see Remarkable take a longer period of time between updates, but that we see much more thoughtful and meaningful empowerment of the platform and the vision that the Remarkable 2 stood for initially. And of course, properly bug tested...

This functionality is so simple, that I can confidently say that it has nothing to do with the platform constraints, and absolutely everything with developers simply not doing a good job. Technically speaking, it knows how to select the text, maintain the selection and move it to the proper place, and this is what they focused on when testing. However, the formatting issues are rule sets that have to be established for the software to know what to do in which situation, and this has clearly either not been done, or has been done very badly. These are very amateurish mistakes that are regularly seen in beginners, and I did expect them from my students while learning, but not in their final delivery. As for a paid professional to actually deliver something like this as finished work, and for a big company development department to let it be released, it's troublesome.

I thought that I was doing something wrong, and often my touch gestures can get unnoticed when recording in the lightbox (I'm not sure why, but whenever I record in the box, my touch gestures, on all devices are way more imprecise. Either the light or much more likely it is the unnatural angle from which I interact with the device that causes it). Either way, I was completely unable to exit with the swipe down, but I thought it was me, and not the device no longer being able to do it. I'll have to check it in a more controlled setting and maybe even on my RM 1 before updating and then after, to verify. Thanks for sharing your views.

That is very sad to hear, that people are forced to update to versions they might not want to run...

It compiled with no errors!!!! Job done, push it!

"reMarkable have their priorities currently set incorrectly and it's a shame." - yes, this is the thing that makes it painful to experience updates like these... especially after the whole 2.x line of updates which were so good and meaningful. Not perfect, but they had a couple that were really awesome and have helped the platform become even more of a focused, yet effective tool. It's sad to see the change in the direction...

I thought they wanted to be like Apple but have never been good enough to actually deliver...?

On what planet is a .11 release a "major" update? Who called it that?

Remarkable did by giving it a new sub-version iteration "11" and not "10.1". If my memory serves me right, way back in the older days, they did have a 1.5, 1.5.1 and 1.5.2 (maybe more, don't remember exactly), but this is basically what the version numbers are for, to communicate to the users what type of an update it is. Bigger features and functionalities iterate the sub-version, small updates, iterate the sub-sub-version, and huge platform changes iterate the version number.

@@MyDeepGuide I don't think subversions should result in rants. If it were 4.x and it had such a paucity of content, then I'd understand the reaction more. This is just a personal taste thing bleeding in, like when one says "people buy this because of the marketing"

Do you think that what was released to the public in 3.11 (not the complexity of it, just the completeness of it) was on a passable level? If you were the development lead, and this is what the team delivered as the Release Candidate version to you to test it out, would you let it be released and would you consider that your team did a good job?

Thank you very much for the kindness and support! :)

I sold my Remarkable 1 that I'd originally gotten on Kickstarter - it was essentially BNIB, I'd even kept the plastic film for the screen, and got my money back. I found it an equally inconsistent experience. I will admit I was hoping the second generation would be better - I have a grandfathered account with unlimited cloud storage so it'd be nice for them to eventually sell a model that's actually good.. they are so design forward but now can't also keep up with their competition

@@sh0 I moved to Boox because the rM1 sync was extremely buggy. But then they got funding - after you gave up on them - and fixed the sync. And when the rM2 came out I bought it and the performance, synch and other features were added. including the elegant, excellent keyboard. Since then they've sold over 1M devices. I recommend you take a second look. I too enjoy the grandfathered account. It's pretty great. It just works

I sold my Remarkable 1 TB, and got the one with the Tandam OLED nano texture glass e-paper display. With the tumble roll marker, and the Markable 4 processor (M4), it’s looking Remarkable. Only if this was real…

you're wrong, they are laughing, because the reMarkable is a super easy to use device - many customers are looking exactly for that. I own both, RM2 and BOOX Note Air 3C, and the BOOX is a nightmare in terms of handling, I've decided to use the BOOX because of some special features I currently need (PDF annotations and local files without cloud sync). But on every single day I do miss the easy-of-use of the RM2 (just try to read an eBook incl. your annotations on your mobile device while on the road or the unified storage system of RM2, one place for PDFS, eBooks AND your notebooks - both features are not available on BOOX to just name a few)

Well, how would they know what they are missing, if they aren't even aware of what else is out there? It's the same story with Kindle users. There are still a lot of people out there, who simply think that E-ink = Kindle, and that the expectations and capabilities of these devices should match the limited capability of an e-ink screen.

I would have too if it wasn't INSANELY priced in EU.

Thank you, and why not. It would show in a very real way what the new focus and direction of the company might be.

Interesting that the beta has the same bugs. I can excuse 3.11 having one feature and bug fixes. However it does seem egregious that 3.11 has this bug with bullet formatting, being specifically advertised as improved, being broken. And Voya had 3.11.5 so this was not just the first first crack by the software engineers. As a software engineer I know it takes a team to ship a quality product. I speculate the entire team is embarrassed and some are in a delusional state like everything's good or are afraid perhaps afraid that their work isn't good enough. And the ultimate issue I speculate the team isn't working well together. Perhaps they are all remote? Perhaps no one at remarkable wants to show off their work to their colleagues in person? Perhaps the culture is toxic in some small way? A bug I reported too remarkable around file naming and renaming seems to have been fixed. Is confused at what a finger versus what a pencil can and should do and so far as moving the insert cursor when naming files. It's unfortunate because not everyone has a pencil and they are making it difficult for those who do not by removing the ability to set your insert cursor in previous versions. I contacted support and they said this is how we want it to be. I don't trust that message was genuine however and like Voya I am feeling mistrustful of their development.

I do know some insider things about the work culture inside of Remarkable development team, and while I will not share them publicly, I can say that the first-hand accounts don't reflect what I would describe as a healthy team environment, and work will always reflect that in some way or another. As for a difference between pen and touch input, well the first place I'd look at would be the accuracy of their averaging calculations for the touch input interpretation. Math being off would be the most likely suspect. On the other hand, If they have separate systems for touch and pen that do not converge into just a singular input interpretation of type 1 or 2 that is being fed into a common input logic, but instead have a mess of conditions and logic for touch that is separate from conditions and logic for the pen, than that could also cause different behaviour between two different input methods. But the formatting issues are simply incomplete logic implementation and testing, nothing else, which is an embarrassing thing to see, honestly.

I think they are doing great marketing for...eink. About 3,5 years ago I was seduced and just about to buy the RM2, but I finally bought the Note Air.

I have never used a tablet as buggy as my Onyx Boox tablets (3 of them). Two of them bricked themselves after a simple firmware update