itch.io

Unfortunately, the current program system only supports English display, so it is not possible to do so. (This may be improved in the next-generation version.)

But there is no problem with translating the manual. (Currently, there are only English and Japanese versions available.)

https://doc1oo.github.io/LovelyComposerDocs/en/index.html

Thank you for your kind offer!

Basically, when creating new song data in this program, you should clear the existing song data or use an unused number. However, sample songs are also stored in a separate folder (LC_SAMPLE_xxx), so there's no need to worry about losing the original sample songs.

You can also directly manipulate song data files on the OS. The folder where the data is saved can be opened by pressing the "Open Data Folder" button in the program.

Also, You can add a new folder by copying and renaming the LC_USER folder in that location (making a duplicate of LC_USER with a different name). The folder list in the program will be updated after the program is restarted.

Note: General folders are not displayed in the app's folder list. Only folders that contain the "lcdata.jsonl" file, such as the LC_USER folder, are displayed in the list.

Hello, thanks for the happy words and questions.

Normally, "Random Compose" will set scale to "Magical Scale1". This is is to make the melody not dissonant with the chords generated random chord.

But if you click the button with pressing SHIFT key, it will generate a melody based on the scale you have selected, without changing the scale. (And it will also not change the tempo or delete other parts that are not selected.)

And If you right-click on "Random Compose", then melody will not generate.

Also "Random Melody" button will only generate a melody based on the scale for the selected part.

Can you do what you want with these?

Thanks, but there is currently no English version. If there is a remake in the future, I think an English version will be available at that time.

There is also some hope for automatic translation technologies such as Google Lens.

Thank you for your message, Kris! We are so happy!

We're trying to make a good tool that's fun, but we won't know if it's good for users until we get feedback. It's encouraging to see users who actually love our software.

Thanks

This is the first case I've heard of, but you can initialize the settings by deleting or renaming the

C:\Users\Your user name\Documents\LovelyComposer

folder, so please try that and see if the problem is resolved.

Hello, thank you for the request. It's easy to understand. And it's cool that the explanation images are also drawn using pixel art. :)

Since it is not designed with a design theme in mind, it is difficult to freely and easily customize everything on the app. So please don't expect much customizability.

Some enthusiastic power users can take the freedom into their own hands, but can't expect official support.

The function on the app is changing color themes only. But now, in ver.1.3.4, users can now access and edit material images and source code directly, so I think they can customize all UI parts if they want to.

For example, how to rewrite a character image is as follows.  :)

https://1oogames.itch.io/lovely-composer/devlog/616009/134-released-now-runs-pyt...

Thank you, we trying to keep the options as few as possible for beginners(Just like we prepared separate pro modes), but right now there are still too many options. I feel that smartphones and simple UI go well together and It will become more friendlier.

Since the user interface is different from PC, it will not be ported as it is. But mobile devices are attractive, so the next generation Lovely Composer will probably try support Android.

I just got a reply from McAfee saying it was a false positive and was whitelisted. So don't worry, it's actually harmless.

The latest version 1.3.3 is currently receiving 15/70 malware judgments on VirusTotal. However, we believe it is a false positive and are working on it.

We have asked Microsoft/Avast/AVG/Symantec/Malwarebytes to handle false positives. As a result of the each expert's inspection was a false positive of all. And the false detection was deleted. 

A few days ago, also we've sent a request to McAfee to fix false positives, but haven't received a response yet. 

It's actually harmless, but if you're still worried, use 1.3.2 as it's less likely to be suspected.

----

The virus false positive problem is a common problem with modern programs, and it is difficult for home-developed software to adequately deal with it.

Especially now when using Python3.10 and the Nuitka --onefile setting it's even happening with simplest "Hello world" programs and it's out of control. And it is difficult to support all minor anti-virus software and those that do not have a corresponding contact point.

But many users are worried about it, so we're considering recreating apps in a different development environment.

We're really aiming to sell on Steam as well, but it's been two years since then. We would still like to do so, but hopefully it may be a few months away... Thanks.

Thank you for the easy-to-understand image explanation, I understand your request well. I am thinking of such a feature myself. (However, I have a feeling that there will be cases where the values actually entered even  using the straight line tool will not be equidistant.)

Lately I've been thinking that to make everything work very well, the system would need to be overhauled. Then it might be a long further.

After thinking about it again,  I'm still responsible for the problem with our software, so I've let myself report it first to Malwarebytes. I'm sorry if I betray your feelings. Thank you.

Thank you, we appreciate it!

I didn't know about antivirus software called MalwareBytes and Rogue Killer. It may be the result of those software reacting instead of Windows Defender.

Lovely Composer is developed in Python and includes a Python script as an official add-on sample. The add-on's source code is completely public and harmless, and Lovely Composer does not run external scripts without explicit user interaction. However, such aspects cannot be detected by the mechanical processing of anti-virus software, and will only warn that there is a possibility of suspicious behavior.

It seems that in modern software development, the more convenient and powerful functions are added for users, the more antiviruses are suspected of being abused. This tendency seems to be particularly strong in tools rather than simple games.

Basically, I'm a game developer, so I'm confused due to my lack of experience, but I want to prevent false positives as much as possible. Some of the options are expensive and may not be available with cheaper software. It may be necessary to remove the function once implemented depending on the case. It looks like it will take some trial and error for a while.

We understand that the new feature of 1.3.3 may be causing false positives in some antiviruses. But two days ago, we asking Microsoft to inspect the file of the LovelyComposer 1.3.3 and the false positives in Windows Defender have been fixed.  ( It looks a little suspicious to automatic machine judgment, but it actually means that there is no problem when examined accurately by an expert. I'm thinking about how to deal with the false positive problem. )

If you're using Windows defender, I don't know why you're still having issues, but try updating your definition files to the latest version. You can simply update from the security settings or have them try the steps in the image.

If that doesn't work, or if you are using another antivirus, please let us know its name and, if possible, the version of the definition file.

Thank you for your report.

 I think it's a good suggestion. It's true that we didn't use mouse wheel scrolling much. It would be useful for part selection, etc.

As a little worry point, switching between instrument and chord entry also involves part changes.  Also there are multiple numbers on the editor, so the plus and minus keys alone may not directly suggest speed changes.

I am glad you suggested the improvements.

Ah, previous my comment is a kind of joke...   Apple don't gift their special hardware to app developers.  They always demand a lot of money to the developers of the applications.  (So fewer apps for Mac)

The image means it has been checked for viruses with 56 different antivirus programs and detected problems with 2 of them. This means that 54 antivirus software considers this software safe. Rather, we believe that this result indicates a high probability of false positives. (Because if it really contains a virus, it should be detected by more/most of antivirus programs.)

The number of these detections changes due to the daily update of the virus definition file, and there are times when it becomes 0 in ver.1.2.7, and there are times when even ver.1.1.4 is slightly misdetected.

Lovely Composer uses Microsoft Defender to check for viruses with the latest virus definition file and confirms that it has not been detected before every uploading.

Also, Lovely Composer is written in Python, but there seems to be a common problem that applications converted from Python scripts to standalone executables are prone to false positives. This will not be mitigated unless the current application is completely rewritten in a different way, but even then there is no guarantee that false positives will not occur.

No matter how to build any application, there is no sure-fire way to avoid false virus detections. Some functions, such as the ability to open twitter etc. in the browser, are likely to be suspected by antiviruses, but I don't want to remove them for that reason.

We hope that users of our software will understand the above. Thanks.

Wow, we didn't expect it to work on Windows 7, but I'm glad it works! Thank you for your report!

I fixed it on 1.3.1! Also I didn't use JPEG or webp for the time being, so I removed it once. Thank you!

TIFF images were not actually used in the Lovely Composer program, and I had a little concerns about the licensing of libtiff distribution, so I manually removed them from the distribution package.

It worked without errors in the development environment (Ubuntu), but that's probably because libtiff was already installed in the OS side in the development environment, and libtiff was actually being referenced somewhere.

We would like to either make libtiff really unrequired, or include it in the package. Thanks for the accurate reporting of the problem!

I'm really happy to hear that. (We know it is difficult to write and it takes a little courage.)

Software developers often question themselves whether what they have created is meaningful and whether they should continue working on it.

If the existence of this tool leads to confidence in your music and makes your life more enjoyable, then I think that is one of the reasons why this software exists. Thank you!

It's later than I expected, but we added a new scale types in 1.3.0-Beta.  Please check it out! :)

Thank you for your advice!

https://1oogames.itch.io/lovely-composer/devlog/462045/130-beta-relased-nearly-m...

Hello, I'm glad you enjoyed it. Sorry if my answer is wrong.

First, layering the same instrument at the same pitch sounds like a bit increase the volume of one note.

This is because two exactly the same waveform are played with exactly the same timing, so you only hear one sound. It doesn't sound like the volume has doubled either.　

If you want to get a loud volume, it is more effective to raise the volume value from ”C" to "F" than layering sounds.

Also, if you want to make it sound like two sounds are playing, it is good to change the insturument and layer it. It is also effective to change the pitch by octave.

Thank you, I'm glad you like it!

As for scales, they are not difficult to add. So we would like to add them. (The current number of scales is due to my lack of musical knowledge.)

Thank you, we are working on Steam support, but it has been delayed and will take some more time.

DLsite is one of the web sites where LovelyComposer can be purchased overseas. Is it possible to access it?

https://www.dlsite.com/home/work/=/product_id/RJ331224.html/?locale=en_US

(Are there a lot of people in the world who can't buy on itch.io?)

No. Currently LovelyComposer don't have MIDI Import feature.

I'm glad you enjoyed it! Thank you so much!

I just scanned the zip file and the unzipped file, but no virus was detected. It was scanned by Windows 11 Pro with the virus definition file (1.371.895.0) created this morning and the latest virus definition file (1.371.920).

No changes have been made to the uploaded Lovely Composer ver.1.2.6 file from the beginning.

The virus definition file seems to be updated at least once or twice a day. If possible, it would be more helpful if you could tell us the version of Windows and the version of the virus definition file when the virus was detected.

     Windows Security> Virus & threat protection> Protection updates

Thank you for reporting!

A part of this function was implemented in ver.1.2.6. :)

Regarding the chord display in the proposed parenthesis, I did not implement it this time because there may be multiple chord names and the specification becomes complicated.

Thank you!

We have determined that this is due to a false positive and not due to the presence of an infectious virus. (This is due to the results of VirusTotal and the similar detection in the newly generated exe.)

And now, the latest Windows security definition files(1.371.550.0) do not detect malware.

From ver.1.2.6 or earlier, VirusTotal results seem to give false positive results to a small number of minor anti virus software.

If false positives occur frequently, I think it is necessary to change the specifications as a countermeasure(*), but I think that it will be a change that reduces the convenience of the user, so I would like to see the situation for a while.

* One file of exe, online help function, detection of user document folder location and file generation, etc. may be suspected factors.

The version 1.2.6 zip file has been republished.

Temporarily unpublish 1.2.6 for windows until the cause is known.

I confirmed that the virus was detected by "config.exe", as a result of scanning with the latest version of the virus definition file (1.371.503.0) of Windows Security (Defender), 

There is a possibility of false detection (*), but I would like to investigate the cause.

Thank you for reporting!

(*)  It wasn't detected by "lovely_composer.exe" which is basically made in the same way on my environment.

* To be exact, it has dropped from $ 4.99 to $ 4. I'm sorry I made a mistake.

Thank you for your thought good feature suggestions! We want to make it a good tool for learners.

We want to realize it in the not too distant future.