No, "Remove..." is not active in all cases where an image is visible. See screenshot below.
Before this upgrade, this image of the sheet music did not appear in this Karaoke screen. Now it does. Before the upgrade, even if it did appear, I could make it go away; now I can't.
As background, I have been scanning sheet music and converting them into Midi files. I scan using SmartScore and from there save as a MIDI file, then open that in QMidi to add lyrics, etc. In the same directory, I have the original image file, the MIDI file, and the .txt file with the lyrics. All these have the same file name but different extensions.
If I remove the .tif files from that directory, or if I simply rename the file, the image disappears from the background. But this was not necessary before this latest upgrade. I would rather not have to rename or move hundreds of files.
That all may be true. It doesn't change the fact that this behavior changed with the latest upgrade and was not an issue in the last version.
I'm not sure what your proposed solution is. Change the song? how? What precisely do you mean?
Every song I have in my library has three files in the same directory, as I said. A MIDI file, a .txt file, and a .tif file, all with the same file name. When I open a different MIDI file for a different song (if that's what you mean by "change the song"), then the .tif file for that song appears. This happens for every song in my library - the image changes for each song.
I hope I have been clear in stating the issue.
I appreciate the responses. It would be especially helpful if I had responses that addressed the fact that this behavior has changed with the latest upgrade.
I'm not sure I understand you; something may be lost in translation. But in response to your suggestion:
- I opened QMidi with a Karaoke window open with no song loaded.
- I set a background image. The "Remove..." command became active and did remove the image I uploaded.
So perhaps the greying out of that command has nothing to do with the change I am experiencing. Fine.
Still, when I do load a song, with or without the background image set, the sheet music for the current song still appears, as in my screen shot. The presence or absence of a "background image" as set through that menu command has no effect on that. In fact, the background image I have set is no longer visible once a song loads, but the sheet music image is.
I guess I was comparing against 2.4.1, which was the last version that I had installed, which was in Mac OS X 10.6.8 - Snow Leopard, which I have on an older machine still. The issue I raised was using QMidi 2.5 running in Mac OS X 10.11.1 - El Capitan.
So since there seems to be a problem believing what I am saying, I've attached below a screen grab from QMidi 2.4.1, running in Snow Leopard on my old Mac. I have opened exactly the same file from the same Dropbox directory as the screen grab from QMidi 2.5. It shows the Karaoke text without the image of the sheet music.
Perhaps I am not clear on when the change occurred, but this behavior is a change from a previous version, and it's very annoying. If not a bug per se, then Mixage needs to add the ability to turn that off.
While it may not be a bug, it is a change from the last version I had installed, and not a welcome change.
"Just rename the image"?!!! I would have HUNDREDS of images to rename! I would urge you consider implementing a change that would make this an option. I suspect it would be a relatively minor matter and could be a setting to turn off in the preferences pane.
Clearly whoever thought to make this change was not in touch with how users use the software. When users already have the option to set a background image, why would you ever make this automatic without the ability to turn it off?
Thanks anyway. This greatly diminishes my enthusiasm for this software.
The feature of linking a background image file was introduced in version 2.0
(May 2011), so it's not a recent change
Anyway, I understand your problem and I will add a user setting to disable
Thank you very much for understanding. I look forward to the next upgrade.
It may help to clarify that when I replaced 2.5 with 2.4.6, the problem went away for me. So while you may have introduced the change in version 2.0, for some reason it didn't affect me through 2.4.6 and until I upgraded to 2.5, even on my new Mac, which never had any of the previous versions installed (and I did not migrate the user from an old machine).