Recommended Posts

RAM: 1 GB

Processor: ARM Cortex-A8 OMAP3630 1 GHz

GPU: PowerVR SGX 530

It was right there in the first post...

Dayum, I must be going blind or something... thanks :laugh:

Yeap, I apparently missed it... thanks :pinch:

It looks very good. Too bad it didn't come out earlier, horrible timing.

Agreed, I love the design and the UI, both.

Hardware looks amazingly good. Software looks boring. nothing different from what other phone manufactures are doing (samsung et al) and could be a skin for android if i didnt know any better. The swipe feature is the softwares only saving grace. If this ran WP7 mango it would be almost perfect.

As opposed to boring rectangular tiles on the side of a screen?

Except for the fact that they're not boring plain tiles and most update with a good chunk of usefull information, even more so with Mango in a few months. Nothing is more boring than a grid of icons that just take up screen space with no other job than to start an app.

I'll take a grid of icons over some giant, flat squares with a boring white icon in the middle any day.

Which just tells me you have no clue about Live tiles and how they work or what they can do, even more so with mango.

Looks stylish and simple to use...but do we need Meego :)

[RANT] And did we really need to post all the videos and screenhots of every page on the webpage in the first post? Simple links would have sufficed! [/RANT]

smugcat.jpg

It's never late for open sauce.

It's still pointless to release a phone running MeeGo knowing that Nokia is switching to WP7. It's nice and all, but likely to remain the only Nokia MeeGo phone. What earthly reason do customers have to buy this instead of one of the many Android phones or WP7 devices or iOS devices? 'It's open source!' is not a valid reason for 99.9% of all potential customers.

The problem is that these Meego phones are going to be priced at the higher end. Look at the N8 as an example, I can buy it for 500euros right now but it's been out how long? The E7, 600euros. I mean these aren't even new last I checked. I'm sure this N9 will sell for 800euros brand new without some expensive contract which, in the end, you'll still have to pay 300-400euros for the phone.

Android got to where it is off of lower end cheap phones that are given away for free or basically for free with a contract.

It's still pointless to release a phone running MeeGo knowing that Nokia is switching to WP7. It's nice and all, but likely to remain the only Nokia MeeGo phone. What earthly reason do customers have to buy this instead of one of the many Android phones or WP7 devices or iOS devices? 'It's open source!' is not a valid reason for 99.9% of all potential customers.

But 'brand' is of value to a lot of customers, especially the hardcore Nokia ones, and on the other end of the spectrum, the un-knowledgeable ones that just replace the phone when they release the 'next' version of it. That's why I'm so confused by this move, a lot of people will buy this one and then expect something similar from N10 and I can bet any amount of money it'll happen and it'll be running MeeGo. As I said, horrible timing, they should have had this ready last year, then test it and definitely decide to go either full on Windows Phone, or invest in MeeGo (which has potential, especially with backing from someone like Nokia). I just don't see how they plan on supporting both, seems actually worse than ditching both Symbian and MeeGo and going WP only.

As it stands now, even if there are no new Symbian phones announced, they need to take care of the userbase (maintain the Ovi Store and services etc), but by introducing this one, they are actually obliged to take care of MeeGo, all the while working on introducing WP. So, right now they're basically having three OS's. Next year they'll maybe have just two. No wonder their CTO left the company, there's still no clear roadmap imo. Either they're flip flopping to see which one does better, or they're just doing the people who expected MeeGo a favor and releasing this one as 'hello and goodbye.'

But 'brand' is of value to a lot of customers, especially the hardcore Nokia ones, and on the other end of the spectrum, the un-knowledgeable ones that just replace the phone when they release the 'next' version of it. That's why I'm so confused by this move, a lot of people will buy this one and then expect something similar from N10 and I can bet any amount of money it'll happen and it'll be running MeeGo. As I said, horrible timing, they should have had this ready last year, then test it and definitely decide to go either full on Windows Phone, or invest in MeeGo (which has potential, especially with backing from someone like Nokia). I just don't see how they plan on supporting both, seems actually worse than ditching both Symbian and MeeGo and going WP only.

As it stands now, even if there are no new Symbian phones announced, they need to take care of the userbase (maintain the Ovi Store and services etc), but by introducing this one, they are actually obliged to take care of MeeGo, all the while working on introducing WP. So, right now they're basically having three OS's. Next year they'll maybe have just two. No wonder their CTO left the company, there's still no clear roadmap imo. Either they're flip flopping to see which one does better, or they're just doing the people who expected MeeGo a favor and releasing this one as 'hello and goodbye.'

Not really though since MS handles taking care of WP and the OS compared to Nokia having to take care of it like they do with Symbian and MeeGo. The only problem is the integrated Ovi Store that they're probably going to run, but I don't see it as a big problem in the end. Symbian and Meego development isn't exactly burning hot right now. All they really need to think about is hardware when it comes to WP and any services they add in, like their Maps for example, so that those work. That's really it, no more than any other WP OEM.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • LosslessCut 3.69 by Razvan Serea LosslessCut aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. The main feature is lossless trimming and cutting of video and audio files, which is great for saving space by rough-cutting your large video files taken from a video camera, GoPro, drone, etc. It lets you quickly extract the good parts from your videos and discard many gigabytes of data without doing a slow re-encode and thereby losing quality. Or you can add a music or subtitle track to your video without needing to encode. Everything is extremely fast because it does an almost direct data copy, fueled by the awesome FFmpeg which does all the grunt work. Features Lossless cutting of most video and audio formats Losslessly cut out parts of video/audio (for cutting away commercials etc.) Losslessly rearrange the order of video/audio segments Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. from the same camera) Lossless stream editing: Combine arbitrary tracks from multiple files (ex. add music or subtitle track to a video file) Losslessly extract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files) Batch view for fast multi-file workflow Remux into any compatible output format Take full-resolution snapshots from videos in JPEG/PNG format Manual input of cutpoint times Apply a per-file timecode offset (and auto load timecode from file) Change rotation/orientation metadata in videos View technical data about all streams Timeline zoom and frame/keyframe jumping for accurate cutting around keyframes Saves per project cut segments to project file View FFmpeg last command log so you can modify and re-run recent commands on the command line Undo/redo Give labels to cut segments View segment details, export/import cut segments as CSV Import segments from: MP4/MKV chapters, Text file, YouTube, CSV, CUE, XML (DaVinci, Final Cut Pro) Video thumbnails and audio waveform Edit file metadata and per-stream metadata Edit per-stream disposition Cut with chapter marks Annotate segments with tags View subtitles Example lossless use cases Cut out commercials from a recorded TV show (and re-format from TS to MP4) Remove audio tracks from a file Extract music track from a video and cut it to your needs Add music to a video (or replace existing audio track) Combine audio and video tracks from separate recordings Include an external subtitle into a video Quickly change a H264/H265 MKV video to MOV or MP4 for playback on iPhone Import a list of cut times from other tool as a EDL (edit decision list, CSV) and run these cuts with LosslessCut Export a list of cut times as a CSV EDL and process these in another tool Quickly cut a file by its MP4/MKV chapters Quickly cut a YouTube video by its chapters (or music times from a comment) Change the language of a file's audio/subtitle tracks Attach cover art to videos Change author, title, GPS position, recording time of a video Fix rotation of a video that has the wrong orientation flag set Great for rotating phone videos that come out the wrong way without actually re-encoding the video. Loop a video / audio clip X times quickly without re-encoding LosslessCut 3.69.0 changelog: Add lossless cropping & aspect ratio override via bitstream and container metadata #643 Alow shifting tracks for each file (-itsoffset) #216 Add "decimate video" tool to filter away all non-keyframes #2111 Add Windows ARM 64 native build with native ffmpeg Move timecode out of timeline and make it copy-able #2592 #2691 #2800 #483 #2808 Upgrade Electron to latest Add new "opposing" align mode #2654 Add FFmpeg -hwaccel auto setting for hardware acceleration of certain operations Add API events export-start and export-complete Allow deleting track metadata #2819 Improve shift segments dialog #2839 Show keyboard shortcuts inside button tooltips in UI Warn if trying to cut with too few keyframes around cutpoint #516 #2780 #2756 (Linux) include app name in notification #2794 Pull latest translations Other notable changes: Advanced output directory selector #2101 #2115 #2755 increase max file name length to 250 (truncation) #2779 don't reset playback speed when using special playback modes #2889 preserve chapters when merging files that already have chapters don't merge adjacent segments in combineOverlappingSegments #2896 don't transfer segment name when filling gaps #2754 always scroll up to zoom in #2703 #2786 increase max keyframes to 10000 Don't bind ctrl/cmd+c by default (they interfer with copying text) Many other improvements and fixes Download: LosslessCut 3.69.0 | ARM64 | ~100.0 MB (Open Source) Links: LosslessCut Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Doesn't even need a UI for point 2 - use some sort of JSON/XML container - because MOST users won't even bother.
    • Legit concern or publicity stunt considering this is the first time I'm hearing the name?
  • Recent Achievements

    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      487
    2. 2
      PsYcHoKiLLa
      263
    3. 3
      Skyfrog
      85
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!