Skip to main content
Topic: NWC2 on Linux/Wine (Read 85607 times) previous topic - next topic

NWC2 on Linux/Wine

Godd day all, and all my best wishes for the coming new year!

I'm trying to use NWC2 on my Linux box with the Wine (non-)emulator.

I'm confronted with three curious problems:

- I can perfectly install NWC2, but it's then impossible to upgrade it (error during the copy of nwc2.exe)
- "wings" of notes shorter than quarters are replaced by bizarre vertical rectangles, but only if not beamed
- the "Tab" key is interpreted twice in dialogs (e.g. it skips two fields rather than one).

In fact, the second issue is the most important, because it prevents me from printing the music I compose.

Anybody here having any idea?

Thank you in advance...

Re: NWC2 on Linux/Wine

Reply #1
NWC2 uses the font: NWC2STDA.TTF to render musical symbols.  The flags are the only things that are mapped above 127.  I'd look for something in your configuration that is restricting character codes to 7 bits (0 to 127).  Try to view NWC2STDA with CharMap. The flags should be on the 4th line down.

I know nothing of Linux, but your upgrade problem may a lack of permission to overwrite an executable file.
Registered user since 1996

Re: NWC2 on Linux/Wine

Reply #2
Matt Johnson has posted some instructions for getting NWC running under the wine emulator in Linux plus a few downloads you might need. This has been posted on the Scriptorium - However it is a while since it was updated (2002) so I don't know how current it is.

http://nwc-scriptorium.org/helpful.html#Wine

Worth a try though I would think.

Rich.

Re: NWC2 on Linux/Wine

Reply #3
Hi Rick and Rich,

Thank you for your answers.
I've already followed Matt's instructions, but it refers to a fairly old Wine version and on NoteWorthy version 1.
What I'm trying to do is having version 2 working on a recent Wine version and whereas most of what Matt says still applies, I'm confronted with new issues.

For the font characters, I can see chars above 127 (It's fundamental for me as I'm french and use accented chars).
Can it be a problem of hardcoding ? On my Linux box, the flag for a sixteen note with stem down is character "à" (a with a grave accent). Is this encoding ok? I'm afraid the Windows codepage and the ISO 8859-15 encoding don't match exactly...

With charmap, I can see the flags encoded as follows:

8th stem up : Ç (C cedilla)
8th stem down: á (a acute)
16th stem up: É (E acute)
16th stem down: à (a grave)
32th stem up: Ñ (N tilde)
32th stem down: â (a circ)
64th stem up: Ö (O diaeresis)
64th stem down: ä (a diaeresis)

(Well, they're not all on the 4th line down but it's certainly a problem of screen resolution: I can only have 14 characters on one line)

Concerning the permissions, I own the integrality of files in my wine environment. I'll try this as root, it can be an idea, thanks.

Re: NWC2 on Linux/Wine

Reply #4
On my Linux box, the flag for a sixteen note with stem down is character "à" (a with a grave accent). Is this encoding ok? I'm afraid the Windows codepage and the ISO 8859-15 encoding don't match exactly...
No, that is not right. NWC2STDA is a symbol font and you are not getting symbol font mapping.

Quote from: my font editor (Softy) documentation
When assigning codes for the Microsoft map, these should be Unicode values. Windows remaps these when the font is installed. For Symbol fonts, which should have codes starting at 0xf020, Windows assumes that the first character corresponds to a space (code 0x20, decimal 32), then that the next 223 character codes map to (decimal) 33-255. 0xf000 is added to the input value when a glyph is mapped to a character in this context. For UGL character sets, the following mappings are made to produce the Windows ANSI character set where the Unicode value is not the same as the Windows character set value.

Mapped to   From
130 (0x82)   8218   (0x201A)   8th upflag
131 (0x83)     402   (0x0192)  16th upflag
132 (0x84)   8222   (0x201E)  32nd upflag
133 (0x85)   8230   (0x2026)  64th upflag
134 (0x86)   8224   (0x2020)
135 (0x87)   8225   (0x2021)   8th downflag
136 (0x88)     710   (0x02C6)  16th downflag
137 (0x89)   8240   (0x2030)  32nd downflag
138 (0x8A)     352   (0x0160)  64th  downflag
I don't know if any of that will help.
Worst case, you may need a custom version of the font.
Registered user since 1996

Re: NWC2 on Linux/Wine

Reply #5
No, that is not right. NWC2STDA is a symbol font and you are not getting symbol font mapping.
I don't know if any of that will help.
Worst case, you may need a custom version of the font.

Well, I don't know what you mean with "symbol" font. All I know is that a font is a map of characters into a certain encoding. Perhaps I don't have to make a parallel with alphabetic chars, but I think it's not that important.

Your idea may not be bad: making a custom font may be a good idea. It seems that there is no common place between the encoding I get and the one which exists on Windows. So I can perhaps enrich the font with a copy of the flags at the right place for ISO-8859 encoding...

Thank you for the detailed map, I'll try this, I think.

Re: NWC2 on Linux/Wine

Reply #6
Well, I don't know what you mean with "symbol" font.
What he means is that instead of "a" coming out as "a", "a" comes out as a treble clef.

For a full list of everything, download one of Lawrie Pardy's fonts and look at the documentation.

Re: NWC2 on Linux/Wine

Reply #7
What he means is that instead of "a" coming out as "a", "a" comes out as a treble clef.
No, that is not what I mean. Windows fonts have bits set in their headers to describe how to "map" a character to a glyph. Search for "symbol" on the following page to read Microsoft's terse decription:
http://www.microsoft.com/typography/OTSPEC/cmap.htm

Marlett, Wingdings and Webdings are all Windows symbol fonts.

If you google "wine" and any of the above, you will get a list of user problems with them.  
Registered user since 1996


Re: NWC2 on Linux/Wine

Reply #9
Well, on WineHQ, someone asked me an excellent question: Does the bug appear with version 1.75 ?

So I installed V1.75b and tried, and the flags appear perfectly.

Does someone have an explanation? a turnaround? something?

Re: NWC2 on Linux/Wine

Reply #10
NWC 1.75 does not use a Symbol font for notation. It also uses a significantly different scheme for displaying notation glyphs.

Re: NWC2 on Linux/Wine

Reply #11
By the way, the NWC Viewer also uses the same NWC2 symbol font, and can be freely acquired from our site (uploading it to another site is not permitted by its license).

You might also want to try creating a metafile snapshot, and then viewing it with our viewer to see if the EMF render of the font looks any better than what is seen inside NWC2:

NoteWorthy Software's Enhanced Metafile Viewer
http://ntworthy.com/nwc2/nwemfviewer.htm

Re: NWC2 on Linux/Wine

Reply #12
NWC 1.75 does not use a Symbol font for notation.
Sure it does. What is does not do is use 8bit characters. The range from 0x80 to 0x9f is a particular problem as Windows treats these differently from every other OS in the galaxy.
Registered user since 1996

Re: NWC2 on Linux/Wine

Reply #13
Just to repeat: The NWC 1.75 notation font, NWCV15, is not a Symbol font.

As a matter of trivia, the early development of NWC2 also did not use a Symbol font. The NWC2 notation font was changed to a symbol font with the release of NWC2 Private Preview 2 on 2002-10-25. Official NWC2 testers can read the announcement here. This change revealed a metafile problem with Symbol fonts in OpenOffice (see also, Copying notes from the editor). We privately released a utility, WMFixup, which could change the NWC2 font mapping in a WMF file, so it would be rendered correctly by OpenOffice. The final resolution of this issue in OpenOffice was announced here.

Re: NWC2 on Linux/Wine

Reply #14
Microsoft TrueType CmapEditor Version 0.60 (Feb 14 2002)
reports this:

[subtable2]
platformID = 3
encodingID = 0
format = 4
version = 0
0x0020, 59
0x002C, 42
0x002D, 43
  •  •  •
0x0077, 29
0x0078, 25
0x0079, 27
0x007A, 22

Quote
www.microsoft.com/typography/OTSPEC/cmap.htm
When building a symbol font for Windows, the platform ID should be 3 and the encoding ID should be 0.
So, the actual encoding is not symbol, but the encoding ID is symbol. I was hasty in calling it a symbol font.
Since it doesn't encode anything below 0x20 or above 0x7E, it probably doesn't matter.

BTW, the two topics you reference (2774.0 and 3294.0) lead to a page that says:
An Error Has Occurred!
The topic or board you are looking for appears to be either missing or off limits to you.

Registered user since 1996

 

Re: NWC2 on Linux/Wine

Reply #16
SMF doesn't return a very useful response for permission issues. We'll try to improve this.

Re: NWC2 on Linux/Wine

Reply #17
Possibly ...   
I'm still holding out for Certified Hack ...

Back to the topic at hand. The best solution for this might be for NoteWorthy to change ncw2stda.ttf and the way it uses it. Currently, replacement fonts are few (Lawrie Pardy and I have some). Everything in ncw2stda.ttf will fit in the range from 0x20 - 0x7E.

NoteWorthy Composer is an inexpensive program. It is not memory or resource hungry. (It will still run on a 486 with Win95, I think) It is a natural fit for Windows emulators running on non-Windows platforms. NWC2 might do well to make this as easy as possible.

When the time comes that more character slots are needed, the emulators may have reached a consensus on a font standard.
Registered user since 1996

Re: NWC2 on Linux/Wine

Reply #18
Ok, I think I've understood grosso modo what you speak about concerning symbol fonts.
But I don't understand really how I can have NWC2 work under Wine/Linux?
The problem may be very simple an resolved with a duplication of the glyphs at the places Wine tries to find them, no?

The problem is, I don't now anything about creating TTF fonts, nor can I figure out WHERE NWC2 hits the font map in thos cases.
Does someone know enough to build a test font that I may try?

Re: NWC2 on Linux/Wine

Reply #19
We will try to look into this further.

I have started the process of analyzing this problem. If there is a simple change in NWC2 that we can make to resolve this problem, we will do so.

Technical info:
Quote
The problem most likely starts somewhere in here:

BOOL WINAPI ExtTextOutA
http://source.winehq.org/source/dlls/gdi32/font.c#L1675

Assuming the latest WINE mostly handles Symbol fonts properly, the most probable place of problems is the IsDBCSLeadByte logic, which disregards the character "count" when doing its calculations:

BOOL WINAPI IsDBCSLeadByte
http://source.winehq.org/source/dlls/kernel32/locale.c#L1545

I'll try to get a current edition of WINE running here in the lab in the next few days to see what can be done.

Re: NWC2 on Linux/Wine

Reply #20
Thanks very much.

If I can be of any help (essentialy on Linux, I think), please don't hesitate to contact me.

Re: NWC2 on Linux/Wine

Reply #21
Thanks for the offer. Can you try the latest NWC Viewer? It is available at:

NoteWorthy Composer Viewer
http://ntworthy.com/nwc2/viewer.htm

If Wine handles Symbol encoding properly (other than its failure to respect the character count mentioned in my previous reply), then this new release of the Viewer should work better.

Re: NWC2 on Linux/Wine

Reply #22
A friend of mine just made the test. He gets the same result.

Do you want me to do some more tests with the viewer?


Re: NWC2 on Linux/Wine

Reply #24
The screen shot was taken before the release of the latest NWC Viewer (Beta 2.11), but the comment about the win32 font viewer program probably confirms a more serious Wine problem.

Old links about this problem:

Re: NWC2 on Linux/Wine

Reply #25
We have the latest NWC Viewer (Beta 2.11) running with Wine (wine-0.9.28) on Ubuntu 6.10. We get the same results with regard to the NWC2 font. I do not have anything more to report at this time.

Re: NWC2 on Linux/Wine

Reply #26
Update: I used NWC2 to create a *.emf file in Windows XP. In Ubuntu, I opened the emf file with the Enhanced Metafile Viewer using Wine. It displayed all of the NWC2 notation symbols correctly. Therefore, Wine is capable of properly rendering Symbol fonts when rendering Enhanced Metafiles. Perhaps it has problems with the handling of the Symbol font when given ANSI strings.

Re: NWC2 on Linux/Wine

Reply #27
I'm not sure about how emf files are created.  If an emf file actually uses the font, that's a completely different matter then if it's just like a jpeg.

If emf is just a bunch of pixels like a jpeg, of course it would render correctly.  You say that it has problems when given ANSI strings, which are far from a bitmap.

What happens if you create an emf file in Ubuntu and view it in Windows XP?

Re: NWC2 on Linux/Wine

Reply #28
When created by NWC2, *.emf files contain vector graphics and font data.

Re: NWC2 on Linux/Wine

Reply #29
I tried it and it won't work. NWC2 refuses to use an ANSI encoded font as its System Font. Too bad.

I did discover that system fonts are not restricted to those identified as NWC2*
That is just a filter to populate the dropdown .  You can type in: marlett
But if you type in: arial, nothing changes.
Registered user since 1996

Re: NWC2 on Linux/Wine

Reply #30
Any NWC2 notation font has to be encoded as a Symbol font.

Re: NWC2 on Linux/Wine

Reply #31
OK. The bug in Wine is basically what Rick G identified in his first reply. Wine uses the wrong code page in its Symbol encoded ANSI string conversion. The exact bug is (apparently) contained in this function:

static LPWSTR FONT_mbtowc
http://source.winehq.org/source/dlls/gdi32/font.c#L352

I suspect that this function should really include the device context in its processing. If the currently selected font is Symbol encoded, then this function should use the CP_SYMBOL code page (42) in its call to MultiByteToWideChar.

It looks like we might add a work around for this within NWC2. We have a working patch here in the lab, but I have not yet authorized it for inclusion in NWC2 Beta cycle. I will schedule some extensive regression testing on the patch...

Re: NWC2 on Linux/Wine

Reply #32
I have posted a fix to your Bugzilla report.

The changes necessary to fix Wine's "font.c" text handling are shown below:

Code: [Select · Download]
352c352
< static LPWSTR FONT_mbtowc(LPCSTR str, INT count, INT *plenW)
---
> static LPWSTR FONT_mbtowc(HDC hdc, LPCSTR str, INT count, INT *plenW)
354c354
<     UINT cp = CP_ACP;
---
>     UINT cp = (GetTextCharset(hdc) == SYMBOL_CHARSET) ? CP_SYMBOL : CP_ACP;
1025c1025
<     LPWSTR p = FONT_mbtowc(str, count, &wlen);
---
>     LPWSTR p = FONT_mbtowc(hdc, str, count, &wlen);
1134c1134
<     p = FONT_mbtowc(str, count, &wlen);
---
>     p = FONT_mbtowc(hdc, str, count, &wlen);
1651c1651
<     wstr = FONT_mbtowc(str, count, &wlen);
---
>     wstr = FONT_mbtowc(hdc, str, count, &wlen);
1686c1686
<     p = FONT_mbtowc(str, count, &wlen);
---
>     p = FONT_mbtowc(hdc, str, count, &wlen);
2298c2298
<     wstr = FONT_mbtowc(str, count, &wlen);
---
>     wstr = FONT_mbtowc(hdc, str, count, &wlen);
2436c2436
<         p = FONT_mbtowc(mbchs, len, NULL);
---
>         p = FONT_mbtowc(hdc, mbchs, len, NULL);
2742c2742
<     lpstrW = FONT_mbtowc(lpstr, count, &countW);
---
>     lpstrW = FONT_mbtowc(hdc, lpstr, count, &countW);
2794c2794
<     lpStringW = FONT_mbtowc(lpString, uCount, &uCountW);
---
>     lpStringW = FONT_mbtowc(hdc, lpString, uCount, &uCountW);
2934c2934
<     wstr = FONT_mbtowc(str, count, &wlen);
---
>     wstr = FONT_mbtowc(hdc, str, count, &wlen);

Re: NWC2 on Linux/Wine

Reply #33
I have posted a fix to your Bugzilla report.
I hope Wine users appreciate the time that fix took. If they implement it, it will probably fix the problem for every music notation program.

But why does NWC2 treat the Notation font differently from say, User 1 or Staff Bold?
An issue for a new thread ...
Registered user since 1996

Re: NWC2 on Linux/Wine

Reply #34
Thank you very much, admin.

To make sure, I've posted your patch to wine-patches@winehq.org but I suppose you've already done that.

Okay, let's concentrate on the other issues (the tab key one, for example...)

Re: NWC2 on Linux/Wine

Reply #35
Oops! I realize that I've not described this issue here.

Under Wine, when I use the tab key to navigate between fields, the cursors moves _two_ fields away instead of one.
If I use shift-tab, the same occurs (to fields before instead of one).

Very strange, no?

Re: NWC2 on Linux/Wine

Reply #36
Wine had lots of trouble with NWC's tabbed dialog boxes (which are modeless, but with special hooks to make them modal). I suspect that you won't see much improvement on that front any time soon.

Re: NWC2 on Linux/Wine

Reply #37
Oh! What a pity. Okay, it's not blocking for now.

Another problem I have is that it's impossible to me to run the upgrade installers. The copy fails on nwc2.exe.

I've opened the bug 7046 on http://bugs.winehq.org/show_bug.cgi?id=7046 for that, but I'm a bit clueless...

Re: NWC2 on Linux/Wine

Reply #38
Well, at wine-hq, they want a diff -u, but I can't create it for them...

Date: Tue, 9 Jan 2007 06:18:27 +0100
From: Marcus Meissner <meissner@suse.de>
To: wine-devel@winehq.org, me@me.org
Subject: Re: Proposed patch for "fonts.c"

(...)

> 352c352
> < static LPWSTR FONT_mbtowc(LPCSTR str, INT count, INT *plenW)
> ---
> > static LPWSTR FONT_mbtowc(HDC hdc, LPCSTR str, INT count, INT *plenW)

Please use "diff -u".

Ciao, Marcus

Re: NWC2 on Linux/Wine

Reply #39
Regarding the NWC2 installer/updater on Wine, I added the following to your Wine report:

Quote
The NWC2 install programs use NSIS CopyFiles instruction with the /SILENT directive, which calls the Windows Shell function SHFileOperation with the operation set to FO_COPY. In Windows, this operation can be used to replace an existing file. In Wine, this operation will fail when the target file exists.

The exact cause can be found here:

http://source.winehq.org/source/dlls/shell32/shlfileop.c#L1075

Code: [Select · Download]
if (SHNotifyCopyFileW(entryToCopy->szFullPath, fileDest->szFullPath, TRUE))

By setting the parameter "bFailIfExists" to true, the file copy operation will fail when the target file exists.

The "diff -u" for font.c is as follows (we will e-mail it to the Wine folks):

Code: [Select · Download]
--- orig-font.c	Mon Jan  8 07:27:52 2007
+++ font.c Mon Jan  8 07:30:55 2007
@@ -349,9 +349,9 @@
  * the number of WCHARs that have been written.  The caller should free
  * the returned LPWSTR from the process heap itself.
  */
-static LPWSTR FONT_mbtowc(LPCSTR str, INT count, INT *plenW)
+static LPWSTR FONT_mbtowc(HDC hdc, LPCSTR str, INT count, INT *plenW)
 {
-    UINT cp = CP_ACP;
+    UINT cp = (GetTextCharset(hdc) == SYMBOL_CHARSET) ? CP_SYMBOL : CP_ACP;
     INT lenW;
     LPWSTR strW;
 
@@ -1022,7 +1022,7 @@
 {
     BOOL ret = FALSE;
     INT wlen;
-    LPWSTR p = FONT_mbtowc(str, count, &wlen);
+    LPWSTR p = FONT_mbtowc(hdc, str, count, &wlen);
 
     if (p) {
  ret = GetTextExtentPoint32W( hdc, p, wlen, size );
@@ -1131,7 +1131,7 @@
        NULL == (walpDx = HeapAlloc(GetProcessHeap(), 0, count * sizeof(INT))))
        return FALSE;
     
-    p = FONT_mbtowc(str, count, &wlen);
+    p = FONT_mbtowc(hdc, str, count, &wlen);
     ret = GetTextExtentExPointW( hdc, p, wlen, maxExt, lpnFit, walpDx, size);
     if (walpDx)
     {
@@ -1648,7 +1648,7 @@
     for(i = 0; i < count; i++)
  str[i] = (BYTE)(firstChar + i);
 
-    wstr = FONT_mbtowc(str, count, &wlen);
+    wstr = FONT_mbtowc(hdc, str, count, &wlen);
 
     for(i = 0; i < wlen; i++)
     {
@@ -1683,7 +1683,7 @@
     if (flags & ETO_GLYPH_INDEX)
         return ExtTextOutW( hdc, x, y, flags, lprect, (LPCWSTR)str, count, lpDx );
 
-    p = FONT_mbtowc(str, count, &wlen);
+    p = FONT_mbtowc(hdc, str, count, &wlen);
 
     if (lpDx) {
         unsigned int i = 0, j = 0;
@@ -2295,7 +2295,7 @@
     for(i = 0; i < count; i++)
  str[i] = (BYTE)(firstChar + i);
 
-    wstr = FONT_mbtowc(str, count, &wlen);
+    wstr = FONT_mbtowc(hdc, str, count, &wlen);
 
     for(i = 0; i < wlen; i++)
     {
@@ -2433,7 +2433,7 @@
             len = 1;
             mbchs[0] = (uChar & 0xff);
         }
-        p = FONT_mbtowc(mbchs, len, NULL);
+        p = FONT_mbtowc(hdc, mbchs, len, NULL);
  c = p[0];
     } else
         c = uChar;
@@ -2739,7 +2739,7 @@
     TRACE("(%p, %s, %d, %p, 0x%x)\n",
           hdc, debugstr_an(lpstr, count), count, pgi, flags);
 
-    lpstrW = FONT_mbtowc(lpstr, count, &countW);
+    lpstrW = FONT_mbtowc(hdc, lpstr, count, &countW);
     ret = GetGlyphIndicesW(hdc, lpstrW, countW, pgi, flags);
     HeapFree(GetProcessHeap(), 0, lpstrW);
 
@@ -2791,7 +2791,7 @@
     /* both structs are equal in size */
     memcpy(&resultsW, lpResults, sizeof(resultsW));
 
-    lpStringW = FONT_mbtowc(lpString, uCount, &uCountW);
+    lpStringW = FONT_mbtowc(hdc, lpString, uCount, &uCountW);
     if(lpResults->lpOutString)
         resultsW.lpOutString = HeapAlloc(GetProcessHeap(), 0, sizeof(WCHAR)*uCountW);
 
@@ -2931,7 +2931,7 @@
     for(i = 0; i < count; i++)
         str[i] = (BYTE)(first + i);
 
-    wstr = FONT_mbtowc(str, count, &wlen);
+    wstr = FONT_mbtowc(hdc, str, count, &wlen);
 
     for (i = 0; i < wlen; i++)
     {

Re: NWC2 on Linux/Wine

Reply #40
Okay, perfect, thank you.

Do you want me to do something on this?

Re: NWC2 on Linux/Wine

Reply #41
I'm really looking forward to this NWC2 / WINE thing.
What holds me away from using Linux is actually the NWC and GigaStudio.
But I've seen, there is a Linux sampler project which makes *gig Files Avaible. With the NWC2 in WINE it would be really nice.

Thanks for all your work and keep on :)

NWC2 Beta 2.12 on Linux/Wine

Reply #42
Although we do not officially support Wine, NWC2 Beta 2.12 does include several changes that should help your situation.

  • Modify the notation font rendering to avoid a bug in Wine handling of Symbol enclosed strings

    Even though we submitted a fix for this bug, we went ahead and included changes in NWC2 that will also circumvent this bug for notation display. The bug will still appear if you use Symbol fonts in other areas of NWC2 (such as Insert, Text).

  • Add a 'retry' prompt to install and update programs, which will enable users to work around a bug in Wine file handling

    When the copy operation fails on Wine, you are now given the opportunity to retry. This enables you to manually delete the target file before continuing the update. Do not delete the file too early in the process, or the update will not even be able to start.


Beta 2.12 is available now.

Re: NWC2 on Linux/Wine

Reply #43
Good.  This means that if bersyl91 says it works fine, I might actually be able to switch to Linux if I wanted to.  This would also open up NWC2 to the Mac OS X crowd.

Now, if only we could go through a Wizard like the NWC2 Enrollment Wizard to download an installer package... ;-)

Re: NWC2 on Linux/Wine

Reply #44
Thank you NoteWorthyComposer Team. i'm not at home till march but i'm looking forward to try NWC2 in Linux.

Eventhough it's not official (which, I think, means 'no support') I think this really helps for the popularity of NWC2 which is a tool I prefer because of it's low cost and its handyness.



Re: NWC2 on Linux/Wine

Reply #45
This means that if bersyl91 says it works fine, I might actually be able to switch to Linux if I wanted to.

Well, what a responsibility! I don't know if I'm that important...

I want to thank very much the development team for it's reactivity, I'm really impressed.

And YES! I now *can* write eigths with their flags visible *and* proceed to the update.
Of course, it'll be better if Wine's bugs are fixed, but many thanks again for the workarounds.

That said, I have to mention that I haven't tested the MIDI output nor any and all NWC2's funcionnalities under Wine. So I can't assert for sure that what I think sufficient for me is enough for others. Your mileage may vary.

It's enough to build, edit and print scores of 25 pages for SATB, organ and gong (this is what I just did).

..and now, I go to bed, because here, it's 2:00AM ;-))

Re: NWC2 on Linux/Wine

Reply #46
Just a little Report.
I switched to Ubuntu 6.10 and trying to use it as a musicians/composers System. For me, the workspace and feeling is very important for composing. I very much like the linux and open source spirit and I always wanted to switch.

Now its done.
NWC2 with WINE works fast and with no complaining. But I have difficulties with my Midi Output, with Ubuntu in generally.
I thought I was pretty good with all these sequencer, sampler and midi stuff, but now it turns out that linux is a bit more complex (in positive as in negative meaning) with Midi and Audio. All these JACK and ALSA and OSS and you have to keep watch what is running because they are blocking each other...

However: I didn't heard a note out of NWC2 in Wine. That doesn't mean, it has anything to do with NWC, I think its more WINE and this ALSA/JACK thing, because I'm running JACK for my sampler and I dont think WINE has JACK Support. But I dont know if this counts for midi.. I see all the Midi-Ports (inclusive of JACK and the own Sampler Port) in NWC and its playing, but there is just no output.

Generally it works. I connected my Midi Masterkeyboard to my M-Audio Audiophile 2469 and can use NWC to grab the Input (only plain input tested, no recording). Second I can use this Master Keyboard to connect to the Sampler (in JACK) and I can hear the Soundfonts.
All in all, it looks like a softwareconnection problem. I'll see how it turns out.

All in all I just want to use NWC. I don't like the WYSIWYG Editors in whole paper-format, I like the scrolling and the complete partiture-layout without breaks as we all know it. I don't know any other program which is similar to NWC, especially in Linux. Since I have still WindowsXP Notebook I will continue to use NWC.  But WINE is WINE... its not an emulator, but It's still an additional layer with additional problems :(

Why don't you go Open Source or make at least a linux version, Noteworthys? :)

Nils, sharing his experience

Re: NWC2 on Linux/Wine

Reply #47
+1
I've got the same problem on Debian, without JACK but I never heard a note too :-(

Re: NWC2 on Linux/Wine

Reply #48
I've done it!
What I've forgot (I didn't know it and all the time I only thought about Noteworthy itself) is that WINE itself is capable of JACK.

Here is my setup:

Ubuntu 6.10 (Edgy) comes with ALSA. (that is not so important)
then JACK trough QT Jack Control Interface.
Fluidsynth through Qsynth with a random GM-Soundfont (SF2) from Hammersound.net (.com?)
then you need libjack, I used synaptics package manager for libjack0.100.0-0 and libjack0.100.0-0-dev
WINE has to be a pretty new version, I have 0.932 . With the package from ubuntu 6.10 you will get JACK Errors.
NWC2, a version after the WINE Patches (.9 or .11 ?)

now, in terminal, run winecfg and go to the audio-tab. You should get no warnings or errors, specially none about JACK.
deactive all drivers, because probably ALSA or OSS is already activated, and then active JACK and everything concerning JACK.

close the config-dialog and then launch NWC. In the Midi menu choose the fluidsynth directly. Maybe it will be a bit slow at first and take some time, but I will go on.
Then play. If you don't hear anything be sure that in your JACK Connections Fluidsynt is connected to your PCM output.


My next step is to run the Linux Sampler Project instead of Fluidsynth. I think that would'nt be a big problem. Then I have support for die *.gig Sample Format.

Re: NWC2 on Linux/Wine

Reply #49

Good day,

Wine had lots of trouble with NWC's tabbed dialog boxes (which are modeless, but with special hooks to make them modal). I suspect that you won't see much improvement on that front any time soon.

I'm back with this (old) issue because there are news: The 1.0 version of Wine is out and I'm asked wether the bug still exists.

I've tried some softs around but I couldn't reproduce the bug with any of them apart NWC2.
Even there, it's not pretty clear.

For example, in the File/Open or File/Info dialog boxes, the Tab key functions perfectly, but under Staff Properties, Tools/Options or File/Page Setup, the bug appears.

I wonder if there isn't something peculiar in those dialogs?