audacity-devel — Discussion among Audacity developers

Re: [Audacity-devel] Aup3 and blockfiles

[Greg S. <mai...@gm...>]

He just did; Leland was the lead developer for v3.

On 24-Mar-21 10:01, freddyjohn via audacity-devel wrote:
>
> Alright thank you, I will look at source code here 
> -> https://github.com/audacity/audacity/tree/master/src/blockfile 
> <https://github.com/audacity/audacity/tree/master/src/blockfile>
> A bit later tonight. It would be awesome if someone who worked on 
> these could chime in though!
>
> Sent from ProtonMail Mobile
>
>
> On Tue, Mar 23, 2021 at 9:44 PM, Petr Pařízek via audacity-devel 
> <aud...@li... 
> <mailto:aud...@li...>> wrote:
>> freddyjohn writes:
>>
>> <<<<<
>> Is there anything special about these blockfiles?
>> >>>>>
>>
>> Depends on what you mean by special. In all of my experimental files,
>> the audio was stored as standard 32-bit floats.
>>
>> <<<<<
>> Are they more than just raw byte chunks of sampled audio?
>> >>>>>
>>
>> Apparently they are, meaning that each of them contains some kind of
>> header. But I'm currently unable to verify what the actual header 
>> data is.
>>
>> Petr
>>
>>
>> --
>> Tento e-mail byl zkontrolován na viry programem AVG.
>> http://www.avg.cz
>>
>>
>>
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>
>
>
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Aup3 and blockfiles

[freddyjohn <fre...@pr...>]

Alright thank you, I will look at source code here ->https://github.com/audacity/audacity/tree/master/src/blockfile
A bit later tonight. It would be awesome if someone who worked on these could chime in though!

Sent from ProtonMail Mobile

On Tue, Mar 23, 2021 at 9:44 PM, Petr Pařízek via audacity-devel <aud...@li...> wrote:

> freddyjohn writes:
>
> <<<<<
> Is there anything special about these blockfiles?
>>>>>>
>
> Depends on what you mean by special. In all of my experimental files,
> the audio was stored as standard 32-bit floats.
>
> <<<<<
> Are they more than just raw byte chunks of sampled audio?
>>>>>>
>
> Apparently they are, meaning that each of them contains some kind of
> header. But I'm currently unable to verify what the actual header data is.
>
> Petr
>
> --
> Tento e-mail byl zkontrolován na viry programem AVG.
> http://www.avg.cz
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Aup3 and blockfiles

[Leland <ll...@ho...>]

The sample data is just raw samples, no headers, but the samples can be in different formats.  You need to look at “sampleformat” in sampeblocks to get the format which are all little endian:

 

   int16Sample = 0x00020001,

   int24Sample = 0x00040001,

   floatSample = 0x0004000F,

 

The XML doc that you referred to is actually still being used, but it is stored in a “binary” format.  The easiest way to get an idea of the sequence the individual blocks are assigned to a specific channel would be to use “Help -> Generate Support Data” and look at the “project.txt” file.  The “decoder” for this XML doc can be found in “ProjectSerializer::Decode()”.

 

From: freddyjohn via audacity-devel <aud...@li...> 
Sent: Tuesday, March 23, 2021 7:56 PM
To: aud...@li...
Cc: freddyjohn <fre...@pr...>
Subject: Re: [Audacity-devel] Aup3 and blockfiles

 

 

I do not know what you mean by tracks and I am not talking about project files.

Specifically I am talking about these

 

SELECT samples FROM sampleblocks WHERE blockid=n

 

And 

 

If you look at blockfiles generated in >3 they are same structure just now in SQLite3 database inside .aup3 file instead of referenced via xml b-tree in .aup file

 

Is there anything special about these blockfiles? Are they more than just raw byte chunks of sampled audio? 

Those are the questions.

 

Sent from ProtonMail Mobile

 

 

On Tue, Mar 23, 2021 at 8:11 PM, Petr Pařízek via audacity-devel <aud...@li... <mailto:aud...@li...> > wrote:

Freddyjohn writes:

<<<<< 

Hello, I am writing an application similar to audacity for android. I am currently working on the data structure to support editing. I was studying the old format with what I think was B-tree inside xml doc until I read the articles about 3.0 yesterday. It is a lot easier to reverse. But one thing I ask out of Curiosity, what is with the encoding for the block files? It looks like the samples are aligned in some pattern. If you drop the output of these files into HxD for example.

It’s like this with spacing increasing linearly

s1.s2

s100..s101

s200...s201

If you unpack these bytes as 32 bit float and graph the samples it looks like audio data. But if I multiply each sample by 32767 and throw on a wav header it sounds like the bytes are offset(very horrible noise you don’t want to be familiar with). So is there more going on in a blockfile than just raw audio data? If so why?

>>>>> 

 

I've tried it with a simple two-track project and here's what I've been able to find:

- The data is indeed written as standard 32-bit IEEE float.

- To find the start of the first sample, I had to skip an odd number of bytes, which meant that when loading the file as raw data (including all the headers), the number of skipped bytes had to be one more than a multiple of 4.

-That's why many editors are unable to play it correctly because, for 32-bit data, they only allow skipping a number of bytes that is a multiple of 4.

- Surprisingly, when data from one track finish and data from another track begin, the byte offset changes. Therefore, when I skipped one byte, the first track sounded okay. When I skipped 0 bytes (i.e. loaded the entire thing), the second track sounded okay.

-From that I'm gathering (not verified yet but I can do that if someone desires) that if my project had one more track, it would probably load correctly if I chose to skip 3 bytes.

 

Petr

 

 

 


 <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> 

Bez virů.  <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> www.avg.com 

 

 

Re: [Audacity-devel] Aup3 and blockfiles

[Petr P. <pet...@ya...>]

freddyjohn writes:

<<<<<
Is there anything special about these blockfiles?
 >>>>>

Depends on what you mean by special. In all of my experimental files, 
the audio was stored as standard 32-bit floats.

<<<<<
Are they more than just raw byte chunks of sampled audio?
 >>>>>

Apparently they are, meaning that each of them contains some kind of 
header. But I'm currently unable to verify what the actual header data is.

Petr


-- 
Tento e-mail byl zkontrolován na viry programem AVG.
http://www.avg.cz

Re: [Audacity-devel] Aup3 and blockfiles

[freddyjohn <fre...@pr...>]

I do not know what you mean by tracks and I am not talking about project files.
Specifically I am talking about these

SELECT samples FROM sampleblocks WHERE blockid=n

And

If you look at blockfiles generated in >3 they are same structure just now in SQLite3 database inside .aup3 file instead of referenced via xml b-tree in .aup file

Is there anything special about these blockfiles? Are they more than just raw byte chunks of sampled audio?
Those are the questions.

Sent from ProtonMail Mobile

On Tue, Mar 23, 2021 at 8:11 PM, Petr Pařízek via audacity-devel <aud...@li...> wrote:

> Freddyjohn writes:
>
> <<<<<
>
> Hello, I am writing an application similar to audacity for android. I am currently working on the data structure to support editing. I was studying the old format with what I think was B-tree inside xml doc until I read the articles about 3.0 yesterday. It is a lot easier to reverse. But one thing I ask out of Curiosity, what is with the encoding for the block files? It looks like the samples are aligned in some pattern. If you drop the output of these files into HxD for example.
>
> It’s like this with spacing increasing linearly
>
> s1.s2
> s100..s101
> s200...s201
> If you unpack these bytes as 32 bit float and graph the samples it looks like audio data. But if I multiply each sample by 32767 and throw on a wav header it sounds like the bytes are offset(very horrible noise you don’t want to be familiar with). So is there more going on in a blockfile than just raw audio data? If so why?
>>>>>>
>
> I've tried it with a simple two-track project and here's what I've been able to find:
> - The data is indeed written as standard 32-bit IEEE float.
> - To find the start of the first sample, I had to skip an odd number of bytes, which meant that when loading the file as raw data (including all the headers), the number of skipped bytes had to be one more than a multiple of 4.
> -That's why many editors are unable to play it correctly because, for 32-bit data, they only allow skipping a number of bytes that is a multiple of 4.
> - Surprisingly, when data from one track finish and data from another track begin, the byte offset changes. Therefore, when I skipped one byte, the first track sounded okay. When I skipped 0 bytes (i.e. loaded the entire thing), the second track sounded okay.
> -From that I'm gathering (not verified yet but I can do that if someone desires) that if my project had one more track, it would probably load correctly if I chose to skip 3 bytes.
>
> Petr
>
> http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient	Bez virů. [www.avg.com](http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient) #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2

Re: [Audacity-devel] Aup3 and blockfiles

[Petr P. <pet...@ya...>]

P.S.:

Sorry for sending your original attachment, that was a mistake I made. I 
didn't mean to include any attachments.


Petr



-- 
Tento e-mail byl zkontrolován na viry programem AVG.
http://www.avg.cz

Re: [Audacity-devel] Aup3 and blockfiles

[Petr P. <pet...@ya...>]

Freddyjohn writes:

<<<<<

Hello, I am writing an application similar to audacity for android. I am 
currently working on the data structure to support editing. I was 
studying the old format with what I think was B-tree inside xml 
doc until I read the articles about 3.0 yesterday. It is a lot easier 
to reverse. But one thing I ask out of Curiosity, what is with the 
encoding for the block files? It looks like the samples are aligned in 
some pattern. If you drop the output of these files into HxD for example.

It’s like this with spacing increasing linearly
s1.s2
s100..s101
s200...s201
If you unpack these bytes as 32 bit float and graph the samples it looks 
like audio data. But if I multiply each sample by 32767 and throw on a 
wav header it sounds like the bytes are offset(very horrible noise you 
don’t want to be familiar with). So is there more going on in a 
blockfile than just raw audio data? If so why?
 >>>>>

I've tried it with a simple two-track project and here's what I've been 
able to find:
- The data is indeed written as standard 32-bit IEEE float.
- To find the start of the first sample, I had to skip an odd number of 
bytes, which meant that when loading the file as raw data (including all 
the headers), the number of skipped bytes had to be one more than a 
multiple of 4.
-That's why many editors are unable to play it correctly because, for 
32-bit data, they only allow skipping a number of bytes that is a 
multiple of 4.
- Surprisingly, when data from one track finish and data from another 
track begin, the byte offset changes. Therefore, when I skipped one 
byte, the first track sounded okay. When I skipped 0 bytes (i.e. loaded 
the entire thing), the second track sounded okay.
-From that I'm gathering (not verified yet but I can do that if someone 
desires) that if my project had one more track, it would probably load 
correctly if I chose to skip 3 bytes.

Petr



-- 
Tento e-mail byl zkontrolován na viry programem AVG.
http://www.avg.cz

Re: [Audacity-devel] Aup3 and blockfiles

[freddyjohn <fre...@pr...>]

damn it I meant to send the aup3 file. it does not matter you can run it on any aup3 file it only reads

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, March 23, 2021 7:29 PM, freddyjohn <fre...@pr...> wrote:

> Sorry I did not know 32 bit wav exists I changed my wav header accordingly but it still does not sound correct. Am I an idiot or am I missing something about these blocks?
>
> Sent with [ProtonMail](https://protonmail.com) Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Tuesday, March 23, 2021 6:25 PM, freddyjohn via audacity-devel <aud...@li...> wrote:
>
>> Hello, I am writing an application similar to audacity for android. I am currently working on the data structure to support editing. I was studying the old format with what I think was B-tree inside xml doc until I read the articles about 3.0 yesterday. It is a lot easier to reverse. But one thing I ask out of Curiosity, what is with the encoding for the block files? It looks like the samples are aligned in some pattern. If you drop the output of these files into HxD for example.
>> It’s like this with spacing increasing linearly
>>
>> s1.s2
>> s100..s101
>> s200...s201
>> If you unpack these bytes as 32 bit float and graph the samples it looks like audio data. But if I multiply each sample by 32767 and throw on a wav header it sounds like the bytes are offset(very horrible noise you don’t want to be familiar with). So is there more going on in a blockfile than just raw audio data? If so why?
>>
>> Sent from ProtonMail Mobile

[Audacity-devel] Aup3 and blockfiles

[freddyjohn <fre...@pr...>]

Hello, I am writing an application similar to audacity for android. I am currently working on the data structure to support editing. I was studying the old format with what I think was B-tree inside xml doc until I read the articles about 3.0 yesterday. It is a lot easier to reverse. But one thing I ask out of Curiosity, what is with the encoding for the block files? It looks like the samples are aligned in some pattern. If you drop the output of these files into HxD for example.It’s like this with spacing increasing linearly

s1.s2
s100..s101
s200...s201
If you unpack these bytes as 32 bit float and graph the samples it looks like audio data. But if I multiply each sample by 32767 and throw on a wav header it sounds like the bytes are offset(very horrible noise you don’t want to be familiar with). So is there more going on in a blockfile than just raw audio data? If so why?

Sent from ProtonMail Mobile

Re: [Audacity-devel] Zero length clips corrupt envelopes

[Steve F. <ste...@gm...>]

If email will allow, attached is a small version of the project.

If you render to a new track you will (probably) observe that the fade out
after 2.0 seconds is wrong (does not fade out enough).

Observe that there is a zero length clip at 2.83261
If that zero length clip is removed, the envelope works correctly.

The BIG question in my mind is "why do we still allow zero length clips?"

Steve

On Tue, 23 Mar 2021 at 12:13, Steve Fiddle <ste...@gm...> wrote:

>
>
> On Tue, 23 Mar 2021 at 12:02, Peter Sampson <
> pet...@gm...> wrote:
>
>>
>>
>> On Tue, Mar 23, 2021 at 11:57 AM Steve Fiddle <ste...@gm...>
>> wrote:
>>
>>> I think there's already a bug logged about zero length clips but I can't
>>> find it as bugzilla search appears to be broken.
>>>
>>> The bug reported on the forum is illustrated in this video:
>>> https://youtu.be/NVrhc5buDoE
>>>
>>> Observe that playback is not following the envelope until subsequent
>>> clips are removed from the track.
>>>
>>> The problem is related to the presence of zero length clips in the
>>> project.
>>> The full project is available here:
>>> https://www.mediafire.com/file/hz5wv7d7c97wqrf/m_sf_recap_intermission.zip/file
>>> (45MB) but I should have a much smaller version soon.
>>>
>>> The forum thread is here:
>>> https://forum.audacityteam.org/viewtopic.php?f=46&t=116777
>>>
>>
>> Is this a regression Steve?
>>
>
> As I recall appearance of zero length clips has been around for a while
> (sorry, still not found it in bugzilla).
> I suspect that the envelope problem is a symptom of that bug rather than a
> new bug.
>
> Steve
>
>
>>
>> Peter.
>>
>>
>>
>>> Steve
>>> _______________________________________________
>>> audacity-devel mailing list
>>> aud...@li...
>>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>>
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
>

Re: [Audacity-devel] Zero length clips corrupt envelopes

[Steve F. <ste...@gm...>]

On Tue, 23 Mar 2021 at 12:02, Peter Sampson <pet...@gm...>
wrote:

>
>
> On Tue, Mar 23, 2021 at 11:57 AM Steve Fiddle <ste...@gm...>
> wrote:
>
>> I think there's already a bug logged about zero length clips but I can't
>> find it as bugzilla search appears to be broken.
>>
>> The bug reported on the forum is illustrated in this video:
>> https://youtu.be/NVrhc5buDoE
>>
>> Observe that playback is not following the envelope until subsequent
>> clips are removed from the track.
>>
>> The problem is related to the presence of zero length clips in the
>> project.
>> The full project is available here:
>> https://www.mediafire.com/file/hz5wv7d7c97wqrf/m_sf_recap_intermission.zip/file
>> (45MB) but I should have a much smaller version soon.
>>
>> The forum thread is here:
>> https://forum.audacityteam.org/viewtopic.php?f=46&t=116777
>>
>
> Is this a regression Steve?
>

As I recall appearance of zero length clips has been around for a while
(sorry, still not found it in bugzilla).
I suspect that the envelope problem is a symptom of that bug rather than a
new bug.

Steve


>
> Peter.
>
>
>
>> Steve
>> _______________________________________________
>> audacity-devel mailing list
>> aud...@li...
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

Re: [Audacity-devel] Zero length clips corrupt envelopes

[Peter S. <pet...@gm...>]

On Tue, Mar 23, 2021 at 11:57 AM Steve Fiddle <ste...@gm...>
wrote:

> I think there's already a bug logged about zero length clips but I can't
> find it as bugzilla search appears to be broken.
>
> The bug reported on the forum is illustrated in this video:
> https://youtu.be/NVrhc5buDoE
>
> Observe that playback is not following the envelope until subsequent clips
> are removed from the track.
>
> The problem is related to the presence of zero length clips in the project.
> The full project is available here:
> https://www.mediafire.com/file/hz5wv7d7c97wqrf/m_sf_recap_intermission.zip/file
> (45MB) but I should have a much smaller version soon.
>
> The forum thread is here:
> https://forum.audacityteam.org/viewtopic.php?f=46&t=116777
>

Is this a regression Steve?

Peter.



> Steve
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

[Audacity-devel] Zero length clips corrupt envelopes

[Steve F. <ste...@gm...>]

I think there's already a bug logged about zero length clips but I can't
find it as bugzilla search appears to be broken.

The bug reported on the forum is illustrated in this video:
https://youtu.be/NVrhc5buDoE

Observe that playback is not following the envelope until subsequent clips
are removed from the track.

The problem is related to the presence of zero length clips in the project.
The full project is available here:
https://www.mediafire.com/file/hz5wv7d7c97wqrf/m_sf_recap_intermission.zip/file
(45MB) but I should have a much smaller version soon.

The forum thread is here:
https://forum.audacityteam.org/viewtopic.php?f=46&t=116777

Steve

[Audacity-devel] Update Windows Batch scripts to use python3

[NIKITA M. <mah...@gm...>]

Dear Sir,
I have written a batch file to *Update Windows Batch scripts to use
python3.*
Please find a text document as an attachment to this mail.
Yours sincerely
Nikita Mahoviya
3rd Year B.Tech Undergraduate
Department of Electronics and Communication Engineering
National Institute of Technology Hamirpur (H.P.)

Re: [Audacity-devel] Japanese language issues

[Leland <ll...@ho...>]

Well, I guess I was right…it didn’t make any sense at all.  It still doesn’t, but I can no longer recreate the issue after installing Windows updates.  Along with driver updates, ther other updates installed were:

 

https://support.microsoft.com/en-us/topic/kb4589212-intel-microcode-updates-for-windows-10-version-2004-and-20h2-and-windows-server-version-2004-and-20h2-9f8641b3-bd8e-6fe7-ab4d-4603847c4030

 

https://support.microsoft.com/en-us/topic/february-24-2021-kb4601554-cumulative-update-preview-for-net-framework-3-5-and-4-8-for-windows-10-version-2004-windows-server-version-2004-windows-10-version-20h2-and-windows-server-version-20h2-958fff0c-783b-27b3-8a93-226f7798225a

 

https://support.microsoft.com/en-us/topic/kb4577586-update-for-the-removal-of-adobe-flash-player-october-27-2020-931521b9-075a-ce54-b9af-ff3d5da047d5

 

https://support.microsoft.com/en-us/topic/march-18-2021-kb5001649-os-builds-19041-870-and-19042-870-out-of-band-ebbe0617-3a63-467a-aaaa-2a4c68a6de33

 

Since that last one seemed to be the most likely candidate for fixing it, I went ahead and uninstalled it.  Still unable to reproduce the problem.  I may get more ambitious later today and uninstall the others…maybe. 

 

From: Leland <ll...@ho...> 
Sent: Monday, March 22, 2021 7:58 AM
To: aud...@li...
Subject: Re: [Audacity-devel] Japanese language issues

 

It’s not a 32-bit vs 64-bit thing.  It’s not a VS2017 vs VS2019 thing.  It just doesn’t make any sense.  That commit should not be causing this.

 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 7:36 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

Well, I’ve tracked it down to commit b32ce8ab210700fe3de23353b6ff504b70e5ef7f. If I build that commit, Audacity freezes when I try to type a Japanese character.  If I build the previous commit, 98d86039316d87b7c81b97eb757b6af2b0c99728, there is no such freeze and I can type Japanese characters just fine.

 

But, it makes absolutely no sense to me.  That commit shouldn’t have anything at all to do with keyboard input.

 

Would be nice if someone else could confirm this as well.

 

From: Peter Sampson <pet...@gm... <mailto:pet...@gm...> > 
Sent: Monday, March 22, 2021 6:58 AM
To: Devel <aud...@li... <mailto:aud...@li...> >; Peter Sampson <pet...@gm... <mailto:pet...@gm...> >
Subject: Re: [Audacity-devel] Japanese language issues

 

 

 

On Mon, Mar 22, 2021 at 11:40 AM Leland <ll...@ho... <mailto:ll...@ho...> > wrote:

I was able to get past this by fixing Windows Update here, but it still didn’t correct the Audacity freeze.  The only thing that works for me so far is the workaround suggested by Microsoft.

 

I recall seeing on the Forum this morning that the Japanese user had fixed this freeze when hitting any key

 

And as Homer Simpson once so famously said:   "Where's the "Any" key?"

 

Peter.

 

 

 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:31 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

This might also have some relevance.  I happened to look into the Japanese language options and found this.  It shows that I DO have the language pack installed, but it did not install any typing support.  I’m trying to work through this now.

 



 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:23 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

I also ran in to that IME thing that pikap did.  Just add the Japanese language in Windows:

 

Settings -> Time & Language -> Language -> Preferred languages -> Add a language

 

This should also enable the Language toolbar to the Windows Taskbar.  If you open Audacity, change the language in the Taskbar to Japanese (don’t worry…you can change it back and nothing happens visually), and then press a key in Audacity, it will completely freeze.

 

And I just found some info and a workaround that works perfectly here:

 

https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692

 

Workaround

You can mitigate Issues 3, 5, 6 and 7 in the short term by following the steps below to enable compatibility mode:

1.       Select Start, type Settings, and select it or press enter.

2.       Type IME settings into the search box within Settings and select the IME settings that are appropriate to your language, for example Japanese IME Settings.

3.       Select General.

4.       Turn on Use previous version of Microsoft IME.

Note We do not recommend using the compatibility setting for the long term, but rather as a temporary workaround for users who are impacted by this issue.

 

From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > 
Sent: Monday, March 22, 2021 4:34 AM
To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> >
Subject: [Audacity-devel] Japanese language issues

 

For any devs looking into the Japanese language issue(s), there's additional information in this forum topic that may be useful: https://forum.audacityteam.org/viewtopic.php?f=46 <https://forum.audacityteam.org/viewtopic.php?f=46&t=116720> &t=116720

 

Steve

_______________________________________________
audacity-devel mailing list
aud...@li... <mailto:aud...@li...> 
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Japanese language issues

[Joost A. <Joo...@gm...>]

Hi Leland,


maybe creating a callstack from that freeze might help to get some idea 
what function resulted in that freeze. Using windbg should also allow 
this kind of debugging on windows.

Am 22.03.2021 um 13:58 schrieb Leland:
> It’s not a 32-bit vs 64-bit thing.  It’s not a VS2017 vs VS2019 thing.  It just doesn’t make any sense.  That commit should not be causing this.
> 


Just my 2cents..

Kind regards, Joost

Re: [Audacity-devel] Japanese language issues

[Leland <ll...@ho...>]

It’s not a 32-bit vs 64-bit thing.  It’s not a VS2017 vs VS2019 thing.  It just doesn’t make any sense.  That commit should not be causing this.

 

From: Leland <ll...@ho...> 
Sent: Monday, March 22, 2021 7:36 AM
To: aud...@li...
Subject: Re: [Audacity-devel] Japanese language issues

 

Well, I’ve tracked it down to commit b32ce8ab210700fe3de23353b6ff504b70e5ef7f. If I build that commit, Audacity freezes when I try to type a Japanese character.  If I build the previous commit, 98d86039316d87b7c81b97eb757b6af2b0c99728, there is no such freeze and I can type Japanese characters just fine.

 

But, it makes absolutely no sense to me.  That commit shouldn’t have anything at all to do with keyboard input.

 

Would be nice if someone else could confirm this as well.

 

From: Peter Sampson <pet...@gm... <mailto:pet...@gm...> > 
Sent: Monday, March 22, 2021 6:58 AM
To: Devel <aud...@li... <mailto:aud...@li...> >; Peter Sampson <pet...@gm... <mailto:pet...@gm...> >
Subject: Re: [Audacity-devel] Japanese language issues

 

 

 

On Mon, Mar 22, 2021 at 11:40 AM Leland <ll...@ho... <mailto:ll...@ho...> > wrote:

I was able to get past this by fixing Windows Update here, but it still didn’t correct the Audacity freeze.  The only thing that works for me so far is the workaround suggested by Microsoft.

 

I recall seeing on the Forum this morning that the Japanese user had fixed this freeze when hitting any key

 

And as Homer Simpson once so famously said:   "Where's the "Any" key?"

 

Peter.

 

 

 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:31 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

This might also have some relevance.  I happened to look into the Japanese language options and found this.  It shows that I DO have the language pack installed, but it did not install any typing support.  I’m trying to work through this now.

 



 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:23 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

I also ran in to that IME thing that pikap did.  Just add the Japanese language in Windows:

 

Settings -> Time & Language -> Language -> Preferred languages -> Add a language

 

This should also enable the Language toolbar to the Windows Taskbar.  If you open Audacity, change the language in the Taskbar to Japanese (don’t worry…you can change it back and nothing happens visually), and then press a key in Audacity, it will completely freeze.

 

And I just found some info and a workaround that works perfectly here:

 

https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692

 

Workaround

You can mitigate Issues 3, 5, 6 and 7 in the short term by following the steps below to enable compatibility mode:

1.       Select Start, type Settings, and select it or press enter.

2.       Type IME settings into the search box within Settings and select the IME settings that are appropriate to your language, for example Japanese IME Settings.

3.       Select General.

4.       Turn on Use previous version of Microsoft IME.

Note We do not recommend using the compatibility setting for the long term, but rather as a temporary workaround for users who are impacted by this issue.

 

From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > 
Sent: Monday, March 22, 2021 4:34 AM
To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> >
Subject: [Audacity-devel] Japanese language issues

 

For any devs looking into the Japanese language issue(s), there's additional information in this forum topic that may be useful: https://forum.audacityteam.org/viewtopic.php?f=46 <https://forum.audacityteam.org/viewtopic.php?f=46&t=116720> &t=116720

 

Steve

_______________________________________________
audacity-devel mailing list
aud...@li... <mailto:aud...@li...> 
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Japanese language issues

[Leland <ll...@ho...>]

Well, I’ve tracked it down to commit b32ce8ab210700fe3de23353b6ff504b70e5ef7f. If I build that commit, Audacity freezes when I try to type a Japanese character.  If I build the previous commit, 98d86039316d87b7c81b97eb757b6af2b0c99728, there is no such freeze and I can type Japanese characters just fine.

 

But, it makes absolutely no sense to me.  That commit shouldn’t have anything at all to do with keyboard input.

 

Would be nice if someone else could confirm this as well.

 

From: Peter Sampson <pet...@gm...> 
Sent: Monday, March 22, 2021 6:58 AM
To: Devel <aud...@li...>; Peter Sampson <pet...@gm...>
Subject: Re: [Audacity-devel] Japanese language issues

 

 

 

On Mon, Mar 22, 2021 at 11:40 AM Leland <ll...@ho... <mailto:ll...@ho...> > wrote:

I was able to get past this by fixing Windows Update here, but it still didn’t correct the Audacity freeze.  The only thing that works for me so far is the workaround suggested by Microsoft.

 

I recall seeing on the Forum this morning that the Japanese user had fixed this freeze when hitting any key

 

And as Homer Simpson once so famously said:   "Where's the "Any" key?"

 

Peter.

 

 

 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:31 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

This might also have some relevance.  I happened to look into the Japanese language options and found this.  It shows that I DO have the language pack installed, but it did not install any typing support.  I’m trying to work through this now.

 



 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:23 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

I also ran in to that IME thing that pikap did.  Just add the Japanese language in Windows:

 

Settings -> Time & Language -> Language -> Preferred languages -> Add a language

 

This should also enable the Language toolbar to the Windows Taskbar.  If you open Audacity, change the language in the Taskbar to Japanese (don’t worry…you can change it back and nothing happens visually), and then press a key in Audacity, it will completely freeze.

 

And I just found some info and a workaround that works perfectly here:

 

https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692

 

Workaround

You can mitigate Issues 3, 5, 6 and 7 in the short term by following the steps below to enable compatibility mode:

1.       Select Start, type Settings, and select it or press enter.

2.       Type IME settings into the search box within Settings and select the IME settings that are appropriate to your language, for example Japanese IME Settings.

3.       Select General.

4.       Turn on Use previous version of Microsoft IME.

Note We do not recommend using the compatibility setting for the long term, but rather as a temporary workaround for users who are impacted by this issue.

 

From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > 
Sent: Monday, March 22, 2021 4:34 AM
To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> >
Subject: [Audacity-devel] Japanese language issues

 

For any devs looking into the Japanese language issue(s), there's additional information in this forum topic that may be useful: https://forum.audacityteam.org/viewtopic.php?f=46 <https://forum.audacityteam.org/viewtopic.php?f=46&t=116720> &t=116720

 

Steve

_______________________________________________
audacity-devel mailing list
aud...@li... <mailto:aud...@li...> 
https://lists.sourceforge.net/lists/listinfo/audacity-devel

Re: [Audacity-devel] Japanese language issues

[Peter S. <pet...@gm...>]

On Mon, Mar 22, 2021 at 11:40 AM Leland <ll...@ho...> wrote:

> I was able to get past this by fixing Windows Update here, but it still
> didn’t correct the Audacity freeze.  The only thing that works for me so
> far is the workaround suggested by Microsoft.
>

I recall seeing on the Forum this morning that the Japanese user had fixed
this freeze when hitting any key

*And as Homer Simpson once so famously said:   "Where's the "Any" key?"*

Peter.



>
> *From:* Leland <ll...@ho...>
> *Sent:* Monday, March 22, 2021 6:31 AM
> *To:* aud...@li...
> *Subject:* Re: [Audacity-devel] Japanese language issues
>
>
>
> This might also have some relevance.  I happened to look into the Japanese
> language options and found this.  It shows that I DO have the language pack
> installed, but it did not install any typing support.  I’m trying to work
> through this now.
>
>
>
>
>
> *From:* Leland <ll...@ho...>
> *Sent:* Monday, March 22, 2021 6:23 AM
> *To:* aud...@li...
> *Subject:* Re: [Audacity-devel] Japanese language issues
>
>
>
> I also ran in to that IME thing that pikap did.  Just add the Japanese
> language in Windows:
>
>
>
> Settings -> Time & Language -> Language -> Preferred languages -> Add a
> language
>
>
>
> This should also enable the Language toolbar to the Windows Taskbar.  If
> you open Audacity, change the language in the Taskbar to Japanese (don’t
> worry…you can change it back and nothing happens visually), and then press
> a key in Audacity, it will completely freeze.
>
>
>
> And I just found some info and a workaround that works perfectly here:
>
>
>
>
> https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692
>
>
>
> *Workaround*
>
> You can mitigate *Issues 3, 5, 6 and 7 *in the short term by following
> the steps below to enable compatibility mode:
>
> 1.       Select *Start*, type *Settings,* and select it or press enter.
>
> 2.       Type *IME settings* into the search box within *Settings* and
> select the IME settings that are appropriate to your language, for example *Japanese
> IME Settings*.
>
> 3.       Select *General*.
>
> 4.       Turn on *Use previous version of Microsoft IME*.
>
> *Note* We do not recommend using the compatibility setting for the long
> term, but rather as a temporary workaround for users who are impacted by
> this issue.
>
>
>
> *From:* Steve Fiddle <ste...@gm...>
> *Sent:* Monday, March 22, 2021 4:34 AM
> *To:* Audacity-Devel list <aud...@li...>
> *Subject:* [Audacity-devel] Japanese language issues
>
>
>
> For any devs looking into the Japanese language issue(s), there's
> additional information in this forum topic that may be useful:
> https://forum.audacityteam.org/viewtopic.php?f=46&t=116720
>
>
>
> Steve
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

Re: [Audacity-devel] Japanese language issues

[Leland <ll...@ho...>]

I was able to get past this by fixing Windows Update here, but it still didn’t correct the Audacity freeze.  The only thing that works for me so far is the workaround suggested by Microsoft.

 

From: Leland <ll...@ho...> 
Sent: Monday, March 22, 2021 6:31 AM
To: aud...@li...
Subject: Re: [Audacity-devel] Japanese language issues

 

This might also have some relevance.  I happened to look into the Japanese language options and found this.  It shows that I DO have the language pack installed, but it did not install any typing support.  I’m trying to work through this now.

 



 

From: Leland <ll...@ho... <mailto:ll...@ho...> > 
Sent: Monday, March 22, 2021 6:23 AM
To: aud...@li... <mailto:aud...@li...> 
Subject: Re: [Audacity-devel] Japanese language issues

 

I also ran in to that IME thing that pikap did.  Just add the Japanese language in Windows:

 

Settings -> Time & Language -> Language -> Preferred languages -> Add a language

 

This should also enable the Language toolbar to the Windows Taskbar.  If you open Audacity, change the language in the Taskbar to Japanese (don’t worry…you can change it back and nothing happens visually), and then press a key in Audacity, it will completely freeze.

 

And I just found some info and a workaround that works perfectly here:

 

https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692

 

Workaround

You can mitigate Issues 3, 5, 6 and 7 in the short term by following the steps below to enable compatibility mode:

1.       Select Start, type Settings, and select it or press enter.

2.       Type IME settings into the search box within Settings and select the IME settings that are appropriate to your language, for example Japanese IME Settings.

3.       Select General.

4.       Turn on Use previous version of Microsoft IME.

Note We do not recommend using the compatibility setting for the long term, but rather as a temporary workaround for users who are impacted by this issue.

 

From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > 
Sent: Monday, March 22, 2021 4:34 AM
To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> >
Subject: [Audacity-devel] Japanese language issues

 

For any devs looking into the Japanese language issue(s), there's additional information in this forum topic that may be useful: https://forum.audacityteam.org/viewtopic.php?f=46 <https://forum.audacityteam.org/viewtopic.php?f=46&t=116720> &t=116720

 

Steve

Re: [Audacity-devel] Japanese language issues

[Leland <ll...@ho...>]

This might also have some relevance.  I happened to look into the Japanese language options and found this.  It shows that I DO have the language pack installed, but it did not install any typing support.  I’m trying to work through this now.

 



 

From: Leland <ll...@ho...> 
Sent: Monday, March 22, 2021 6:23 AM
To: aud...@li...
Subject: Re: [Audacity-devel] Japanese language issues

 

I also ran in to that IME thing that pikap did.  Just add the Japanese language in Windows:

 

Settings -> Time & Language -> Language -> Preferred languages -> Add a language

 

This should also enable the Language toolbar to the Windows Taskbar.  If you open Audacity, change the language in the Taskbar to Japanese (don’t worry…you can change it back and nothing happens visually), and then press a key in Audacity, it will completely freeze.

 

And I just found some info and a workaround that works perfectly here:

 

https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692

 

Workaround

You can mitigate Issues 3, 5, 6 and 7 in the short term by following the steps below to enable compatibility mode:

1.       Select Start, type Settings, and select it or press enter.

2.       Type IME settings into the search box within Settings and select the IME settings that are appropriate to your language, for example Japanese IME Settings.

3.       Select General.

4.       Turn on Use previous version of Microsoft IME.

Note We do not recommend using the compatibility setting for the long term, but rather as a temporary workaround for users who are impacted by this issue.

 

From: Steve Fiddle <ste...@gm... <mailto:ste...@gm...> > 
Sent: Monday, March 22, 2021 4:34 AM
To: Audacity-Devel list <aud...@li... <mailto:aud...@li...> >
Subject: [Audacity-devel] Japanese language issues

 

For any devs looking into the Japanese language issue(s), there's additional information in this forum topic that may be useful: https://forum.audacityteam.org/viewtopic.php?f=46 <https://forum.audacityteam.org/viewtopic.php?f=46&t=116720> &t=116720

 

Steve

Re: [Audacity-devel] Japanese language issues

[Leland <ll...@ho...>]

I also ran in to that IME thing that pikap did.  Just add the Japanese language in Windows:

 

Settings -> Time & Language -> Language -> Preferred languages -> Add a language

 

This should also enable the Language toolbar to the Windows Taskbar.  If you open Audacity, change the language in the Taskbar to Japanese (don’t worry…you can change it back and nothing happens visually), and then press a key in Audacity, it will completely freeze.

 

And I just found some info and a workaround that works perfectly here:

 

https://support.microsoft.com/en-us/topic/you-might-have-issues-on-windows-10-version-20h2-and-windows-10-version-2004-when-using-some-microsoft-imes-63696506-47d2-9997-0b72-41a68e328692

 

Workaround

You can mitigate Issues 3, 5, 6 and 7 in the short term by following the steps below to enable compatibility mode:

1.       Select Start, type Settings, and select it or press enter.

2.       Type IME settings into the search box within Settings and select the IME settings that are appropriate to your language, for example Japanese IME Settings.

3.       Select General.

4.       Turn on Use previous version of Microsoft IME.

Note We do not recommend using the compatibility setting for the long term, but rather as a temporary workaround for users who are impacted by this issue.

 

From: Steve Fiddle <ste...@gm...> 
Sent: Monday, March 22, 2021 4:34 AM
To: Audacity-Devel list <aud...@li...>
Subject: [Audacity-devel] Japanese language issues

 

For any devs looking into the Japanese language issue(s), there's additional information in this forum topic that may be useful: https://forum.audacityteam.org/viewtopic.php?f=46 <https://forum.audacityteam.org/viewtopic.php?f=46&t=116720> &t=116720

 

Steve

[Audacity-devel] Japanese language issues

[Steve F. <ste...@gm...>]

For any devs looking into the Japanese language issue(s), there's
additional information in this forum topic that may be useful:
https://forum.audacityteam.org/viewtopic.php?f=46&t=116720

Steve

Re: [Audacity-devel] wxWidgets Menu Problem on Big Sur M1 11.1, 11.2, 11.3 beta 3 with Foreign Language

[Peter S. <pet...@gm...>]

But Bill reports in this Forum thread
https://forum.audacityteam.org/viewtopic.php?f=68&t=114537&start=10

> I do not have this problem on my M1 Macbook Air under Big Sur.
>We have had no other reports of this. You *may* be the only one.

I can't test, my Macbook Pro is Intel-powered

Peter.

On Sat, Mar 20, 2021 at 10:42 PM John Colket <jc...@gm...> wrote:

> We have one report on the forum of a French user running MacOS Big Sur sur
> Mac Mini 2021 Apple Silicon who has problems with menu check marks not
> being displayed and with sub-menus not being available.  The problem
> appears with Audacity 3.0.0, but also with 2.4.2, so it is not a regression
> problem.
>
> There is a report on the wxWidets forum here:
> https://forums.wxwidgets.org/viewtopic.php?p=204874#p204874
>
> which thread points to a wxWidgets trouble ticket here:
> https://trac.wxwidgets.org/ticket/19023
>
> and to a "Locales in wx" google group discussion here:
> https://groups.google.com/g/wx-dev/c/1EmqyDWGzfE
>
> - John Colket
>
> _______________________________________________
> audacity-devel mailing list
> aud...@li...
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

[Audacity-devel] wxWidgets Menu Problem on Big Sur M1 11.1, 11.2, 11.3 beta 3 with Foreign Language

[John C. <jc...@gm...>]

We have one report on the forum of a French user running MacOS Big Sur sur
Mac Mini 2021 Apple Silicon who has problems with menu check marks not
being displayed and with sub-menus not being available.  The problem
appears with Audacity 3.0.0, but also with 2.4.2, so it is not a regression
problem.

There is a report on the wxWidets forum here:
https://forums.wxwidgets.org/viewtopic.php?p=204874#p204874

which thread points to a wxWidgets trouble ticket here:
https://trac.wxwidgets.org/ticket/19023

and to a "Locales in wx" google group discussion here:
https://groups.google.com/g/wx-dev/c/1EmqyDWGzfE

- John Colket