Orion Platinum v7 released
- Suspended
- 17889 posts since 14 Jun, 2001 from Somewhere you're not!
Rich could probably give you a debug build if you were serious but as no-one else has had this problem, I have no idea whether he would or not. You'd have to ask him.
BTW, are we talking about the Toxic 3 that comes with ORION [in the Generators list not the VSTi list] or the VSTi version? Because we had problems with early versions of the generator that Rich seems to think were resolved in the third version we got. Its possible those problems have not been addressed in the VSTi.
BTW, are we talking about the Toxic 3 that comes with ORION [in the Generators list not the VSTi list] or the VSTi version? Because we had problems with early versions of the generator that Rich seems to think were resolved in the third version we got. Its possible those problems have not been addressed in the VSTi.
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron
-
- KVRAF
- 3345 posts since 8 Nov, 2003 from Amsterdam
It's the included Toxic 3 Generator. I don't have the other one. I downloaded and installed OP7 on Friday.
btw. The problem happened the first time I used OP. The second time everything was ok, so it's hard to reproduce.
btw. The problem happened the first time I used OP. The second time everything was ok, so it's hard to reproduce.
- KVRist
- 352 posts since 8 Jul, 2003
Rich and I take any crash bug seriously. If we can reproduce it even better, but crash bugs get higher priority on fixing. Can't fix something we haven't heard of or haven't encoutered ourselves.
The current version is pretty stable on my computer and most crashing I get is most likely due my memory chips being problem (I get some BSODs). Luckily I'm upgrading my computer this week and hoping that the dual core CPU will reveal some harder to reproduce bugs (many of those are already fixed in v7, mostly related to editing while playback).
That Insert Toxic 3 problem, I tried to reproduce, but no luck. What Record you mean? The main toolbar or the track record? Also which audio output you are using? ASIO? Also what's the audiocard? What do you mean with "playing"; hitting song play (spacebar) or playing from midi keyboard for recording?
The current version is pretty stable on my computer and most crashing I get is most likely due my memory chips being problem (I get some BSODs). Luckily I'm upgrading my computer this week and hoping that the dual core CPU will reveal some harder to reproduce bugs (many of those are already fixed in v7, mostly related to editing while playback).
That Insert Toxic 3 problem, I tried to reproduce, but no luck. What Record you mean? The main toolbar or the track record? Also which audio output you are using? ASIO? Also what's the audiocard? What do you mean with "playing"; hitting song play (spacebar) or playing from midi keyboard for recording?
jouni - www.markvera.net - Stardrive Studio - Orionology
-
- KVRAF
- 3345 posts since 8 Nov, 2003 from Amsterdam
Memory chips sounds like something to look into... since I have a 400Mhz chip in a 330Mhz machine...
To answer your questions (probably using non-Orion terminology, and not at my music pc now):
After opening the Midi editor for Toxic3 - which maximizes automatically - I clicked the red button to start recording, which arms the track for recording AFAIK. Then I clicked the play button. Both are at in the top window on the toolbar. btw. the second time I did it, it worked correctly, so it's probably OP7's interaction with my pc causing unpredictable errors. And I don't mind having a good excuse to buy new and bigger memory chips
.
I'm using an M-Audio 24/96 card and its ASIO drivers.
To answer your questions (probably using non-Orion terminology, and not at my music pc now):
After opening the Midi editor for Toxic3 - which maximizes automatically - I clicked the red button to start recording, which arms the track for recording AFAIK. Then I clicked the play button. Both are at in the top window on the toolbar. btw. the second time I did it, it worked correctly, so it's probably OP7's interaction with my pc causing unpredictable errors. And I don't mind having a good excuse to buy new and bigger memory chips
I'm using an M-Audio 24/96 card and its ASIO drivers.
- KVRist
- 352 posts since 8 Jul, 2003
Do you have the metronome count down enabled or is it with zero count down? I found one problem with Toxic 3 atleast, but it might be problem of Toxic 3 and might not be possible to make workaround (it sends patch changes as event autiomations for all parameters; haven't seen any other VSTi do the same). Something to report to Maxx.M'Snah wrote:...I clicked the red button to start recording, which arms the track for recording AFAIK. Then I clicked the play button.
jouni - www.markvera.net - Stardrive Studio - Orionology
-
- KVRAF
- 3345 posts since 8 Nov, 2003 from Amsterdam
The count down is enabled (probably the default, I didn't touch it).Mark Vera wrote:Do you have the metronome count down enabled or is it with zero count down? I found one problem with Toxic 3 atleast, but it might be problem of Toxic 3 and might not be possible to make workaround (it sends patch changes as event autiomations for all parameters; haven't seen any other VSTi do the same). Something to report to Maxx.M'Snah wrote:...I clicked the red button to start recording, which arms the track for recording AFAIK. Then I clicked the play button.
-
- KVRAF
- 3046 posts since 30 Mar, 2002 from 51°53'N 02°15'W
I can confirm the Toxic 3 insert bug.
It only happened the first time I used V7 and went into the Toxic 3 piano roll. I just got dropped back to windows.
Steve
It only happened the first time I used V7 and went into the Toxic 3 piano roll. I just got dropped back to windows.
Steve
其余的是噪音
- Suspended
- 17889 posts since 14 Jun, 2001 from Somewhere you're not!
So it might be in the middle of writing some initialisation parameters or something to the disk the first time you run it and object to the Play button being pressed? Sound likely?
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron
-
- KVRer
- 4 posts since 26 Jun, 2006 from California
I am wondering if these issues will ever be fixed in O. Plat 6 and released.
Or these problems were so great that it needed an upgrade to fix the bugs….
(* Bug fixes
- Many stability issues fixed
- Playlist paintbrush tool could paint over audiotracks. Fixed
- Playlist grid was occasionally off beat. Fixed
- Playlist wasn't updated properly when patterns were edited. Fixed
- Sidechain loopback configurations were possible. Fixed
- Sidechains in master section did not work properly. Fixed
- Some generators flickered on non-maximized pianoroll window. Fixed
- Pitchbend didn't work when Playback stopped+record was enabled. Fixed
- IRP waveform background bitmap was blitted upside down. Fixed
- Cut pattern cleared whole pattern even if only few notes were selected. Fixed
- Markers jittered somewhat in playlist. Fixed
- Highest/lowest numbers in event editors now readable
- Occasional crashes after saving OSPs from the Sampler editor dialog. Fixed.
- Playlist pattern double click behaved wrong when Pianoroll already visible. Fixed.
- Adding active patterns (F11) added patterns to audiotracks. Fixed.
- Keyboard focus not handled properly certain situations (several non-functional shortcuts). Fixed.
- When copying a mixer channels settings to another mixer strip, the Mute/Solo settings were not properly updated. Fixed.
- Tempo spinner max constraint was wrong. Fixed.
- double-click on desktop files crashed Orion. Fixed.
- Clicks on AudioTrack clip start/end. Fixed.
- Overlapping patterns could not be dragged. Fixed )

Or these problems were so great that it needed an upgrade to fix the bugs….
(* Bug fixes
- Many stability issues fixed
- Playlist paintbrush tool could paint over audiotracks. Fixed
- Playlist grid was occasionally off beat. Fixed
- Playlist wasn't updated properly when patterns were edited. Fixed
- Sidechain loopback configurations were possible. Fixed
- Sidechains in master section did not work properly. Fixed
- Some generators flickered on non-maximized pianoroll window. Fixed
- Pitchbend didn't work when Playback stopped+record was enabled. Fixed
- IRP waveform background bitmap was blitted upside down. Fixed
- Cut pattern cleared whole pattern even if only few notes were selected. Fixed
- Markers jittered somewhat in playlist. Fixed
- Highest/lowest numbers in event editors now readable
- Occasional crashes after saving OSPs from the Sampler editor dialog. Fixed.
- Playlist pattern double click behaved wrong when Pianoroll already visible. Fixed.
- Adding active patterns (F11) added patterns to audiotracks. Fixed.
- Keyboard focus not handled properly certain situations (several non-functional shortcuts). Fixed.
- When copying a mixer channels settings to another mixer strip, the Mute/Solo settings were not properly updated. Fixed.
- Tempo spinner max constraint was wrong. Fixed.
- double-click on desktop files crashed Orion. Fixed.
- Clicks on AudioTrack clip start/end. Fixed.
- Overlapping patterns could not be dragged. Fixed )

-
- KVRian
- 866 posts since 18 Apr, 2004 from Hungary
I don't understand you, what do you want to mean?m kemp wrote:I am wondering if these issues will ever be fixed in O. Plat 6 and released.
Or these problems were so great that it needed an upgrade to fix the bugs….
Anyway this upgrade is simply huge.
-
- Pick Me Pick me!
- Topic Starter
- 10263 posts since 12 Mar, 2002 from a state of confusion
hes asking if the bug fixes in v7 will be released for v6 or were the bugs so problematic that the newer version was necessary to fix them (that is, it wasnt physically possible to resolve the bugs in v6 or not)
unsure... interesting question though..
I'm assuming Richard is super busy.. I emailed him around a week ago.. and I still have yet to recieve a response of any sort...
unsure... interesting question though..
I'm assuming Richard is super busy.. I emailed him around a week ago.. and I still have yet to recieve a response of any sort...
-
- KVRAF
- 3345 posts since 8 Nov, 2003 from Amsterdam
That question is IMHO theoretical, unless you definitely don't want to upgrade. Most users probably agree that the new additions, a.o. Toxic 3, are worth the upgrade, and it's a very decent upgrade price. (I strongly believe that upgrades cannot always be free!)
- Suspended
- 17889 posts since 14 Jun, 2001 from Somewhere you're not!
1. What kind of lunatic would provide any support for an old version? The first response to any support call is always "are you using the latest version?". Everybody bundles bug-fixes with upgrades.m kemp wrote:I am wondering if these issues will ever be fixed in O. Plat 6 and released.
Or these problems were so great that it needed an upgrade to fix the bugs….
2. None of those bugs are worth a separate release, surely? Rich just waited until the next update to roll them in. Maybe the first one is, if you are experiencing those problems, but if you can't be arsed paying $39 for an upgrade that will both fix problems and give you heaps of other stuff, why would any company bother with you?
But at the end of the day, the fact is that Rich has one part-time helper and there is no way they could maintain multiple code versions for each stream so it seems likely that things that get fixed along the way could probably not easily be removed for a bug-fix update to v6. I'm surprised he still bothers with ORION Pro, it must be way more work than its worth to keep it around.
NOVAkILL : Legion GO, AMD Z1x, 16GB RAM, Win11 | Audient EVO 8 | Lumi Keys | Studio Pro 8
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron
Korg Odyssey, bx-oberhausen, Proxima, PolyMax, GR8, JP6K, Union, Atomika,
Invader 2, Flow Motion, Olga, TRK 01, Thorn, Spire, VG Iron
-
- Banned
- 2631 posts since 12 Oct, 2005 from the garden state
I finally did the upgrade dance
the new skin is the same as the one I've been using for the past years so...I'm not asking for much,just a 5 dollar refund
No crashes yet.Behaving nicely as a rewire slave
thank you Mr developer-man for that right-click menu
the new skin is the same as the one I've been using for the past years so...I'm not asking for much,just a 5 dollar refund
No crashes yet.Behaving nicely as a rewire slave
thank you Mr developer-man for that right-click menu
