Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Last post by korth -
I saw the same error as the OP in 1.6.16 (I've already deleted the files) Tests (foo_verifier and flac -t) showed the original flac file was ok. I re-encoded as I posted above and with CUETools. Both new files played track 9 fine in foobar2000 using original CUE. foo_bitcompare and CUETools showed no difference in audio after re-encode. ?
Last post by CherylJosie -
Hi there, I'm trying to author some amateur video recordings for distribution on optical media and having some difficulty.
I don't have cash for tools. I'm running Linux on all of my computers because I don't even have cash for an operating system. I'm on fixed income and inflation is killing me.
I'm running the 22.04 LTS of Ubuntu, and for editing video I'm using KDENLive (Version 21.12.3, probably doesn't match the numbering scheme at KDENLive web site because Ubuntu verified repository renames everything per their qualification and integration procedure).
I've just recently become familiar enough with KDENLive to add key frames for motion effects and compensate video levels for low light capture of bar bands on cellphones and fixed lens Zoom Q2N. I'm really green at this stuff and making slow progress from lack of funds and mentoring.
I have an NVIDIA graphics card and I'm using that for the final render through its CUDA. I don't have integrated graphics in my AMD CPU.
The various encode options in KDENLive include what appears to be a single pass average bit rate and it uses a deprecated NVENC-H265 procedure call in the GUI profile. I don't see the parameters in this command line GUI matching what the ffmpeg command line help seems to want, and the KDENLive log file has a warning that NVENC-H265 has been deprecated. The new procedure call is H265-NVENC.
Also, since this NVENC-H265 appears to be the only profile that explicitly supports Blu-Ray encoding in this version of KDENLive, and the command line parameters in KDENLive GUI don't seem to match what ffmpeg wants, I'm thinking that these command line parameters in the GUI are possibly translated and elaborated internally by KDENLive before they are handed off to ffmpeg, but I'm not sure because I haven't attempted to intercept the command line. I could probably figure out how to do that with an alias or a temporary tweak in the KDENLive configuration eventually, if I cared, but honestly why make this harder than it needs to be?
I've considered adding a KDENLive profile for software encoding that uses H.265 and has Blu-Ray compatibility, but I'm unsure of whether these parameters pass through from the GUI unedited to ffmpeg command line, or if it is possible to launch a two-pass encode from the GUI. If anyone has a working ffmpeg command line for Blu-Ray, that would go a long way toward helping me out. I could potentially store a lossless encode from KDENLive and submit the job manually to ffmpeg if I have no other choice. The other sites I've checked are so out of date, I'm looking at questions about authoring Blu-Ray media that were answered a decade ago with, "Here, try this." "Nope, didn't work."
In any case, I'm not confident in how to manually submit jobs to ffmpeg, especially for Blu-Ray compatibility, even if I were to export a lossless edit. I have never authored optical media before. A known good workflow would be gold.
I am using tsMuxeR to generate an ISO with chapters but no menu and have barely completed a single authoring that hasn't been burned or tested yet, using the NVENC-H264 Constant Quantization (as far as I can tell from the GUI parameters) option.
tsMuxeR is another one that is deprecated and I can't figure out how to add the 32 bit libraries for the GUI support so I'm flying blind on that one too. I don't even know if the GUI supports menus in addition to chapters because I can't see the GUI and the documentation of the command line version is sparse.
I'd prefer to do a proper two-pass average bit rate encode for best quality and compatibility using the appropriate Blu-Ray options in ffmpeg, but boy, nobody does optical media on FOSS any more do they? It's slim pickings out there finding a work flow.
The ideal solution for me would be to create a profile in KDENLive that will handle it in the job queue. If there's no way to start a two-pass encode from the GUI so I have to export a lossless encode first and write a script, that's okay, provided I have good insight into what sensible parameters to use for good quality efficient encoding with Blu-Ray compatibility.
Failing that, I'll probably just burn and distribute what appears to be the working one-pass average bit rate hardware encode of H265 at the highest bit rate that fits on a single layer DVD, currently for a 2.5 hour gig that's about 22750bps, the second highest setting on the KDENLive slider. Even though KDENLive is using a deprecated NVENC-H265 function call, at least it still generates output that might work on a Blu-Ray player and maybe the bit rate is high enough to overcome limitations of a single-pass encode.
But until I burn a disc and try it, I won't know if I'm there yet. I'm running the encode again right now because the first time I ran an encode I used the H264 to test for file size using the Constant Quantization option out of ignorance. I didn't understand what these bit rate control modes meant until I stumbled across this site by a contributor to ffmpeg:
and the only way I found HydrogenAudio as a reference for help with Blu-Ray was from Doom9.
The Videohelp web site is where I found the information about tsMuxer.
I tried using devede first but although it supports menus it doesn't support chapters and it also transcodes everything to SD for a maximum file size of dual layer DVD media. That's not going to work with Blu-Ray.
I found info about DVDStyler, but their track record of installing browser toolbar hijack seems sketchy even if Wikipedia says they don't do that anymore. I don't feel like risking system damage just to try out a tool that isn't vetted well enough for the repository and may not do what I need anyway.
Then there's something I read somewhere (can't remember where) about the data stream encoded by gstreamer, mkisofs, or something where UDP? support has fallen behind and whatever version is available won't support Blu-Ray burning with the latest tools? I can't remember what I read and like everything else it's probably out of date and poorly documented.
Please, guys, this is really tough for a noob. I've already floundered for a week and I'm just barely comprehending what I'm reading. Can anyone point me to a workflow or tools that will make this a little easier?
Or am I condemned to spend thousands on Windows/Mac OS and possibly proprietary tools to burn a probably inferior disk using their canned settings, especially if it's freeware? I don't want to go down that path. I've never needed antivirus software for Ubuntu Linux desktop and never detected an infection for the past 15 years. I don't want to go back to the promiscuous computing scene. I like it quiet.
If MKV has any solutions for me, that's okay. I'm not married to any particular format. As long as I can pop the disc in a Blu-Ray player and it looks visually transparent with no stutters or artifacts, I'm good. Chapters would be nice so I can scan through the songs. Menus would be even better so I can distribute two gigs per disc on dual layer media. But honestly, a working flow is what I most need right now because on my budget I can't afford to burn a rack of Blu-Ray coasters at $1-$3 per pop just to come up empty handed and revert to DVD anyway.
Here's a copy of the existing constant quantization H.264 hardware encode that I uploaded to YouTube so you can see what I produced so far. It's mostly done in the edits but is not the final version that I have on my PC. I'm guessing that it only plays okay over streaming because YouTube transcoded it to a rate-limited version. Mediainfo doesn't seem to understand how to display peak bit rates that exceed a 1Gbps threshold. I think the peak rate on that file was 2Gbps, not 2000Kbps.
The second file in this list is another encode that I did originally before I had knowledge and tools to attempt a disc authoring for the client. I have no idea what I did. I was using an older Ubuntu and an older KDENLive when I did that one and it was one of my very first attempts at motion animation.
I'm hoping that I might eventually gain enough expertise to sell my services as a video documentarian to supplement my income. These bar band gigs I record are my raw material for the learning experience. I'm also doing some mixing on occasion. I mixed or assisted in mixing about half of the gigs I recorded, but the percentage of mixing went down with the pandemic. Just FYI that's the context of why I'm bothering to produce media of these latest gigs, that was part of the original deal long ago that I'm just now attempting to make good on because...you know...
Last post by Gus. -
Do the streams work if you remove the "s" from https, like this http:// https is a secure encrypted connection, which is probably not necessary when listening to radio streams (it's up to you). Foobar doesn't support DirectShow, that's why codec packs don't work. You can use the ffmpeg wrapper and a 32-bit build of ffmpeg in the root Foobar folder, if some formats are not internally supported: https://www.foobar2000.org/components/view/foo_input_ffmpeg
Last post by Compact Dick -
Hi, Case. Is it possible to compile foo_out_wasapis 0.6.18 for foobar2000 1.4x-1.6x? I have a foobar2000 1.6.16 installation, and 0.6.16 (for foobar2000 1.4x) has a bug: it does not stop playback after the last track in the playlist. 0.6.18 (for foobar2000 2.0x) has fixed this issue, but cannot be used with foobar2000 1.6.16.
Last post by TT -
I really like this idea and it would help and make life easier for other users too! Would be cool if @TheQwertiest would make an extra section on SMP and showcase them all. Also put them in a new .js file in the SMP docs.