Weird and annoying automatic zoom during playback





Hello everybody.

Have been using Premiere for a while now but never had this happening before. Got a footage from client shot on GH5 ( never worked before with footage from this camera). Project is 1080, footage is 4k. I drop it on timeline and scale to 50% and it looks as it should but once playback starts or i move playhead with mouse it automatically scales back to 4k. Playback stops and it scales back to 1080. See the attached video. Any advice would be highly appreciated! Thank you.
For GH5 footage on the current release of PrPro, you need to right-click in the Program Monitor, and in the options that pop up, select 'High Playback Quality'.

Neil
It seems to be fixed as of tonight. Thanks to everyone for their support on this issue@!

(fix took approximately four months to implement)




[View solution in original post](/t5/Discussions/TCL-Roku-device-suddenly-does-not-render-Prime-in-4K-HDR/m-p/614077#M11370) OK I figured it out, I'll put it here to help someone in the future. The key point is the pitch scale change changes the currently PLAYING sound, so it must be used after the play command.


I now have this:



```
soundSamplePlayer.play('success01')
soundSamplePlayer.voice_set_pitch_scale(0,1.2)

```

Basically in `voice_set_pitch_scale(0,1.2)` the first argument (which I have as `0`) is the index of the sound that's playing, so in my case, the first (and only) sound.


The second argument, which I'm testing with `1.2` is the scale change, so 20% higher in this case.


I hope that helps someone in the future. this is an update to wowza player to help prevent playback issues in browsers that are changing their autoplay policies. more information can be found in our release notes.

<https://www.wowza.com/docs/latest-wowza-player-updates> there is no update from you for a period, assuming this is not an issue any more.

hence we are closing this topic. if need further support, please open a new one.

thanks

what’s the frame rate? have you try boost the system to performance mode to try? fox and fx-1 are carried in 4k uhd sporadically on ch 1498 and 1499 for
sporting events. maybe your tivo is seeing that and switching to it
automatically. i know there were issues with the guide not showing
events properly, and it's being worked on for th... turns out what solved the problem was setting the cullpadding property using the setcullpadding() property.

per [the docs](https://photonstorm.github.io/phaser3-docs/phaser.tilemaps.tilemaplayer.html):

when a camera culls the tiles in this layer it does so using its view into the world, building up a rectangle inside which the tiles must exist or they will be culled. sometim… hi yassineh,

here is our test result of no\_render cases:

[gstreamer]

gst-launch-1.0 nvcamerasrc num-buffers=300 ! ‘video/x-raw(memory:nvmm),width=1920,height=1080’ ! fakesink

ram 1486/3995mb (lfb 355x4mb) cpu [6%,0%,9%,6%]@1734 emc 4%@1600 avp 66%@12 nvdec 192 msenc 192 gr3d 0%@998 edp limit 173… right: that's because your play:1 speakers do not support airplay. the support article below may help.
https://www.sonos.com/en-gb/airplay You are using position:absolute; Don't, it usually leads to endless problems.



Even if you had a real need to use it, why are you placing things at left 1400px!!!



This is right on the edge of the average monitor - how large is your monitor? I work with my browser open at a width of about 1000-1200px (note I didn't mention the size of my monitor). The main reason people have big monitors is so they can have two windows open next to each other, not so that they can run a browser window open at 2800px wide.



I suggest you start by looking at ordinary websites and studying the css. you'll discover that many sites use a wrapper div with a fixed width, while others use a wrapper div with a percentage width and a max-width, to prevent ending up with a huge long line of text 2500px long for example. Then they center the div using margin:auto. That gets the content in the middle of the page on the vast majority of screens, and browser viewports.



Don't lay out a screen using position:absolute. You are not painting pretty pictures on a screen, you should be using html and css to control the layout and check how the layout looks every time, by resizing the window looking for errors.



Also, a contact form needs the input boxes to be part of a <form>, so you'll have to read up on how they work. And a form needs an action, so you'll have to learn a bit about scripting, probably php. Reason: `s` starts at 1 and is incremented on first call, but is never reset. On seconds and subsequent calls `s` no longer starts at 1. `s` is actually unnecessary as you can use the loop counter `i` instead.



A more conventional way to do this sort of thing would be with a single function, not embedded in an object, and to control the detailed behaviour by passing parameter(s).



```
function loadGame(level){
	var values;
	switch(level){
		case 'hard':
			values: [7,8,9],
		break;
		case 'normal':
			values: [4,5,6],
		break;
		default://easy
			values: [1,2,3],
	}
	for(i=0;i<=this.values.length;i++){
		document.getElementById('n'+i).innerHTML=this.values[i];
	}
}
```


```
<div id="n0"></div>
	<div id="n1"></div>
	<div id="n2"></div>
	<input type="button" value="easy" onClick="loadGame('easy')"/>
	<input type="button" value="normal" onClick="loadGame('normal')"/>
	<input type="button" value="hard" onClick="loadGame('hard')"/>
```

**Airshow**