`--bitrate 128 --no-phase-inv` 128 because 96 is where it starts to be transparent for me and I'd like to have a little bit of safety margin --no-phase-inv because from what I've read I definitely don't want out of phase sounds; if it decides it not worthy to encode sound location the it'd better be just normal mono instead of out of phase mono. Opus encoder will probably not use this trick at this quality level anyway, but this option shouldn't hurt either way...
Then it is worth using --no-phase-inv? Disables the use of phase inversion for intensity stereo. Because that exchanges some stereo quality for a higher quality mono down mix, which they say is useful when you encode stereo audio that will probably become mono after decoding. It reminds me of the discussion of stereo vs. joint stereo vs. intensity stereo.
Last post by Case -
Am I hallucinating, or did you dramatically edit the post #4? It used to say that when a file is playing it can't be copied and now it says something entirely different. My reply was for the original post, not the later edit.
Last post by Peter -
1. Playlist creation will fail if called from an illegal context - wrong thread, called from a global callback, fb2k shutdown in progress. If your code already ensures running in main thread, an assert check should be sufficient. You cannot call any methods that alter the state of playback, playlist, etc from a global callback - such as playlist/playback/etc callback - because the method by itself dispatches callbacks, which cannot be done recursively. 2. Returned value from playlist_insert_items is the index of the first inserted track - or pfc_infinite on failure (conditions above or an autoplaylist that refuses insertions). 3. u* methods used to be relevant when Win9X was still supported - Win9X users got a different build of the DLL which called non-Unicode APIs. By now there's no difference. These methods are mainly retained for backwards compatibility. Though you can sometimes reduce the size of your component by calling them instead of converting UTF-8 to wchar_t by yourself.
Last post by Case -
I mistakenly thought the feature requires a recent version (1.4) but copying the playing file seems to have (always) worked. Just tested with a truly ancient version 1.1.5. Are you using some weird input plugins or other components that lock the file?
I have a theoretical question. I have an amplifier, 2x50W, and two speakers, 2x70W - for example. Usual way of connecting them would be from amp plus to speaker plus, minus to minus, both speakers. If one speaker is connected in reverse order, amp plus to speaker minus, speakers would be in reverse phase, and sound would be very bad. But, what happens if both speakers are connected reversed, from amp plus to speaker minus? My understanding is that speakers would still play as they should, because signal is alternating current. But my colleagues say that they won't play as good as they should, especially at higher loudness level, arguing that speakers would make stronger inward motion than outward which could be blocked by magnet and/or something in speaker construction. I find that hard to believe, but again, I don't know much about speaker construction, and how much the membrane is moving forward, outward, and how much back, inward. Also, that situation is supposedly worse for compression boxes vs bass-reflex boxes. How much of that is true? Can somebody explain that, give examples, links...? I've tried searching for that, but web searches gave various situations, and 99,99% are reverse phase situations.