135 postsPage 5 of 7
1, 2, 3, 4, 5, 6, 7
WaterlooSunset wrote
musicchamber wroteI have found another problem and it's to do with EZ Drummer VST or AU. When I go to the mixer section of EZ Drummer and then try to set separate channel outs for the individual percussion parts Studio One crashes instantly.

Anyone else having this problem?
I have the latest version of EZ Drummer and all kits are up to date.



I just created a new song, added EZD2 (mine is up to date as well). Selected Americana and basic drum kit. Added in the first 4/4 Balled loop. Went to mixer, and changed mixer to 6 outputs. I had no crash.
I have no new latency/drop out settings active..


In that case I'm now wondering if it just a mac specific issue - I'm on High Sierra.
Can anyone one on macOS confirm?

UPDATE:
I have just tried EZ drummer in a completely new song and no problems with it. It must be something to do with the song I am working on. Very bizarre!

Studio One Professional v6, Apple iMac Pro 14 core, 128gb memory, 4TB SSD. macOS Ventura, Main audio interface is RME Babyface Pro. Presonus 192, DP88 (not currently used), RC500, ADL600, Focusrite ISA430, TC4000 reverb, SPL Phonitor, Monitoring: Event Opal, IK Multimedia MTM Studio Monitors x 5, DMAX audio Super Cubes. HD800s mastering reference headphones. Sequential Prophet 12, Prophet 12 modules x4, E-MU 4XT Ultra, Roland Fantom 8, Korg Pa3x, Roland Fp7-F, MOTU midi express 128, Xkey air 37, Studiolive CS18, Atari STE with Notator plus loads of microphones and plugins etc
User avatar
by niclasgustafsson1 on Sat Oct 07, 2017 2:09 pm
musicchamber wrote
WaterlooSunset wrote
musicchamber wrote UPDATE:
I have just tried EZ drummer in a completely new song and no problems with it. It must be something to do with the song I am working on. Very bizarre!


I have experienced the same thing when updating in the middle of projects.
Plugs that starts behaving strangely, automation stops working, faderport beeing unresponsive etc. And it all goes away then i change to an new project.

And its not just this update. So i guess with S1 more than any other daw the "dont update and drive" applies.


Anyone else experiencing trouble with AU plugins?
I had another project failing on me today. Havn't reversed to 3.5.1 yet. Still hoping its going to go away. lol. I was importing chains from an older session, all AU, and it just went haywire and started to blast noise. I got lucky and nither my speakers or my ears blew. But it was bleep close this time. Damn that noise was loud...

Macbook Air M1 16/512, Metric Halo ULN2, MOTU 8pre usb, MunroSonic the Egg 150,
User avatar
by Skaperverket on Sun Oct 08, 2017 8:33 am
guitarism wroteLoop recording has become unusable. It seemed to work for a very shot time but now, if I record several takes, only the first take records and sometimes , not even that. The loop recording a big problem a few versions back and it was finally working OK prior to 3.5. Now it's regressed and worse than ever. It even crashed Studio One when I was using it yesterday.


Hi. I had some takes/layers disappear today while recording in loop mode in v. 3.3.4. A real pain. Do you know which thread on this forum this has been discussed before? I tried searching, but couldn't find it. Thanks.
User avatar
by roland1 on Sun Oct 08, 2017 11:50 am
Skaperverket wrote
guitarism wroteLoop recording has become unusable. It seemed to work for a very shot time but now, if I record several takes, only the first take records and sometimes , not even that. The loop recording a big problem a few versions back and it was finally working OK prior to 3.5. Now it's regressed and worse than ever. It even crashed Studio One when I was using it yesterday.


Hi. I had some takes/layers disappear today while recording in loop mode in v. 3.3.4. A real pain. Do you know which thread on this forum this has been discussed before? I tried searching, but couldn't find it. Thanks.


Reading your post, I recall this happening to me, too, when I updated to 3.52. I'd record a track and then it would disappear from the timeline. Weird stuff.

I'm now back to using 3.5.1 again and my recording of audio and midi is fine.

Studio One Pro (v5) on i7 7700 win10 PC w16GB RAM and a Mac Pro Tower (w/RME & Focusrite interfaces.)

I use S1 as an author/musician/multi-media artist.
My work includes the newly released: Clearing a Path to Joy (And finding contentment along the way) [AuroraSkyPublishing.com]
and my upcoming music video, Too Big To Fail, which introduces Citizen Based Social Planning — "the next step in the evolution of democracy." You know...typical everyday stuff. :)
User avatar
by santeripilli on Sun Oct 08, 2017 4:38 pm
roland1 wroteGlad / annoyed that others are reporting the missed MIDI notes issue. I would assume something so basic would have been tested prior to release. Guess not.

!%&$! :p



Roland1, ditto. This is exactly what I've been ranting about here quite a few times.


Dear Presonus developers, please START BETATESTING YOUR SOFTWARE PROPERLY and not DELEGATING BUG SQUASHING to your CLIENTS who paid proper money! You are supposed to provide a stable (under basically any condition) environment for professional music making. This is not it.

This is both unfair and unethical businesswise, has been since day 1 (of S1 v3). That's why the emphasis here, whether you find it annoying or not.




Yours truly,

Still Unstable, Still quite hoping that one day it would not be.

Apple MacBook Pro 13" (Early 2011):
2,7 GHz Intel Core i7
16 GB 1333 MHz DDR RAM, 500 GB HD (7200 RPM),
OSX version 10.12.4. (Sierra),

Interface: TC Electronic Konnekt 6 FireWire


Presonus Studio One 3, newest version, always (except when too buggy to work with daily).
User avatar
by Thareh on Mon Oct 09, 2017 12:49 am
They really should release a hotfix for a bug affecting such an important part of the program..
User avatar
by Robert Johnson III on Mon Oct 09, 2017 1:54 pm
Let me add some full to the fire... :readit: :roll: viewtopic.php?f=151&t=26273 (bend marker editing unreliable) Core functionality... Reported, confirmed and still "broken".

MacMini M2 Pro
Memory: 16 GB
OS X latest version
Apollo X6 Thunderbolt
Studio One Pro latest version

https://open.spotify.com/album/5DQ0uQnTPGAQH4rmaNboE8?si=DH54HeplSO2hVxPFLmUVNQ
User avatar
by multifederal on Wed Oct 11, 2017 5:59 am
:reading:
User avatar
by America Sauce on Sun Oct 15, 2017 9:55 am
After updating to 3.5.2 I would get a message on startup saying "Restart requested by audio device". I'm just using windows audio like I always have. Does anybody know why I'd be having this issue after the update?
I've rolled back to 3.5.1 and everything is working fine now, but I'm wondering if there is a simple fix for my issue in case I ever want to, you know, update my software again.
User avatar
by Skaperverket on Sun Oct 15, 2017 11:34 am
saradis wroteGuys, why isn't automation copied along with the clips when using ctrl+c ctrl+v? On previous versions everything underneath the clip was copied. Even if I pasted a clip on another channel, the automation envelopes that had the same name as on the original channel were duplicated.

Now, depending on which automation stripe was changed last or clicked on before selecting the clip and pressing ctrl+c, automation is either pasted to the wrong stripe or not pasted at all :O


I decided to try 3.5.2 for a bit today and I also had problems with copying automation with the key commands. And this was on a Mac (cmd+c/cmd+v).
User avatar
by scottyo7 on Mon Oct 16, 2017 1:57 am
Glad I read all these posts. ;)

I'm not even going to bother trying 3.5.2. :roll:
Seems like 80% of the issues described would certainly affect me since I use those same methods and techniques.

Please add your System-Gear-Info to your Profile here.
-S1 Pro 5.5.2. Win11 Pro 22H2. Behringer UMC404HD. Melodyne Studio 5.3.1.018.
-MSI 12th Gen i7, 16GB, 1GB SSD x2, 7200rpm 2TB HD, NVIDIA RTX 3060.
-EZD3 & EZD2. Helix Native, Scuffham S-Gear. iZotope Ozone 5.
-Akai MPK249. 6 Guitars. Line 6 Helix LT, 2 POD's & an E-bow. 8-)
-Adam Audio T8V's. Dual 28" ViewSonic Displays. Rode NT1. SM58. Original Faderport.


-Just My Songs
-My Previous Band: 2GUYZINABASEMENT
User avatar
by Skaperverket on Mon Oct 16, 2017 8:36 am
If I use cmd+B (or choose Bounce Selection) in 3.5.2, the resulting file is longer than the event originally selected. The new file gets time added both before and after. This does not happen in 3.3.4, where the resulting file is of the same length as the original event.

Has anyone else noticed this?
User avatar
by Skaperverket on Mon Oct 16, 2017 9:46 am
Skaperverket wroteIf I use cmd+B (or choose Bounce Selection) in 3.5.2, the resulting file is longer than the event originally selected. The new file gets time added both before and after. This does not happen in 3.3.4, where the resulting file is of the same length as the original event.

Has anyone else noticed this?


Also Merge to Audio Part seems to behave similarly in 3.5.2.

How to reproduce:

Import an audio file.
Use the split tool and split it into a few smaller events.
Select one or two of the newly created events.
Go to the Audio menu in the top bar and select Merge to Audio Part.
After this I get an Audio Part with the wrong length.

The same happens if you follow the same procedure for Bounce Selection:

Import an audio file.
Use the split tool and split it into a few smaller events.
Select one or two of the newly created events.
Go to the Event menu in the top bar and select Bounce Selection.
After this I get an Event/file with the wrong length.

Neither Merge to Audio Part nor Bounce Selection work like this in S1 3.3.4.
User avatar
by niles on Mon Oct 16, 2017 9:59 am
@Skaperverket, any difference when you disable Snap to grid?

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by Skaperverket on Mon Oct 16, 2017 10:48 am
niles wrote@Skaperverket, any difference when you disable Snap to grid?


Yes! My mistake. User error. Both work as expected.

Thanks, niles. Helpful and insightful, as always.
User avatar
by niles on Mon Oct 16, 2017 12:31 pm
Skaperverket wroteYes! My mistake. User error. Both work as expected.
I don't blame you. It is rather odd behavior because it only extends parts and bounced selections when Snap is on and the Timebase is Bars. :hunf:

OS: Windows 11 Pro | HW: Gigabyte Z690-UD-DDR4 • INTEL i7 12700K • 64GB • 3x EVO 860 • NVIDIA GT1030 (@WQHD) • RME AIO
User avatar
by billmihalik on Tue Oct 17, 2017 10:03 am
This is driving me crazy. Since the last update every time I record multiple takes only a few of them show up. I just recorded 5 takes of a vocal track and the first and last takes show up as a 2 second blip. The "pool" shows the track recorded in full, but will only playback the 2 seconds, completely unusable. Is there any way to recover those recordings?

PC AudioLabs, Win 10 Pro 64bit, AMD FX-4350 Quad-Core 4.20 GHz, 32 GB RAM, Studio One Pro, Focusrite Scarlett 18i20
User avatar
by jpettit on Tue Oct 17, 2017 10:32 am
billmihalik wroteThis is driving me crazy. Since the last update every time I record multiple takes only a few of them show up. I just recorded 5 takes of a vocal track and the first and last takes show up as a 2 second blip. The "pool" shows the track recorded in full, but will only playback the 2 seconds, completely unusable. Is there any way to recover those recordings?

Not seeing this

Please respond with exact steps to reproduce.

What is layer follow take set to?
What are the settings Record panel for Record mode?
What are you Option for tracks set at?

My Website, Free Studio One Advance Training
SPECS: Win 11 23H2, 18 Core i9: 32Gb DDR4 ram, 42" 4K monitor, StudioLive 24/16, Faderport16, Central Station Plus, Sceptre 6, Sceptre 8, Temblor T10, Eris 4.5, HP60, Studio One Pro latest, Test Platforms Reaper latest, Cakewalk latest
User avatar
by billmihalik on Tue Oct 17, 2017 11:08 am
I have "Instrument Loop Record" set to "record Takes", and "Record Mode" is "Takes to Layers". I just recorded 2 takes of guitar tracks twice (total of 4 takes on 2 separate tracks) and I could not reproduce the problem. However, I have not changed any settings since recording the vocal takes. This is not the first time I have had this problem though, and it has happened on both mic and direct input recordings.

PC AudioLabs, Win 10 Pro 64bit, AMD FX-4350 Quad-Core 4.20 GHz, 32 GB RAM, Studio One Pro, Focusrite Scarlett 18i20
User avatar
by jpettit on Tue Oct 17, 2017 12:43 pm
billmihalik wroteI have "Instrument Loop Record" set to "record Takes", and "Record Mode" is "Takes to Layers". I just recorded 2 takes of guitar tracks twice (total of 4 takes on 2 separate tracks) and I could not reproduce the problem. However, I have not changed any settings since recording the vocal takes. This is not the first time I have had this problem though, and it has happened on both mic and direct input recordings.

There was a bug about a year ago that had to do with where you started in the loop.
It was thought to be fixed, but you might want to experiment with started before the loop, just inside the loop and at the end of the loop to see if that give different results.

My Website, Free Studio One Advance Training
SPECS: Win 11 23H2, 18 Core i9: 32Gb DDR4 ram, 42" 4K monitor, StudioLive 24/16, Faderport16, Central Station Plus, Sceptre 6, Sceptre 8, Temblor T10, Eris 4.5, HP60, Studio One Pro latest, Test Platforms Reaper latest, Cakewalk latest

135 postsPage 5 of 7
1, 2, 3, 4, 5, 6, 7

Who is online

Users browsing this forum: BobF, SwitchBack, Tacman7 and 73 guests