@ivwshane said in Raspberry Pi4 released - 3 times the performance.:

When the pi3+ came out it was said that a total rewrite of the core was required (I may not have the terminology correct). Are we looking at the same type of rewrite required or will this be something akin to recompiling the code to recognize the new hardware?

^^ This is entirely new hardware. Different CPU, Different Ram, etc. And since the Recalbox crew took like a year to make it compatible with the Pi3b+, I don't expect Recalbox to work with the Pi4 for a long, LONG, LOOOOONG time.

But when 2020 or 2021 rolls around and Recalbox does finally become compatible? I'm sure it'll be amazing!

Also this claim of the Pi4 being compatible with existing Pi products? Horsecrap! None of the existing Pi3 cases will fit, none of the existing Pi3 software will work, etc.

@anderdog to my knowledge the behaviour you mention is not possible, as we have deliberatly chosen not to update ppsspp yet because a newer version hits performance. It must be something else.

@substring said in Cluster computing for better performance:

ll, emulation is mainly monothreaded

ah well it is what it is, thank you for the quick reply

@tony-amprou said in Performance Core 2 Duo:

En test sur l’émulateur de genesis même Sonic ne semble pas fluide.

Le GPU ne devrait pas faire de différence sur ce type de jeu, après tu ne donnes aucune précision sur l'émulateur utilisé. Le CPU pourrait également avoir une basse fréquence, voire être en mode "powersave" (c'est un portable ?)

@profknt Kannst testen vielleicht mit Sandisk karte ? Manche SD karten machen einfach Probleme. Versuch bitte mit Sandisk karte. Habe keine wie von dir beschriebene Probleme bei mir.

Issue solved :) check this thread https://forum.recalbox.com/topic/11249/performance-issues-after-update-rpi3/3

@srato if it's only kodi, no

@Substring
J'ai oublié des informations :
Résolution horizontal : 320
Résolution verticale : 240
Fréquence : 60
Horizontal sync pulse : 20 (défaut) à modifier certainement.
Vertical sync pulse : 7 (défaut) à modifier certainement.
Pixel clock frequency : 6400000 (défaut) à modifier certainement.
Avec ces paramètres j'ai ça qui ressort :
Horizontal scan rate : 14.78 kHz
Vertical refresh rate : 48.78 Hz

Every ROM up to the CD images I'm sure is loaded directly into ram.
And with cd based consoles, e.g. the PSX, that had a double speed CD rom, giving a theoretical maximum read speed of 300k a second.
I can't think of any memory card in existence that isn't at least ten times that speed so itd still pull data faster than the original hardware

@DAM

No it's only for PI3, method is the same on PI2 but not the same values

@DjLeChuck
Ok but I never got clear sound on any game with snes9x-next emulator is that normal ?

Das einzige, was ich dir empfehlen kann, ist das richtige global.videomode mit tvservice zu finden und einzustellen. Also, TV Auflösung benutzen, um keine Leistungsminderung zu happen. Ansonstens kannst du, soweit ich weiß, nicht mehr viel vom Pi fördern.

So is this why the changes in the RetroArch confg are never saved for the P2 bindings? Do I need to change that line in the Python script to remedy this? If so, where do I find it?

It doesn't matter overly now though - I've manually set the emulators for the few games that can get by on the other emulators (despite the save game location being different to proper "save" folders!). I've yet to decide whether to use this method or my manual config file.

I think if SNES 9x could be setup to only enable multitap when 3+ controllers are connected, it would be perfect. That and the save locations for the other emulators.

Other that that my setup is god to go. Thanks guys :-)

Super. Vielen, vielen Dank!!

Dann kann ich mir ja jetzt risikolos eine bestellen und einrichten :)

Thanks for the advice.   That will work for a global config with lower input latency.   Additional Question Using the solution you proposed, can I create unique settings for each game system (NES, SNES, Megadrive), not only a global unique config?  Can I use your solution to create  NES configuration of threaded_video=false and another configuration with SNES threaded_video=true while inheriting retroarchcustom.cfg?