Production Pyra photos/videos/thoughts thread


Actually, the REAL old school way to copy and paste is:
ctrl + ins = copy
shift + ins = paste
Which, using those shoulder buttons and the insert (ins) small button in the right game pad is REALLY easy to do.

So, mapping any other button to 'paste' would be pretty darn redundant.

There are definitely people that prefer middle clicking over [ctrl]+v/[ins] on the desktop and don't consider it redundant. I don't see why those people would change that opinion on the pyra(Is a shoulder button that much more convenient than a fullsize [ctrl]-button?). IMHO it's situational and maybe a matter of taste - but not redundant, as it's clicking once+pressing 2 buttons vs just clicking once.
 
Yes, the 4G capable units have an accelerometer in them, I think. I don't think it literally comes as part of the pls8 mobile chipset thoguh, that apparently gives us cellular access and GPS/GLONASS. There must be another chip that gives us barometer and accelerometers. I was looking to check if they're six axis or merely three.

Edit: Yes, it's six axis. We also have along with the barometer a relative hygrometer which I didn't know about before. Now the unit can tell better if you're outdoors or indoors, at least where you have some kind of air conditioning.
 
Last edited:
I don't see why those people would change that opinion on the pyra(Is a shoulder button that much more convenient than a fullsize [ctrl]-button?). IMHO it's situational and maybe a matter of taste - but not redundant, as it's clicking once+pressing 2 buttons vs just clicking once.
But the ctrl button is under the finger or your hand assuming your holding the unit and thumb-typing. If you've got it on the desk and typing you need to find the physical ctrl key and use that with the insert key so it costs the same as ctrl+c or +v and more than middle click if we've got one, but if you're thumbtyping (I did all of my typing on my Pandora handheld for reference), then it just requires you to select one of two buttons with your fingers and to find the smaller insert key in the gaming controls and chord them together. I'm certainly glad that I learned about ctrl+ and shift+ins because that actually works across bash and my browser, so I don't have the problem of constantly bringing up the firefox inspector when I'm trying to copy text out of my browser.
 
For copy, paste I find autocutsel particularly useful. It is in Debian repos. On my laptop autocutsel is configured to keep primary selection and clipboard in sync, so there is no need for Ctrl+C, anything selected (primary buffer) is automatically copied to clipboard, and can be pasted with either shift+insert or Ctrl(+shift)+v
 
Ditnt though about my Upcoming Pyra Video the last week, so maybe its time to ask for some suggestions:

- What should i show, and how to say it?
- I cant show mame as i dont had this on my Pandora, just PS1, Gameboy Gameboy Collor, SNES NES N64 DS GBA and some of the Sega Stuff including Genesis (Megadrive)

- I will not make an Unboxing Video, just Pictures as its a bit divicult whit my Setup to show things bigger than the Pyra..

Its One Take as i dont know how to cut Movies..

Oh and as i plan to make this Video when i have some time, its may be that the Pyra then got allready some use bevor, so its not just out of its box
 
You can try cutting/joining video on pyra using handbrake. ffmpeg is another option but it will require command line or scripts.
 
If i would try to cutt or to join, the Video would take another 2 Months (tm)..
I think One Take is a bit more autenthic, i dont want to make this on a uber provessional Base ^^

Some Books as a Kickstand, this time a bit more preparation on my English, and hopefully more fluid speek should work out..
 
  • Like
Reactions: rSl
For copy, paste I find autocutsel particularly useful. It is in Debian repos. On my laptop autocutsel is configured to keep primary selection and clipboard in sync, so there is no need for Ctrl+C, anything selected (primary buffer) is automatically copied to clipboard, and can be pasted with either shift+insert or Ctrl(+shift)+v

Oddly enough, it's that very behaviour that leads me to tend to prefer Ctrl+C & Ctrl+V to using the middle mouse button for copy and paste. I have a tendency to want to paste over a selection, which is somewhat difficult if the act of selecting the text I want to replace pushes it into the clipboard buffer.

-Neelix
 
Ditnt though about my Upcoming Pyra Video the last week, so maybe its time to ask for some suggestions:

- What should i show, and how to say it?
- I cant show mame as i dont had this on my Pandora, just PS1, Gameboy Gameboy Collor, SNES NES N64 DS GBA and some of the Sega Stuff including Genesis (Megadrive)

- I will not make an Unboxing Video, just Pictures as its a bit divicult whit my Setup to show things bigger than the Pyra..

Its One Take as i dont know how to cut Movies..

Oh and as i plan to make this Video when i have some time, its may be that the Pyra then got allready some use bevor, so its not just out of its box
One take is fine, your conversational english is easily good enough for that. And as you say, it does seem more authentic sometimes to do that, like Dave on EEVBlog usually just waffles on.

I don't know how soon a lot of these emulators will be released. I mean, davashah's already got retroarch running, as as long as you can get that set up the same on your system a lot of this stuff should just come as part of that. I don't know if N64 and even PS1 will work out of the box, so if you could report on that to set my expectations that'd be nice. I'll have to put my thinking cap on if you want suggestions on actual games to try out, since beyond F-Zero on N64 and maybe Mario Kart: Super Circuit on GBA I don't really have go-to games on a lot of those systems.
 
Since the devs are still working on the battery control from a software side and the bits of the SoC that offload computation still being worked on, it is hard to say what battery life -will- be. What it is right now is ~8+ hours sitting on the desk with the screen on and about 2-3 hours doing stuff that pegs the CPU. Frankly we need a way to easily purposely throttle the CPU on a per-app basis because 150+ fps on some games like Hostile Takeover is a waste of cycles. A lot of programs are built to consume all resources available to boost frame rate - which doesn't help battery life. But, what it is now could also be seen as 'worst case' where the CPU is doing 3D, MPEG, etc instead of offloading those to specialized circuits. The software side for the 3D is in the works, I have played around with it a bit - so great progress is ongoing!
Thanks for the detailed and informative response! Makes a lot of sense. Some partners and I did an early Android handset back in 2008, and I watched the battery tuning from the sidelines (I was upper layers of Android, Input Methods, bundled apps, signaling for push). I know it's challenging, especially for some of the use cases this group will throw at it. As a volunteer effort, it's impressive, and I don't presume too much expressing appreciation on everyone's part for the great work by the developers. I'm really looking forward to getting my hands on mine. and hacking as I can.
 
Since the devs are still working on the battery control from a software side and the bits of the SoC that offload computation still being worked on, it is hard to say what battery life -will- be. What it is right now is ~8+ hours sitting on the desk with the screen on and about 2-3 hours doing stuff that pegs the CPU. Frankly we need a way to easily purposely throttle the CPU on a per-app basis because 150+ fps on some games like Hostile Takeover is a waste of cycles. A lot of programs are built to consume all resources available to boost frame rate - which doesn't help battery life. But, what it is now could also be seen as 'worst case' where the CPU is doing 3D, MPEG, etc instead of offloading those to specialized circuits. The software side for the 3D is in the works, I have played around with it a bit - so great progress is ongoing!
I know next to nothing, so the following could be wrong but...

Frankly we need a way to easily purposely throttle the CPU on a per-app basis because 150+ fps on some games like Hostile Takeover is a waste of cycles.


I believe this is already doable, via the linux kernel with cgexec. And pretty easy to, I think, as I was able to use it to do ram limiting, and I don't know jack.

I would bet, once the Pyra is fully "out", we will get a nice cgexec cpu:cpulimit guide on the best setup, how much cpu popular programs need, etc. Then its just a mstter of changing .desktop files exec setting, aliasing, whatever.

Sent from my H3123 using Tapatalk
 
Last edited:
Since the devs are still working on the battery control from a software side and the bits of the SoC that offload computation still being worked on, it is hard to say what battery life -will- be. What it is right now is ~8+ hours sitting on the desk with the screen on and about 2-3 hours doing stuff that pegs the CPU. Frankly we need a way to easily purposely throttle the CPU on a per-app basis because 150+ fps on some games like Hostile Takeover is a waste of cycles. A lot of programs are built to consume all resources available to boost frame rate - which doesn't help battery life. But, what it is now could also be seen as 'worst case' where the CPU is doing 3D, MPEG, etc instead of offloading those to specialized circuits. The software side for the 3D is in the works, I have played around with it a bit - so great progress is ongoing!
Throttling the cpu on a per-app basis is indeed possible now.

Start reading from this post: https://pyra-handheld.com/boards/threads/preparing-for-a-prototype.76956/page-33#post-1667599

tl;dr Use cgroups. Set up is a 'bit finicky', but the capability is built in to Linux.
 
Back
Top