Bug v0.4.0 - Sound lag
Ultrahead opened this issue · 12 comments
Ultrahead commented
There is a lag in sounds, at least for Mac, of about 1 or 2 seconds.
Dotneteer commented
Issue fixed. To be released in 0.5.0.
Dotneteer commented
Released in 0.5.0
Ultrahead commented
It's still happening in v0.5.0. Weird.
Dotneteer commented
The sound lag seem to appear again in 0.5.0
Dotneteer commented
Fixed, will be released in v0.7.0
TurtleQuality commented
I'm getting several seconds sound lag in Klive v0.9.0 in Windows
Dotneteer commented
@TurtleQuality, could you give me some more details on your Windows machine? Windows version, CPU, memory,etc?
TurtleQuality commented
Hi,
thanks for the quick response.
Edition Windows 10 Pro
Version 21H1
Installed on 13/08/2020
OS build 19043.1237
Experience Windows Feature Experience Pack 120.2212.3530.0
Processor AMD A6-5400B APU with Radeon(tm) HD Graphics 3.60 GHz
Installed RAM 8.00 GB (7.19 GB usable)
System type 64-bit operating system, x64-based processor
By modern standards it's quite underpowered.
Just installed Klive yesterday, I've been using Zeus for about 3 years.
Install went well except on page "Setup » Configure the Emulator" you refer
to file "klive.config" which is actually "klive.setup".
Have a good weekend,
Thomas Quillin
…On Fri, 24 Sept 2021 at 08:07, Istvan Novak ***@***.***> wrote:
@TurtleQuality <https://github.com/TurtleQuality>, could you give me some
more details on your Windows machine? Windows version, CPU, memory,etc?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUAYMKP6KFAIKBM72VPK3QLUDQBQVANCNFSM4RJTFJGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
Dotneteer commented
Thomas, thanks for the info!
Unfortunately, the sound lagging is caused by the Electron shell, so I can't do too much to improve it. Nonetheless, v0.9.0 uses Electron shell v11.1.1, while the current development branch relies on 13.1.6, which is much faster. A few of my friends tried it (on Mac, where the sound issue was always the worst), and they experienced that the issue vanished with the new Electron version.
Since March, I'm working on a brand-new version of Klive that has its own IDE, and does not need VS Code. Though it is still not stable enough for release, you can try it to check the sound issue:
Clone the repository (git clone), use the master branch
npm run bootstrap
Select the packages/klive-emu folder (this contains the brand-new, single-app Klive version)
npm run build (it takes about 1-2 minutes)
npm start
Select ZX Spectrum 48/128
Start the machine, run LOAD "", and check the sound.
Here are a few screenshots from the new IDE (click IDE|Show IDE window in the main menu):
TurtleQuality commented
Hi Ivan,
it was a learning experience, but I wanted to try it out. So I installed
Github Desktop, the Command Line tool and Node.JS for the NPM commands. But
NPM start fails with the errors copied below
Not sure if I need to specifically install Electron 13.1.6 or if it's some
other issue.
I mainly needed an assembler / emulator to check and play with some "chase
the raster" code - is it correct that the debugger raster tracker follows
only the top line to show horizontal position ? I was hoping it would move
down the screen
Look forward to the new release
Regards,
Thomas
C:\Users\User1\Documents\GitHub\kliveide\packages\klive-emu>npm start
***@***.*** start
C:\Users\User1\Documents\GitHub\kliveide\packages\klive-emu
electron ./dist/main.bundle.js
internal/modules/cjs/loader.js:892
throw err;
^
Error: Cannot find module
'C:\Users\User1\Documents\GitHub\kliveide\packages\klive-emu\node_modules\electron\cli.js'
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:889:15)
at Function.Module._load (internal/modules/cjs/loader.js:745:27)
at Function.executeUserEntryPoint [as runMain]
(internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ***@***.*** start: `electron ./dist/main.bundle.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ***@***.*** start script.
…On Fri, 24 Sept 2021 at 09:50, Istvan Novak ***@***.***> wrote:
@TurtleQuality <https://github.com/TurtleQuality>
Thomas, thanks for the info!
Unfortunately, the sound lagging is caused by the Electron shell, so I
can't do too much to improve it. Nonetheless, v0.9.0 uses Electron shell
v11.1.1, while the current development branch relies on 13.1.6, which is
much faster. A few of my friends tried it (on Mac, where the sound issue
was always the worst), and they experienced that the issue vanished with
the new Electron version.
Since March, I'm working on a brand-new version of Klive that has its own
IDE, and does not need VS Code. Though it is still not stable enough for
release, you can try it to check the sound issue:
Clone the repository (git clone), use the master branch
npm run bootstrap
Select the packages/klive-emu folder (this contains the brand-new,
single-app Klive version)
npm run build (it takes about 1-2 minutes)
npm start
Select ZX Spectrum 48/128
Start the machine, run LOAD "", and check the sound.
Here are a few screenshots from the new IDE (click *IDE|Show IDE window*
in the main menu):
[image: electron_koyCcJCiN3]
<https://user-images.githubusercontent.com/4783390/134630639-7c384253-df60-40a9-bb86-d0019c74d896.png>
[image: electron_ib1arX8WYM]
<https://user-images.githubusercontent.com/4783390/134630708-533ab895-a3ce-48c2-8b06-af7da2e11dd0.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUAYMKP4C5K4JOETK2MTMSDUDQNSLANCNFSM4RJTFJGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
Dotneteer commented
Thomas,
Sorry for the build does not work on your machine ☹. During the weekend, I will create a build with the newest Electron so that you can try that version on your Windows machine.
“Chasing the raster code” works for the entire screen area and not just for the top line 😊. When you stop the code, it always happens after a screen has been entirely rendered, so you see the current raster be the top one after pausing the machine.
So, after a pause, use the step-into and step-over buttons on the toolbar. As you use them, you will see the raster/pixel position move.
Later, I will add a debug feature to pause the code when the screen rendering reaches a particular raster line.
Istvan
Feladó: TurtleQuality ***@***.***>
Küldve: 2021. szeptember 27., hétfő 15:53
Címzett: Dotneteer/kliveide ***@***.***>
Másolatot kap: Istvan Novak ***@***.***>; State change ***@***.***>
Tárgy: Re: [Dotneteer/kliveide] Bug v0.4.0 - Sound lag (#90)
Hi Ivan,
it was a learning experience, but I wanted to try it out. So I installed
Github Desktop, the Command Line tool and Node.JS for the NPM commands. But
NPM start fails with the errors copied below
Not sure if I need to specifically install Electron 13.1.6 or if it's some
other issue.
I mainly needed an assembler / emulator to check and play with some "chase
the raster" code - is it correct that the debugger raster tracker follows
only the top line to show horizontal position ? I was hoping it would move
down the screen
Look forward to the new release
Regards,
Thomas
C:\Users\User1\Documents\GitHub\kliveide\packages\klive-emu>npm start
***@***.***<mailto:***@***.***> start
C:\Users\User1\Documents\GitHub\kliveide\packages\klive-emu
electron ./dist/main.bundle.js
internal/modules/cjs/loader.js:892
throw err;
^
Error: Cannot find module
'C:\Users\User1\Documents\GitHub\kliveide\packages\klive-emu\node_modules\electron\cli.js'
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:889:15)
at Function.Module._load (internal/modules/cjs/loader.js:745:27)
at Function.executeUserEntryPoint [as runMain]
(internal/modules/run_main.js:76:12)
at internal/main/run_main_module.js:17:47 {
code: 'MODULE_NOT_FOUND',
requireStack: []
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! ***@***.***<mailto:***@***.***> start: `electron ./dist/main.bundle.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ***@***.***<mailto:***@***.***> start script.
On Fri, 24 Sept 2021 at 09:50, Istvan Novak ***@***.***<mailto:***@***.***>> wrote:
@TurtleQuality <https://github.com/TurtleQuality>
Thomas, thanks for the info!
Unfortunately, the sound lagging is caused by the Electron shell, so I
can't do too much to improve it. Nonetheless, v0.9.0 uses Electron shell
v11.1.1, while the current development branch relies on 13.1.6, which is
much faster. A few of my friends tried it (on Mac, where the sound issue
was always the worst), and they experienced that the issue vanished with
the new Electron version.
Since March, I'm working on a brand-new version of Klive that has its own
IDE, and does not need VS Code. Though it is still not stable enough for
release, you can try it to check the sound issue:
Clone the repository (git clone), use the master branch
npm run bootstrap
Select the packages/klive-emu folder (this contains the brand-new,
single-app Klive version)
npm run build (it takes about 1-2 minutes)
npm start
Select ZX Spectrum 48/128
Start the machine, run LOAD "", and check the sound.
Here are a few screenshots from the new IDE (click *IDE|Show IDE window*
in the main menu):
[image: electron_koyCcJCiN3]
<https://user-images.githubusercontent.com/4783390/134630639-7c384253-df60-40a9-bb86-d0019c74d896.png>
[image: electron_ib1arX8WYM]
<https://user-images.githubusercontent.com/4783390/134630708-533ab895-a3ce-48c2-8b06-af7da2e11dd0.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#90 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUAYMKP4C5K4JOETK2MTMSDUDQNSLANCNFSM4RJTFJGQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FDotneteer%2Fkliveide%2Fissues%2F90%23issuecomment-927896812&data=04%7C01%7C%7Cbe34ed85918f430dcd8d08d981be242d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637683475910660993%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=L%2BjsWqF5P%2BHDi1qRkbTD6UITvlsZlyLNekReMSs%2BIdo%3D&reserved=0>, or unsubscribe<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABEP2HXN5NSCIZO6BKTNJ6DUEBZMLANCNFSM4RJTFJGQ&data=04%7C01%7C%7Cbe34ed85918f430dcd8d08d981be242d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637683475910670946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=dtgUDdueyFHnpUUf7lRHLnf6mIjd7AxCj%2BdYmmz6jhc%3D&reserved=0>.
Triage notifications on the go with GitHub Mobile for iOS<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04%7C01%7C%7Cbe34ed85918f430dcd8d08d981be242d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637683475910670946%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=wDuXzndfIMfV%2B7FP6hAPLfLjdT6g83dMNc03%2BsUp%2F84%3D&reserved=0> or Android<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04%7C01%7C%7Cbe34ed85918f430dcd8d08d981be242d%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637683475910680902%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=q1tTnRwzAoWYwt9gR7Yg2ReVGZ8r9oIrWsXgAMDyQ%2BQ%3D&reserved=0>.
Dotneteer commented
By my experience, the sound lagging issue goes away with Electron v16. I cannot reproduce it wiht Klive v0.11.0.