1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Absynth 3.0.1 update now available

Dieses Thema im Forum "ABSYNTH" wurde erstellt von Nils @ NI, 17. Februar 2005.

Status des Themas:
Es sind keine weiteren Antworten möglich.
  1. Nils @ NI

    Nils @ NI NI Team NI Team

    Beiträge:
    50
  2. Tarekith

    Tarekith NI Product Owner

    Beiträge:
    578
  3. dreamkeeper

    dreamkeeper NI Product Owner

    Beiträge:
    492
    Ja, ist denn schon Weihnachten? ;-)
     
  4. JF Paris

    JF Paris Member

    Beiträge:
    51
    Nice !

    - Many fixes, stability improvements, and enhancements for all platforms
    - Diverse minor cosmetic enhancements
    - GUI update issues solved
    - Undo waveform edit fixed
    - Copy, Paste & Undo function for notescale fixed
    - Control of sliders in the 3rd row fixed
    - Redraw issue when loading channel in the patch window fixed
    - Pitch wheel visualisation when using a MIDI device
    - "Import Preset" dialog cancel issue solved
    - Standalone PC "no undo record" function fixed

    Thank, Nils !

    --
    Jym Feat -- Paris FR 75018
     
  5. dreamkeeper

    dreamkeeper NI Product Owner

    Beiträge:
    492
    OK, no more stuck notes so far :), copy/paste notescale map is fixed, recorder works too

    But, just from the first few minutes of trying:

    - VSTi in Sonar4 still not usable
    - Windows resizing problems of DXi not solved
    - 'store to' button still doesn't work for me (hmmm...)
    - envelopes still don't update after paste or undo (stand-alone)
    - max no. of sliders is now 8 (plus vol+pan)
    - keyboard doesn't select note in notescale map

    (Win XP pro SP2)
     
  6. sturelof

    sturelof NI Product Owner

    Beiträge:
    58
    The 62 Viral Flux and 63 Revox is still pushing the cpu to 100%! :-(
     
  7. Tarekith

    Tarekith NI Product Owner

    Beiträge:
    578
    Damn, standalone mode totally locks up my PC now, doesn't work at all. Windows Performance meter jumps to 99% the second I launch it. This was the mode that gave me the least amount of troubles before too. Reverting to version 3 fixes this, so it's something in 3.01.

    VSTi mode.

    Try loading the Microbeat channels from the Library, they play for about 3 seconds, then I get a pulsating click sound even after the sound dies away. The CPU meter jumps from 0 to full in time with the clicking pulses.

    I too can't get the envelopes to update unless I click somere where else in the plug in.
     
  8. Kevan

    Kevan NI Product Owner

    Beiträge:
    102
    System: Mac OS 10.3.8
    Host app: SX 3

    Absynth 301 is still stealing keyboard control of the computer. Once the GUI is open you can't access any host functions like play and stop. When will this be fixed. How can you edit while a sequence is playing? You can't.

    Also any patch changes made in the GUI are not reflected in the Inspector of SX.

    Kevan
     
  9. ew

    ew Moderator Moderator

    Beiträge:
    21.328
    I'll answer the ones I can;
    First, Werner's-
    The VST issue in Sonar (just getting the title bar when using a wrapper in Sonar)- I didn't notice that one until you pointed it out to me. I reported it, but it was late in the beta cycle for this update. Hopefully next time.
    DXi resize- that one's sporadic on my machine. On my machine, once you resize the window, you're fine- until you close the GUI and reopen it. They're aware of it.
    Store to- that one's weird. That's worked for me all along.
    Haven't checked the others in the release version.
    Next, Tarekith's-
    There's something really screwy here. I get 16% CPU readings in Task Manager when Absynth opens, and the same with both microbeat 1 and 2. I don't get any increase in use over time with those either. I'm using a 933 PIII with XP SP2.
    Third, sturelof's-
    I see the same thing as you here. The only things these two patches really have in common is that they both use multiple granular oscillators accessing the same sample data; Maybe that's the issue? It was reported back before the original release.
    Kevan, I'm neither a Mac or a SX user. Maybe Joakim will have something to say here.
    ew
     
  10. Tarekith

    Tarekith NI Product Owner

    Beiträge:
    578
    I can can confirm the the patch change issue in SX Kevin, just FYI.

    Took a look at the sample data for those two patches in wavelab, just out of curiousity since they share the same samples. I can't see anything wrong with the data, it's not a funky sample rate or anything screwy like that. Maybe an error in the wave file header, something we can't readily see?
     
  11. dreamkeeper

    dreamkeeper NI Product Owner

    Beiträge:
    492
    Thanks, Eric! I just found out by chance how 'store to' works now. It's definitely neither as described in the manual nor the way it used to be in v2. For those morons like me: while 'store to' is blinking just click on any slot you want to store the patch to.

    werner
     
  12. Joakim F

    Joakim F New Member

    Beiträge:
    327
    Hi Kevan,

    Could you please clarify #1, you can click on start / stop of the transportbar with the mouse, or are you not able to click on start / stop once you've opened the GUI of Absynth. Or are you referring to the fact that the host quick-keys are not responding whilst the GUI is the active window?

    The second one I'm not sure what you mean, it works for me, however when you load a new bank the names are not updated in the host preset list. This has been reported, and will hopefully be addressed in a forthcoming update. Meanwhile I would recommend using the patch management from within the GUI and skip the preset management in SX.

    Regards
    Joakim
     
  13. Tarekith

    Tarekith NI Product Owner

    Beiträge:
    578
    Ok, I think I may have gotten this sorted now, though it's still a bit strange.

    If I install the 3.01 update over the regular 3.00 version, I get the same problems everytime, general instability in VSTi mode (lots of random CPU spikes, stuck notes, etc), and the standalone mode doesn't work at all.

    However, then I copied all the 3.00 library and sound files to a different directory, then uninstalled the 3.00 program. Installed the 3.01 update on its own, and recopied the libraries and samples back to the install directory, and THEN it works fine.

    Very good in fact, I can even play the Revox and Viral Flux presets with no CPU issues, and load the libraries I was having problems with mentioned above. However, these only work when I use a midi controller (an O2 in this case), if I attempt to play any of them via mousing the GUI keyboard, they all CPU spike and it's the same problems other people have reported. Just FYI to any Absynth programmers reading this.

    I'll play with it some more today and report any thing else I find.
     
  14. kuniklo

    kuniklo NI Product Owner

    Beiträge:
    265
    While I'm glad that the Absynth update is out, it PISSES ME OFF that I'm still waiting for my copy to arrive!!!!

    This is unacceptable!
     
  15. Kevan

    Kevan NI Product Owner

    Beiträge:
    102
    Thanks Joakim

    I mean the basic keyboard commands for controlling the transport are not working when the Absynth gui is open. As you know SX has a preference for VST plugins recieve key commands. This allows all VSTi to be able to use the computer keyboard for entering values and names etc etc but the numeric keypad is supposed to be off limits so basic control of the host is still possible. All the plugins I have work fine except for Absynth and FM7. Just to be absolutely clear about this. Open Absynth and then hit 'Enter' on the numeric keypad. This should put SX into play but it does nothing. Got it?

    Ok just to be clear. From the Inspector in SX you can select patches. This works fine. A popup list shows all the currrent patches in Absynth. Select a patch and it works. Now open the Absynth GUI and select a different patch. The Inspector in SX still shows the previous patch. In other words Absynth isn't telling SX that it has changed patches. FM7 and Pro53 both work correctly in that any changes made in the GUI are reflected in the Inspector.

    My point is if some of your plugins work correctly and other don't what's the problem? Pro53 works perfectly in regard to these two issues. When it's GUI is open you can still control the host app and all patch changes are reflected in the host app.

    I hope that makes it perfectly clear.

    Kevan
     
  16. Joakim F

    Joakim F New Member

    Beiträge:
    327
    Hi Kevan,

    Now I'm with you. I think they're both on the list of things to be fixed, so I'm hoping, just as you are, that they'll get sorted in a not too future update.

    Though I don't agree with you when you write "How can you edit while a sequence is playing? You can't.". I'd say you can, just use your mouse to start/stop the song and edit what every want ;)

    And yes, it would be nice if SX own preset management could be used, but at the moment it doesn't work to 100% so I would advice that you use the built in patch management to choose presets and load banks.

    Have fun

    Joakim
    (moderator - albeit not an NI employee)
     
  17. Kevan

    Kevan NI Product Owner

    Beiträge:
    102
    Thank you sir. I hope so but I've been told that this was going to fixed in FM7 over a year ago so I'm not holding my breath. I'm still glad you confirmed that it is something on the list of things to do. Nice to know it hasn't been forgotten.

    Kevan
     
  18. elektrolurch

    elektrolurch NI Product Owner

    Beiträge:
    66
    "Last Edits" list doesn't open in PC VST. So I can't save a preset into another bank than the opened.
     
  19. Madlab

    Madlab Forum Member

    Beiträge:
    83
    Registration system f+++ed up

    Two days ago, I logged in the forum using my regular mail adress and password. When i clicked on the link to download the Absynth 3.01 upd, the download started immediatly, and I ws noticed I was logged in as chris@-------.demon.co.uk, which is not my identity, I'm sure (I don't write the full adress because I'm concerned with this lack of security for my peers) !! So I clicked to fill in a support form to warn NI about this. To my surprise, the whole form was pre filled with this 'Chris guy' information. So I sent a regular mail to NI but got no answer, not even an automatic one !
    Did anybody have the same experience ? This is really serious for an editor which is so picky about the registration process. Sometimes NI sucks, and we have the right to tell it when it's true.
     
  20. ew

    ew Moderator Moderator

    Beiträge:
    21.328
    What host? It's working fine here...
    That IS serious- I'll forward this to some people. Thanks for letting me know.
    ew
     
Status des Themas:
Es sind keine weiteren Antworten möglich.