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 Case -
I'm definitely against the idea of loop settings altering cached track lengths. But I suppose changing default length for tracks that have no length is a valid reason to update cached data.
Adding something like this to open() is at least one way to achieve info update.
try { auto mio = metadb_io_v2::get(); auto mdb = metadb::get(); service_ptr_t<metadb_hint_list> hint_list = mio->create_hint_list(); metadb_hint_list_v3::ptr hint_list_v3; hint_list_v3 ^= hint_list; metadb_handle_ptr track; mdb->handle_create(track, make_playable_location(p_path, 0)); if (track.is_valid()) { file_info_impl info; get_info(info, p_abort); // info.set_length(new_length); // you can force a new length here if get_info() doesn't return the value you want hint_list_v3->add_hint_forced(track, info, get_file_stats(p_abort), true); fb2k::inMainThread([=] {hint_list->on_done(); }); } } catch (pfc::exception) {}
I've resolved this issue by slightly dragging the window size in windowed mode but this seems to happen when Auto-scale Columns with Window Size is enabled and then resizing the window to a specific place where the Playlist Viewer displays a scrollbar to the right. I cannot reproduce it now but at the time of this event, this was what caused it.
Finally got this beauty to work & loving it. Just 1 thing i need help with... I have it setup to use just play/pause & next. I was able to reduce the empty space on the right side but can't seem to do the same on the left side. Any help would be so much appreciated,
By default the left side is where album art picture is placed. If you don't need it, you can turn it off and move buttons to the left by setting their X coordinate respectively (starting from 0 for very left side).
I fail to see why a reported track length would depend on input decoder settings.
A chiptune is stored as a computer program. My plugin emulates the computer. For chiptunes not tagged with playback length, the plugin provides configuration option to set some fixed playback time.
I'm afraid my experiences with 0.4.0.0 are the same as wojak--there is no visible X-axis labelling either by frequency or note. This is using Foobar 2.1 x64 2023-11-22 preview, Windows x64 at 125% scale on a 1920X1080 display resolution. The images attached here show what I am seeing, and what my settings are. The plugin was added as a regular tabbed fixed UI element using Layout Editing Mode, like all my stuff is.
A new "irritation" of this version is the inablity to change band no. or frequency range quickly by using the delete or backspace key in the setting boxes and typing the desired value--now you must use the small up/down arrow buttons for any change made.
Yes, the inability to manually put desired values into boxes is a shortcoming for me too. Plus if we are abe to make the X-axis values visible, it would be nice to also have the ability to see the valuses directly on the bars (which is impossible for me now) - ex. if I put "notes" on the X-axis I would see the notes on the bottom and when going on the actual bars with the mouse I would see the frequencies corresponding with those notes.