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

[Sound Mechanics]

The latset version is crashing my Cubase 5

[martin_l]

The latset version is crashing my Cubase 5

Thanks for letting me know.

Are you running the 32bit version of Cubase 5 on 64bit Win7? This combination caused problems before. I am currently trying to fix the problem, but it looks like a trickey one, especially since it only occurs on some combinations of host and operating system...

Regards,
Martin

[Sound Mechanics]

W7 32bit v.-55b works fine.

[tman2k (Meathook Audio)]

@akademie
"Never change a running system", but SP1 is really to old. At least, update your system to WinXP SP3, it's working very well and costs you nothing.
If you're unsure, make a backup of your system before.

+1 to this comment! I have never had a problem updating any XP SP1 system up to SP3...you should really, really do this!

[fateamenabletochange]

awesome work Martin

all go in 64 bit Reaper

I have the JX10 and PG controller, mainly for the Voices and Soundtrack preset sounds. Some humour and truth now to Urs's 'retired your old synths now'.

Great modeling. Always liked the way a deep bass note will start to break up held a long time on the Soundtrack preset, which is happening nicely with your version.

[aciddose]

+1 to this comment! I have never had a problem updating any XP SP1 system up to SP3...you should really, really do this!

sp2 -> sp3 gave me a couple problems, but those are specific to certain types of software. if you don't run into them, which you probably won't, it isn't an issue. what i had to do was install a couple "unpatches" which reverted some files/settings to fix the problems.

one example of a problem was a "locked up" console window when executing a binary from the debugger and exiting by breaking rather than using the "stop debug" command.

so, this stuff is quite rare. i also agree, definitely start using sp3 unless you have a very specific reason not to. problems do occur, but they're mostly fixed and easy to install patches for at this point.

[LXNDR1]

c'mon guys it's not about ridiculing someone who still runs Windows SP1, if it works and is stable why change it

but to the best of my knowledge SynthEdit 1.1 is only compatible with SP2 and higher, i had to upgrade my service pack in order to be able to install SynthEdit 1.1

so if anybody gots to upgrade it's not because SP1 isn't cool but cause the plugin compiled with SP2 dependencies simply won't run on SP1

[cevin]

The latset version is crashing my Cubase 5

Thanks for letting me know.

Are you running the 32bit version of Cubase 5 on 64bit Win7? This combination caused problems before. I am currently trying to fix the problem, but it looks like a trickey one, especially since it only occurs on some combinations of host and operating system...

Regards,
Martin

The latset version is crashing my Cubase 6 32bit

[cevin]

The latset version is crashing my Cubase 5

Thanks for letting me know.

Are you running the 32bit version of Cubase 5 on 64bit Win7? This combination caused problems before. I am currently trying to fix the problem, but it looks like a trickey one, especially since it only occurs on some combinations of host and operating system...

Regards,
Martin

The latset version is crashing my Cubase 6 32bit

I forgot 32bit Win7

[martin_l]

The latset version is crashing my Cubase 5

Thanks for letting me know.

Are you running the 32bit version of Cubase 5 on 64bit Win7? This combination caused problems before. I am currently trying to fix the problem, but it looks like a trickey one, especially since it only occurs on some combinations of host and operating system...

Regards,
Martin

The latset version is crashing my Cubase 6 32bit

I forgot 32bit Win7

Thanks for letting me know, cevin. Could you tell me more about the crash? Do you get some error message, or is Cubase just quitting or freezing?

Cheers,
Martin

[echopark]

I'm running it on Cubase 6 32 Bit on Windows 7 64BIT without any problems

[martin_l]

I'm running it on Cubase 6 32 Bit on Windows 7 64BIT without any problems

I am absolutely puzzled why it is working on some systems, and not on others...

With reaper, it seems that there are problems with reaper 32bit on Win7 64bit,
while Cubase seems to have problems when runnign on Win7 32bit but running fine with on Win7 64bit...


Martin

[PAK]

I'm running it on Cubase 6 32 Bit on Windows 7 64BIT without any problems

I am absolutely puzzled why it is working on some systems, and not on others...

Permissions Martin.

To be much more explicit than my previous comments; PG8X also crashed for me. If you have UAC enabled on Windows Vista/7 (And people do if they don't know what that means) PG8x simply will not work under Cubase if the file is in under a path "protected" by UAC (Program Files is one such path). Ain't gonna happen. Plus it doesn't just fail to load the plugin. It will most likely hang Cubase, and then Cubase will blacklist the plugin in its XML file, so it won't load until you remove the backlist entry or rename the plugin!

If someone's disabled UAC, or runs Cubase with the Admin checkbox checked in its shortcut, they won't experience the issue. All you need to do is run Cubase as an admin once and it allows the creation of the Synthedit folder. It can then function normally. This is NOT optional for Cubase 5 or 6 (whether x32 or x64) on Windows 7 with UAC. If you don't do this the likelihood is PG8x simply will not work and it will actually crash Cubase if it attempts to load it.

So, if you use Cubase and can't load the plugin, run Cubase as an admin! If you can already use the plugin and are experiencing crashing at some other point during usage then obviously it's an unrelated issue. (And, to be honest, Synthedit based plugins often do seem to be a teensy bit unstable under Cubase on Windows 7 if used over long periods of time.. IE 24 hours + etc).

[martin_l]

Hi PAK,

thanks very much for elaborating on this issue. Let's see whether this solves some of the problems.

I wonder, though, since it seems that people could run the earlier version of my plugin without issues, and if it was down to file permissions, I cant understand why there should be a difference now...

Cheers,
Martin

[PAK]

I wonder, though, since it seems that people could run the earlier version of my plugin without issues, and if it was down to file permissions, I cant understand why there should be a difference now...

From previous experiences I do recall that there seem to be some differences between various Cubase/Synthedit versions as well as plugins and permissions. Some plugins would outright crash. Some will eventually reach a GUI after multiple launch attempts, but might not make sound. It's also possible (you'd need to check) that Windows may write the synthedit folder to a different location if it doesn't have permission under somewhere like program files, and that could cause some issues if something doesn't know where to find what it's looking for.

I just learned early on with Cubase on Windows 7 that whenever there's any weirdness or crashing on load issues with Synthedit plugins, it's pretty much always guaranteed to be related to permissions in some way.