foo_youtube Reply #350 – 2014-09-15 12:49:34 Quote from: mire777 on 2014-09-12 20:45:453dyd, about video , on my system if i set video quality larger than 360p, then video have interruption and problem with synchronization, even if i manualy click play. I assume that this is because internet speed.It is not necessary because of Internet speed. As for me, more or less problems have all formats except regular mp4 (i.e. mp4 with aac, it differs with video-only mp4), even if mp4 filesize is noticeably greater than filesize of video-only streams with equivalent quality. So my current recommendation regarding video - use only mp4 and disable all others through Features -> Video -> 'Formats to ignore'.About mp4 quality. Available mp4 qualities are 360p (always) and 720p (if clip has such quality). Qualities greater than 720p on Youtube presented only via video-only streams. Between 360p and 720p there are only 480p quality and it also almost always presented only via video-only streams (except rare cases with 3D videos).Also note about video & audio synchronisation. If audio stream is not seekable (e.g. m4a) then synchronisation workarounds will not work. So if video playback is important then better to disable m4a. As for me in this case is better to just disable all except ogg which now available for all clips.Quote from: carpman on 2014-09-12 21:25:30Not sure why it says "FFmpeg: no" above in settings? I have FFmpeg installed and component points to the correct place and the component can see (Found = Yes) all the required *.dlls.Which FFmpeg binaries you are using? I've checked by different ways and cannot reproduce this. If it says no, then FFmpeg will be not used. Btw, info about what are used for decoding and downloading shows in foobar console at track opening. The same is with video at its opening.Also you better select in Downloading only foobar2000. Since some time content on Youtube can appear also via https from time to time (instead of http) and ffmpeg builds on Windows can't use https.Quote from: WilB on 2014-09-14 17:17:35However, I am confused by what the following means: "AAC 256kbps is tricky, it appears even for the clips which definitely haven't such quality".Actually this concerns OGG 192kbps too. Look for example on this clip. Before the moment when audio-only qualities appeared the max audio quality within available video files there was 96-128kbps. Now there are also 192kbps ogg and 256kbps AAC. So can be two possibilities. They have original quality with audio bitrate >=256kbps. Or they transcoded available source to aac/ogg with higher bitrate. Personally I not really believe in the first variant.Quote from: WilB on 2014-09-14 17:17:35So can the bitrates displayed in properties or status bar be relied upon as being correct;Most likely you have there actual bitrate info from the decoder i.e. it is definitely correct.Quote from: WilB on 2014-09-14 17:17:35Incidentally one minor point is that in properties and status bar it always says 254kbps and not 256kbps (it is correct in youtube source history)History shows expected bitrate of the stream which may differ with the actual bitrate. More info about quality estimation are here.Quote from: WilB on 2014-09-14 17:17:35It seems that audio at 48000Hz is always preferred to 44100Hz regardless of the bitrate. Thus Opus 48000Hz 160kbps is chosen instead of M4a 44100Hz 256kbps, while I thought the bitrate might have higher priority when the Hz aren't that different.Yeah, frequency currently has first priority along with the channels count. I agree, need to do something with this.