All times are UTC+02:00




Post new topic  Reply to topic  [ 155 posts ]  Go to page Previous 16 7 8 9 1016 Next
Author Message
PostPosted: Mon Nov 06, 2017 9:42 pm 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Tryed differend things you said, but nothing worked, only errors. Finally i removed radiocaster from my pc and installed it again.
Copyed the dsp into the plugin directory and start it. Now it works without any error. The only difference with before is that there is now just one dsp in the directory of radiocaster. So it seems the problem is that there were too many dsp's /vst's in the plugin directory of radiocaster.
Hm.. so maybe it was a memory issue anyway then? Did you remove the Stereo Tool .ini file? If not, it must have been a RadioCaster issue, but I have no idea how that would not have been an issue with earlier versions.. Unless you placed all the DLL's in the directory and there were just too many?


Top
   
PostPosted: Mon Nov 06, 2017 11:23 pm 

Joined: Tue Aug 02, 2011 5:24 pm
Posts: 101
Hi Hans,

It seems that radiocaster reads the dll files in the directory of the plugins dir, even when they are not selected.
I had 24 dsp and 2 vst in the directory. If i put them all back in the folder, i get this messages when i try to load one of them.

Image
Image

I also deleted the stereotool.ini file but that didn't work.


Top
   
PostPosted: Mon Nov 06, 2017 11:46 pm 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Ok, but if this only happens if all the files are there, I'm assuming for now that it's indeed an out of memory error. If RadioCaster keeps all the DLL's in memory then it will fail once it runs out of memory....

I see that you kept the full name with BETA854-008 in the name, so if they are loaded (or even just found) in alphabetical order then it makes perfect sense that the last few are causing issues, and the older ones aren't.


Top
   
PostPosted: Mon Nov 06, 2017 11:55 pm 
User avatar

Joined: Sat Mar 10, 2012 8:15 pm
Posts: 154
Location: Nederland
Hans..


This does not happen with Radio Caster onley!, multiple vst / dsp host give this same error, easy to blame a program while every build you explode does something wrong.
Do you test the builds yourself? or may "customers" do that..

_________________
Garbage in is Garbage out !


Top
   
PostPosted: Tue Nov 07, 2017 12:02 am 
User avatar

Joined: Thu Apr 07, 2011 2:37 am
Posts: 149
Location: Napier, New Zealand
Quote:
Hans..


This does not happen with Radio Caster onley!, multiple vst / dsp host give this same error, easy to blame a program while every build you explode does something wrong.
Do you test the builds yourself? or may "customers" do that..

I don't understand your attitude. These are beta builds (See Thread title!) - they are exactly for us to test out and help find bugs and problems. And it's not like Hans hasn't been responsive in trying to fix bugs that are reported.

I'll go far as to suggest I think you should edit your original post and/or at least apologise.

_________________
I just use ST with liquidsoap to enhance a streaming radio station I like...


Top
   
PostPosted: Tue Nov 07, 2017 12:05 am 
User avatar

Joined: Sat Mar 10, 2012 8:15 pm
Posts: 154
Location: Nederland
Never! ;) input for years where mister does not do anything about it, and not the only one ( Stream encoders!!! )


And you do not want any criticism, you just have no forum

_________________
Garbage in is Garbage out !


Top
   
PostPosted: Tue Nov 07, 2017 12:35 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Of course I test them, and they are running perfectly stable in all the programs I tested with. Beside that, I'm running tools such as Valgrind to verify for errors that could cause such issues.

One problem with recent builds is that I switched to a newer compiler (which was needed for Omnia.9sg and Omnia.9 developement), but unfortunately the compiler turns out to have several bugs. I've had multiple instances where where the compiler itself would just crash with some internal error or segmentation failt, and several others where it didn't complain but generated broken code, which ran on some CPU's but not on others. I've asked multiple people to look into some of these issues with me to verify that it wasn't a bug in my code and they too did not understand why the compiler was doing what it did - again, only for some CPU types. So certain things might run fine on all CPU's except on certain Core2Quad models, for example.

I think that I'm close to having workarounds for all the problems with the new compiler now, but if things keep being this problematic I will switch back to the old compiler. It had other bugs (which is why I actually switched to the latest version), but at least the bugs of the old version are reasonably documented - that version is 3 years old and people have posted comments about them.

But I really prefer to stick with the new compiler, instead of having to rely on several years old software. It wouldn't be the first time though that I would have to do that. Obviously things have to be perfectly stable again before I can release a new version.


Top
   
PostPosted: Tue Nov 07, 2017 12:41 am 
User avatar

Joined: Mon Nov 23, 2015 12:39 am
Posts: 32
Quote:
Of course I test them, and they are running perfectly stable in all the programs I tested with. Beside that, I'm running tools such as Valgrind to verify for errors that could cause such issues.

One problem with recent builds is that I switched to a newer compiler (which was needed for Omnia.9sg and Omnia.9 developement), but unfortunately the compiler turns out to have several bugs. I've had multiple instances where where the compiler itself would just crash with some internal error or segmentation failt, and several others where it didn't complain but generated broken code, which ran on some CPU's but not on others. I've asked multiple people to look into some of these issues with me to verify that it wasn't a bug in my code and they too did not understand why the compiler was doing what it did - again, only for some CPU types. So certain things might run fine on all CPU's except on certain Core2Quad models, for example.

I think that I'm close to having workarounds for all the problems with the new compiler now, but if things keep being this problematic I will switch back to the old compiler. It had other bugs (which is why I actually switched to the latest version), but at least the bugs of the old version are reasonably documented - that version is 3 years old and people have posted comments about them.

But I really prefer to stick with the new compiler, instead of having to rely on several years old software. It wouldn't be the first time though that I would have to do that. Obviously things have to be perfectly stable again before I can release a new version.
Just switch back to the old compiler for now for public builds and make some private builds for testing the new one? Saves a lot of frustration if you ask me.


Top
   
PostPosted: Tue Nov 07, 2017 1:17 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
If we switch back to the old compiler we need to make workarounds for the bugs that we were running into a few weeks ago that prompted us to update to the new compiler. So, it's not just a matter of installing the old compiler and going with that. If things work well with the new compiler (I know, if), then we don't need to program those workarounds.

Most of the issues mentioned in this thread are fixed now (and some weren't caused by Stereo Tool at all). What remains at this moment:
- octavafm's issue... Happened once, in code that I didn't change in over a year.
- Someone else reported seeing an exception via email in another piece of code that hasn't changed in years. Also happened once, several beta's ago, ran fine after that.

I'm not sure what Fario's problem with RadioCaster is exactly. I've just tested it here and I don't see that it uses memory for each instance that's in the directory. But, if adding the old DLL's to the plugins-directory causes things to hang, it kinda has to be something in one of the older DLL's that causing problems... Not so much in the latest DLL. Waiting what happens with the next updates.


Top
   
PostPosted: Tue Nov 07, 2017 1:23 am 
Site Admin
User avatar

Joined: Mon Mar 17, 2008 1:40 am
Posts: 11425
Quote:
Hans..


This does not happen with Radio Caster onley!, multiple vst / dsp host give this same error, easy to blame a program while every build you explode does something wrong.
Do you test the builds yourself? or may "customers" do that..
Which other programs? I've tried it here in Radio Caster with dozens of DLL's and I don't see any problems... So this issue defintely doesn't reproduce on my end. If you have more programs that show this same thing let me know and I'll try to reproduce it in those as well.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic  [ 155 posts ]  Go to page Previous 16 7 8 9 1016 Next

All times are UTC+02:00


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Limited