I get problems loading LS 1.3.5 into a new song EnergyXT (several versions, including 1.3.6]
On loading LS and connecting its MIDI input, I get "Exception EInvalidPointer . . . at 00002A52".
Then on closing energyXT, I get "Exception EInvalidPointer . . at 0001FCFE"
and "EAccessViolation . . . at 00002053 . . . Write of address 02497FE8."
Beta 5 loads fine.
Anyone else?
BR thread: LiveSlice 1.3.5
-
- KVRian
- 1263 posts since 15 Jun, 2004 from hamburg
no problems here, works fine without errors in eXT. see the other thread for my guess what's wrong.DarkStar wrote:Anyone else?
btw. after a long time i visited my buddy to make music this weekend and for the first time i used LS on my personal laptop (b4 i only used it on my corporate laptop and my desktop).. and i had some problems with the gui, everything responded and there were no sound-problems, but the graphics reacted slow.
unfortunately my notebook is 3 years old, so it has not much power. i reckon the cpu and ram aren't the problem, but the gfx-chip which is an ati rage mobility m1 (not very up-to-date
).perhaps there's a way for some tweaks in the next update to make it display better on my old laptop.
-
- KVRAF
- 1511 posts since 2 Jul, 2004
Darkstar - could you please try deleting your LiveSlice.ini file (backup the original first and email it to me if it helps)
thanks
R.A.W. I had to change the way I allocate bitmaps for the wave-displays because some graphics drivers had a limit to the size of bitmaps (my own driver would allow 32 loops to be displayed counting ALL liveslice instances).
This means the graphics card has to do a little conversion each time the display is updated.
There might be room for optimizations here though - I even have an old laptop of my own with the exact same graphics card for testing
thanks
R.A.W. I had to change the way I allocate bitmaps for the wave-displays because some graphics drivers had a limit to the size of bitmaps (my own driver would allow 32 loops to be displayed counting ALL liveslice instances).
This means the graphics card has to do a little conversion each time the display is updated.
There might be room for optimizations here though - I even have an old laptop of my own with the exact same graphics card for testing
http://www.livelab.dk - slice up your life
-
- KVRian
- 1263 posts since 15 Jun, 2004 from hamburg
that's niceohm wrote:I even have an old laptop of my own with the exact same graphics card for testing
i'm up for tests as soon as you got optimized versions. this time i'll test on my personal notebook as well.
-
- KVRian
- 1263 posts since 15 Jun, 2004 from hamburg
i have to apologize.. there is no gfx issue at all, it was my eXT project which had a too high hit on the cpu of my old notebook which made the display respond so slow.. sorry, ohm!R.A.W. wrote:that's niceohm wrote:I even have an old laptop of my own with the exact same graphics card for testing
i'm up for tests as soon as you got optimized versions. this time i'll test on my personal notebook as well.
-
- KVRAF
- 1511 posts since 2 Jul, 2004
there was a minor issue actually - I did improve the performace on my system - so don't be sorry
http://www.livelab.dk - slice up your life
-
- KVRAF
- Topic Starter
- 10366 posts since 2 Sep, 2003 from Surrey, UK
[as in my other thread]
Ohm has sorted this out, and the fix will be in the next release.
- It was caused by the particular combination of the ASIO settings on my PC.
- In energyXT, my Setup settings were: Buffer Size 441, Sample Rate 44100, and in my ASIO Sound Control Panel the Latency was set to 10 mS.
- for the moment, all I need to do is increase the Buffer Size (450 works for me).
Ohm has sorted this out, and the fix will be in the next release.
- It was caused by the particular combination of the ASIO settings on my PC.
- In energyXT, my Setup settings were: Buffer Size 441, Sample Rate 44100, and in my ASIO Sound Control Panel the Latency was set to 10 mS.
- for the moment, all I need to do is increase the Buffer Size (450 works for me).