Thanks for the hard work guys! From the list it looks like a ton of the v4 issues I was keeping track of are taken care of, even ones that seemed to be pretty recently reported!

Haven't explored every aspect of it yet so far the main Sample One v3 compatibility issues were improved greatly.

no problem with Melodyne, all works fine now

wdkbeats wrote1. "Edit with Melodyne" opens audio editor instead of Melodyne window.

I can reproduce that when an audio event is longer than 90 bars. If I make 2 slices and want to use Melodyne the audio editor opens instead. Below 90 bars everything is normal and the Melodyne editor opens directly on the sliced part. The length of the audio event seems to be crucial to reproduce this behaviour and there need to be sliced parts.

andreasmller1 wrote

wdkbeats wrote1. "Edit with Melodyne" opens audio editor instead of Melodyne window.

I can reproduce that when an audio event is longer than 90 bars. If I make 2 slices and want to use Melodyne the audio editor opens instead. Below 90 bars everything is normal and the Melodyne editor opens directly on the sliced part. The length of the audio event seems to be crucial to reproduce this behaviour and there need to be sliced parts.

Could you please put this in step format To reproduce?
Thanks

I can always reproduce it with the following steps:

- Create an empty song
- Load a sample with a length >90 bars in that new song
- Make 2 slices anywhere
- Right click on the sliced event and edit with Melodyne
- The audio editor opens instead of the Melodyne editor
- When the audio editor is closed the next double click on the slice opens the Melodyne editor correctly

This doesn´t happen with events shorter than 90 bars on my system.

andreasmller1 wroteI can always reproduce it with the following steps:

- Create an empty song
- Load a sample with a length >90 bars in that new song
- Make 2 slices anywhere
- Right click on the sliced event and edit with Melodyne
- The audio editor opens instead of the Melodyne editor
- When the audio editor is closed the next double click on the slice opens the Melodyne editor correctly

This doesn´t happen with events shorter than 90 bars on my system.

On my system the same happens no matter the length of an audio track.

wdkbeats wrote

andreasmller1 wroteI can always reproduce it with the following steps:

- Create an empty song
- Load a sample with a length >90 bars in that new song
- Make 2 slices anywhere
- Right click on the sliced event and edit with Melodyne
- The audio editor opens instead of the Melodyne editor
- When the audio editor is closed the next double click on the slice opens the Melodyne editor correctly

This doesn´t happen with events shorter than 90 bars on my system.

On my system the same happens no matter the length of an audio track.

Yes - this is a bug. Try to open Melodyne and first time the normal editor opens up - close that and ask again and then Melodyne opens. This occurs in any song, and is regardless of audio length. All you have to do is select an audio event, click edit with Melodyne, and the normal editor opens (which I never use anyway - I snip and cut in the arrange page and then go straight to Melodyne).

Is anyone reporting this back to Presonus? I can raise a ticket if necessary. This is a really annoying bug and may necessitate a return to the previous version.

garyshepherd wrote

wdkbeats wrote

andreasmller1 wroteI can always reproduce it with the following steps:

1- Create an empty song
2- Load a sample with a length >90 bars in that new song
3- Make 2 slices anywhere
4- Right click on the sliced event and edit with Melodyne
5- The audio editor opens instead of the Melodyne editor
6- When the audio editor is closed the next double click on the slice opens the Melodyne editor correctly

This doesn´t happen with events shorter than 90 bars on my system.

A) 1) On my system the same happens no matter the length of an audio track.

B)
1) Try to open Melodyne and first time the normal editor opens up
2) close that and ask again and then Melodyne opens.
3) This occurs in any song, and is regardless of audio length.

1) All you have to do is select an audio event, click edit with Melodyne, and the normal editor opens (which I never use anyway - I snip and cut in the arrange page and then go straight to Melodyne).

We have different conditions and symptoms listed but, not happening here with a shorter than 90 bar test on Win 10.
1- Create an empty song
2- Load a sample or record 8 bars
3- Right-click on the event and edit with Melodyne
5- The audio editor opens with Melodyne editor

I see we have two WIn7 and a Mac user anyone can confirm on Windows 10?
UPDATE: just had it happen once with a stereo file vs mono file. (not sure that means anything yet)

Hi,

Updated to S1Pro 4.01, now my Faderport 8 is not detecting Studio One, so not working. I updated Universal Control Application to ver. 2.8, Fader Port Firmware Ver. 2.02

Any Help to fix this would be appreciated.

UPDATE: (Issue Fixed)

OK. FP8 Working with S1Pro 4 after I re-booted my PC.

Thanks,
Muziksculp

I have submitted a support ticket for the Melodyne edit bug.

wdkbeats wrote

garyshepherd wroteI have submitted a support ticket for the Melodyne edit bug.

Thank you! What about the rest of the bugs I mentioned? Anyone?

2. Solo-safe busses (Shift+solo) - unable to listen in solo, described in detail here:
viewtopic.php?f=151&t=30785

3. Import song data - cannot import from templates, described here:
viewtopic.php?f=151&t=30356&p=173812#p173812

4. Copy & paste audio events broken when using templates, described here:
viewtopic.php?f=151&t=30784&p=176797#p176797

5. Tracks in Console jumping around when using templates with busses and fx channels:
viewtopic.php?f=151&t=24132

6. Inacurrate automation timing:
viewtopic.php?f=151&t=22254

wdkbeats wrote

wdkbeats wrote

garyshepherd wroteI have submitted a support ticket for the Melodyne edit bug.

Thank you! What about the rest of the bugs I mentioned? Anyone?

2. Solo-safe busses (Shift+solo) - unable to listen in solo, described in detail here:
viewtopic.php?f=151&t=30785

3. Import song data - cannot import from templates, described here:
viewtopic.php?f=151&t=30356&p=173812#p173812

4. Copy & paste audio events broken when using templates, described here:
viewtopic.php?f=151&t=30784&p=176797#p176797

5. Tracks in Console jumping around when using templates with busses and fx channels:
viewtopic.php?f=151&t=24132

6. Inacurrate automation timing:
viewtopic.php?f=151&t=22254

I have only submitted the one I know about concerning Melodyne editing. Someone else needs to submit other bug reports - why can't you do this?

wdkbeats wrote

wdkbeats wrote

garyshepherd wroteI have submitted a support ticket for the Melodyne edit bug.

Thank you! What about the rest of the bugs I mentioned? Anyone?

2. Solo-safe busses (Shift+solo) - unable to listen in solo, described in detail here:
viewtopic.php?f=151&t=30785

3. Import song data - cannot import from templates, described here:
viewtopic.php?f=151&t=30356&p=173812#p173812

4. Copy & paste audio events broken when using templates, described here:
viewtopic.php?f=151&t=30784&p=176797#p176797

5. Tracks in Console jumping around when using templates with busses and fx channels:
viewtopic.php?f=151&t=24132

6. Inacurrate automation timing:
viewtopic.php?f=151&t=22254

Not all issues reported have been fixed. They make the priority call.

2) I reported to developers
3) Import data is what it is by design at the moment. Buses can be imported if associated with automation track. It will improve over time or an actual track will be added over time.
4) This was only reproducible in the broken song submitted and was never reported. More work here to figure out how to recreate that broken scenario.
5) Bbd looks like he found the15 step procedure to recreate it and he can report it when he returns from vacation.
6) Old one but I believe never reported. Jemusic was the last to work with that one. Perhaps he can take it to the next step?

wdkbeats wrote
1. "Edit with Melodyne" opens audio editor instead of Melodyne window.

Reply from the Support Ticket - seeming to imply at first this is not a bug and then updated to show its noted and may be fixed in future updates.

Technical Support

Maybe not a bug in the literal sense but more perhaps just a minor change in behavior from version 3. No need to close anything there, just double click the clip and the Melodyne editor should appear.

Quick update: We've logged this internally. If or when it changes you will see it in possible future version release notes.

Overall I'm very pleased with all the new features and the bug fixes in v4 .

Today I noticed some very strange things though. I use external synthesizers and there is always some MIDI jitter going on. So, when I record my drums from a drum expander they are never exactly on the grid. This has nothing to do with S1 - it's a general problem with MIDI. To remedy this I quantize the audio afterwards. This worked fine in v3 except that the quantization always put them a bit too early, but this was no problem.

Today I did the same in v4 and then I saw that basically every drum hit was quantized differently because the transients were not detected correctly. OK ... I moved the bend markers and quantized them manually which was combersome already. Then I bounced the events. Afterwards the quantization was off again. So, bouncing the audio events changed the timing of the audio. This is absolutely unacceptable.

Did anyone else notice this? How are we supposed to quantize drums if things like these happen? It seems like something was changed that worked fine in v3?!

Hi ya'll (yes, ya'll)
Is anybody familiar with PreSonus sale seasons? When can we expect a sale to happen? or some promo codes for upgrading from S14 Artist to Pro? Maybe on the Black Friday only? Is it really a sale offer or just some low discount?
I really want to use VTS and note fx but I can't on artist. Do you guys advice to buy better the VTS add on? or should I wait and save money for pro?
Pro is too expensive for my country. I think I'll take me more than a year to save all that jush!
Hope to hear any comments from you guys.
Thanks in advance

danielbayer wroteOverall I'm very pleased with all the new features and the bug fixes in v4 .

Today I noticed some very strange things though. I use external synthesizers and there is always some MIDI jitter going on. So, when I record my drums from a drum expander they are never exactly on the grid. This has nothing to do with S1 - it's a general problem with MIDI. To remedy this I quantize the audio afterwards. This worked fine in v3 except that the quantization always put them a bit too early, but this was no problem.

Today I did the same in v4 and then I saw that basically every drum hit was quantized differently because the transients were not detected correctly. OK ... I moved the bend markers and quantized them manually which was combersome already. Then I bounced the events. Afterwards the quantization was off again. So, bouncing the audio events changed the timing of the audio. This is absolutely unacceptable.

Did anyone else notice this? How are we supposed to quantize drums if things like these happen? It seems like something was changed that worked fine in v3?!

Check that Input Quantise is not ON. This is very easy to overlook. It has fooled me a few times that is for sure.

Which interface are you using to get the midi in. The RME or the Focusrite. Maybe the the whole aggregate device thing is not working too well. I have never been a fan.

FYI I am running a separate midi interface (Steinberg Midex 8) on its own USB port that is plugged into a PCI card that provides multiple USB outputs. Timing is exceptional for me on V4. No jitter. Everything plays back perfectly so Studio One is actually excellent in this regard. In fact better than many other DAW's. Midi timing is one of its exceptional features. Whether the midi data is quantised or not.

Jemusic wrote

danielbayer wroteOverall I'm very pleased with all the new features and the bug fixes in v4 .

Today I noticed some very strange things though. I use external synthesizers and there is always some MIDI jitter going on. So, when I record my drums from a drum expander they are never exactly on the grid. This has nothing to do with S1 - it's a general problem with MIDI. To remedy this I quantize the audio afterwards. This worked fine in v3 except that the quantization always put them a bit too early, but this was no problem.

Today I did the same in v4 and then I saw that basically every drum hit was quantized differently because the transients were not detected correctly. OK ... I moved the bend markers and quantized them manually which was combersome already. Then I bounced the events. Afterwards the quantization was off again. So, bouncing the audio events changed the timing of the audio. This is absolutely unacceptable.

Did anyone else notice this? How are we supposed to quantize drums if things like these happen? It seems like something was changed that worked fine in v3?!

Check that Input Quantise is not ON. This is very easy to overlook. It has fooled me a few times that is for sure.

Which interface are you using to get the midi in. The RME or the Focusrite. Maybe the the whole aggregate device thing is not working too well. I have never been a fan.

FYI I am running a separate midi interface (Steinberg Midex 8) on its own USB port that is plugged into a PCI card that provides multiple USB outputs. Timing is exceptional for me on V4. No jitter. Everything plays back perfectly so Studio One is actually excellent in this regard. In fact better than many other DAW's. Midi timing is one of its exceptional features. Whether the midi data is quantised or not.

Thank you for this answer. 'Input Quantize' was activated in this project, indeed. I almost never use it, which would explain why I never had this issue before.
I also tried to replicate the issue in a fresh song, to create a song file that I can send to Presonus and there everything was fine and IQ was off in this case. So I think, this is the answer.

Regarding MIDI jitter - I get that a dedicated card may improve USB performance/stability and I will try to find a similar PCI card that works with a Mac/Hackintosh (although both interfaces have their own dedicated USB3 port). This is a good hint, so thank you again.