I don’t understand the request, and the concepts above don’t sound right, so maybe I’m missing what you’re trying to do. You have to actually slow down the speed of the video and audio accordingly to do an actual PAL to NTSC conversion. If you were converting between different forms of NTSC, we could maybe do some inverse telecine stuff, but PAL puts things in a whole different ballpark.
Is that sufficient? The only way I’m aware to get a smoother transition between frame rates would be some kind of optical flow interpolation, but there’s a chance that could really mess up some edges. I think you have to manually edit the top line of the MLT XML project file to change fps after the fact. I don’t think it changes an existing project. The video mode can be changed from the menu bar: Settings > Video Mode >. And yes, Shotcut uses the actual 24000/1001 in the video mode rather than the decimal estimate. Same thing if going PAL to NTSC except it will discard frames as necessary. If we created a new project using the “HD 1080i 25fps” video mode and dropped the NTSC video onto the timeline, Shotcut will duplicate frames as necessary to get to 25fps. Suppose we have an NTSC video at 24000/1001 and we want to convert to PAL 25fps. I would think Shotcut already does this, unless I’m not understanding the problem or the request. Also, for me this is all in SD because they the PAL videos I have are from DVDs so I didn’t convert them to NTSC 23.976 but instead aiming for NTSC would you happen to have any knowledge in this area?
I should note that the issue with the video is not noticeable at all unless you are actually comparing the frames between a video that you converted with one that was commercially converted to PAL. That thread is a year old so I don’t know if the issue has been fixed or if it still exists. However, Dan in the thread above said there was a bug with the spinner control.
Or maybe the issue could be that more decimal points are needed to get the frames to match up perfectly. I don’t know if this is normal when converting a 25fps source to slow down to an NTSC frame rate such as 29fps or 23fps. Sometimes the frames will match up but every now and then they will be off by one or two in the converted video then match up later but then down the line be off by a frame or two again. I’ve done comparisons with video that were sold in PAL and an identical one sold in NTSC. The only issue is that the frame rate for video will vary by a frame or two every now and then. Please try it and see how it comes out for you.īased on audio, the conversion comes out right. After experimenting A LOT, I came to the speed change of 0.95902 to convert PAL to NTSC speed. So it went from just 2 decimal points to now 6. Could …ĭan kindly added more decimal points to the speed control in the Properties tab after each time I requested it. Audacity has two options for Speed control one being “Speed Multiplier” (which functions similar to Shotcut’s “Speed” control) and a second option right next to it called “Percent Change” which allows for even more specific control of the speed as it even goes into the negatives. In regards to the speed control option in Shotcut that is in the Properties menu, I was wondering if a 2nd option could be added that would be a setting based on percentage similar to Audacity.
Can "Percentage" Be Added In Properties As A 2nd Option For Speed Control? Suggestion