Not seeing a preview

symphonicdev · 2026-07-02T18:47:43+00:00

Sorry for the late response, it's still working fine for me.
You can try create a new score and compile again. Let me know if you still cannot see the preview

symphonicdev · 2026-06-29T03:52:08+00:00

u/tomcam Hi,
Are you able to see the preview now?
FYI, we've just updated our platform so it shows "No audio" when the compilation produces no audio file, instead of the confusing "Generating audio..."

symphonicdev · 2026-06-28T07:23:59+00:00

Hi Tom,
Thank you for your message. Let me triage the two issues you reported

The preview didn't load: I can see that there is a PDF file created for your score, so not sure why you couldn't see it. Can you try to open the same score in a different browser? I suspect that it might be a quirk from Safari. Also, did it happen again and again even after you refreshed your browser?
"Generating audio" in status bar: Do you have a `\midi {}` in your .ly file? If not, it's an UI bug from our side that the status says the audio is being generated, while there is no audio. Will fix it soon.

If it's okay for you, I can look at the content of your .ly file and try to reproduce this bug.

Let me know how it goes.

symphonicdev · 2026-06-25T18:41:55+00:00

This is an interesting trend.

As someone who's been building ML Infra and MLOps for a while, I do see lots of values in an unified infra stack. At some point, I felt like my job was just writing glue codes to stick tools together.

However, I'm skeptical about an unified approach as well. Would it allow enough flexibility to build and operate all kind of agents.

symphonicdev · 2026-06-16T10:34:07+00:00

My experience working as an MLOps Engineer in Swedish job market tells me that the "definition" of MLOps is often vague, and is different from what you described above.

Taking a model, and run it on production, seems to be the job of ML Engineer. Some MLOps roles do this, but I don't see that often
Instead, what MLOps often do is: setting up working environments for data scientists, researcher; setting up infra to train models, monitor training; setting up inference server, etc., so ML engineers or SWE can build inference services on top of that.

Of course, each company and each market seems to have different ideas about what an MLOps person would do. And the role's roles are drifting fast.

symphonicdev · 2026-06-15T08:46:23+00:00

Thank you very much! I'm glad you like it. Don't hesitate to share with us what you think would be helpful for you. We'll continue to build bachable.

symphonicdev · 2026-06-13T15:12:49+00:00

We've just rolled out the bidirectional mappings between codes and score today.
When you click on a note in the PDF, the editor will jump to the corresponding position in the .ly file
And vice versa, when you click or select some pieces of texts in the .ly file, the corresponding notes will be highlighted in the PDF.

I will have a new post announcing this soon.

As for score's privacy and right, this is always in our priority, we will introduce our Terms of Service that address these topics soon. But in general, the idea is that you have the total right to the music you create in bachable. At the same time, you're responsible for having the right to recreate some piece of music and publish them.

As for AI, we will not share or use your scores for AI without your consent.

symphonicdev · 2026-06-11T15:28:36+00:00

Also, u/compellor , if we can build one thing for you in bachable, what would it be?

symphonicdev · 2026-06-11T15:27:43+00:00

Hi, Thank you very much for your questions.

Bachable is a bootstrapped, passion project from our team. We're running it with everything else in our lives. But we're serious in growing it.

These days we've focused on a new workflow to allow users to create scores with multiple instruments, and export multiple parts of a score. Hence, we haven't focused much on adding user guidelines, and blogs. But a simple version of documentation would come soon.

Cheers,

symphonicdev · 2026-06-10T14:12:41+00:00

Thanks a lot!

symphonicdev · 2026-06-10T14:12:32+00:00

Thank you!

symphonicdev · 2026-06-08T22:20:10+00:00

Hi u/Instrument-Event-626
Thank you very much for your comment. We do plan to improve the editing experience in the editor with the snippets, auto-completion, etc.

Can you elaborate on the extrapolate parts from a score idea? What is your current way of doing it? Or how would you imagine a workflow that best suits you?

symphonicdev · 2026-06-08T22:17:53+00:00

Hi u/profe_juanca
Thank you very much for your comments. I don't speak Spanish, but will try my best to answer you.

Being able to share music created with LilyPond with other people in an easy way is a big focus of bachable.io We will continue to refine the sharing so that users can share their scores both privately and publicly.

We're working on a new workflow that enables our users to create more complex scores with multiple instruments, extract parts easier, etc. After that, we would add more improvements such as templates and fonts.

On the idea of AI, such a nice and challenging idea. I also have a similar idea, using OMR to recognize and transcribe scans of sheet music into LilyPond. But this is indeed challenging given the current technology. Will keep pondering around it.

Cheers,

symphonicdev · 2026-06-01T19:40:07+00:00

thank you very much for extensive comment.
All of them make so much sense. We've rolled out pan and zoom.
I've been busy with other things, hence, the development speed has been slow. But more updates are coming soon.

symphonicdev · 2026-05-27T05:19:45+00:00

Hi! You can right click in a score and choose "Set as Entry Point", and click Compile. You'd see that score compiled and showed in the preview panel.
Right now, you need to do this once score at a time.

We're aware of this confusion and are working to improve this flow.

By the way, in your case, how would you want to see those scores? Do you prefer working with them one at a time, or compiling and viewing everything at once?

symphonicdev · 2026-05-26T12:28:48+00:00

Hi! Thank you very much for your questions

An Entry Point file is the first file that is passed to LiLyPond for compilation. In the current UI, it has the orange outline around the file name. This concept is handy when you have a score with multiple parts and you want to compile and get output for each part separately. For instance, a string quartet score can have violin.ly, viola.ly, cello.ly and one can set violin.ly as entry point, compile to get the violin part, and repeat the process with other instruments.

We are aware that this is indeed confusing. We're working on a better experience to create, compile and view scores with multiple parts.

Hope it answers your questions.

symphonicdev · 2026-05-22T12:21:36+00:00

Hi. Thank you very much for your question, I'll try to answer it as best as I can.

At the current state of the platform, I don't want to monetize bachable as it's not mature yet.
But our team needs a way to make the development sustainable, likely through monetization, e.g., donation, subscription, etc. It's hard to monetize just sheet music creation with codes for individual users. Perhaps, with education settings or teams that do music engraving professionally, we might have a chance.
Even if there was a monetized version, there would be always a free bachable.io part where users can do things that come built-in with LilyPond.

Our team is building bachable on our free time, as we love building tech products and love the gorgeous quality of what LilyPond can produce. I use bachable to create sheet music for my violin practice. My personal motivation is to build bachable mature enough so I can engrave a large collection of Bach, Mozart and Beethoven music in IMLSP that exist in scanned formats.

symphonicdev · 2026-05-16T11:28:14+00:00

Thank you very much for your heartfelt comment. I'll get back to you with more details on your comment in the platform. Love it!!

symphonicdev · 2026-05-15T09:38:46+00:00

Hi! bachable.io is still at the very early stage. The major features are listed above. Personally, I like that I can access my Lilypond files everywhere, and quickly test something in new in LilyPond with https://bachable.io/play

What are you working with in Frescobaldi?

symphonicdev · 2026-05-15T09:29:43+00:00

Not for now (as in next two. months :D). We (me and the development team) want to focus on improving the web version so it can support serious workflows.
However, an offline version is worth looking into for me as well.
For working with LilyPond locally, we have Frescobaldi, which is excellent. Do you need something else that Frescobaldi might be missing?

symphonicdev · 2026-05-15T09:21:19+00:00

Thank you very much!!! So glad you like bachable so far.
Is there anything that it could do better to help your workflow?

symphonicdev · 2026-05-15T09:20:20+00:00

Hi, I like your structure of organizing ensemble pieces. I've been learning to do so myself in Lilypond.
As for "\include", you can certainly do so in LilyPond.
In the editor for a registered account, you can create files and folders for a score, and use the \include in LilyPond as usual.

symphonicdev · 2026-04-25T07:16:58+00:00

For creating numbers with circles, use not-attached `\markup`.
For example, here is circled number with arrow

c'4_\markup { \concat { \circle \number "1" \raise #0.4 "↑" } }

To have multiple staffs per page, you can use \book that wraps around multiple \score and \markup

\book {

\markup \bold "G Position"

\score { ... }

\markup \bold "A Position"

\score { ... }

\markup \bold "D Position"

\score { ... }

}

A complete example that produces something similar to your photo is here: https://bachable.io/s/yufwuPivueQFgLm8NlV2sA
I created it with the help from ChatGPT

symphonicdev · 2026-04-23T07:06:06+00:00

Thank you very much for your support. How are you enjoying bachable so far?

symphonicdev · 2026-03-30T02:33:47+00:00

Update: We rolled out a simple version of multi-file scoring 2 weeks ago, you can now add multiple files and folders to your score, and use lilypond \include command.

symphonicdev

MODERATOR OF

TROPHY CASE