tried streaming a file at 96k/24bit today, got a crash screen 'something really f"+cked up just happened, and Orion will now terminate you' or whatever it says. The funny thing is, that the song was streaming in the background, so we let it run until it was finished. The streamed song was in it's proper place, and intact, but I had to kill Orion to get out of the program.
Maybe I forgot something, or is this a bug?
stream to crashModerators: Christophe, Mark
15 posts
• Page 1 of 1
stream to crashCould be a glitch with a VST synth or effect at that rate? You sure the song was intact when it was done? Sometimes I would think that when these problems happened to me, and realised a certain synth or reverb effect was indeed not in the streamed song.
stream to crashyes, everything was there............... however, there was a big difference with one of the sounds. It usually sounds like a growl of some sort, and it ended up sounding like a croaking frog on acid.
I've noticed that sort of thing before though, when trying out bouncing songs in high sample rates. I figured that was normal, due to how the higher sampe rate effects aliasing, etc. Maybe bouncing in higher sample rates transmographies the substrate of the vertebrate involed? Like for instance, turns a bull into a chipmunk, etc. Seriously though, it was just a test to show to the guy I'm collaborating with. I've bounced stuff into soundforge at 32 bits from Cubase, and also had differences in sound. Usually I stick to 44.1/24bit, and then convert bitrate + dither, after the master. Last edited by Icaro on Sat Aug 08, 2009 9:26 pm, edited 1 time in total.
stream to crashI think some plugs can't handle it? And/or it's a driver speed/latency issue? OR - it's a OP issue? Had a bugger of a time getting the SOSF song of mine done. Plays great in OP, the RealStrat should be a downstroke only at the intro. But everytime i streamed it, it's this Keith Richards up/down chuck? Tried in numerous sample rates, driver speed settings - can't shake it? But in OP it plays great and precise?
So something might not be 'syncing up' during streaming - which might be affecting certain synths and effects, at extreme or even normal sampling rates? I just live with my MusicLab axes as best I can now. ML blames OP, Rich blames ML - the proverbial 'hot potato'. Is this OP's own synths turning into frogs on acid, or someone elses?
stream to crashactually, it's gladiator that gets it's balls chopped off.
stream to crashTone2 Gladiator? That's a awesome synth! No problems with it for me, I use it in my SOSF song too, and came through just fine when I was trying all the different methods to get the RealStrat correct.
Unless RealStrat was stroking it's shaft, and it was cutting the balls off my axe? But Tone2 are some serious mo-fo's that should work fine on all levels I would think?
stream to crashso, as you can see, the issue wasn't with Gladiator per say; but with what happened after a bounce out at 96k. Don't know why it happened, but we compared the 44.1 and 96k back to back, and it's quite noticeable. So is it Orion, or is it a result of the bounce down at 96k. What do you think?
and yes, Gladiator is a GREAT synth.
stream to crashAt the time, I was more concentrating on RealStrat, but didn't notice anything too weird with Gladiator? Then again, I was just using that bubbly little arp biz. Maybe your sound had some sideband issues coming out at 96? The filters on that thing can be pretty awesome, but then with the effects and stuff - might've been a bit of 'clashing' going on as you went at such a high rate for clarity? I'm a firm beliver of inaudible frequencies coluring natural sound. And with something as powerful as Gladiator at 96k, you may have opened up a Pandora's box of colour.
I would think that might not be OP's problem per say?
stream to crashactually, that makes a lot of sense. Especially with what frequencies seemed to have disappeared from the sound. Thanks for your insight on that!
Although, that still leaves the question of the 'stream to crash phenomenon'. This isn't the first time it's happened, just the first time I've tried to report it. Last edited by Icaro on Mon Aug 10, 2009 6:12 am, edited 1 time in total.
stream to crashI have had Gladiator2 make a croaky noise on one track I had saved. Nothing I could do would make that preset work right. If I chose a different preset it worked OK, but return to the original one it croaked. Replacing the instance one Gladiator with a new one, and then copy and pasting fixed it. I have had a couple of strange crashes in Orion beta when using Gladiator2 , sent one to Rich so we'll see what happens. Have you guy's had any other problems with Gladiator and Orion playing together nicely?
stream to crashAll's been good for me so far. I wanted to use it as a lead as well for my little SOSF tune. But just couldn't find that patch. And I think I already had Pro53's sound in mind and knew what I was after on it.
And i know the Pro53 is great with the Mod Wheel and PB. But even for my noodling with bad sounds on Gladiator, it held up pretty good to all the bending and LFO raising. But that was just playing it live over the song - how it would fair recording it and streaming I don't know? But it's a pretty tough synth like the Pro53 - so I wouldn't be too nervous of it. Last edited by Dungeon Studio on Mon Aug 10, 2009 3:54 pm, edited 1 time in total.
stream to crashI'm wondering if it's to do with cpu load. I was looking at the FAQ's on Tone2's site and reducing cpu load appeared to be a common suggestion for allot of problems. The track I was working on was drawing 40% at idle and was 56-69% when playing but occasionally spiked. Does streaming to wave increase cpu load?
Last edited by heks on Mon Aug 10, 2009 6:12 pm, edited 1 time in total.
stream to crashIf I understand right how things work, I think streaming works sort of offline, and being that it doesn't stream realtime, seems pretty much impossible to use more of your CPU for it than during playback.
SoundCloud ::: Facebook
stream to crashJust streamed to wave my troublesome track, and your right HYPNAGOGIA, there were no problems and less CPU usage than normal play. Thats that theory stuffed,,,back to the lab
stream to crashRight, right, right, said Alex to the Droogies. But given effects, EQ, and Bus inserts and EQ... A world of difference. I mean I usually mix for the 128kbs crowd, and don't do too much beyond that. A bloke took some of my stuff for a live performance (and will again as of next week - niudge, nudge) But I was horrified at the amount of Bass involved. Yes, I use Maxx Bass - but in a club environment and Bass bins - My God! So again, what sounds good for one realm may sound totally horrid in another. 96k - only if I knew I had the best of the best sound and samples. and Abbey Road was going to futher it from there. All the science stuff I'll leave for the engineers to work out.
15 posts
• Page 1 of 1
Who is onlineUsers browsing this forum: No registered users and 355 guests |
© 2017 Synapse Audio Software. All Rights Reserved. |