Avidemux Forum

Quote from: eumagga0x2a on September 17, 2020, 04:10:45 pmDecoding support is now available in the latest Avidemux nightly

Quote from: eumagga0x2a on September 16, 2020, 02:00:57 pmfor a limited variety of Ut Video formats added

Thanks. I was about to say it doesn't work before I realized RGB/RGBA formats aren't supported yet. The playback of YUV variants (OpenGL for me, as usual, quadcore Intel+Nvidia) is as following:

ULY0 (1080p 50fps 420) plays fine
ULY2 (1080p 50fps 422) plays fine
ULY4 (1080p 50fps 444) stutters
UQY2 (1080p 50fps 422 10-bit) plays fine
UMH2 (1080p 50fps 422) plays fine
UMH4 (1080p 50fps 444) plays fine

any kind of 4K, obviously, stutters heavily, as it does in any other program/player anyway

Frankly, I wasn't even aware of the UMxx formats, apparently, they are a newer "T2" version of codec or something. I searched the web for a couple hours but still couldn't figure out how to encode them through FFmpeg. So I used Adobe Media Encoder to make those.
The UQxx are 10-bit versions, I was able to make the 422 10-bit UQY2 in VirtualDub2, but when I tried 420, it produced a seemingly ok file which however no player or program would decode/play as if decoder was missing, so I couldn't test that.

Personally, I generally use UtVideo for lossless 8-bit RGB/RGBA renders, and Quicktime-wrapped DNX/Prores/Cineform for everything else intraframe.
Although performance-wise, I gotta admit 8-bit UtVideo 420/422 is very competitive with Prores/DNX at up to 1080p while being truly lossless (aside from chroma subsampling).

Will playback of ULxx (RGB/RGBA) flavors of UtVideo be possible to add to Avidemux in future?

Quote from: Urik on September 17, 2020, 03:47:07 pmIf you need to trim those files, I can suggest VirtualDub2 project.

Decoding support is now available in the latest Avidemux nightly (currently 200917 from https://avidemux.org/nightly/win64/), can be edited in copy mode and saved as MKV (and also as AVI).

Encoding support should be easy to add.

edit: Playback of 720p@25fps was AFAIR real-time on my 8 years old dual-core. At 4k and 60fps this might have been different.

Quote from: Videograbber on September 16, 2020, 09:11:34 amAs you know Ut Video became one of the most important (if not the most important) capture codec

This is an unusual statement. Though I've used UT Video as an intermediary / lossless archival format for various renders/logos/intros for many years, and it is a great free codec, in my experience from articles and conversations online, it's far from being widely used in professional or hobbyist production, where DNX/Prores is mostly used, ( and to lesser extent, Cineform).

If you need to trim those files, I can suggest VirtualDub2 project. Although the playback depends on CPU performance, and likely won't be realtime (at least not for me on a quad-core Intel), it is able to trim and save UT Video in .avi container with "export > stream copy" option.
However, sadly, joining files doesn't work in stream copy mode there.

Quote from: TheJazzHole on September 16, 2020, 05:53:43 pmEl televisor es un Samsung UN40D5500

--> Modelo 2012.

Gracias!

Hola,

Quote from: eumagga0x2a on September 16, 2020, 05:37:02 pm¿Podría especificar el modelo exacto del televisor?

El televisor es un Samsung UN40D5500

Quote from: eumagga0x2a on September 16, 2020, 05:37:02 pmDebe deshabilitar "Usar la configuración avanzada" en el cuadro de diálogo de configuración de x264. Esto permite elegir el "Preajuste", "Ajuste" y el "Perfil" (pruebe "high" y "main" si "high" no funciona).

Lo probaré

Quote from: eumagga0x2a on September 16, 2020, 05:37:02 pmParece que algunas versiones x264 producen transmisiones H.264 que funcionan perfectamente en casi todas partes excepto en una pequeña minoría de dispositivos. Los x264 más antiguos están bien al igual que los más nuevos (la versión en la compilación MinGW es más antigua que en la compilación VC++ que no funciona, mientras que la versión en mi sistema es más nueva que la de VC++)

Entendido
Muchas gracias!

Hola,

Quote from: TheJazzHole on September 16, 2020, 03:16:24 pmEntiendo que es un "problema" con el codificador x264 y con la próxima versión estable de avidemux estará solucionado, es correcto?

No necesariamente. Es complicado. Parece que algunas versiones x264 producen transmisiones H.264 que funcionan perfectamente en casi todas partes excepto en una pequeña minoría de dispositivos. Los x264 más antiguos están bien al igual que los más nuevos (la versión en la compilación MinGW es más antigua que en la compilación VC++ que no funciona, mientras que la versión en mi sistema es más nueva que la de VC++).

¿Podría especificar el modelo exacto del televisor?

Quote from: TheJazzHole on September 16, 2020, 03:16:24 pmNo he podido encontrar la opción para poder hacer una prueba con eso.

Debe deshabilitar "Usar la configuración avanzada" en el cuadro de diálogo de configuración de x264. Esto permite elegir el "Preajuste", "Ajuste" y el "Perfil" (pruebe "high" y "main" si "high" no funciona).

De nada :-)

Hola,

Quote from: eumagga0x2a on September 15, 2020, 10:48:51 pm¿Podría intentar una compilación Avidemux 2.7.7 por MinGW? --> https://avidemux.org/nightly/win64/
Estas compilaciones usan una versión x264 diferente.

Probé la conversión con la versión avidemux_2.7.7 r200903_win64.exe y funciono perfectamente!
Entiendo que es un "problema" con el codificador x264 y con la próxima versión estable de avidemux estará solucionado, es correcto?

Quote from: eumagga0x2a on September 15, 2020, 10:48:51 pmPor favor, inténtelo, pero sinceramente, no creo que ayude.

No he podido encontrar la opción para poder hacer una prueba con eso.

Muchas gracias!

Quote from: Videograbber on September 16, 2020, 09:11:34 amAs you know Ut Video became one of the most important (if not the most important) capture codec

Never heard about this codec.

Quote from: Videograbber on September 16, 2020, 09:11:34 amCan you add proper UTVIDEO decoding in the next release of Avidemux?

Decoding support for a limited variety of Ut Video formats added: [1], [2], [3], [4]. You might want to try a future nightly build.

Muxing support is provided by MKV and AVI muxers (for now, copy mode only, but adding an encoder should not be difficult).

Hello!

As you know Ut Video became one of the most important (if not the most important) capture codec, however Avidemux can not handle / decode it, which often results in black preview window.

Can you add proper UTVIDEO decoding in the next release of Avidemux?

Thank you!

I understand that the 1960s ASCII terminal environment in Unix gave birth to the argv[] approach, and it still rules to this day in defining shell interaction with apps. However, because OS X defined a message passing and object oriented layer above their Unix kernel, the Mac intends to offer a "richer" and "improved" app environment. Regardless of any feelings for the two environments, I certainly understand the Mac's environment is different from the more "pure" derivatives of Unix shells like Linux, FreeBSD, and Windows.

Although the shell message passing approach provides a way for an app to be designed to prevent multiple instances, I wouldn't say its purpose was primarily aimed at avoiding the launching multiple instances of applications. Many Mac apps do open multiple instances: TextEdit, Preview, QuickTime Player, and VLC are just a few examples. I wouldn't say those apps are "working around" an OS X mechanism designed to prevent that behavior. Instead, I would say they are implementing the normal, desired behavior of a Mac app that is intended to open an instance of itself when asked to open a file from the Finder.

I hope QFileOpenEvent turns out to be compatible with the current Avidemux app approach. If it is, it doesn't look like too much code is needed. If it isn't, I understand why this can't be easily addressed.

Thanks for the tip regarding using Terminal to open multiple instances.

I hear you when you express doubts about Avidemux's future on the Mac platform. I know the changes Apple has made--and plans to make--is making it harder and harder to have common source code to serve the ever increasing differences in the platforms.

Very sorry to hear about your 2016 MacBook Pro. From what I've heard, the keyboard on that model is destine to fail. I know some folks got a whole new upper case along with a new keyboard when they took advantage of the Apple extended replacement program after having troubles with their butterfly keyboards. If you have a key already not working well, maybe you should try and get Apple to replace it while you still can. I'm sure all the other users of Mac Avidemux would appreciate knowing you'd be more likely to be able to support it for a little longer into the uncertain future.

Thanks for all your replies and consideration. And if you can't get your keyboard replaced, here's hoping you got the one good butterfly keyboard that lasts!