@ED
When I said loading data, then mentioned video , I meant loading the video up into the app for minor video editing(ie loading data as opposed to streaming it), ie not playing videos. I do make videos on youtube and it would be handy to have something to make minor edits with on the road..
I'm not sure you know how video editing works... it doesn't load the video you're editing into RAM, heck, that would be horrible!
As you might know, I'm doing video editing as my main job and I've got projects with video clips of more than 100GB... if it would load everything into RAM first, it would take AGES to load a project (and I'd need about 500GB RAM in my system as well).
Videos are made for editing / streaming, which means they have an index.
If your video editing software requests to go to 3:01min in the video, it doesn't LOAD the video up until then, it just jumps there in the file (so it would load about 10 - 20 MB, depending on the video compression and how much it buffers)
The eMMC is probably more than 3 times faster than what you need here.
But it's not just that, it's everytime it reads the emmc, there is that little hit speed wise. If you have an app that makes lots of regular reads, that adds up ,.
Nope, not at all. The time the program needs to request the files, process the data, etc. is probably 5 - 10 times higher than the loading time of the files, the eMMC also needs to seek there.
That's one of the reasons reading a lot of tiny files from an eMMC (or any other storage) is a lot slower than reading big files.
So you won't even get close to the eMMC Bus limit we have right now in most cases (if ever).
Also as I mentioned if you play games that like to load next stage data regularly , it can be a little taxing. etc etc.
I can't think of any game where that difference (probably around 40MB/s) would be noticeable, unless they're very badly coded (or way too heavy for the processor anyways).
If the next level needs to load 100MB more data, the difference is about 0,3s.
So yeah, if the next level is 500MB (half a gig!) of data, then it would take about 1,5s longer to load the level (and then only if the game is actually able to process the data in fullspeed).
How many games are there that need to load THAT much data for a level?
That sounds like "too big for the system" or horribly bad coding.
And properly coded games that have huge data often load stuff in the background. While you're running around, it already buffers the next area, so you won't even have an issue here.
I'm not sure what games you expect to run on the Pyra though
Maybe give some examples.
The process along the way has been a step by step stripping down of my wants for the Pyra.
How so? AFAIK, the eMMC speed right now (which seems to not really be an issue at all) is the only thing that comes to my mind. Everything else has been UPGRADED from the initial announcement (except for a 1080p screen, but that was NEVER a sure thing).
And eMMC speed was never even in the specs and is still faster than most mobile devices...?
2) There was the SOC selected which was another let down for me. Not the SOC I'd expect to have in an $800AUD device.
Ah, wait. The SoC was clear a LONG time before the ordering even started.
How can THAT lower the expectations AFTER ordering?
3) Then there was the emmc being just 32GB. That really put me on the razor edge.
... which initially was planned with 4GB, so a huge step up as well.
Sure a biigger emmc option would be more, as with the 30 euro extra for a 4GB RAM option, a number of people probably would have taken the option up though.
Which isn't even feasible, as you have a minimum order quantity of parts.
I cannot simply order 300x32GB eMMCs and 50x128GB eMMCs.
Okay, sure, I could, but then the price would be triple as high (as it would be less than the minimum order quantity).
Additionally, the part needs to be changed during the production run as well, which would mean higher costs as well.
4) Of course the emmc speed possibly being handicapped , is as I said, the straw that tipped me.
Yes, but you still keep insisting it's an issue even though in all use cases you told me, it doesn't even affect anything.
Unless your hobby is to copy huge files to the eMMC and back the whole day, you won't notice a difference.
You know I have backed the Pyra for a long time now, even on a number of occasions writing into tech sites to get stories written up about it. So thats to say, this isn't a hate campaign. I wrote what I wrote because it's how I feel, I know it's not going to resonate with everyone. But if anything, it gives an insight into at least my perspective.
I don't see it as a hate campaign, I just don't see why you still think the eMMC is horribly crippled when in reality, it turned out it isn't so far.
At this stage though with the MUX stripped out it seems that it's still not going to hit 192mb/s, but we shall see first.
That will never happen, as that's the theoretical maximum speed from the datasheet (meaning: no OS overhead, no filesystem, no anything).
