Thank you very much, your comment made me watch the video again, and re-living the memory did me good 👍😊

Ja, gibt es: www.komoot.de/tour/39777372 da sollte es "an der rechte Seite" eine Funktion geben um es als GPX für GPS gerät herunter zu laden. Ich bin natürlich in 2018 gefahren, ich kann in 2022 nicht sagen ob alle pfade noch "offen" oder zugänglich sind...aber das gehörte auch damals schon zum Abenteuer dazu... ;-)

But Source Playback Framerate is good? Or is the CPU low and Source Playback Framerate also Low?

Danke!! Ja, war sehr schön, sind gute errinnerungen 😊👍

I have spent a lot of time on this with Corel Support, and they seem to be unable to fix it. I dont care about the Display quality of the Source Screen, so that needs a Quality Setting that enables fluent Playback in the Editor, but Corel seem to be unable or unwilling to make that Split between the Edit Window and the Render window...which would fix the whole thing in my opinion. But "of course" also that they will/would never admit...

@@mstenvers Hi Martin, So far Corel's help has been little more than a 100% uninstall - reinstall, which I'd already done before asking for support. My workaround is to use my wife's S Book 3, i7, 32Gb RAM, which has a discreet GPU. It is able to render many times faster than my SP. Pinnacle works perfectly on it so far. You could be correct in your theory that a lower resolution for source might allow better Timeline playback. I doubt they'll add this unfortunatly.

@@ramble-on-overland as you might have seen from my Video, i have a Dual CPU 32Core AMD 6373 Workstation with a GTX1050ti, so i believe i can say also on my end Performance cannot be the Issue, Reinstalls have been completed wo any positive results...currently i edit Gopro Video´s by viewinging them in VLC and then entering the Time Manually to jump where the Marker should be set, but its far from ideal...

@@mstenvers Hi Martin, Looks like we're in for the longhaul. Please keep me updated as I will you, of any progress. Good luck.

@@ramble-on-overland would be nice, i will also let you know when i have found a fix... the reason why i had posted this is also partially the hope to find as many possible people experiencing the same, and exactly have this discussion...i know hope is the last thing to die, but still...without hope no glory ;-)

Muchas gracias!!

Dankeschön 😀👍

Hallo, vielen dank :-) !! Ich denke mal sie meinen den "Eibsee". Siehe zum Eibsee auch dieses Video: kzbin.info/www/bejne/npy0nYN3gsl9a80

Hi Charles, Pinnacle did not yet Solve or Respond, for sure if get/find a Solution i will post it here. Last week i received a quite large Studio 23 update which made me hope it would improve, but it did not solve the issue, i am now at Version 23.2.0.290.

@@mstenvers , I am on that version now as well. I am working with them in chat as we speak. The update was all the help that Level 1 tech support offered. They have now moved me to Level 2. If I make any head way I will let you know.

@@92greymare Ok, Great!! I have also reminded Pinnacle Studio again yesterday. btw. i believe it´s potentially really easy to solve this, from this Video you can see that i have a pretty performant system, and surely my 1050ti GPU is not the issue, but still this issue occurs... This "my opinion" can only be caused by Pinnacle Studio trying to inefficiently display the original format (in my case Gopro 1440P 50fps 50mbps recordings). My monitor is 1080P, so in the source window that is not even covering 20% of the screen, the software has to display/calculate a video which is 77% bigger than the full 1080P of my monitor (pixelwise). In any case it´s strange how pinnacle is "handling" that source content, especially compared to starting the same source video multiple times in VLC, Windows Media etc, it will play these fluently in paralell without any substancial CPU Loading. Eventually "Of course", you'll need the full 1440P for the rendering process, but just for viewing the video in the editor it does not need that quality or resolution. Therefore Pinnacle Programmers would be smart if they create a Quality setting for BOTH the Source AND the Timeline, as the source monitor for me only serves the purpose of setting markers and deciding what to use, for that even 360 or 480p would be more than enough as long it´s in sync with the performance of the system, and foremost enabling stutterfree editing.... Even if i want to edit color or brightness or do other modifying with the Material, i do all of that in the timeline AFTER i am ready with the Source...So long story short, quality setting for the Source and making it more CPU efficient should do the trick...."i believe..."