PG8X (inspired by the JX8P): new beta version uploaded

[Kriminal]

I actually was hoping to release it with a full bank of patches, so no INIT sounds should be necessary.

i would include just 1, at the end of the bank, it makes life easier

[s_t]

Ok, and now v.0.99 is not working again in Reaper.
It's the same C++ runtime error. Also when I open the task manager I see Reaper process hogging about 4Gb of memory before it closes down!

And the same with both Reaper 3.75 & 4.0alpha

I dont't get this.

[martin_l]

Ok, and now v.0.99 is not working again in Reaper.
It's the same C++ runtime error. Also when I open the task manager I see Reaper process hogging about 4Gb of memory before it closes down!

And the same with both Reaper 3.75 & 4.0alpha

I dont't get this.

This will be very difficult to fix, I'm afraid...

Please, try to figure out whether there was any difference in the procedure of starting up reaper and loading the plugin when it crashed and when it did not crash. Did you have any other plugin loaded? Did you use the same samplerate and latency, etc.? Can you tell whether the plugin breaks when the audio engine is started or when the GUI is opened?

Did you have any problems with other plugins?

Is reaper a 32 bit or 64 bit host? (Sorry, I am not familiar with reaper...). If it is 64bit, there might be problems, since SE plugins are 32 bit plugins. I have no idea about how well they work (if at all) on 64 bit platforms.

Best Regards,
Martin

[AdmiralQuality]

Is reaper a 32 bit or 64 bit host? (Sorry, I am not familiar with reaper...). If it is 64bit, there might be problems, since SE plugins are 32 bit plugins. I have no idea about how well they work (if at all) on 64 bit platforms.

Best Regards,
Martin

Both. He mentioned he was using it on Win7 x64, so I assume he's using the x64 version of Reaper.

Reaper has a fully functional, non-expiring demo by the way. You're supposed to buy it if you use it for more than a month, but I'm sure they don't mind us developers using the demo purely for testing. http://reaper.fm

It's quite a nice host actually, and is constantly being improved. And I get lower latency from my Edirol UA-1000 in Reaper using WDM drivers (64 samples) than I get from the Edirol's ASIO driver in any other host (96 samples).

I've been meaning to test this for you in Win7 x64 next time I boot into it. Busy week, but I'll test it when I get a chance.

[s_t]

This will be very difficult to fix, I'm afraid...

Please, try to figure out whether there was any difference in the procedure of starting up reaper and loading the plugin when it crashed and when it did not crash. Did you have any other plugin loaded? Did you use the same samplerate and latency, etc.? Can you tell whether the plugin breaks when the audio engine is started or when the GUI is opened?

Did you have any problems with other plugins?

Is reaper a 32 bit or 64 bit host? (Sorry, I am not familiar with reaper...). If it is 64bit, there might be problems, since SE plugins are 32 bit plugins. I have no idea about how well they work (if at all) on 64 bit platforms.

Best Regards,
Martin

I'm using 32-bit version of Reaper in W7 x64
Sample rate and latency remains the same.
The procedure is the same every time:

1. Start Reaper
2. Create empty track
3. Select pg8x from the plugin list

- Immediately after selecting pg8x Reaper freezes. It takes about 10 sec and nothing happens. During that time I can see memory usage rising to 4Gb in task manager.

- After about 10 sec an error message pops up telling about Visual C++ error.

So I never get the plugin gui open as the crash happens on loading.
It doesn't matter whether audio engine is active (aka monitoring activated) or passive before loading. I have no idea what was different when it worked. This is the exact procedure every time I have tried it.
Sorry if this wasn't much of help..

Cheers

[AdmiralQuality]

I'm using 32-bit version of Reaper in W7 x64
Sample rate and latency remains the same.
The procedure is the same every time:

1. Start Reaper
2. Create empty track
3. Select pg8x from the plugin list

- Immediately after selecting pg8x Reaper freezes. It takes about 10 sec and nothing happens. During that time I can see memory usage rising to 4Gb in task manager.

- After about 10 sec an error message pops up telling about Visual C++ error.

So I never get the plugin gui open as the crash happens on loading.
It doesn't matter whether audio engine is active (aka monitoring activated) or passive before loading. I have no idea what was different when it worked. This is the exact procedure every time I have tried it.
Sorry if this wasn't much of help..

Cheers

A couple of things to check...

Reaper is working OK when you load other instruments?

Have you tried rebooting? Any difference?

[osiris]

I played with this last night. Some lovely sounds.

[martin_l]

This will be very difficult to fix, I'm afraid...

Please, try to figure out whether there was any difference in the procedure of starting up reaper and loading the plugin when it crashed and when it did not crash. Did you have any other plugin loaded? Did you use the same samplerate and latency, etc.? Can you tell whether the plugin breaks when the audio engine is started or when the GUI is opened?

Did you have any problems with other plugins?

Is reaper a 32 bit or 64 bit host? (Sorry, I am not familiar with reaper...). If it is 64bit, there might be problems, since SE plugins are 32 bit plugins. I have no idea about how well they work (if at all) on 64 bit platforms.

Best Regards,
Martin

I'm using 32-bit version of Reaper in W7 x64
Sample rate and latency remains the same.
The procedure is the same every time:

1. Start Reaper
2. Create empty track
3. Select pg8x from the plugin list

- Immediately after selecting pg8x Reaper freezes. It takes about 10 sec and nothing happens. During that time I can see memory usage rising to 4Gb in task manager.

- After about 10 sec an error message pops up telling about Visual C++ error.

So I never get the plugin gui open as the crash happens on loading.
It doesn't matter whether audio engine is active (aka monitoring activated) or passive before loading. I have no idea what was different when it worked. This is the exact procedure every time I have tried it.
Sorry if this wasn't much of help..

Cheers

I will download reaper tonight and see whether I can reproduce the problem. However, I only have a 32bit XP SP3 machine...

[wwjd]

If no one else report that issue, it's probably not a big deal.
I could install W7 64 on my system and test it out also in a few days

[martin_l]

If no one else report that issue, it's probably not a big deal.
I could install W7 64 on my system and test it out also in a few days

Although I can't promise that I will be able to fix it (especially if I cannot reproduce the behaviour), I will at least try...

@ s_t: Which samplerate were you using?

Martin

[edteneyck]

I tried pg8x-0.99 with the Reaper 64bit demo and it runs fine here.

Vista 64bit
Intel Core2Duo 2.5ZGhz
4Gb Ram
M-Audio Mobile Pre USB set at 44/16

[fateamenabletochange]

I am having no trouble with Reaper 64 on Windows 7 Pro. I haven't had a crash with any version.

[iNNeRNoiZe]

No Probs here in REAPER 32/64 & Cubase 5.5 (32).

I love this Plug!

[rsmus7]

the0.99 did load here in reaper on Win7 64bit,
but irt crashed while changing presets,
and now it doesn't load again,
I get a runtime error and programm termination
same in XT2 here

might need to reboot my system,

but this shouldn't happen imho

[martin_l]

the0.99 did load here in reaper on Win7 64bit,
but irt crashed while changing presets,
and now it doesn't load again,
I get a runtime error and programm termination
same in XT2 here

might need to reboot my system,

but this shouldn't happen imho

Does it crash at every patch change, or are there some specific patches which lead to a crash?

Which samplerate are you using?

Did you try any of the previous versions of the plugin? Did they work?